Control and edit your CR process XML file only on the main server. The process package you generate from this file must be copied from the main server to all secondary servers. Your generated process package can be found on your primary server, and must be copied to the same directory on every secondary server. For each server, install the process package with the Package Installer as normal.
For example: CHANGE_APP_HOME/WEB-INF/packages
Control and edit your list box entries only on the main server. List box values are saved in the applicable directory. When modified, this file must be copied to the same location on every secondary server. For each secondary server, load the new list box values by selecting
.For example: CHANGE_APP_HOME/WEB-INF/wsconfig/pt_listbox.cfg
Control and edit your access control lists (ACLs) only on the main server. ACL definitions are saved in several files in the applicable directory.
The ACL files are Extensible Markup Language (XML) files that contain all the information required to manage read/write security. The tools to create, edit, and install these XML files are part of the Administration GUI.
You must have only one ACL file for each type installed at a time for each IBM® Rational® Change installation. For example, one file for CRs, one for tasks, and one for objects. These files are stored in the CHANGE_APP_HOME/WEB-INF/wsconfig/acl directory.
When modified, all these files must be copied to the same location on every secondary server. For each secondary server, load the new ACL definitions by selecting
. Next, go to , and enable the same ACLs as on your primary server.For example: CHANGE_APP_HOME/WEB-INF/wsconfig/acl
As with your CR process package, any packages installed onto the primary server must be copied to and installed on all secondary servers.
If you modify any settings on
of the primary server, you must apply the same changes on every secondary server.If you manually modify any pt.cfg settings on your primary server, you must make the same changes on every secondary server. For each secondary server, load the new pt.cfg settings values by selecting
.