HCL Workload Automation, Version 9.4

Integrating dynamic workload broker with Configuration Management Database

This section describes the integration of dynamic workload broker with Configuration Management Database.

Using this integration you can interact with the Tivoli® Change and Configuration Management Database to manage the automatic discovery of available resources in the scheduling environment according to their characteristics and relationships.

Through the integration, dynamic workload broker imports resources from the Configuration Management Database and integrates them as resources in the environment where your jobs run. In this way you can:

Optimize capacity across the IT infrastructure and run an enormous workload. For example, if you have a problem and a primary server cannot process the workload, you can automatically discover a new server with the same characteristics as the primary server and quickly redistribute your workload to this server. In this way you can save costs by reducing the recovery time.
Use the resources available in the environment to support the application.
Dynamically adapt job processing in response to changes in the environment.
Minimize the total amount of time that is required to deliver the output of the task resolution processes.
Assign to the job the appropriate resources it needs to run, based on the job requirements and on the administration polices.
Optimize the use of the resources by assigning to the job the required resources based on the SLA.
Manage and control the resource usage and load.
Send jobs to target resources that meet the requirements needed to run the job.

The integration with Configuration Management Database is installed when you install the dynamic workload broker server. For more information about installing the Configuration Management Database enablement, see Dynamically Scheduling your Workload. For more information about Configuration Management Database, refer to the Configuration Management Database documentation.

The following limitations apply when importing resources:

You can submit jobs only to endpoints that are discovered by dynamic workload broker. Any resources that are suitable to be imported must exist in the dynamic workload broker environment. This means that you can only import from Configuration Management Database the resources that run on dynamic workload broker computer systems.
The resource-matching is performed by using the fully qualified host name of the computer on which they run. Therefore the matching can be performed only for those resources running on dynamic workload broker computer systems that have a fully qualified host name matching the host name listed in the RunsOn column in Configuration Management Database.
You can only import resources of the AppServer type and all inherited types, because only these resource types meet the fully qualified host name criterion. You can specify the resource types to be imported in the CCMDBconfig.properties file.

A dynamic workload broker logical resource is created for each discovered Configuration Management Database resource. A relationship of the Contains type is defined between the new logical resource and the dynamic workload broker computer system defined in the RunsOn column in Configuration Management Database.

After importing the Configuration Management Database resources, they can be accessed from the dynamic workload broker Web console using the Scheduling Environment > Logical Resources task from the console navigation tree. They can be identified in the Logical Resources table by the value in the Owner column. The value for imported Configuration Management Database resources is CCMDB. The name of logical resources of this type cannot be modified from the dynamic workload broker Web console.

Table 1 shows details about the attribute mapping between the two products.

Table 1. Mapping between dynamic workload broker and Configuration Management Database attributes
dynamic workload broker attribute	Configuration Management Database attribute
DisplayName	Display Name or Label if Display Name is not available
Name	GUID
Administrative Status	Admin State
Configuration Management Database SubType	CollationType
Creator Name	CDMSource or “CCMDB” if CDMSource is not available
Owner Name	“CCMDB”
Quantity	1

Configuring the integration with Configuration Management Database

You can use the CCMDBConfig.properties file to configure the integration with Configuration Management Database. The CCMDBConfig.properties file is installed in the following path:

installation_directory/TDWB/config

The following parameters are available in the CCMDBConfig.properties file:

CCMDB.user

Specifies the user ID used to connect to the Configuration Management Database server. You must specify this value at installation time. You can change the value afterwards. To make effective the change, you must stop and restart the dynamic workload broker server.

CCMDB.softwareElements

Specifies the comma-separated list of software elements that the user wants to import. By default, all software elements of the AppServer type are imported. You can add or change software elements in the list. If this parameter is changed, the CMDB.lastUpdate property must be set to 0 to perform a full import instead of an update by differences. The following elements types can be specified in this parameter:

AppServer: Represents a server program. Includes the following element types: CIMOM, CitrixServer, DatabaseServer, DominoServer, GenericAppServer, J2EEServer, MQQueueManager, MySAPABAPApplicationServer, OracleAppProcessManager, ServerProcess, SMSServer, WebServer
Db2System: Represents an IBM® DB2® system.
OracleServer: Represents an instance of the Oracle Server.
Service: Includes the following element types: DNSService, FileSystemService, GenericService, LDAPService, SMTPService, WebService
WebSphereNode: Represents a WebSphere® node. A node is a logical grouping of managed servers. A node usually corresponds to a physical computer system with a unique IP host address. Node names are usually identical to the host name of the computer.

Note: This information refers to the Common Data Model 2.6.5 documentation.

CMDBAddress.port

Specifies the Configuration Management Database server port. The default value is 9530. You must specify this value at installation time. You can change the value afterwards. To make effective the change, you must stop and restart the dynamic workload broker server.

CCMDB.pwd

Specifies the password for the user ID used to connect to the Configuration Management Database server. You must specify this value at installation time. The password is automatically encrypted when the command line is used. You can change the value afterwards. To make effective the change, you must stop and restart the dynamic workload broker server.

CCMDB.lastUpdate

Specifies the last time that an import operation completed successfully. The unit of measurement is milliseconds. You can modify this parameter only when the CCMDB.softwareElements parameter is changed. In this case, you must set this parameter to 0.

CMDBAddress.host

Specifies the Configuration Management Database server address. You must specify this value at installation time. You can change the value afterwards. To make effective the change, you must stop and restart the dynamic workload broker server.

The trace file is created in the following path:

installation_directory\TDWB\log\CCMDB.log

ccmdbdataimport command - Importing resources from Configuration Management Database

A dedicated command line is provided to import the resources. If you install the CCMDB enablement, the command is stored on dynamic workload broker servers in the following location:

installation_directory/TDWB/bin

Syntax

ccmdbdataimport ?

ccmdbdataimport [-usr user_name] [-pwd password] -v

Description

This command performs a number of queries on the dynamic workload broker server to retrieve computer systems on which Configuration Management Database resources can run. It then connects to the Configuration Management Database server to find the related resources.

When new resources are created or deleted in Configuration Management Database, run the command again to update the dynamic workload broker server. When an update is performed, the modifications you have applied to the resources in the dynamic workload broker environment might be overwritten with the new information from the Configuration Management Database. This is because the update operation is performed only on the resources that have changed in the Configuration Management Database rather than on all resources.

Log and trace information for this integration is stored in the dynamic workload broker command-line log and trace files. These files are stored in the following directories:

trace file: installation_directory/TDWB/logs/CLItrace.log.0
log file: installation_directory/TDWB/logs/CLI.log.0

Options

?: Displays help information.
-usr user_name: Specifies the user name for a user who is authorized to perform operations on the command line. This parameter is required when security is enabled and the user name is not defined in the CLIConfig.properties configuration file.
-pwd password: Specifies the password for a user who is authorized to perform operations on the command line. This parameter is required when security is enabled and the password is not defined in the CLIConfig.properties configuration file.
-v: Used to obtain a verbose output.

Authorization

TDWBConfigurator.

Return Values

The ccmdbdataimport command returns one of the following values:

0: Indicates that ccmdbdataimport completed successfully.
< > 0: Indicates that ccmdbdataimport failed.

Enabling the trace for dynamic workload broker

To enable the trace for dynamic workload broker, edit the file installation_directory/TDWB/config/CLIConfig.properties by setting the parameter .level to ALL.