Configuration updates on demand

A running IBM® z/OS® Connect server uses information from various files that are stored in UNIX System Services.

These files can be modified and the changes activated while the server is running. The following IBM z/OS Connect files can be configured dynamically:

Server configuration file.
Data transformation files, if any of your IBM z/OS Connect services use DataXForms.
API archive files.
API Requester archive files.
Service archive files.
Policies and rule sets.
Keystores.

If you need to modify, create or delete these files while the server is running, you can use one of these methods to activate the changes:

Use polling. Continuous polling uses CPU resources. This method can be useful in a development or test environment.
Use an MBean to trigger an update on demand. This method can be useful in a production environment.
Use the Refresh Modify command to activate all changes in all the files. This method can be useful in a production environment. For more information, see The MODIFY command.

The update mechanism is specified on the following server configuration elements. For more information, see the element description in the Reference section.

Updates to the server configuration files are controlled by the config element.
Updates to data transformation files are controlled by the zosconnect_zosConnectDataXform element.
Updates to APIs are controlled by the zosconnect_zosConnectAPIs element.
Updates to API Requesters are controlled by the zosconnect_apiRequesters element.
Updates to services are controlled by the zosconnect_services element.
Updates to policies and rule sets are controlled by the zosconnect_policy element.