FileNet P8 Application Engine, Version 5.2.1              

Preparing for Application Engine upgrade

Before you upgrade your Application Engine installation, you must prepare your existing configuration for the upgrade. This preparation includes backing up existing files and undeploying your web application.

About this task

See the topic on removing software in the IBM FileNet P8 eForms Installation and Upgrade Guide.

High availabilityImportant: In a highly available clustered server environment, you need to perform the steps on all nodes in your cluster.
To prepare for the Application Engine upgrade:

Procedure

  1. Log on to the Application Engine server:
    Option Description
    AIX®, HPUX, Linux, Linux on System z®, Solaris Log on as a user with read, write, and execute access to the directory where you plan to install Application Engine.
    Windows Log on as a member of the local Administrators group or a user with equivalent permissions.
  2. (Windows) Using the Windows Task Manager, verify that no javaw.exe processes are running. If the applications in the preceding steps stopped correctly, no Application Engine related javaw.exe processes should be running.
    1. Use Windows Services to stop the Process Application Engine Services Manager Service. Select Start > Programs > Administrative Tools > Services. If the Process Application Engine Services Manager status is started, right-click the item and click Stop.
    2. If there are still javaw.exe processes running after stopping the Process Application Engine Services Manager, use the Windows Task Manager to stop any Application Engine related javaw.exe processes.
  3. Back up, undeploy, and remove the Workplace Web application from the Java™ EE application server.

    During this step you will create a backup copy of the deployed Web application containing all customized files and all configuration files stored in the WEB-INF directory.

    Even though the installer automatically creates a backup of your existing Application Engine 3.5 or 4.0.1 configuration files, it is a best practice to back up the following directories to get a complete backup of your deployed system. You might need these files in later steps to retain your 3.5 or 4.0.1 settings. For example, when you copy modified files to the installed Workplace directory and perform the upgrade and configuration of Application Engine,

    Option Description
    WebSphere® Application Server
    1. Make a backup copy of the deployed Workplace directory (deploy_backup): WAS_HOME/profiles/default/installedApps/node_name/app_engine_war.ear/app_engine.war

      Your path might vary if you created a new profile or renamed your WAR file.

    2. Stop the Workplace application from the WebSphere administrative console.
    3. Uninstall the Workplace application from Enterprise Applications.
    4. Save the changes and stop the WebSphere Application Server instance.
    5. Delete the temp Workplace directory (default: app_engine_war) from: WAS_HOME/profiles/default/temp/node_name/instance/app_engine.war
    WebLogic Server
    1. From the WebLogic Server Administration Console, stop the Workplace web application module.
    2. Make a backup copy of the Workplace folder (deploy_backup): AE_install_path/Workplace
    3. Delete the Workplace Web Application Module.
    4. Stop the WebLogic Server instance.
    JBoss Application Server
    1. Stop the JBoss Application Server instance.
    2. Make a backup copy of the deployed Workplace directory (deploy_backup): JBoss_HOME/server/default/deploy/Workplace.war
    3. Delete the deployed Workplace directory: JBoss_HOME/server/default/deploy/Workplace.war
    4. Delete the temporary Workplace directory for JBoss: JBoss_HOME/server/default/work/jboss.web/localhost/Workplace
  4. Copy modified files to the installed Workplace directory. During the upgrade, the configuration files will be moved from the following directory:

    AE_install_path/Workplace/WEB-INF

    to

    AE_install_path/Config/AE

    If you have made modifications to any of these files directly in the deployed Workplace directory (app_engine.war for WebSphere Application Server or Workplace.war for JBoss) in your 3.5. or 4.0.1 environment, you must copy the modified version of these files from the deploy_backup directory to the installed directory AE_install_path/Workplace/WEB-INF before you run the installer.
    • actions.xml
    • bootstrap.properties
    • ClassFilter.xml
    • ConfigurableLabels.xml
    • containericons.properties
    • content_redir.properties
    • customobjecticons.properties
    • download_redir.properties
    • fnsoap.xml
    • icons.properties
    • InfoPages.xml
    • PagingConfiguration.xml
    • PolicyProcessors.xml
    • PrimaryViews.xml
    • PropertiesPages.xml
    • SimpleSearch.xml
    • SystemsPropertiesView.xml
    As part of the upgrade the installation program automatically creates a backup of your existing Application Engine 3.5 or 4.0.1 configuration files, appending the suffix .old to the file names.
    • actions.xml.old
    • ClassFilter.xml.old
    • ConfigurableLabels.xml.old
    • containericons.properties.old
    • content_redir.properties.old
    • icons.properties.old
    • SystemsPropertiesView.xml.old
    • UpdateActions.xml.old
    • UpdateClassFilter.xml.old
    • UpdateConfigurableLabels.xml.old
    • UpdateProps.xml.old
    • UpdateSystemPropertiesView.xml.old
    • UpdateWeb.xml.old
    • web.xml.old

    The backed up files are located in: AE_install_path/backup-4_0_2

  5. High availabilityIf you are upgrading in a highly available environment, perform the following additional backup steps.
    • Back up the shared bootstrap.properties file in the shared network location.
    • Copy all of the configuration files to the shared configuration directory, if you are using one.
    • (Application Engine 3.5 upgrades only) A shared configuration directory will be created beneath the original location of the bootstrap file.

      Example: If your 3.5.x shared bootstrap location was Z: the newly created shared configuration directory will be Z:\AE\.



Last updated: October 2015
p8pup068.htm

© Copyright IBM Corporation 2013, 2015.