IBM BJ0NJML Integration Guide - Page 278
Integration Module Components, Operational Management Products
View all IBM BJ0NJML manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 278 highlights
Integration Module Components Integration Module Components An integration module is composed of defined integration framework components. You can configure the integration module to be implemented as a Java class or as an invocation channel. When you install the integration module, integration module artifacts with the Java class and XSL files are provided. An integration module also provides logical management operation definitions. The integration module definition includes the following information: T Name, version, and description T Operational management product and version - Identifies the operational management product and version that the integration module can run. T Handler - Identifies the protocol that the integration module uses to invoke an operational management product. T Integration module implementation choice - Either a Java class or invocation channel. The following components are contained in the integration module definition: T The logical management operations that the integration module supports. T The integration module properties that are unique to the integration module. Use the properties to configure the behavior of the integration module. Operational Management Products An operational management product, such as Tivoli Provisioning Manager, automates system processes, such as software deployment. Operational management product services are run on assets, such as servers. The assets are referred to as configuration items. Multiple instances of operational management products can exist in a production environment. More than one operational management product can manage a single configuration item. Each operational management product has its own unique identifier, a source token, for each configuration item. The database includes a repository of operational management product and configuration item information. This information includes relationships between the operational management products and configuration items, and the source tokens that drive the integration between process management products and operational management products. You can load operational management products and configuration items into the system database from a discovery engine, such as Tivoli Application Dependency Discovery, or an asset management database. First load your operational management product and configuration item data into the discovery engine using the bulk loader interface. The discovery engine combines data from multiple sources into one data model. You can use the IBM® Tivoli® Integration Composer 264 Integration Guide