FileNet P8 Content Engine, Version 5.0.+       Application server:  WebSphere Application Server     

Deploying Content Engine Web Upgrade Tool (WebSphere Application Server)

You need to deploy IBM® FileNet® Content Engine Web Upgrade Tool on the application server where version 5.0.0 of Content Engine is deployed.

If Content Engine is deployed on a managed node, you must deploy Content Engine Web Upgrade Tool on the that node. If Content Engine is deployed in a cluster, you must deploy Content Engine Web Upgrade Tool in that cluster.
High availability Important: You must specify a URI to a single node instance. During the upgrade the upgrader must not be load-balanced to another node in the highly available Content Engine configuration.
To deploy IBM FileNet Content Engine Web Upgrade Tool on WebSphere® Application Server:
  1. Log in as ce_install_user to the application server machine where you installed version 5.0.0 of the Content Engine software.
  2. Determine the directory that contains the upgrader.war file, depending on the operating system where Content Engine is installed:
    Option Description
    UNIX /opt/IBM/FileNet/ContentEngine/lib
    Windows C:\Program Files\IBM\FileNet\ContentEngine\lib
  3. In the WebSphere Application Server administrative console, navigate to Applications > Enterprise Applications and click Install.
  4. (WebSphere 6.1) Specify the path to the upgrader.war file, set the context root to /upgrader, and complete the following substeps:
    1. In the step to select installation options, set the application name to upgrader.
    2. If your deployment environment is WebSphere Application Server Network Deployment, select the node or cluster where Content Engine is deployed; otherwise, skip past the step to map modules to servers and the step to map virtual hosts to Web modules.
    3. Skip to the summary. Click Finish, and then click Save.
  5. (WebSphere 7.0) In the Install New Application page, specify the path to the upgrader.war file, click Next, and then click OK to confirm the path. Then complete the following substeps:
    1. In the step to select installation options, set the application name to upgrader.
    2. If your deployment environment is WebSphere Application Server Network Deployment, select the node or cluster where Content Engine is deployed; otherwise, skip past the step to map modules to servers and the step to map virtual hosts to Web modules.
    3. In the step to map context roots for Web modules, set the context root to /upgrader.
    4. Skip to the summary. Click Finish, and then click Save.
  6. Ensure that the class loader policy is set to Multiple by completing the following substeps on each server where you are deploying the upgrader.war file:
    1. In the WebSphere Application Server administrative console, navigate to Servers > WebSphere application servers and click the name of the server where you just deployed the upgrader.war file.
    2. Click the Configuration tab and under Server-specific Application Settings set the Classloader policy to Multiple.
  7. Synchronize nodes if needed.
  8. If your deployment environment is WebSphere Application Server Network Deployment, complete the following substeps:
    1. Open for editing the deployed version of the config.properties file. This file is at one of the following locations.
      Operating system Path to config.properties file
      UNIX /opt/IBM/WebSphere/AppServer/profiles/profile_name/installedApps/cell_name/upgrader_war.ear/upgrader.war/WEB-INF/classes
      Windows C:\Program Files\IBM\WebSphere\AppServer\profiles\profile_name\installedApps\cell_name\upgrader_war.ear\upgrader.war\WEB-INF\classes
    2. Find the line in the file that starts with SOAPConnectorAddress and change the port (the value after the =) to the port number that the WebSphere deployment manager uses.
  9. Navigate back to Applications > Enterprise Applications, select upgrader, and then click Start.


Feedback

Last updated: November 2010


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