[Java programming language only]

Merging plug-in configuration files for deployment to the application server plug-in

Generate plug-in configuration files after you configure a unique clone ID in the Liberty server.xml configuration file.

Before you begin

If you are generating and merging plug-in configuration files to configure HTTP session failover in a Liberty profile, then you must complete the following tasks:

About this task

Use the WebSphere® Application Server administrative console to complete this task.

Procedure

  1. Merge the plugin-cfg.xml files from multiple application server cells.
    You can either manually merge the plugin-cfg.xml files or use the pluginCfgMerge tool to automatically merge the plugin-cfg.xml file from multiple application server profiles into a single output file. The pluginCfgMerge.bat and pluginCfgMerge.sh files are in the install_root/bin directory.

    For more information about manually merging the plugin-cfg.xml files, see the technote about merging plugin-cfg.xml files from multiple application server profiles.

  2. Ensure that the cloneID value for each application server is unique.
    Examine the cloneID value for each application server in the merged file to ensure that this value is unique for each application server. If the cloneID values in the merged file are not all unique, or if you are running with memory to memory session replication in peer to peer mode, use the administrative console to configure unique HTTP session cloneIDs.

    To configure a unique HTTP session clone ID with the WebSphere Application Server administrative console, complete the following steps:

    1. Click Servers > Server Types > WebSphere application servers > server_name.
    2. Under Container Settings, click Web Container Settings > Web container.
    3. Under Additional Properties, click Custom properties > New.
    4. Enter HttpSessionCloneId in the Name field, and enter a unique value for the server in the Value field. The unique value must be eight to nine alphanumeric characters in length. For example, test1234 is a valid cloneID value.
    5. Click Apply or OK.
    6. Click Save to save the configuration changes to the master configuration.
  3. Copy the merged plugin-cfg.xml file to the plugin_installation_root/config/web_server_name directory on the web server host.
  4. Ensure that you defined the correct operating system, file access permissions for the merged plugin-cfg.xml file. These file access permissions allow the HTTP server plug-in process to read the file.

Results

When you complete this task, you have one plug-in configuration file for multiple application server cells, and your eXtreme Scale applications that run in the Liberty profile are enabled for session replication.