Integrating Dynamic workload broker with Tivoli Provisioning Manager
How dynamic workload broker integrates with Tivoli Provisioning Manager version 7.1.1.
- Ensure that during peak periods the jobs in the critical path are run in the required time frame.
- Automatically transfer entire workloads and update policies across multiple platforms.
- Assign to the job the appropriate resources that 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.
- Dispatch jobs to target resources that meet the requirements to run the job.
- Respond to any unexpected and unplanned-for demands; individual jobs can be added ad hoc to the scheduling plan at any time.
The integration with Tivoli Provisioning Manager can be installed when installing the dynamic workload broker server. For more information about installing the Tivoli Provisioning Manager enablement, see Tivoli Provisioning Manager Installation and Configuration Guide.
Configuring the integration with Tivoli Provisioning Manager
The TPMConfig.properties file defines the integration with Tivoli Provisioning Manager and is created when the extension is installed. You can modify the file. Restart the WebSphere Application Server to implement the changes.
installation_directory/configThe following parameters are available in the TPMConfig.properties file:
- TPMAddress.hostname
- Specifies the host name of the Tivoli Provisioning Manager server to be used when running the recovery action.
- TPMAddress.port
- Specifies the port number of the Tivoli Provisioning Manager server to be used when running the recovery action.
- TPM.user
- Specifies the user name of a user with the authority to run workflows.
- TPM.pwd
- Specifies the password for the user to be used when running a Tivoli Provisioning Manager workflow.
Log and trace information for this integration is stored in the WebSphere Application Server logs and traces, stored in the following path: WAS_profile_root /AppSrv01/logs/ server1.