Tivoli System Automation for Multiplatforms

Gran disponibilidad y automatización según las políticas para las aplicaciones y servicios de entornos heterogéneos

Garantiza una alta disponibilidad continua y reduce la frecuencia y la duración de las interrupciones de los servicios de las aplicaciones y middleware más importantes, que se ejecutan en plataformas y tecnologías de virtualización heterogéneas.

Aumenta la disponibilidad y reduce las interrupciones en varias plataformas heterogéneas y entornos virtuales, como Microsoft Windows, IBM AIX, Linux (incluyendo Linux en IBM System z, System p, System i, System x) y Solaris.

  • Inicia, ejecuta y coordina el arranque, parada, reinicio y migración tras error automatizados de componentes de aplicaciones individuales o de aplicaciones compuestas enteras para reducir la frecuencia y duración de incidentes que afectan a la disponibilidad de las TI
  • Proporciona un conjunto de herramientas estándar que da soporte a diversos escenarios de migración tras error relacionados con entornos virtuales y físicos
  • Ofrece tecnologías avanzadas de agrupación en clúster, incluido el soporte a las configuraciones sofisticadas de agrupación en clúster, —como N:1 o N:M— con el fin de reducir el número de servidores de hardware necesarios y garantizar una alta disponibilidad continua de servicios vitales para la empresa
  • Ofrece funciones avanzadas de automatización basadas en políticas para facilitar la gestión operativa de infraestructuras de TI complejas, hecho que elimina la necesidad de tener amplios conocimientos de programación para crear y mantener scripts y procedimientos
  • Amplía el soporte a la virtualización a través de políticas de automatización
  • Proporciona módulos de políticas plug and play que contienen las mejores prácticas para las soluciones de software clave de Tivoli y de terceras partes. Ello permite la detección y recuperación de anomalías predefinidas, lo que conlleva un ahorro en costes operativos, así como una alta disponibilidad continua
  • Proporciona una GUI basada en web potente y fácil de usar con la que es posible hacer cambios sin errores en la configuración
  • Agiliza la recuperación gracias a la capacidad de definir dependencias entre los recursos para asociar de forma rápida las condiciones con los recursos, de modo que los operadores puedan escoger las acciones correctivas más adecuadas en el contexto correcto
  • Automatización basada en objetivos con nuevos elementos de políticas para reducir el tiempo de inactividad y agilizar las operaciones
  • Protección de datos cruciales mediante quórum, dispositivo del hombre muerto y factor de desempate de disco y red
  • Permite optimizar la utilización de los recursos de TI
  • Se integra con el extenso portfolio de productos de alta disponibilidad y automatización de sucesos de Tivoli que permiten la implementación y ejecución sistemática de operaciones de alta disponibilidad en aplicaciones, middleware y plataformas
  • Se integra con IBM Tivoli System Automation Application Manager para una automatización total y para gestionar aplicaciones compuestas y una extensa variedad de informes

Novedades de IBM Tivoli System Automation for Multiplatforms

  • Admite plataformas adicionales, como Sun Solaris y Windows Server 2008
  • Un componente xDR opcional que amplía Geographically Dispersed Parallel Sysplex (GDPS) —la solución de recuperación en caso de siniestro para z/OS de primera clase— para ofrecer una continuidad de la actividad sólida para Linux en System z
  • Soporte para las principales tecnologías de virtualización de las plataformas admitidas, incluyendo IBM z/VM, VMware y las nuevas funciones de virtualización AIX 6
  • Posibilidad de realizar un seguimiento y de crear informes del tiempo que se tarda en arrancar, parar o migrar tras error las aplicaciones durante el tiempo de ejecución, para gestionar de forma más eficiente los tiempos de recuperación y conseguir los objetivos marcados
  • Configuración mejorada de la interfaz gráfica de usuario para crear y editar políticas de forma rápida y sencilla, sin necesidad de visualizar o editar XML
  • Políticas predefinidas para dar soporte a soluciones de alta disponibilidad para centros de datos dinámicos y virtualización

Descubra más

Comprar Tivoli System Automation for Multiplatforms

IBM Software Suscription y Software Support está incluido en el precio del producto para el primer año.

Descarga del software online después de la compra - sin gastos de envío.

No disponible para la compra online. Otros medios de compra o solicitar información adicional.

¿Necesita ayuda? Contacte IBM

Mostrar información Ocultar información


Features, advantages and benefits
FeaturesAdvantagesBenefits
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.

Una manera fácil de adquirir nuestros productos u obtener más información.

Contáctenos

Una manera fácil de adquirir nuestros productos u obtener más información.

Tivoli System Automation for Multiplatforms

 

 

 

IBM Software