Home
HCL Workload Automation
Welcome to the HCL Workload Automation documentation, where you can find information about how to install, maintain, and use HCL Workload Automation. The documentation has been updated for HCL Workload Automation Version 10.2.2.
Administration Guide
Connection security overview
Extending communication scenarios to other server components
Apply custom certificates to backup master domain manager and dynamic domain manager
Creating brand new keystores for the dynamic agent
Create brand new keystores for the dynamic agent

HCL Workload Automation
Welcome to the HCL Workload Automation documentation, where you can find information about how to install, maintain, and use HCL Workload Automation. The documentation has been updated for HCL Workload Automation Version 10.2.2.
- Planning and Installation
- User's Guide and Reference
- Administration Guide
  - Customizing and configuring HCL Workload Automation
  - Configuring the Dynamic Workload Console
  - Configuring user authorization (Security file)
  - Configuring authentication
  - Network administration
  - Connection security overview
    - Creating a Certificate Authority and generating certificates
      Sample steps to create a CA and generate default certificates.
    - SSL connection by using the default certificates
      The SSL connection between product components is enabled by using the default certificates.
    - Customizing certificates for master domain manager and dynamic agent communication
      Supported scenarios for creating custom certificates for communication between master domain manager and dynamic agent
    - Scenario: Connection between the Dynamic Workload Console and the HCL Workload Automation components
      The Dynamic Workload Console connects in SSL mode with the HCL Workload Automation components by using the default certificates. You might configure the Dynamic Workload Console to connect in SSL mode by using your certificates.
    - Extending communication scenarios to other server components
      Apply custom certificates to backup master domain manager and dynamic domain manager
      - Creating new brand keystores
        Creating new brand keystores for the server components and dynamic agent
      - Creating brand new keystores for the server components
        Create brand new keystores for the master domain manager (backup master domain manager, dynamic domain manager) and Dynamic Workload Console
      - Creating brand new keystores for the dynamic agent
        Create brand new keystores for the dynamic agent
    - Scenario: SSL Communication across the fault-tolerant agent network
  - Data maintenance
  - Administrative tasks
  - Administering IBM i dynamic environment
    On overview on how to administer the HCL Workload Automation IBM i dynamic environment.
  - Performance
  - Availability
  - License computation model
- Scheduling with the Agent for z/OS
- Database Views
- High Availability Cluster Environment
- Driving HCL Workload Automation
- Extending HCL Workload Automation

Creating brand new keystores for the dynamic agent

Create brand new keystores for the dynamic agent

About this task

To create brand new keystores for the dynamic agent, perform the following steps:

Procedure

On the dynamic agent, create a CMS keystore.
On the dynamic agent, use the twsManageKey script to convert the keystore created in step 1.
Stop the dynamic agent using the ShutDownLwa command.
Browse to the ita.ini file, which is located in the following paths:

On Windows systems

<TWA_home>\TWS\ITA\cpa\ita

On UNIX systems

<TWA_DATA_DIR>/ITA/cpa/ita
Edit the following properties in the ita.ini file:

key_db_name

file name of the generated in step 1 (CMS)

key_repository_dir

path to the generated in step 1

java_truststore_password_file

absolute path to the generated in step 2 (pwd = default)

java_truststore_file

absolute path to the generated in step 2
Restart the dynamic agent using the StartUpLwa command.
To verify that the certificate customization has completed successfully, delete the old certificates and optionally rename the new certificates with the names of the certificates you deleted.