異機種混合環境でのアプリケーションおよびサービスの高可用性およびポリシー・ベースの自動化
異機種混合プラットフォームおよび仮想化テクノロジーで実行されている重要なアプリケーションおよびミドルウェアの連続的な高可用性を確実にし、サービス中断の頻度と期間を軽減します。
Microsoft® Windows®、IBM AIX®、Linux® (Linux on IBM System z®、System p®、System i®、System x® を含む)、および Solaris を含めた、多数の異機種混合プラットフォームおよび仮想環境にわたり、可用性を高め、中断を軽減します。
- 個々のアプリケーション・コンポーネントまたは複合アプリケーション全体の自動開始、停止、再開、およびフェイルオーバーを開始、実行、および調整して、IT の可用性に影響を与える問題の頻度と期間を軽減します。
- 物理環境と仮想環境の両方が関与する複数のフェイルオーバー・シナリオをサポートする標準ツール・セットを提供します。
- 高度なクラスタリング構成 (N:1 または N:M 構成など) のサポートを含む先進的なクラスタリング・テクノロジーを提供して、必要なハードウェア・サーバーの台数を減らします。
- 先進的なポリシー・ベースの自動化を提供して、スクリプトおよびプロシージャーを作成および保守するための幅広いプログラミング・スキルの必要性をなくすことにより、複雑な IT インフラストラクチャーの運用管理を容易にします。
- 自動化ポリシーをとおして仮想化サポートを拡張します。
- 主要な Tivoli® ソフトウェア・ソリューションおよびサード・パーティー・ソフトウェア・ソリューションのベスト・プラクティスを統合するプラグ・アンド・プレイ方式のポリシー・モジュールを提供して、すぐに使用可能な障害検出およびリカバリーを実現し、運用コストの節約と持続的な高可用性を促進します。
- Web ベースで使いやすく強力な GUI を提供し、構成変更をエラー・フリーにします。
- 条件を素早くリソースに関連付けるリソース依存関係の定義機能を通してリカバリーを迅速化し、オペレーターが正しいコンテキスト内で適切な修正アクションを選択できるようにします。
- 目標駆動型自動化と新規ポリシー要素により、ダウン時間を削減しオペレーションをスピードアップ
- クォーラム、デッドマン・スイッチ、ディスクおよびネットワーク・タイブレーカーによる重要なデータの保護
- IT リソース使用効率の最適化を支援します。
- アプリケーション、ミドルウェアおよびプラットフォーム全体にわたって、系統的な実装と高可用性オペレーションの実行を可能にする、高可用性とイベント自動化オファリングの幅広い Tivoli ポートフォリオを統合します。
- IBM Tivoli System Automation Application Manager と統合してエンドツーエンドの自動化をして、複合アプリケーションと広範なレポート作成の操作を行います。
IBM Tivoli® System Automation for Multiplatforms の新機能
- Sun Solaris および Windows Server 2008 を含む追加のプラットフォームのサポート
- Linux® on System z® で堅固な事業継続性を実現するために Geographically Dispersed Parallel Sysplex™ (GDPS®) (z/OS® 用の世界クラスの災害時回復ソリューション) を拡張するオプションの xDR コンポーネント
- IBM z/VM®、VMware などのサポートされるプラットフォームでの主要な仮想化テクノロジー、および AIX® 6 の新しい仮想化機能のサポート
- 一般的な実行時にアプリケーションの開始、停止、およびフェイルオーバーにかかる時間を追跡および報告する機能。リカバリー時間をリカバリー時間目標に照らして管理できます。
- XML を表示または編集する必要なしにポリシーを素早く簡単に作成および編集できる拡張構成グラフィカル・ユーザー・インターフェース
- ダイナミック・データ・センター・ソリューションと仮想化向けの高可用性をサポートする既成のポリシー
製品について
ご購入 Tivoli System Automation for Multiplatforms
初年度の IBM ソフトウェア・サブスクリプション & サポートは製品価格に含まれています。
ご購入には諸手続きが必要になりますので、弊社窓口までお問い合わせください。
| Features | Advantages | Benefits |
|---|---|---|
| Customizable out of the box resource monitoring | Out of the box outage detection | Fast outage detection reducing operator requirements for manual monitoring |
| Automatic start, stop and move of your applications | Takes care of cluster-wide relationships, start/stop order and required pre and post start/stop actions | Relieves operator from manual command entry. Improves efficiency by reducing operator errors. |
| Resources can be grouped into applications. Grouping can be cluster-wide | Reduces complexity of operations by automating at the application level, reducing manual intervention and need to remember application components and dependencies | Improves efficiency, reliability and serviceability of the IT Infrastructure enabling a better integration of IT resources with business goals |
| Able to define interdependent resource relationships and associate conditions with resources | Frees operators from remembering application components and relationships. Can use sophisticated knowledge about application components and their relationships to decide corrective actions within the right context. | Reduces operations errors. Improves service levels and optimal IT resource utilization by enabling lower-priority business applications to be shut down while keeping higher-priority business applications running based on business priorities. |
| Policy-based automation | New resources or systems can be added without re-writing scripts | Reduces automation implementation time, and coding and support effort. Leverages manpower through reduced education requirements. No programming skills are required for policy definition. Eases application growth and scaling. |
| Graphical user interface policy editor | Create policies easier with no XML or command line scripting and allows you to quickly visualize dependencies | Lowers the learning curve and enables operators to identify application dependencies quickly |
| Reliable and Scalable | Cluster-wide heart-beating and reliable messaging service | Helps faster cluster implementation to enable a more reliable, dynamic automation |
| Disk Heart beat | This feature adds resilience to the cluster infrastructure. It helps to avoid the trade-off between data integrity and application availability in the majority of cases. | This improves the availability of the applications being managed by System Automation for Multiplatform (SA MP). |
| Integration with GPFS | Seamless integration of GPFS with SA MP | Customers can benefit from GPFS features like data mirroring and information lifecycle management while keeping their application highly available. |
| Support for up to 130 nodes per cluster | Much greater flexibility. DB2 customers in particular have a need to support large clusters. | Supports more of the customer's actual infrastructure as it is today. |
| Operations Console support for Moving Applications | Previously, moving applications to another machine to perform maintenance on the first machine could only be carried out from the CLI. Users can now use the same Operations Console as they use for other functions to perform the move. | Greater user productivity. Less knowledge needed of command-line interface to carry out routine tasks. Improved user interface. Actions to be taken to move the Application can be checked against policies for consistency'. |
| Support for Solaris IP Multipathing | This Solaris feature combines two network adapters to a virtual adapter in order to provide network adapter redundancy for applications. | Solution is more integrated with customer's other high availability strategies. Customers can benefit from network as well as server redundancy. |
| RSCT Resource Harvesting Capabilities | RSCT resources belonging to the classes IBM.NetworkInterface and IBM.AgFileSystem can be harvested (auto-detected). These are the two typical classes for which resources are referenced by customers. All found RSCT resources can be easily selected from a table when defining an SA MP resource. | Improved Time-to-Value through increased productivity and decrease in errors associated with the manual process. |
| Failback of IBM.Application resources | SA MP can start, stop, and monitor arbitrary applications when defined as IBM.Application resources in an SA MP policy. If such an application fails on one system, SA MP re-starts the application on a different system to make it available again. With Failback, SA MP can return the application to the original system once it is available again. | Better productivity, less effort to get an Application back to the primary server. Supports the way customers set up their infrastructure. |
| User interface improvements 1) Remove resource name truncation in Policy Editor 2) Auto-Save in Policy Editor 3) Printing graphical policy view in Policy Editor |
1) Objects in the Operations Console are shown with their full name instead of a truncated name. As many customer naming conventions led to machines with non-unique character strings at the beginning of the name, truncated names caused confusion. 2) Automatically saves work done in the policy editor which can be recovered should the WebSphere session timeout due to inactivity. 3) Users can print the graphical policy view to share with stakeholders, eg, the Application SMEs whose applications are being made highly available. |
1) Improved productivity and usability. Users can tell at-a-glance which component of their infrastructure they are viewing. 2) Saves user time reworking lost policy changes, and improves user satisfaction. 3) Improved usability facilitates communications of processes and leads to better HA planning. |
| Trace File Size Expansion | Trace file size is expanded to provide sufficient first failure data for analysis by the service team. | Improved Serviceability lowers TCO by reducing the time taken to identify product errors. |
| Additional preconfigured policies | New out-of-the-box policies will be provided via OPAL. | Faster Time-to-value. Saves effort in configuring policies for specific situations. |
Product requirements
Platform specific requirements for IBM Tivoli System Automation for Multiplatforms (V1.2 only):
xSeries, 32 bit Intel based servers:
If RHAS 3.0 or RHEL 3.0 is used, the library compat-libstdc++ is required:
Check if the compat-libstdc++ is installed, with: rpm -q compat-libstdc++. If it is installed at that or a higher level, no further action is required.
Copy the compat-libstdc++-7.3-2.96.123.i386.rpm to all the nodes where you want to install SA for Linux. If you cannot find it on the RH installation CDs please go to: https://rhn.redhat.com/network/software/packages/details.pxt?pid=199449
Run the following on all of the nodes: rpm -U compat-libstdc++-7.3-2.96.123.i386.rpm
Install SA for Linux
pSeries:
If RHAS 3.0 or RHEL 3.0 is used, the library compat-libstdc++ is required:
Check if the compat-libstdc++ is installed, with: rpm -q compat-libstdc++. If it is installed at that or a higher level, no further action is required.
Copy the compat-libstdc++-7.3-2.96.123.ppc.rpm to all the nodes where you want to install SA for Linux. If you cannot find it on the RH installation CDs please go to: https://rhn.redhat.com/network/software/packages/details.pxt?pid=199449
Run the following on all of the nodes: rpm -U compat-libstdc++-7.3-2.96.123.ppc.rpm
Recommendation for 1-2 node cluster
RSCT requires that at least one other adapter in the network exists, so that packets can be exchanged between the local and remote adapter. Without such an adapter, a local adapter would be unable to receive any packets. Therefore, there would be no way to confirm that the local adapter is working. Therefore we recommend to add machine names to file /usr/sbin/cluster/netmon.cf on each cluster node. These machines should be routers or any machines that are external to the configuration, but are reachable from one of the networks being monitored by the subsystem. Any entry in this file is used as a target for a probing packet when RSCT is attempting to determine the health of a local adapter. The format of the file is as follows:
machine name or IP address 1
machine name or IP address 2
.........
Where the IP addresses are in dotted decimal format. If the file does not exist, it should be created. To remove this recovery action, remove the entries added to the file, delete the file, or rename the file.
Page last updated on August 28, 2007.
-
スケジューリングおよびシステム・オートメーション
- IBM SmartCloud Provisioning
- Tivoli Service Automation Manager
- Tivoli System Automation Application Manager
- Tivoli System Automation for Integrated Operations Management
- Tivoli System Automation for Multiplatforms
- Tivoli System Automation for z/OS
- Tivoli Workload Scheduler for Applications
- Tivoli Workload Scheduler for Virtualized Data Centers
- Tivoli Workload Scheduler for z/OS
- Tivoli Workload Scheduler
- Tivoli Workload Scheduler LoadLeveler