6.3. Configuring and Loading Secondary Application Instances (for Multi-JVM operation)

1. After configuring and loading the primary server instance, extract the active configuration parameters with ccm get --all > primary-server.properties

2. Follow all installation instructions on the second server up to the beginning of Section 6.2 Configuring and Loading the Primary Application Instance.

3. If there were any customized enterprise.init files created for the primary server, copy them into the same location for each secondary server.

4. Data and schema loading is unnecessary for secondary servers, so we will invoke ccm as follows, passing in the generated properties file from the first server instance and overriding any host-specific values on the command line (interactive setup is also an option at this point) — when using this command, remove the escape character "\" and make the command all one line; the "\" is used to format the line for printing:

   ccm load pkg-key1 pkg-key2 ... --config --parameter-file \ primary-server.properties waf.web.host=server2:9090

5. Run ccm hostinit with the same arguments as with the primary instance.