FileNet P8 Workplace XT, Version 1.1.5              

Deploying multiple Workplace XT instances

You can deploy multiple instances of Workplace XT on a single application server. Each deployment of Workplace XT must use the same Content Engine, Process Engine, and connection point. Each deployment of Workplace XT might use different Site Preference files and might provide access to different object stores.

Note:
  • The procedure below assumes that you have already installed Workplace XT and deployed one instance of the Workplace XT application. You might or might not have signed in and configured your bootstrap preferences.
  • For more information on how to deploy and manage multiple identical applications, see your application server documentation.
  • For WebLogic, deployment using a flat directory is not recommended when there will be multiple deployments.

To deploy a second instance of the Workplace XT application:

  1. Copy the Workplace XT configuration folder.

    On the Workplace XT server, make a copy, WebClient2 of the Workplace XT configuration folder found at:

    install_path/IBM/FileNet/Config/WebClient

    and place it in the same directory to create install_path/IBM/FileNet/Config/WebClient2.

  2. Copy the deploy folder.

    On the Workplace XT server, make a copy, deploy2, of the Workplace XT deploy folder found at:

    install_path/IBM/FileNet/WebClient/deploy

    and place it in the same directory to create install_path/IBM/FileNet/WebClient/deploy2.

  3. Delete the .war file and the .ear file from the deploy2 directory.
  4. In the install_path/IBM/FileNet/WebClient/deploy2 directory, edit the create_web_client_war.bat or .sh file.
    1. Make a backup of the file.
    2. Change the following lines:
      cd /D "%WEB_HOME%\WorkplaceXT"
      "%WEB_HOME%\_AEjvm\bin\jar" -cf
      "%WEB_HOME%\deploy\web_client.war" author containerSecured css
      download eprocess FnJavaV1Files images include is js operations
      portlets properties redirect regions scripts select UI-INF utils
      WEB-INF wizards *.jsp
      rem Add P8 eForms if installed.
      if exist "%WEB_HOME%\deploy\eforms_add_to_war.bat"
      call "%WEB_HOME%\deploy\eforms_add_to_war.bat"

      to this:

      cd /D "%WEB_HOME%\WorkplaceXT"
      "%WEB_HOME%\_AEjvm\bin\jar" -cf
      "%WEB_HOME%\deploy2\web_client2.war" author containerSecured css
      download eprocess FnJavaV1Files images include is js operations
      portlets properties redirect regions scripts select UI-INF utils
      WEB-INF wizards *.jsp
      rem Add P8 eForms if installed.
      if exist
      "%WEB_HOME%\deploy2\eforms_add_to_war.bat" call
      "%WEB_HOME%\deploy2\eforms_add_to_war.bat"

      to include the modified folder name and the new name for the WAR file, such as web_client2.war.

  5. If you want to deploy as an EAR file, modify the create_web_client_ear.bat or .sh file in the install_path/IBM/FileNet/WebClient/deploy2 directory to point to the modified folder names and to rename the EAR file.
    1. Make a backup of the create_web_client_ear.bat or .sh file.
    2. Edit the create_ear.bat or .sh file to change these lines:
      cd /D "%WEB_HOME%\deploy"
      "%WEB_HOME%\_AEjvm\bin\jar" -cvf
      "%WEB_HOME%\deploy\web_client.ear" META-INF *.war

      to this:

      cd /D "%WEB_HOME%\deploy2"
      "%WEB_HOME%\_AEjvm\bin\jar" -cvf
      "%WEB_HOME%\deploy2\web_client2.ear" META-INF *.war
  6. In the Workplace XT installation directory, edit the web.xml file.
    1. In FileNet\WebClient\WorkplaceXT\WEB-INF, rename web.xml to web.xml.1.
    2. Create a copy of web.xml.1 , and name it web.xml.
    3. In the new web.xml, change the following parameter value:

      <param-name>configurationDirectory</param-name> <param-value>C:/Program Files/IBM/FileNet/Config/WebClient</param-value>

      to set the path to the new configuration folder copy you created, for example, install_path/IBM/FileNet/Config/WebClient2

      Remember: On Windows, use double back slash (\\) in place of the forward slash in the configurationDirectory.
    4. (For deployments using the EAR file only) Change the value of the context root to the custom name you have chosen for the new application instance, for example, WorkplaceXT2.
  7. Re-create the WAR file by running create_web_client_war.bat or .sh.
  8. (For EAR file deployments only) Re-create the EAR file by running create_web_client_ear.bat or .sh.
  9. Rename the web.xml files.
    1. Rename the web.xml file that applies to the second instance to web.xml.2.
    2. Rename the original file, now called web.xml.1, back to web.xml.

    The original web.xml file is for the original application instance, and web.xml.2 is for the new instance. If you need to do further configuration for either instance, you must rename the appropriate version of the file to web.xml during the configuration.

  10. Clean up the bootstrap.properties file.

    If you haven't yet signed in to the Workplace XT application as part of your first Workplace XT installation there is no need to clean up the file.

    When you first sign in to Workplace XT certain values in the bootstrap.properties file, such as the name and location of the site preferences file, are set. To use different settings for your new Workplace XT application you must remove the existing entries from the copied file.

    The bootstrap.properties file is located in:

    install_path/IBM/FileNet/Config/WebClient2

    Edit the bootstrap.properties file:

    1. Remove the value entered for the prefName setting. This entry contains the name of the site preferences file stored on the object store.
    2. Remove the value entered for the objectStoreId. This entry contains the object store name where your site preferences will be stored.
    3. Remove or edit any of the other values as needed.
  11. In the relevant configuration files in the new IBM/FileNet/Config/WebClient2 directory, remove any comments and custom changes that should not apply to the second Workplace XT instance.

    If you have not yet signed in to the Workplace XT application as part of your first Workplace XT installation, there is no need to clean up the files.

  12. Deploy the second Workplace XT instance.

    Follow the application server specific procedures to deploy your second instance of Workplace XT using a unique name, such as Workplace XT2.

    When deploying the second instance, use the newly created web_client2.war or web_client2.ear file (depending on which method you choose) to deploy the application:

    deploy2/web_client2.war or deploy2/web_client2.ear

  13. Sign in and set bootstrap preferences for the new application.

    Use the following URL when signing in to set the bootstrap preferences for your new Workplace XT instance.

    http://WorkplaceXTServerName:port#/WorkplaceXT2

    You must specify a unique name for the Preference name for each deployment.



Feedback

Last updated: March 2013
wxtip068.htm

© Copyright IBM Corporation 2013.
This information center is powered by Eclipse technology. (http://www.eclipse.org)