IBM FileNet P8 Application Engine 3.5.1 Fix Pack Readme: P8AE 3.5.1-021
© Copyright IBM Corporation 2006, 2010. All Rights Reserved.

About this fix pack

Accessing IBM FileNet documentation, compatibility matrices, and fix packs

Compatibility

Known issues

New in this fix pack

Installation, migration, upgrade, and configuration

Requirements

Install this fix pack

Uninstall this fix pack

Product fix history

Contact customer support

Notices

Trademarks

About this fix pack

This document provides information about the IBM® FileNet® Application Engine P8AE-3.5.1-021 fix pack and new features provided. The P8AE-3.5.1-021 fix pack upgrades an existing Application Engine system. Application Engine fix packs are cumulative; each fix pack contains the content from all previously released fixed packs.

Accessing IBM FileNet documentation, compatibility matrices, and fix packs

Documentation and compatibility matrices

To access documentation and compatibility matrices for IBM FileNet products:

1. Navigate to the Product Documentation for FileNet P8 Platform support page (www-1.ibm.com/support/docview.wss?rs=3247&uid=swg27010422).
2. Select a PDF or a Doc Link, whichever is appropriate.

Fix packs

To access fix packs:

1. You can navigate directly to the Application Engine 3.5.1.x fix packs or manually locate the fix packs by doing one of the following:
• Navigate to the Fix Central page for the Application Engine 3.5.1.x fix packs.
• Manually locate the fix packs by specifying the product group, product, installed version, and platform with the following options:
  • Product Group: Information Management
  • Product: FileNet Application Engine
  • Installed Version: 3.5.1.*
  • Platform: All

  Click Continue and identify the fixes you want to locate or select Browse for fixes.

2. View the list of available fix packs.

Compatibility

• As of P8AE-3.5.1-018, an updated security certificate used to sign FileNet Application Engine .jar and client installer files is included with the installation. The previous certificate signature expires October 30, 2009 and the files need to be resigned. The resigned .jar files provided by this fix pack will be valid from the time of installation until March 16, 2012. It is also required that you update any Process Engine .jar files using the Process Engine interim fix or fix pack that matches the Process Engine version installed on your system.
• As of P8AE-3.5.1-013, Windows Vista Service Pack 1 is supported
• As of P8AE-3.5.1-012, Federal Desktop Core Configuration (FDCC) support on Windows Vista
• As of P8AE-3.5.1-012, support for Microsoft SQL Server 2005
• As of P8AE-3.5.1-011, MS Office 2007 Service Pack 1 is supported
• As of P8AE-3.5.1-011, MS Office 2003 Service Pack 3 is supported
• As of P8AE-3.5.1-011, Federal Desktop Core Configuration (FDCC) support on Windows XP
• As of P8AE-3.5.1-011, Java SE Runtime Environment 6 (1.6.x) for client machines is supported
• As of P8AE-3.5.1-010, WebSphere 6.1.x is supported.
• As of P8AE-3.5.1-009, Firefox 2.0 is certified for Workplace.
• As of P8AE-3.5.1-009, Windows Vista Business edition is supported for Workplace. Please consult the documentation regarding Workplace Addon Product support for Vista.
• As of P8AE-3.5.1-008, Windows 2003 Service Pack 2 is supported.
• As of P8AE-3.5.1-008, Microsoft Office 2007 is supported.
• As of P8AE-3.5.1-007, J2SE Runtime Environment 5.0 Update 9 for client machines is supported. This JRE version is compliant with the new Daylight Savings Time regulations that take effect in March 2007.
• As of P8AE-3.5.1-007, Internet Explorer 7 is certified for Workplace.
• As of P8AE-3.5.1-003, Windows 2003 R2 support is effective for the Application Engine.

For compatibility information, see the:

• IBM FileNet P8 Hardware and Software Requirements Guide
• IBM FileNet P8 Fix Pack Dependency/Compatibility Matrix

Details on features introduced in fix packs (formerly called Hotfix Packs)

• The following feature is available after you install P8AE-3.5.1-011:

  • Enhanced annotation tooltips to display the Create and Date Created are implemented.

• The following feature is available after you install P8AE-3.5.1-009:

  • Two new site preferences, 'Multi-Select download behavior' and 'Multi-Content download behavior' are provided. These allow an administrator to select either:

    1. Zipping up the files (the current default behavior).

    2. Enabling individual downloads for each document or content element.

    This feature also provides UI and related changes required to implement the non-zip option.

• The following features are available after you install P8AE-3.5.1-007:

  • A new Site Preference, "Multiple Files Use Zip" is located under the Mail section of General Site Preferences. This new Site Preference allows an administrator to determine whether or not a zip file should be used when sending multiple files in email.

  • DTS 190463 changes the behavior of application integration. When users select the "My Inbox Tasks" menu item, application integration will now launch a web browser to display the tasks rather than a modal dialog. This change allows users to open attachments on inbox tasks since the underlying application is no longer locked while displaying the inbox tasks dialog.

  • This patch now includes J2SE Runtime Environment 5.0 Update 9 for client machines. This JRE version is compliant with the new Daylight Savings Time regulations that take effect in March 2007.

  • The caching of the Property Description XML files will be changing with DTS 193940. The XML will now be cached at the application level instead of at the session level. In order to improve performance when retrieving large, complex choice lists, the internal P8 metadata relating to Document classes and properties will now be cached in an application cache instead of a session cache. This new application cache needs to be cleared in order to force a refresh from the server. This can be accomplished via a new Site Preference called "Class Description Cache", located in the Refresh section. Clearing this cache will pick up changes to existing class property descriptions and choice lists. The application cache does not need to be refreshed in order to pick up new classes. Note A user must log out and log back in to pick up the new changes.

• The following feature is available after you install P8AE-3.5.1-006:

  • If a user’s Simple Search property criteria settings are set to use the “contains”, “starts with”, or “ends with” operator, Simple Search will expose configurable search operands. The user may now select “contains”, “starts with”, or “ends with” via a drop down control on the Simple Search page.

• The following feature is available after you install P8AE-3.5.1-005:

  • Search templates now support configurable search operands. If the operands “is like” or “is not like” are used when designing the search template, at runtime when the search template is used, the user may select “contains”, “starts with”, or “ends with” via a drop down control.

• The following features are available after you install the P8AE-3.5.1-003:

  • The QuickStart feature provides a mechanism for initializing a Web browser, Java, and Image Viewer session. The background task required to initialize an Image Viewer session is done at the time when the web browser is initialized, prior to the time when the Image Viewer is actually required. This reduces the startup time of the Image Viewer. This feature is supported on various operating systems, such as Microsoft Windows 2000 Professional and XP. It also supports the Internet Explorer and Firefox web browsers. The QuickStart feature is not enabled by default; it must be manually enabled.

    Note In order to avoid having to deploy your system twice, make sure to perform the QuickStart configuration steps after you have applied the fix pack but before you redeploy your system.

  • The ability to limit folders displayed in Workplace is provided with a new site preference, “Maximum number of folders to display”.

  • The restriction in P8 3.5.x to use the Email document class or subclasses when adding email using an entry template via Application Integration has been lifted. Other document classes may now be used.

• The following features are available after you install P8AE-3.5.1-002:

  • File Tracker tracks a document on your local machine after you check it out from an object store.
    The following Known Issue exists with File Tracker (DTS 175464):
    When an Application Engine is configured to use port 80 (or port 443 when using SSL), the Port number that is passed to file tracker code is null. This causes an error when adding a document via Workplace when File Tracking is enabled. (This is fixed in P8AE-3.5.1-003.)

  • Folder content caching may or may not be enabled depending on settings specified by your site administrator.

  • Annotation security has been updated for the Image Viewer.

Known Issues

• Defect ecmdb 866740 Installer fails to install to folder name with non_alphanumeric characters.
• Defect ecmdb 849609 The P8AE-3.5.1-019 fix pack cannot be deployed using the Oracle Application Server (OAS) Enterprise Manager Application Server Control for 10.1.2.0.0 or 10.1.2.0.1 because of an Oracle known issue. This issue is tracked with Oracle bug 7328210. To deploy AE with OAS, either upgrade to at least 10.1.2.0.2 or deploy using the dcmctl utility. In the example below, replace the war file name, application name, context root and component name information for your environment:

  dcmctl deployApplication -f <AE_install_path/Workplace/app_engine.war> -a <Workplace_application_name> -rc /<Context Root> -co <Component Name>

• Defect ecmdb 852883 On a HP-UX 11.11 platform, the /opt/FileNet/_uninst2 and /opt/FileNet/_jvm2HP-UX directories are created after the P8AE-3.5.1 fix pack is installed. These directories should be ignored.

• Defect ecmdb 391301 Users are unable to open an attachment in Firefox 2.0 when launching a workflow with attachments.

  Here is the Mozilla site regarding this issue:

  http://kb.mozillazine.org/Firefox_:_Issues_:_Links_to_Local_Pages_Don't_Work
  Note Some browsers do not handle this link. If it does not work, please copy the URL manually.

New in this fix pack

• This fix pack contains Daeja ViewOne version 3.1.178.

For details about the resolved defects in this fix pack, see "Product fix history".

For more information about Application Engine new features and known issues, see the IBM FileNet P8 Release Notes.

Installation, migration, upgrade, and configuration

Tip It is strongly recommended that all client machines which currently use P8 Office Integration / File Tracker upgrade to the version that corresponds with this fix pack. See the "Upgrade Application Integration and File Tracker" topic in the IBM FileNet P8 Platform Installation and Upgrade Guide for upgrade instructions.

Requirements

• P8eF-3.5.1-011 (with this P8AE-3.5.1-021 fix pack) for eForms to function in SSO environment.

• P8eF-3.5.1-009 or later if you are using eForms.

• You must apply FileNet P8 Application Engine Service Pack 3.5.1 prior to applying this fix pack.

• You will need to run the Process Engine client synch installer on the Application Engine after installing this Application Engine fix pack. The version of the Process Engine client synch installer will depend on the Process Engine fix pack level.

• Changes associated with this Application Engine fix pack were initially tested with and require the 3.5.2 Service Pack versions of the Content Engine and Process Engine. Please check the readmes of any later Service Packs for compatibility with this Application Engine fix pack.

Install this fix pack

• WebLogic Installation Instructions

  • For the initial installation of Application Engine on a WebLogic Application Server

  • For installing the Application Engine on a WebLogic Application Server system with an existing Application Engine installation

• WebSphere Installation Instructions

  • For the initial installation of Application Engine on a WebSphere Application Server

  • For installing the Application Engine on a WebSphere Application Server system with an existing Application Engine installation

  • For configuring the Application Engine on WebSphere 6.1

  • For deploying the Application Engine on WebSphere 6.1

• Tomcat Installation Instructions

  • For the initial installation of Application Engine on a JBoss/Jakarta Tomcat Application Server

  • For installing the Application Engine on a JBoss/Jakarta Tomcat Application Server system with an existing Application Engine installation

• Oracle AppServer Installation Instructions

  • For the initial installation of Application Engine on an Oracle Application Server

  • For installing the Application Engine on an Oracle Server system with an existing Application Engine installation

• Sun Java AppServer Installation Instructions

  • For the initial installation of Application Engine on a Sun Java AppServer Application Server

  • For installing the Application Engine on a Sun Java AppServer Application Server system with an existing Application Engine installation

For the initial installation of Application Engine on a WebLogic Application Server

Note If you plan to install eForms in conjunction with the P8AE-3.5.1-021 fix pack, you must install eForms 3.5.1-004 or later. If eForms was installed on the Application Engine prior to applying AE-3.5.1-006, then you can use any version of eForms 3.5.1.x.

1. Install the FileNet 3.5.1 Application Engine, by running the ‘filenet_app_engine_setup’ executable for your operating system.

2. Go to the "Install the Application Engine" (Task 14) section in the IBM FileNet P8 Platform Installation and Upgrade Guide and follow the instructions for the Application Engine installation.

   Note Do not deploy Workplace until the Application Engine fix pack install has been completed.

3. Once the 3.5.1 installation is complete, go to Task 16 of the Installation Guide where you will find a link to Task 9 of the "Upgrade Core Components" section. Follow the steps in Task 9 to complete the installation of the 3.5.1 Application Engine Service Pack.

4. Once the installation is complete, locate the P8AE-3.5.1-021 executable for your OS, (for example P8AE-3.5.1-021-WIN.exe, P8AE-3.5.1-021-Sol.bin) under P8AE-3.5.1-021.

5. Run the P8AE-3.5.1-021 executable for your operating system.

   1. At the install location panel, the fix pack will recognize your installation directory (or your most recent installation directory if you have collocated more than one instance). Click Next.

   2. At the setup type panel, select the installation type which you used for the initial Application Engine 3.5.1 installation, click Next.

   3. For Custom, you will need to now select the components you had installed during your 3.5.1 installation. Click Next.

   4. At the Application Server panel, select the Application Server type that is currently installed on your system.

   5. A dialog displays reading: “Please read the information below." This box displays all of the files that will be replaced and/or installed. Click Next.

   6. A dialog with various installation information appears. Click Next.

   7. Once setup has installed the Application Engine software, click Finish.

Note You will now need to refer to the 'To configure and start the Application Engine' (WebLogic) (Task 15b) section of the FileNet P8 Platform 3.5.1x Installation Guide (.pdf) to complete your configuration setup.

Note If you plan to install eForms in conjunction with the P8AE-3.5.1-021 fix pack, you must install eForms 3.5.1-004 or later. If eForms was installed on the Application Engine prior to applying AE-3.5.1-006, then you can use any version of eForms 3.5.1.x.

1. Back up the following deployed files:

   • Actions.xml
   • bootstrap.properties
   • primaryviews.xml
   • WcmApiConfig.properties
   • web.xml
   • taskman.login.config

   and/or any files that were customized since the previous installation. The backup of these files is to ensure the files are still available in case there is any reason to go back to the previous versions. When redeploying after installing the fix pack, any custom settings will be added back to the deployed working directory.

   Note If BPF3.6.x or BPF3.5.2.x is installed on this environment, perform a backup of the following files:

   • content_redir.properties
   • Integration.xml
   • InfoPages.xml

   After redeploying Application Engine, add BPF information to the new installation in the Workplace deployed folder.

2. Bring up the Process Task Manager application if not already running. Stop the Process Router and the Component Manager (if running) and then exit the Process Task Manager application.

3. Stop the Process Application Engine Services Manager in the Windows Service.

4. In the WebLogic Admin console, under Web Applications or Web Application Modules, do the following:

   1. Stop or Undeploy Workplace.

   2. Remove the target server for Workplace, click apply.

   3. Delete Workplace from the Web Applications list.

5. Shut down the WebLogic Server.

6. Delete the Workplace temp directory. The default location is:

   <WebLogic_Home>\domains\<AE_domain>\servers\<AE_server>\tmp\_WL_user\Workplace

7. Run the P8AE-3.5.1-021 executable for your operating system (for example P8AE-3.5.1-021-WIN.exe, P8AE-3.5.1-021-Sol.bin).

   1. At the installation location panel, the fix pack will recognize your installation directory. click Next.

   2. At the setup type panel, select the installation type which you used for the initial Application Engine 3.5.1 installation, click Next.

   3. For Custom, you will need to now select the components you had installed during your 3.5.1 installation. Click Next.

   4. At the Application Server panel, select the Application Server type that is currently installed on your system.

   5. A dialog displays reading: “Please read the information below." This box displays all of the files that will be replaced and/or installed. Click Next.

   6. A dialog with various installation information appears. Click Next.

   7. Once setup has installed the Application Engine software, click Finish.

8. If you have manually modified or made custom changes to any of the files listed in Step 1, and they were not retained during the fix pack installation, and would like to retain those settings, copy the custom entries from the backed up version of the files to the newly installed files in the WEB-INF directory on your server. Make sure to complete this before starting WebLogic and redeploying Workplace.

9. You will now need to refer to the To configure and start the Application Engine (WebLogic) (Task 15b) section of the IBM FileNet P8 3.5.1 Application Engine Installation Guide (.pdf) to complete your configuration setup.

10. Restart the Application server and make sure any routers or Component Manager services that were previously stopped are now restarted.

11. Bring up the Process Task Manager application if not already running. Start the Process Router and the Component Manager. Verify the Process Application Engine Services Manager in the Windows Service started.

    Warning Rebooting the P8 system or restarting the P8 services without applying the required P8 patches on all machines may cause the system to become out of synch with the other P8 machines. Having an unsynchronized P8 environment may cause problems because P8 processes may automatically restart before the complete P8 environment has been patched.

For the initial installation of Application Engine on a WebSphere Application Server

Note If you plan to install eForms in conjunction with the P8AE-3.5.1-021 fix pack, you must install eForms 3.5.1-004 or later. If eForms was installed on the Application Engine prior to applying AE-3.5.1-006, then you can use any version of eForms 3.5.1.x.

1. Install the FileNet 3.5.1 Application Engine, by running the ‘filenet_app_engine_setup’ for your operating system.

2. Go to the "Install the Application Engine" (Task 14) section in the IBM FileNet P8 Platform Installation and Upgrade Guide and follow the instructions for the Application Engine installation.

   Note Do not deploy Workplace until the Application Engine fix pack installation has been completed.

3. Once the 3.5.1 installation is complete, go to Task 16 of the Installation Guide where you will find a link to Task 9 of the "Upgrade Core Components" section. Follow the steps in Task 9 to complete the installation of the 3.5.1 Application Engine Service Pack.

4. Once the installation is complete, locate the P8AE-3.5.1-021 executable for your OS (for example P8AE-3.5.1-021-WIN.exe, P8AE-3.5.1-021-Sol.bin) under P8AE-3.5.1-021.

5. Run the ‘P8AE-3.5.1-021' executable for your OS (for example P8AE-3.5.1-021-WIN.exe, P8AE-3.5.1-021-Sol.bin)

   1. At the installation location panel, the fix pack will recognize your installation directory (or your most recent installation directory if you have collocated more than one instance). Click Next.

   2. At the setup type panel, select the installation type which you used for the initial Application Engine 3.5.1 installation, click Next.

   3. For Custom, you will need to now select the components you had installed during your 3.5.1 installation. Click Next.

   4. At the Application Server panel, select the Application Server type that is currently installed on your system.

   5. A dialog displays reading: “Please read the information below." This box displays all of the files that will be replaced and/or installed. Click Next.

   6. A dialog with various installation information appears. Click Next.

   7. Once setup has installed the Application Engine software, click Finish.

Notes

• You will now need to refer to the 'To configure and start the Application Engine (WebSphere) (Task 15a) section of the IBM FileNet P8 Platform 3.5.1x Installation Guide (.pdf) to complete your configuration setup.

• If eForms is installed on your system, or if you are using Process Simulator or Process Orchestration, you will need to delete the deployed commons-logging.jar file.
  Example: \WebSphere\AppServer\profiles\AppSrv01\installedApps\<node>\app_engine_war.ear\app_engine.war\WEB-INF\lib\commons-logging.jar

For configuring the Application Engine on WebSphere 6.1

1. Open the WebSphere Administrative Console.

2. Set JVM settings for JAAS login configuration, memory settings, and UTF-8 encoding.

   1. Expand Servers.

   2. Click Application Servers.

   3. Click <server name>.

   4. Under “Server Infrastructure”, expand Java and Process Management.

   5. Select Process Definition > Additional Properties > Java Virtual Machine.

   6. Set the Initial and Maximum Heap Size.

      Refer to your application server vendor's recommendation for Initial and Maximum heap size values. For FileNet specific recommendations, see the FileNet P8 Platform Performance Tuning Guide on the IBM Customer Service and Support web site for FileNet customers (http:// www.css.filenet.com).

   7. Click Apply.

   8. Click Custom Properties.

   9. Click New.

   10. Verify that the Name field is set to:

       client.encoding.override

   11. Verify that the Value field is set to:

       UTF-8

   12. Click Apply, click Save, and then click Save Changes to the Master Configuration.

3. Verify Application Integration.

   1. From the Administrative Console, expand Environment. Click Virtual Hosts.

   2. Click the default_host (or the host your application is deployed under).

   3. Click MIME Types.

   4. Verify that MIME type is set to application/octet-stream or use the following steps to set it.

      1. Click New.

      2. In the MIME Type field, enter application/octet-stream.

      3. In the Extension(s) field, enter exe. Click OK.

      4. Click Apply, click Save, and then Save changes to the Master Configuration.

      5. Save these settings.

4. Set permissions for the user running the application server. The user that will be running the application server must have read/write permissions on the following (default) folders:

   <WAS_HOME>/profiles/AppSrv01/installedApps/<node_name>/app_engine.ear/ app_engine.war
   <AE_install_path>

For deploying the Application Engine on WebSphere 6.1

1. Start the application server.

2. Log on to the WebSphere administrative console.

3. From the WebSphere Administrative Console, expand Applications. Click Install New Application. The “Preparing for the application installation” dialog opens.

4. Select file to deploy.

   1. Select Path.

      • (If the Administrative Console is running locally) Select Local Path and enter or browse to the location of the app_engine.war file created by Setup (see below for the default path). Do not enter the machine name.

      • (If the Administrative Console is remote) Select Server path and enter the fully-qualified path name to the app_engine.war file. Do not enter the machine name. <AE_install_path>/Workplace

   2. Enter the context root:

      Enter Workplace and click Next to proceed to deploying a new application.

      Note The context root is the name of the application you log in to using the web interface, such as:
      http://<ApplicationEngineServerName>:<port#>/<Context Root>.

5. Click Next.

6. At “Install New Application”, Step 1, specify the application name. Enter Workplace, or the name you chose to call the application, click Next.

7. At “Install New Application", Step 2, Map modules to servers, specify the web server you are planning to use. Check Workplace and click Apply. Verify that the web server you specify is displayed to the right of Workplace. Click Next.
8. At “Install New Application”, Step 3, Map virtual hosts for Web Modules, check Workplace and keep the default virtual host (default_host), click Next.

9. At “Install New Application”, Step 4, verify your configuration and click Finish. Once the configuration is saved, click Save.
10. Configure the Classloader settings.
    1. From the Administrative Console, expand Applications. Click Enterprise Applications, and click your application (default Workplace).
    2. From the Configuration tab, click Class loading and update detection.
    3. Change Classloader order from "Classes loaded with parent class loader first" to "Classes loaded with application class loader first."
       
       NOTE Do this only for the specific web application. Do not change the similar settings for the entire application server.
    4. Change the polling interval to a number appropriate for your environment.
    5. Click Apply.
11. Configure the Web Module Classloader setting.
    1. From the Administrative Console, expand Applications.
    2. Click Enterprise Applications, and click your application (default Workplace).
    3. Under Modules, click Manage Modules. Click Workplace, or your application name.
    4. Change Classloader order from "Classes loaded with parent class loader first" to "Classes loaded with application class loader first."
       
       Note Do this only for the specific web application. There are similar settings for the entire application server. Do not change these.

    5. Click Apply, click Save, and then click Save changes to the Master Configuration.
12. Stop and restart the application server.
13. Verify the Enterprise Application is started. You can do this by signing in to Workplace.
    1. From the Administrative Console, expand Applications.
    2. Click Enterprise Application.
    3. View the "Application status" for Workplace. If the application is started, a green arrow displays in the Application Status window. If it is not running, check the box to the left of the Workplace application (or whatever you named it), and click Start.

For installing the Application Engine on a WebSphere Application Server system with an existing Application Engine installation

Note If you plan to install eForms in conjunction with the P8AE-3.5.1-021 fix pack, you must install eForms 3.5.1-004 or later. If eForms was installed on the Application Engine prior to applying AE-3.5.1-006, then you can use any version of eForms 3.5.1.x.

1. Back up and copying the following deployed files:

   • Actions.xml
   • bootstrap.properties
   • primaryviews.xml
   • WcmApiConfig.properties
   • web.xml
   • taskman.login.config

   and/or any files that were customized since the previous installation, to the install location. When Workplace is un-deployed, the entire working Workplace directory is deleted from the system. The backup of these files is to ensure the files are still available in case there is any reason to go back to the previous versions. When redeploying after installing the fix pack, any custom settings will be added back to the deployed working directory.

   Note If BPF3.6.x or BPF3.5.2.x is installed on this environment, perform a backup of the following files:

   • content_redir.properties

   • Integration.xml

   • InfoPages.xml

   After redeploying Application Engine, add BPF information to the new installation in the Workplace deployed folder.

2. Stop the Process Router and the Component Manager (if running) and then exit the Process Task Manager application.

3. Stop the Process Application Engine Services Manager in the Windows Service.

4. Open the WebSphere Administrative Console. Under “Applications>Enterprise Applications”, stop and uninstall your instance of Workplace (the default name is app_engine_war). Save your Enterprise settings after removing Workplace and stop WebSphere.

5. Delete the Workplace temp directory. The default location is, depending on which version of WebSphere you are on:

   • WebSphere 5.1.x
     c:\<Installation_Directory>\WebSphere\AppServer\profiles\default\temp\Node_Name\<server>\<Workplace_application_name>

   • WebSphere 6.0.x
     c:\<Installation_Directory>\IBM\WebSphere\AppServer\profiles\default\temp\Node_Name\<server>\<Workplace_application_name>

   • WebSphere 6.1.x
     c:\<Installation_Directory>\IBM\WebSphere\AppServer\profiles\AppSrv01\temp\Node_Name\<server>\<Workplace_application_name>

6. Run the ‘P8AE-3.5.1-021' executable for your OS (for example P8AE-3.5.1-021-WIN.exe, P8AE-3.5.1-021-Sol.bin). Note The war file will be overwritten during the installation if you have not customized the name. If you would like to keep a copy of the previous version, copy the existing app_engine.war file to a different location.
   1. At the installation location panel, the fix pack will recognize your installation directory (or your most recent installation directory if you have collocated more than one instance). Click Next.
   2. At the setup type panel, select the installation type which you used for the initial Application Engine 3.5.1 installation, click Next.
   3. For Custom, you will need to now select the components you had installed during your 3.5.1 installation. Click Next.
   4. At the Application Server panel, select the Application Server type that is currently installed on your system.
   5. A dialog displays reading: “Please read the information below." This box displays all of the files that will be replaced and/or installed. Click Next.
   6. A dialog with various installation information appears. Click Next.
   7. Once setup has installed the Application Engine software, click Finish.
7. You will now need to refer to the To configure and start the Application Engine (WebSphere) (Task 15a) section of the FileNet P8 3.5.1 Application Engine Installation Guide (.pdf) to complete your configuration setup.

   Note If you have upgraded from FileNet fix pack P8AE 3.5.1-002 to fix pack P8AE 3.5.1-021, you will need to delete the "commons-logging.jar” file from the Workplace deployed WEB-INF/lib directory.

   Example of the path:

   \user\IBM\WebSphere\AppServer\profiles\default\installedApps\<server>\Instance Name.ear\app_engine.war\WEB-INF\lib\

   The path for your system will vary depending on how your system has been configured.

   Restart the WebSphere Server service after deleting the “commons-logging.jar” file from the deployed location.

   If the Workplace application is redeployed after the file is deleted, it will be necessary to delete the file again and restart the WebSphere service.

8. If you have manually modified or made custom changes to any of the files listed in Step 1, and they were not retained during the fix pack installation, and would like to retain those settings, copy the custom entries from the backed up version of the files to the newly installed files in the WEB-INF directory on your server and re-create war file for Workplace. Make sure to complete this before starting WebSphere and redeploying Workplace.

   If you would like to restore your custom settings, you will need to restore them to the deployed location, which, by default would be:

   • For WebSphere 5.1.x: <Install_Location>\WebSphere\AppServer\\installedApps\Node_Name\server1\Workplace\app_engine.war

   • For WebSphere 6.0.x: <Install_Location>\IBM\WebSphere\AppServer\profiles\default\installedApps\Node_Name\Instance Name.ear\app_engine.war

   • For WebSphere 6.1.x: <Install_Location>\IBM\WebSphere\AppServer\profiles\AppSrv01\installedApps\Node_Name\Instance Name.ear\app_engine.war

   Notes

   • If eForms was installed on your system, or if you are using Process Simulator or Process Orchestration, you will need to delete the deployed commons-logging.jar file.
     Example: \WebSphere\AppServer\installedApps\<node>\Instance Name.ear\app_engine.war\WEB-INF\lib\commons-logging.jar

     Warning The commons-logging.jar file in the 'Installation' folder should not be deleted.

9. Restart the Application server and make sure any routers or Component Manager services that were previously stopped are now restarted.
10. Bring up the Process Task Manager application if not already running. Start the Process Router and the Component Manager. Verify the Process Application Engine Services Manager in the Windows Service started.

    Warning Rebooting the P8 system or restarting the P8 services without applying the required P8 patches on all machines may cause the system to become out of synch with the other P8 machines. Having an unsynchronized P8 environment may cause problems because P8 processes may automatically restart before the complete P8 environment has been patched.

For the initial installation of Application Engine on a JBoss/Jakarta Tomcat Application Server

Note If you plan to install eForms in conjunction with the P8AE-3.5.1-021 fix pack, you must install eForms 3.5.1-004 or later. If eForms was installed on the Application Engine prior to applying AE-3.5.1-006, then you can use any version of eForms 3.5.1.x.

1. Install the FileNet 3.5.1 Application Engine, by running the ‘filenet_app_engine_setup’ for your operating system.

2. Go to the "Install the Application Engine" (Task 14) section in the IBM FileNet P8 Platform Installation and Upgrade Guide and follow the instructions for the Application Engine installation.

   Note Do not deploy Workplace until the Application Engine fix pack install has been completed.

3. Once the 3.5.1 installation is complete, go to Task 16 of the IBM FileNet P8 Platform Installation and Upgrade Guide where you will find a link to Task 9 of the "Upgrade Core Components" section. Follow the steps in Task 9 to complete the installation of the 3.5.1 Application Engine Service Pack.

4. Once the installation is complete, locate the P8AE-3.5.1-021 executable for your operating system.

5. Run the ‘P8AE-3.5.1-021' executable for your OS (for example P8AE-3.5.1-021-WIN.exe, P8AE-3.5.1-021-Sol.bin).

   1. At the installation location panel, the fix pack will recognize your installation directory (or your most recent installation directory if you have collocated more than one instance). Click Next.

   2. At the setup type panel, select the installation type which you used for the initial Application Engine 3.5.1 installation, click Next.

   3. For Custom, you will need to now select the components you had installed during your 3.5.1 installation. Click Next.

   4. At the Application Server panel, select the Application Server type that is currently installed on your system.

   5. A dialog displays reading: “Please read the information below." This box displays all of the files that will be replaced and/or installed. Click Next.

   6. A dialog with various installation information appears. Click Next.

   7. Once setup has installed the Application Engine software, click Finish.

Note You will now need to refer to the 'To configure and start the Application Engine' (JBoss/Tomcat) (Task 15c) section of the FileNet P8 3.5.1 Application Engine Installation Guide (.pdf) to complete your configuration setup.

For installing the Application Engine on a JBoss/Jakarta Tomcat Application Server system with an existing Application Engine installation

Note If you plan to install eForms in conjunction with the P8AE-3.5.1-021 fix pack, you must install eForms 3.5.1-004 or later. If eForms was installed on the Application Engine prior to applying AE-3.5.1-006, then you can use any version of eForms 3.5.1.x.

1. Back up and copying the following deployed files:

   • Actions.xml
   • bootstrap.properties
   • primaryviews.xml
   • WcmApiConfig.properties
   • web.xml
   • taskman.login.config

   and/or any files that were customized since the previous installation, to the install location. When Workplace is un-deployed, the entire working Workplace directory is deleted from the system. The backup of these files is to ensure the files are still available in case there is any reason to go back to the previous versions. When redeploying after installing the fix pack, any custom settings will be added back to the deployed working directory.

   Note If BPF3.6.x or BPF3.5.2.x is installed on this environment, perform a backup of the following files:

   • content_redir.properties
   • Integration.xml
   • InfoPages.xml

   After redeploying Application Engine, add BPF information to the new installation in the Workplace deployed folder.

2. Stop the Process Router and the Component Manager (if running) and then exit the Process Task Manager application. Stop the Process Application Engine Services Manager in the Windows Service.

3. Stop JBoss/Tomcat.

4. Move or Delete the deployed Workplace directory:

   For JBoss: <JBoss_HOME>\server\default\deploy\Workplace.war

   For Tomcat: <Tomcat_HOME>\webapps\Workplace

5. Delete the temporary Workplace directory:

   For JBoss, depending on which level of JBoss you are on:

   • JBoss 3.2.x <JBoss_HOME>\server\default\work\MainEngine\localhost\Workplace

   • JBoss 4.0.x <JBoss_HOME>\server\default\work\jboss.web\localhost\Workplace

   For Tomcat: <Tomcat_HOME>\work\Catalina\localhost\Workplace

6. Copy any files you backed up in Step 1 to the FileNet installation directory (overwriting the existing files in that location. You can rename and backup these files first if you prefer). These files will be updated during the patch installation process.

7. Run the ‘P8AE-3.5.1-021' executable for your OS (for example P8AE-3.5.1-021-WIN.exe, P8AE-3.5.1-021-Sol.bin).

   1. At the installation location panel, the fix pack will recognize your installation directory. Click Next.

   2. At the setup type panel, select the installation type which you used for the initial Application Engine 3.5.1 installation, click Next.

   3. For Custom, you will need to now select the components you had installed during your 3.5.1 installation. Click Next.

   4. At the Application Server panel, select the Application Server type that is currently installed on your system.

   5. A dialog displays reading: “Please read the information below." This box displays all of the files that will be replaced and/or installed. Click Next.

   6. A dialog with various installation information appears. Click Next.

   7. Once setup has installed the Application Engine software, click Finish.

8. If you have manually modified or made custom changes to any of the files listed in Step 1, and they were not retained during the fix pack installation, and would like to retain those settings, copy the custom entries from the backed up version of the files to the newly installed files in the WEB-INF directory on your server. Make sure to complete this before starting JBoss/Tomcat and redeploying Workplace.
9. You will now need to refer to the To configure and start the Application Engine (JBoss/Tomcat) (Task 15c) section of the FileNet P8 3.5.1 Application Engine Installation Guide (.pdf) to complete your configuration setup.
10. Restart the Application server and make sure any routers or Component Manager services that were previously stopped are now restarted.
11. Open Process Task Manager application if not already running. Start the Process Router and the Component Manager. Verify the Process Application Engine Services Manager in the Windows Service started.

    Warning Rebooting the P8 system or restarting the P8 services without applying the required P8 patches on all machines may cause the system to become out of synch with the other P8 machines. Having an unsynchronized P8 environment may cause problems because P8 processes may automatically restart before the complete P8 environment has been patched.

For the initial installation of Application Engine on an Oracle Application Server

Note If you plan to install eForms in conjunction with the P8AE-3.5.1-021 fix pack, you must install eForms 3.5.1-004 or later. If eForms was installed on the Application Engine prior to applying AE-3.5.1-006, then you can use any version of eForms 3.5.1.x.

1. Install the FileNet 3.5.1 Application Engine, by running the ‘filenet_app_engine_setup’ for your operating system.

2. Go to the "Install the Application Engine" (Task 14) section in the IBM FileNet P8 Platform Installation and Upgrade Guide and follow the instructions for the Application Engine installation.

   Note Do not deploy Workplace until the Application Engine fix pack install has been completed.

3. Once the 3.5.1 installation is complete, go to Task 16 of the Installation Guide where you will find a link to Task 9 of the "Upgrade Core Components" section. Follow the steps in Task 9 to complete the installation of the 3.5.1 Application Engine Service Pack.

4. Once the installation is complete, locate the P8AE-3.5.1-021 executable (for your OS, e.g. WIN.exe, Sol.bin).

5. Run the P8AE-3.5.1-021 executable for your operating system (e.g. WIN.exe, Sol.bin)

   1. At the install location panel, the fix pack will recognize your installation directory (or your most recent installation directory if you have collocated more than one instance). Click Next.

   2. At the setup type panel, select the installation type which you used for the initial Application Engine 3.5.1 installation, click Next.

      For Custom, you will need to now select the components you had installed during your 3.5.1 installation. Click Next.

   3. Once setup has installed the Application Engine software, click Finish.

   4. At the Application Server panel, select the Application Server type that is currently installed on your system.

   5. A dialog displays reading: “Please read the information below." This box displays all of the files that will be replaced and/or installed. Click Next.

   6. A dialog with various installation information appears. Click Next.

   7. Once setup has installed the Application Engine software, click Finish.

      Note You will now need to refer to the To configure and start the Application Engine (Oracle Application Server) (Task 15d) section of the FileNet P8 Platform 3.5.1x Installation Guide (.pdf) to complete your configuration setup.

For installing the Application Engine on an Oracle Application Server system with an existing Application Engine installation

Note If you plan to install eForms in conjunction with the P8AE-3.5.1-021 fix pack, you must install eForms 3.5.1-004 or later. If eForms was installed on the Application Engine prior to applying AE-3.5.1-006, then you can use any version of eForms 3.5.1.x.

1. Undeploy Workplace

   1. In the Admin Console select the Applications tabs and undeploy Workplace.

   2. Stop the Oracle App Server.

2. Run the P8AE-3.5.1-021 executable for your operating system (e.g. WIN.exe, Sol.bin). Note The war file will be overwritten during the installation if you have not customized the name. If you would like to keep a copy of the previous version, copy the existing app_engine.war file to a different location.
   1. At the installation location panel, the fix pack will recognize your installation directory (or your most recent installation directory if you have collocated more than one instance). Click Next.
   2. At the setup type panel, select the installation type which you used for the initial Application Engine 3.5.1 installation, click Next.
   3. For Custom, you will need to now select the components you had installed during your 3.5.1 installation. Click Next.

   4. At the Application Server panel, select the Application Server type that is currently installed on your system.

   5. A dialog displays reading: “Please read the information below." This box displays all of the files that will be replaced and/or installed. Click Next.

   6. A dialog with various installation information appears. Click Next.

   7. Once setup has installed the Application Engine software, click Finish.

3. You will now need to refer to the To configure and start the Application Engine (Oracle Application Server) (Task 15d) section of the IBM FileNet P8 Application Engine Installation Guide (.pdf) to complete your configuration setup.
4. Restart the Oracle App Server.
5. After redeploying, make sure to complete the 'Edit Classloader values in orion-web.xml' step (which is part of the IBM FileNet P8 Application Engine Installation Guide, task 15d).

For the initial installation of Application Engine on a Sun Java AppServer Application Server

Notes

• Users of Sun Java Application Server 8.1 need to apply FileNet Software Patch P8AE-3.5.1-006.001 prior to redeploying Workplace on the application server.
• If you plan to install eForms in conjunction with the P8AE-3.5.1-021 fix pack, you must install eForms 3.5.1-004 or later. If eForms was installed on the Application Engine prior to applying AE-3.5.1-006, then you can use any version of eForms 3.5.1.x
  .

1. Install the FileNet 3.5.1 Application Engine, by running the ‘filenet_app_engine_setup' for your operating system.

2. Go to the "Install the Application Engine" (Task 14) section in the P8 3.5.1 Installation Guide and follow the instructions for the Application Engine installation.

   Note Do not deploy Workplace until the Application Engine fix pack install has been completed.

3. Once the 3.5.1 installation is complete, go to Task 16 of the Installation Guide where you will find a link to Task 9 of the "Upgrade Core Components" section. Follow the steps in Task 9 to complete the installation of the 3.5.1 Application Engine Service Pack.

4. Once the installation is complete, locate the P8AE-3.5.1-021 executable for your operating system (e.g. WIN.exe, Sol.bin).

5. Run the ‘P8AE-3.5.1-021-Sol.bin' executable.

   1. At the install location panel, the fix pack will recognize your installation directory (or your most recent installation directory if you have collocated more than one instance). Click Next.

   2. At the setup type panel, select the installation type which you used for the initial Application Engine 3.5.1 installation, click Next.

   3. For Custom, you will need to now select the components you had installed during your 3.5.1 installation. Click Next.

   4. At the Application Server panel, select the Application Server type that is currently installed on your system.

   5. A dialog displays reading: “Please read the information below." This box displays all of the files that will be replaced and/or installed. Click Next.

   6. A dialog with various installation information appears. Click Next.

   7. Once setup has installed the Application Engine software, click Finish.

Note You will now need to refer to the 'To configure and start the Application Engine' (Sun Java Application Server) (Task 15e) section of the FileNet P8 Platform 3.5.1x Installation Guide (.pdf) to complete your configuration setup.

CAUTION The jar files were copied from AE-3.5.1-006.001 to the <Sun_JAVA_AS_home>/lib/endorsed location. Do not perform step 5 in Task 15e.

For installing the Application Engine on a Sun Java AppServer Application Server system with an existing Application Engine installation

Notes

• Users of Sun Java Application Server 8.1 need to apply FileNet Software Patch P8AE-3.5.1-006.001 prior to redeploying Workplace on the application server.

• If you plan to install eForms in conjunction with the P8AE-3.5.1-021 fix pack, you must install eForms 3.5.1-004 or later. If eForms was installed on the Application Engine prior to applying AE-3.5.1-006, then you can use any version of eForms 3.5.1.x.

1. Install the FileNet 3.5.1 Application Engine, by running the ‘filenet_app_engine_setup' for your operating system.

   1. Undeploy Workplace

      1. In the Admin Console select the Applications tabs and undeploy Workplace.

      2. Stop the Sun Java AppServer.

   2. Run the ‘P8AE-3.5.1-021-Sol.bin'. Note The war file will be overwritten during the installation if you have not customized the name. If you would like to keep a copy of the previous version, copy the existing app_engine.war file to a different location.
      1. At the installation location panel, the fix pack will recognize your installation directory (or your most recent installation directory if you have collocated more than one instance). Click Next.
      2. At the setup type panel, select the installation type which you used for the initial Application Engine 3.5.1 installation, click Next.
      3. For Custom, you will need to now select the components you had installed during your 3.5.1 installation. Click Next.
      4. At the Application Server panel, select the Application Server type that is currently installed on your system.
      5. A dialog displays reading: “Please read the information below." This box displays all of the files that will be replaced and/or installed. Click Next.
      6. A dialog with various installation information appears. Click Next.
      7. Once setup has installed the Application Engine software, click Finish.
   3. You will now need to refer to the To configure and start the Application Engine (Sun Java Application Server) (Task 15e) section of the FileNet P8 3.5.1 Application Engine Installation Guide (.pdf) to complete your configuration setup.

      CAUTION The jar files were copied from AE-3.5.1-006.001 to the <Sun_JAVA_AS_home>/lib/endorsed location. Do not perform step 5 in Task 15e.

   4. Restart the Sun Java AppServer.
   5. After redeploying, make sure to complete the following steps (these steps are included as part of the IBM FileNet P8 3.5.1 Application Engine Installation Guide, task 15e):
   6. 'Edit Classloader values in sun-web.xml'
   7. If eForms is installed, make sure that the fix for opening Form Policy (DTS 162369) has been applied: Removing xalan.jar and xercesImpl.jar from the deployed WEB-INF/lib directory.

Uninstall this fix pack

Once this fix pack is installed, the process cannot be reversed.

Product fix history

The table below lists the fixes and features in this fix pack. The following abbreviations are used:

• AE Application Engine
• AppInt Application Integration
• CE Content Engine
• DTS # Defect Tracking System Number
• Enh Enhancement
• ET Entry Template
• ImVrvInt Image Services Integration
• IV Image Viewer
• PA Process Analyzer
• PE Process Engine
• PS Process Simulator
• RM Records Manager
• TCM Team Collaboration Manager
• WCM Web Content Manager
• WF Workflow
• WP Workplace

3.5.1-021

3.5.1-020

3.5.1-019

3.5.1-018

3.5.1-017

P8-3.5.1-016

3.5.1-015

3.5.1-014

3.5.1-013

3.5.1-012

3.5.1-011

3.5.1-010

3.5.1-009

3.5.1-008

3.5.1-007

3.5.1-006

3.5.1-005

3.5.1-004

3.5.1-003

3.5.1-002

3.5.1-001

Contact Customer Support

For information about contacting customer support:

1. Navigate to the Information Management support page (www.ibm.com/software/data/support).
2. On the Information Management Support page, search for: How to get support for IBM FileNet products.

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY  10504-1785
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation
J46A/G4
555 Bailey Avenue
San Jose, CA  95141-1003
U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.

Trademarks

• IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

• Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

• Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

• UNIX is a registered trademark of The Open Group in the United States and other countries.

• Other company, product, or service names might be trademarks or service marks of others.