End-to-end automation with IBM Tivoli System Automation for Multiplatforms
IBM Tivoli System Automation for Multiplatforms monitors and automates applications distributed across Linux® , AIX® , and z/OS operating systems by introducing a new product structure with two major components: - IBM Tivoli System Automation for Multiplatforms Base Component Provides high availabil...
Autor principal: | |
---|---|
Autor Corporativo: | |
Formato: | Libro electrónico |
Idioma: | Inglés |
Publicado: |
White Plains, N.Y. :
IBM
c2005.
|
Colección: | IBM redbooks.
|
Materias: | |
Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009627118106719 |
Tabla de Contenidos:
- Front cover
- Contents
- Figures
- Tables
- Examples
- Notices
- Trademarks
- Preface
- The team that wrote this redbook
- Become a published author
- Comments welcome
- Part 1 Fundamentals
- Chapter 1. IBM Tivoli System Automation for Multiplatforms V2.1
- 1.1 IBM Tivoli System Automation for Multiplatforms V2.1 overview
- 1.1.1 Main features
- 1.2 Base Component overview
- 1.2.1 Reliable Scalable Cluster Technology
- 1.2.2 Resource Managers
- 1.2.3 End-to-end Automation Adapter
- 1.3 End-to-end Automation Management Component overview
- 1.3.1 Automation Engine
- 1.3.2 End-to-end Automation Manager
- 1.3.3 Operations Console
- 1.3.4 Automation database
- 1.3.5 Automation policy
- 1.3.6 End-to-end Automation Adapter
- 1.4 Communication between end-to-end components
- 1.5 Concepts and terminology
- 1.5.1 High Availability and IBM Tivoli System Automation for Multiplatforms
- 1.5.2 Terms used in IBM Tivoli System Automation for Multiplatforms
- Chapter 2. IBM Tivoli System Automation for z/OS V3.1
- 2.1 IBM Tivoli System Automation for z/OS V3.1 overview
- 2.2 What is new in IBM Tivoli System Automation for z/OS V3.1
- 2.2.1 Enhancements to the Customization Dialog
- 2.2.2 IBM Tivoli OMEGAMON integration
- 2.2.3 GDPS Integration
- 2.2.4 IBM Tivoli System Automation for z/OS V3.1 End-to-end Automation Adapter
- 2.3 Overview Planning for installation
- Part 2 Case study scenario implementation
- Chapter 3. Case study scenario overview
- 3.1 Scenario overview
- Chapter 4. Case study scenario: HTTP Servers on Linux first-level automation domain
- 4.1 Apache automation domain overview
- 4.1.1 Installation
- 4.1.2 Automation requirements
- 4.2 Automation domain configuration
- 4.2.1 Create the first-level automation domain
- 4.2.2 Define resources in the automation domain.
- 4.2.3 Create the automation policy using relationship definitions
- 4.2.4 Change the operational state of the resource group
- 4.2.5 Configuration error and recovery example
- 4.2.6 Exercising the automation policy example
- 4.3 End-to-end Automation Adapter configuration
- 4.3.1 Configure the End-to-end Automation Adapter
- 4.3.2 Replicate configuration files to nodes in the automation domain
- 4.3.3 Define the End-to-end Automation Adapter automation policy
- 4.4 Miscellaneous information
- Chapter 5. Case study scenario: Application Servers on AIX first-level automation domain
- 5.1 Application server automation domain overview
- 5.1.1 Automation requirements
- 5.2 Automation domain configuration
- 5.2.1 Create the first-level automation domain
- 5.2.2 Define automation domain resources
- 5.2.3 Create the automation policy using relationship definitions
- 5.2.4 Change the Operational State of the resource group
- 5.2.5 Verify the operational quorum and tie breaker definition
- 5.3 End-to-end Automation Adapter configuration
- 5.3.1 Generate End-to-end Automation Adapter configuration files
- 5.3.2 Replicate the End-to-end Automation Adapter configuration files
- 5.3.3 Define the End-to-end Automation Adapter automation policy
- 5.4 Maintaining defined policies
- Chapter 6. Case study scenario: IBM DB2 on z/OS first-level automation domain
- 6.1 IBM DB2 on z/OS automation domain overview
- 6.2 IBM DB2 on z/OS automation domain configuration
- 6.2.1 Configure NetView for IBM Tivoli System Automation for z/OS
- 6.2.2 Automate NetView startup procedure
- 6.2.3 Allocate System-Unique data sets
- 6.2.4 Configure the Automation Manager
- 6.2.5 Allocate data sets for the ISPF customization dialog
- 6.2.6 Update PARMLIB data sets
- 6.2.7 Update PROCLIB data sets
- 6.2.8 Define the base automation policy.
- 6.3 Configuring automation policies for IBM DB2
- 6.3.1 Identify required IBM DB2 messages
- 6.3.2 Create scenario automation policy database
- 6.3.3 Populate the scenario policy database
- 6.3.4 Define policies for monitoring IBM DB2 application tasks
- 6.3.5 Import customized scenario policy database into production
- 6.3.6 Create application group and define group membership
- 6.3.7 Verify Relationships in the automation policy
- 6.4 End-to-end Automation Adapter configuration
- 6.4.1 Check prerequisites and dependencies
- 6.4.2 Configure NetView and IBM Tivoli System Automation for z/OS
- 6.4.3 Enabling the Event Automation Service
- 6.4.4 Configure the Global Initialization File
- 6.4.5 Configure the NetView Message Adapter Service
- 6.4.6 Customize the End-to-end Automation Adapter
- 6.4.7 Perform configuration for security
- 6.4.8 Verify startup of the Automation Adapter
- 6.4.9 Solve timeout problems
- Chapter 7. Case study scenario: End-to-end automation domain
- 7.1 End-to-end Automation Management Component installation
- 7.2 Installation verification tasks
- 7.2.1 EAUTODB and OPCONDB databases
- 7.2.2 End-to-end Automation Management Component automation engine startup
- 7.2.3 End-to-end Automation Management Component applications status
- 7.2.4 JDBC providers connection
- 7.2.5 ISC portal application startup
- 7.2.6 System Automation operations console
- 7.3 Users and group management
- 7.3.1 Creating users
- 7.3.2 Creating user groups
- 7.3.3 Assigning access permissions to user groups
- 7.3.4 Assigning users to user groups
- 7.3.5 Assigning access roles to user groups
- 7.4 End-to-end Automation Management Component configuration
- 7.5 Defining the end-to-end automation policy
- 7.5.1 Automation requirements and policy overview
- 7.5.2 Creating the end-to-end automation policy file.
- 7.5.3 Verifying the end-to-end automation policy file
- 7.5.4 Activating the end-to-end automation policy file
- Part 3 Appendixes
- Appendix A. Troubleshooting overview
- Communication between end-to-end components
- Location of the root directories
- Tivoli common directory
- Log and trace files
- End-to-end Automation Management Component automation engine
- End-to-end Automation Management Component automation manager
- End-to-end Automation Adapter
- IBM Tivoli System Automation for Multiplatforms Operations Console
- The log viewer tool
- The TraceWizard utility
- Appendix B. Additional material
- Locating the Web material
- Using the Web material
- System requirements for downloading the Web material
- How to use the Web material
- Abbreviations and acronyms
- Related publications
- IBM Redbooks
- Other publications
- Online resources
- How to get IBM Redbooks
- Help from IBM
- Index
- Back cover.