Impact of network changes
Any changes that you make to your network might have an impact on HCL Workload Automation. Workstations can be identified within HCL Workload Automation by host name or IP address. Any changes to host names or IP addresses of specific workstations must obviously be also implemented in the HCL Workload Automation database. However, remember that if those workstations are involved in jobs that are currently scheduled in the Symphony file, those jobs are looking for the old workstation identity.
Changes to host names or IP addresses of specific workstations can be activated immediately by running JnextPlan -for 0000. A new production plan is created (containing the updated IP addresses and host names), but the plan time span is not extended.
Thus, plan any network changes with the job schedules in mind, and for major changes you are advised to suspend HCL Workload Automation activities until the changes complete in the network and also implemented in the HCL Workload Automation database.
- Application server
- If you change the network you will need to change the communication parameters specified in the application server configuration files. How to do this is described in the appendix on the utilities supplied with the WebSphere Application Server Liberty Base in the Planning and Installation Guide.
- Command-line client
- When you connect from the command-line client you supply a set
of connection parameters. This is done in one of these ways:
- From the localopts file
- The default method is that the connection parameters in the localopts file are customized when the command line client is installed.
- From the useropts file
- A useropts file might have been created for the user in question, containing a version of the connection parameters personalized for the user.
- In the command line, individually
- When you invoke one of the command-line programs, you can optionally include the parameters as arguments to the command. These override the values in the localopts or useropts files.
- In the command line, in a file
- When you invoke one of the command-line programs, you can optionally include the parameters in a file, the name of which is identified as the -file argument to the command. These override the values in the localopts or useropts files.