Haute disponibilité et automatisation régie par des règles pour les applications et les services dans plusieurs environnements hétérogènes
Offre des niveaux de disponibilité continue élevés et réduit la fréquence et la durée des interruptions de service des applications et des middleware critiques s'exécutant sur des plateformes hétérogènes et utilisant des technologies de virtualisation.
Augmente la disponibilité et réduit les interruptions sur de nombreux environnements virtuels et plateformes hétérogènes, dont Microsoft Windows, IBM AIX, Linux (notamment Linux on IBM System z, System p, System i, System x) et Solaris.
- Initialise, exécute et coordonne le démarrage, l'arrêt, le redémarrage et la reprise en ligne automatiques de composants applicatifs ou d'applications composites entières afin de réduire la fréquence et la durée des incidents susceptibles d'avoir un impact sur la disponibilité informatique.
- Fournit un ensemble d'outils standard capable de gérer de nombreux scénarios de reprise en ligne, dans des environnements tant physiques que virtuels.
- Utilise des technologies avancées de mise en cluster, avec la prise en charge de configurations en clusters sophistiquées, telles que les configurations N:1 ou N:M, et contribue ainsi à réduire le nombre de serveurs matériels requis et à garantir la haute disponibilité continue de services métier critiques.
- Permet une automatisation avancée régie par des règles afin de faciliter la gestion opérationnelle des infrastructures informatiques complexes, en évitant de devoir recourir à des personnels possédant des compétences poussées en programmation pour la création et la gestion de scripts et de procédures.
- Etend la prise en charge de la virtualisation grâce à des règles d'automatisation.
- Fournit des modules de règles plug-and-play qui intègrent les bonnes pratiques des principales solutions logicielles Tivoli et de fournisseurs tiers. Ces modules fournissent des fonctions de détection des défaillances et des options de reprise immédiatement prêtes à l'emploi, et favorisent les économies de coûts opérationnels et la haute disponibilité continue.
- Fournit une interface graphique conviviale et puissante s'exécutant sur le Web, permettant de modifier la configuration sans commettre d'erreurs.
- Accélère la reprise avec la possibilité de définir des dépendances de ressources afin d'associer rapidement des conditions aux ressources, ce qui permet aux opérateurs de choisir les actions correctives appropriées dans le bon contexte.
- Assure une automatisation déterminée par les objectifs, avec de nouveaux éléments de règle permettant de réduire les temps d'indisponibilité et d'accélérer les opérations.
- Protection des données assurée par un quorum, un indicateur de présence et une condition de départage disque et réseau.
- Optimise l'utilisation des ressources réseau.
- S'intègre au portefeuille Tivoli étendu d'offres de haute disponibilité et d'automatisation d'événements, qui permet l'implémentation et l'exécution systématiques d'opérations à haute disponibilité sur une variété d'applications, de middleware et de plateformes.
- S'intègre à IBM Tivoli System Automation Application Manager afin de permettre une automatisation de bout en bout, l'exploitation d'applications composites et une génération de rapports étendus.
Nouveautés d'’IBM Tivoli System Automation for Multiplatforms
- Prise en charge de nouvelles plateformes, notamment Sun Solaris et Windows Server 2008.
- Fourniture d'un composant xDR en option qui étend GDPS (Geographically Dispersed Parallel Sysplex), la meilleure solution de reprise après incident pour z/OS, et offre une continuité opérationnelle robuste pour Linux on System z
- Prise en charge des principales technologies de virtualisation sur les plateformes compatibles, notamment IBM z/VM, VMware et les nouvelles fonctions de virtualisation dans AIX 6
- Capacité à suivre et signaler la durée nécessaire au démarrage, à l'arrêt et à la reprise en ligne des applications pendant la phase d'exécution générale afin de mieux gérer les temps de reprise par rapport à un objectif préalablement fixé.
- Interface graphique de configuration améliorée permettant de créer rapidement et facilement des règles, sans devoir afficher ou éditer le code XML.
- Règles prédéfinies prenant en charge la haute disponibilité des solutions de centres informatiques dynamiques et la virtualisation.
En savoir plus
Acheter Tivoli System Automation for Multiplatforms
La 1ère année d'IBM Software Subscription and Support est inclus dans le prix d'achat.
Téléchargement en ligne du logiciel après achat - pas de frais de transport.
| 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.
Le Cloud et l'optimisation informatique
-
Ordonnancement et automatisation des systèmes
- IBM Service Delivery Manager
- IBM SmartCloud Provisioning
- Tivoli Dynamic Workload Broker
- 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
Des moyens d'achats faciles ou en savoir plus.
Besoin d'aide ?
Des moyens d'achats faciles ou en savoir plus.
- Demandez un devis
- Envoyez un e-mail à IBM
- Ou appelez-nous au (coût d'un appel local) 0810 016 810
Code prioritaire : 109HJ10W