FileNet Business Process Framework (BPF) Fix Pack Readme: BPF-4.1.0-004
©Copyright IBM Corporation 2009. All Rights Reserved.

About this fix pack

New in this fix pack

New in BPF-4.1.0-002

New in BPF-4.1.0-001

Compatibility

Installation, migration, upgrade, and configuration

Requirements

Certifications

New and changed BPF Web application files

Installing this fix pack

Uninstalling this fix pack

Product fix history

Contacting IBM support

Accessing IBM FileNet documentation, compatibility matrices, and fix packs

Notices

Trademarks

About this fix pack

The IBM® FileNet® Business Process Framework BPF-4.1.0-004 fix pack includes updates to BPF Explorer, BPF operations, and BPF Web application.

The fix pack is intended for installation on an existing BPF-4.1.0 GA, BPF-4.1.0-001, BPF-4.1.0-002 or BPF-4.1.0-003 system that is running in a FileNet P8 4.0.x or 4.5.x environment. If you have not yet installed Business Process Framework, you must install the BPF-4.1.0 GA software before installing this fix pack. For instructions, see the IBM FileNet Business Process Framework Installation and Upgrade Guide.

New in this fix pack

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

Introduced in BPF-4.1.0-002

This fix pack introduces the following new features:

• "Hide Inbaskets when opening Case" option restored
• New settings for Dialog windows in BPF Explorer
• Add Workplace Command 3010, ShowProperties, into the Attachment context menu in BPF
• Multilingual resources added into this fix pack

"Hide Inbaskets when opening Case" option restored

This fix pack restores the BPF 3.5.2 Preferences option "Hide Inbaskets when opening Case" in the BPF Web application.

A BPF user can enable this option only in the default layout - that is, if the BPF user's role has not been assigned a different layout using the BPF Layout Designer.

If the "Hide Inbaskets when opening Case" option is enabled, the BPF Web application behaves as follows when a user opens a case either automatically in GetNext/Sequential mode or by double-clicking a case record in Browse mode:

• The Logo, Filters and Inbaskets List Web modules, which typically appear on the left side of the Web page, are hidden.
• The Case detail area is expanded to occupy the entire Web page.
• An Inbaskets drop down list, which contains all available Inbaskets, is displayed after the Roles drop down list in the Status bar. The user can change to another Inbasket by selecting the Inbasket from this list.

When the user closes the case and returns to the Cases list, the Logo, Filters and Inbaskets List modules reappear and the Inbaskets drop down list is hidden.

New settings for Dialog windows in BPF Explorer

• Action Dialog Window Dimensions in px (Default 350*550)

  This setting configures the height and width dimensions of  the Action Dialog window that appears when a user of the BPF web application selects an Action on which one or more Reasons have been configured.

• Whether Action Dialog Window can be resizable (Default: False)

  If set to True, Action Dialog Window can be resized. Otherwise, Action Dialog Window cannot be resized.

• Whether Action Dialog Window can be scrollable (Default: True)

   If set to True, a scroll bar is displayed in the Action Dialog window if the window cannot display all of the Reasons and buttons. If set to False, no scrollbar is displayed in the Action Dialog window.

Add Workplace Command 3010, ShowProperties, into the Attachment context menu in BPF

This fix pack adds the ShowProperties (Workplace Command 3010) action into the Attachment context menu. By selecting this action,  users can review the properties of attachments.

Multilingual resources added into this fix pack

Starting with this fix pack, multilingual resources are added to the BPF fix pack instead of being being provided in separate language packs. The fix pack includes the following locales: de, es, fi, fr, it, ja, ko, pt-BR, zh-CN, and zh-TW.

BPF language resources are contained in the following files:

• <bpf-app>\WEB-INF\lib\bpfLangResources.jar
• <bpf-app>\WEB-INF\lib\bpfCustomLangResources.jar.

Localized Content Engine manifest XML files are located in the Translation folder of the fix pack. You can import the files of languages that you need into Content Engine by using Enterprise Manager.

New in BPF-4.1.0-001

This fix pack introduces the following new features:

• Support multiple Case tabs in BPF Web application
• Enhancements to the display order of an Inbasket which belongs to multiple roles
• "Display Inbasket tools in CASEQUERY Inbasket" option restored
• Enhancements to custom JavaScript™ EventHandlers

Support multiple Case tabs in the BPF Web application

This fix pack adds support for allowing multiple Case tabs in the BPF Web application.

It is now possible to configure multiple Case tabs and spread your inbasket case fields among them. Nevertheless, some configuration and custom coding (in the EventHandlers.js::onCaseDisplay method) is required. Refer to the IBM FileNet Business Process Framework Developer Guide for more information.

Enhancements to the display order of an Inbasket which belongs to multiple roles

Beginning with 3.6, BPF introduced a feature that allows users to assign multiple roles to a single inbasket. However, if you adjusted the display order of inbaskets for one role, the display order for other roles sharing the inbasket role were also changed.

This fix pack enhances the support for inbaskets that are shared by multiple roles by enabling you to set the inbasket display order for each role without affecting the display order for other roles.

"Display Inbasket tools in CASEQUERY Inbasket" option restored

This fix pack restores the BPF 3.5.2 behavior that the Inbasket Toolbar displays when opening a Case in the CASEQUERY Inbasket from the Search Results.

In addition, a new CASEQUERY Inbasket layout template file, Bp8CaseQueryLayout_TwoLines.xml, is provided to address the problem that caused the Toolbar to overlap the Case area if there were too many tools to be displayed on one line. Refer to Install new and changed files for information on using this file.

This change resulted from fixes to resolve defect 750011.

Enhancements to custom JavaScript EventHandlers

This fix pack introduces a new event, onBeforeDoLookupSearch, and enhances the event, onBeforeProcessLookupItem, by providing one more parameter, valueList, which is the handle to an XML DOM Node list object containing the values for whatever record.  These two events are related to custom Lookups. 

The onBeforeDoLookupSearch event is raised before a custom lookup URL is called. This allows the case field values passed to the custom lookup URL to be validated and/or formatted in a custom fashion to handle differences between the DATE or MONEY format in use on the BPF client, for example, and those expected by the lookup JSP or other resource.

For more information, please refer to the BPF Developer Guide and the code samples. You can find them on the Information Management support page (www.ibm.com/software/data/support). Select FileNet Business Process Manager from the "Select a category" list. Click Documentation under FileNet Business Process Manager Support, click Business Process Framework under Product documentation, and then click the links of FileNet Business Process Framework (BPF) Developer Guide and FileNet Business Process Framework (BPF) Developer Guide Code Samples for v4.1.

This enhancement resulted from fixes to resolve PJ34522.

Compatibility

For information, see the IBM FileNet P8 Hardware and Software Requirements and the FileNet P8 4.5.x Fix Pack Compatibility Matrix or FileNet P8 4.0.x Dependency/Compatibility Matrix.

Installation, migration, upgrade, and configuration

Requirements

The BPF-4.1.0-004 fix pack supports FileNet P8 4.5.x and P8 4.0.x. At a minimum, the following components must be installed before you install this fix pack:

• P8CE-4.0.1 or later
• P8PE-4.0.2-001 or later
• P8AE-4.0.1 with interim fix P8AE-4.0.1-000.001 or later
• P8eForms 4.0.1 or later (Optional. Required only if you are using eForms with Business Process Framework.)

In P8 4.5.x, the Component Manager (CE_Operations) is optional. However, BPF 4.1 requires the Component Manager. For more information, see "Configuring and starting the Component Manager (on an Application Engine server)" in the IBM FileNet P8 Platform Installation and Upgrade Guide.

Certifications

• As of BPF-4.1.0-001, SQL Server 2005 is supported.
• As of BPF-4.1.0-003:
  • DB2 V9.5 and Oracle 11g are supported.
  • WebSphere 7.0, JBoss 4.2.3, and WebLogic 10 are supported.
• As of BPF-4.1.0-004:
  • Microsoft Windows Server 2008 R2(x86, 64-bit) and Microsoft Window 7 (x86, 32/64-bit) are supported.
  • Microsoft Windows Server 2008 R2 Active Directory Lightweight Directory Services is supported.
  • Microsoft SQL Server 2008 is supported.
  • WebLogic 10.3 is supported.
    

NOTE For information about FileNet P8 Platform certification support, refer to FileNet P8 Hardware and Software Requirements, FileNet P8 Release Notes, and the fix pack readme documentation.

New and changed BPF Web application files

This fix pack includes the following changed and new files for your BPF Web application. You will need to install these files in the installation location and deployment location for your BPF Web application. For information about installing these files, see Install new and changed files.

Install this fix pack

To install this fix pack:

1. Install new and changed files.
2. Install the updated BPF Explorer.
3. Update the BPF Web application configuration.
4. Apply eForms changes.
   
5. Update the BPF operations.
6. Validate the BPF Web application.
7. Install inventory marker files.
   

Install new and changed files

To install the new and changed files for this fix pack:

1. If you installed any fix pack that is later than the minimum required version, for the Content Engine, Process Engine, Application Engine, or eForms, replace the following JAR files for that component:
   
   

   Component	JAR Files
   Content Engine	Jace.jar javaapi.jar
   Process Engine	pe.jar peResources.jar
   Application Engine	aeeforms.jar listener.jar mailapi.jar p8ciops.jar (renamed as ContentExtendedOps.jar in P8 4.5.x) p8toolkit.jar soap.jar p8webappLogging.jar commons-fileupload-1.*.jar
   eForms	eforms-resources.jar eforms.jar itext-1.5.2.jar jai_codec.jar commons-httpclient-2.0.2.jar

   You can find the new versions of these files in the Workplace WEB-INF\lib folder. By default the Workplace WEB-INF\lib folder is in the following location:

   • Windows®: C:\Program Files\FileNet\AE\Workplace
   • UNIX®: /opt/FileNet/AE/Workplace

   To replace the JAR files:

   • Copy the p8ciops.jar or ContentExtendedOps.jar from the Workplace WEB-INF/lib folder to the bpfops/lib folder in the BPF installation location.
   • Copy all other JAR files from Workplace WEB-INF/lib folder to the WEB-INF/lib folder in the BPF installation location.

   By default, the BPF installation location is

   • Windows: C:\Program Files\FileNet\BPF
   • UNIX: /opt/FileNet/BPF

   Important: You will also need to copy these JAR files to your BPF Web application deployment location as described in step 7.

2. Download the fix pack and extract the files to a temporary folder on your local system.
3. Copy the files to the appropriate folders in the BPF installation location. For a list of these files and the folders in which they belong, see New and changed BPF Web application files.
4. Stop the application server on which your BPF Web application is running.
5. Use the Export Manifest option in BPF Explorer to back up the BPF Metastore configuration information. To access the Export Manifest option:
   1. Right-click Export and Import Management and select All tasks > Add All Objects to Export List.
   2. Right-click Export and Import Management again and select All tasks > Export XML Manifest.
6. Back up all files in the BPF Web application deploy location. Typically, the deploy location is different from the BPF install home directory.

   If your application is deployed as a WAR or EAR file, back up the WAR or EAR file.

7. Update the BPF Web application files in deploy location with the new and changed files from the fix pack.

   Folder structure

   1. Replace the files in the folder structure with the changed BPF Web application files, and add the new files from the fix pack to the appropriate folders. For a list of the files and the folders in which they belong, see New and changed BPF Web application files.
   2. Copy any JAR files you replaced in step 1 to the /WEB-INF/lib folder in the deployment folder structure.

WAR file

1. Copy the WAR file to a temporary folder. In this procedure, the temporary folder is assumed to be C:\temp_war.
2. Open a command window.
3. Navigate to C:\temp_war and then run the following command to extract the WAR file contents:
   
   jar -xvf bpf_app.war
4. Delete the WAR file from the C:\temp_war folder.
5. Replace the files in the C:\temp_war folder structure with the changed files, and add the new files from the fix pack to the appropriate folders. For a list of the files and the folders in which they belong, see New and changed BPF Web application files.
   
6. Copy any JAR files you replaced in step 1 to the C:\temp_war\WEB-INF\lib folder.

EAR file

1. Copy the EAR file to a temporary folder. In this procedure, the temporary folder is assumed to be C:\temp_ear.
2. Open a command window.
3. Navigate to the C:\temp_ear folder and then run the following command to extract the WAR file and META-INF folder contents to the C:\temp_ear folder:
   
   jar -xvf bpf_app.ear
4. Delete the EAR file from the C:\temp_ear folder.
5. Copy the WAR file from the C:\temp_ear folder to another temporary folder. In this procedure, the second temporary folder is assumed to be C:\temp_war.
6. Navigate to C:\temp_war and then run the following command to extract the WAR file contents:

      jar -xvf bpf_app.war

7. Delete the WAR file from the C:\temp_war folder.
8. Replace the files in the C:\temp_war folder structure with the changed files, and add the new files from the fix pack to the appropriate folders. For a list of the files and the folders in which they belong, see New and changed BPF Web application files.
9. Copy any JAR files you replaced in step 1 to the corresponding folders in the C:\temp_war\WEB-INF\lib folder.
8. Update the web.xml file for your BPF Web application. 
   
   If your application is deployed to a Folder structure, update the web.xml file in the <bpf-app>\WEB-INF folder.
   
   If your application is deployed as an EAR or WAR file, update the web.xml file you extracted to a temporary folder in step 7.
   1. If upgrading from BPF-4.1 GA, BPF-4.1.0-001 or BPF-4.1.0-002, add the following elements after the last <servlet-mapping> element and before the <welcome-file-list> element:  
      
      <!-- mime-mappings below -->
      <mime-mapping>
         <extension>doc</extension>
         <mime-type>application/msword</mime-type>
      </mime-mapping>
      <mime-mapping>
         <extension>docx</extension>
         <mime-type>application/msword</mime-type>
      </mime-mapping>
      <mime-mapping>
         <extension>xls</extension>
         <mime-type>application/vnd.ms-excel</mime-type>
      </mime-mapping>
      <mime-mapping>
         <extension>xlsx</extension>
         <mime-type>application/vnd.ms-excel</mime-type>
      </mime-mapping>
      <mime-mapping>
         <extension>xlsb</extension>
         <mime-type>application/vnd.ms-excel</mime-type>
      </mime-mapping>
      <mime-mapping>
         <extension>xlsm</extension>
         <mime-type>application/vnd.ms-excel</mime-type>
      </mime-mapping>
      <mime-mapping>
         <extension>ppt</extension>
         <mime-type>application/vnd.ms-powerpoint</mime-type>
      </mime-mapping>
      <mime-mapping>
         <extension>pptx</extension>
         <mime-type>application/vnd.ms-powerpoint</mime-type>
      </mime-mapping>
      <mime-mapping>
         <extension>ppsx</extension>
         <mime-type>application/vnd.ms-powerpoint</mime-type>
      </mime-mapping>
      <mime-mapping>
         <extension>svg</extension>
         <mime-type>image/svg+xml</mime-type>
      </mime-mapping>
      <mime-mapping>
         <extension>xfdl</extension>
         <mime-type>application/vnd.xfdl</mime-type>
      </mime-mapping>
      <mime-mapping>
         <extension>xfdd</extension>
         <mime-type>application/vnd.xfdl.design</mime-type>
      </mime-mapping>
      
   2. If AE 4.0.2.7 or higher version is used, add the following setting after the last <context-param> element and (1) before the first <servlet> element if SSO is not configured OR (2) before the <filter> section if SSO is configured:
      
      <!--
              secureAuthenticationParameters: Remove sensitive authentication parameters from the sign-in page. 
              The value is numeric (and not true/false) so that the functionality can be expanded to address more parameters in the future. 
              Here are the current supported values:
      
              0 = Don't secure anything (default).
              1 = Remove the sessionId parameter.
      
              Numbers deemed invalid will result in default "0" behavior.
          -->
          <context-param>
              <param-name>secureAuthenticationParameters</param-name>
              <param-value>1</param-value>
          </context-param>
      
      NOTE:
      (1) This setting is new from BPF 4.1.0-004. Before BPF 4.1.0-004, BPF contains sessionId parameter in url. From BPF 4.1.0-004, this setting is provided to allow you to EITHER keep sessionId parameter in url by setting its value to 0 OR remove this parameter from url by setting its value to 1, and this setting should be set to 1 by default. 
      (2) This setting will only take effect when AE 4.0.2.7 or higher version is applied. If the AE version is lower than 4.0.2.7, you needn't add this setting to BPF web.xml, this setting will be ignored by BPF if it is added to web.xml. You can refer to APAR PJ37346 fixed in AE 4.0.2.7 for more information.
      
      
   3. If you are upgrading from BPF-4.1 GA or BPF-4.1.0-001 and your BPF Web application needs to support clients with double-byte character sets, add the following code after the <context-param> sections:
      
      <filter>
         <filter-name>encoding</filter-name>
         <description>utf-8 filter</description>
         <filter-class>com.filenet.bp8.apps.server.filter.EncodingFilter</filter-class>
         <init-param>
            <param-name>encoding</param-name>
            <param-value>UTF-8</param-value>
         </init-param>
         </filter>
      <filter-mapping>
         <filter-name>encoding</filter-name>
         <url-pattern>/*</url-pattern>
      </filter-mapping>
9. If you have more tools than can fit into the Toolbar area in the BPF Web application, perform the following steps to prevent the tools from overlapping the Case area:

   CASEQUERY inbasket

   Back up the Bp8CaseQueryLayout.xml file and then rename the Bp8CaseQueryLayout_TwoLines.xml file as Bp8CaseQueryLayout.xml. These files are in the <bpf-app>\WEB-INF\ folder.

   Standard inbasket

   After you install the fix pack, use Layout Designer to increase the vertical space for the top Toolbar area in the layout that you are using.

10. WAR or EAR file deployment: Repackage the updated file structure into a new WAR or EAR file:

    WAR file

    1. Repackage the WAR file with the updated files in the C:\temp_war folder by executing the following command:
       
       jar -cvf bpf_app.war *
    2. Copy the WAR file to the BPF Web application deployment location.

EAR File

1. Repackage the WAR file with the updated files in the C:\temp_war folder by executing the following command:
   
   jar -cvf bpf_app.war *
2. Copy the WAR file generated in the previous step from the C:\temp_war folder to the C:\temp_ear folder.
3. Repackage the EAR file by executing the following command:
   
   jar -cvf bpf_app.ear *
4. Copy the EAR file to the BPF Web application deployment location
11. JBoss and WebSphere only: Delete all the cache folders for the BPF Web application.

    The default location of the cache folders for the BPF Web application is

    • JBoss: <JBoss_HOME>\server\default\work\jboss.web\localhost\<bpf-app>
    • WebSphere 5.x: <WAS_Home>\AppServer\temp\<Node_Name>\servers\server1\bpf
    • WebSphere 6.x and 7.x: <WAS_Home>\AppServer\profiles\default\temp\<Node_Name>\server1\bpf
12. JBoss and WebSphere only: Restart the application server on which BPF Web application is running.
13. WebLogic only: Redeploy the BPF Web application.

Install the updated BPF Explorer

1. Run the filenet_bpf_explorer_setup.exe program in the BPF-4.1.0-004 fix pack to uninstall BPF Explorer.
2. Run the filenet_bpf_explorer_setup.exe program in the BPF-4.1.0-004 fix pack again to install the updated BPF Explorer. For information about the setup program, see "BPF Explorer installation" in the IBM FileNet Business Process Framework Installation and Upgrade Guide.

Update your BPF Web application configuration

1. Upgrade the BPF Metastore schema.
   
   TIP Before you upgrade the schema, review the following topics in the Business Process Framework Installation Guide:
   • "Database Security Considerations" in the "Installation Planning Considerations" section, to determine if you need to edit the database scripts that are used to update the Metastore schema.
   • "Load BPF Metastore" in the "Install and Configure BPF Explorer and Metastore" section, for information on running the database scripts.

   In prior releases, you could delete a company object (BUSINESS_UNIT_ID) even if user objects (USER_UNITS) still referenced that company. The BPF-4.1.0-004 fix pack includes a fix to prevent you from deleting a company object that is referenced by a user object. As part of this fix, the Step3 script that you run to upgrade the Metastore schema removes references to any deleted companies from user objects. You must manually reassign companies to these users after you apply the fix pack.

   1. Run the following SQL query against the BPF Metastore to obtain a list of the users for whom the Step3 script will delete the company assignment:
      
      select * from USER_UNITS where BUSINESS_UNIT_ID not in (select BUSINESS_UNIT_ID from BUSINESS_DATA)
   2. Edit the BPF-4.1.0-004 Step3 script to match your environment as needed:
      • If your BPF Metastore is on DB2, edit the Step3.DB2.Bp8.Metabase.1.0.sql script.
        
        Important: You must replace all <BPF_SCHEMA>, <BPF_PROC_SCHEMA> and <BPF_FUNC_SCHEMA> with the real schemas of tables and views, stored procedures and functions of your BPF Metadatabse respectively.
        
      • If your BPF Metastore is on Microsoft® SQL Server, edit the Step3.mssql.Bp8.Metabase.1.0.sql script.
      • If your BPF Metastore is on Oracle, edit the Step3.oracle.Bp8.Metabase.1.0.sql script.
        
        Important: If you run this script using SQL*Plus Worksheet, you must search and replace all &&BPF_SCHEMA with the real schema of your BPF Metadatabase. Otherwise, if using SQL*Plus, you need to enter the real schema when it prompts "Enter value for bpf_schema:". 
   3. Run the Step3 script. For information on running this script, refer to "Loading the BPF Metastore" in the IBM FileNet Business Process Framework Installation and Upgrade Guide.
      
      If you run the script on Oracle, the following error might occur:
      
      ORA-01460: unimplemented or unreasonable conversion requested
      ORA-06512: at "BP8.UPDATE_SETTINGS", line 16
      
      If you receive this error, replace the following line in the BPF-4.1.0-004 Step3.oracle.Bp8.Metabase.1.0.sql script:
      
      CALL UPDATE_SETTINGS (N'WEB', N'DIALOG_WINDOW_RESIZABLE',N'False',N'Whether Action Dialog Window can be resizable (Default:False)');
      
      with the following line:
      
      CALL UPDATE_SETTINGS (N'WEB', 'DIALOG_WINDOW_RESIZABLE',N'False',N'Whether Action Dialog Window can be resizable (Default:False)');
      
      Rerun the script.
2. Log into BPF Explorer.
3. If upgrading from BPF-4.1 GA, BPF-4.1.0-001 or BPF-4.1.0-002, update the Adhoc search definition options:
   1. In the console tree, expand the Application Settings node and click Web Application.
   2. Right-click Attachments tab - Adhoc search definition, click Properties, and add the following text after the select keyword:
      
      a.Bp8ObjectClass as ObjectClassID,
      
      The value is case sensitive, so enter the new text exactly as shown.
   3. Right-click Viewer documents list - Adhoc search definition, click Properties, and add the following text after the select keyword:
      
      a.Bp8ObjectClass as ObjectClassID,
      
      The value is case sensitive, so enter the new text exactly as shown.
4. If you are upgrading from BPF-4.1 GA, BPF-4.1.0-001 or BPF-4.1.0-002, and you customized the Attachment Panel Document List SQL statements for any inbaskets, perform the following steps for each of these inbaskets:
   1. In the console tree, expand the Inbasket Configurations node.
   2. Right-click the inbasket that you want to update and click Properties.
   3. Click the General tab.
   4. In the Attachment Panel Document List SQL field add the following text after the select keyword:
      
      a.Bp8ObjectClass as ObjectClassID,
      
      The value is case sensitive, so enter the new text exactly as shown.
5. If you are upgrading from BPF-4.1 GA or BPF-4.1.0-001 and you are using the sample Case Management application, change the inbasket type for the Indexer role:

1. In the console tree, expand Inbasket Configuration node.
2. Right-click the Matching Inbasket of the Indexer role and click Properties.
3. Click the General tab.
4. From the Inbasket type list, select STANDARD.

Apply eForms changes

If you upgrade eForms to eForms V4.0.2.3 or higher, you must synchronize the eForms JavaScript that is used by Business Process Framework. For information on synchronizing the eForms JavaScript, refer to the Manual_Instruction_Sync_eForms_Script.htm file that is included in this fix pack.

Update the BPF Operations

1. Stop Component Manager by using Process Task Manager on the Application Engine.
2. Back up the bp8ciops.jar file. By default, this file is in the following folder:
   • Windows®: C:\Program Files\FileNet\BPF\bpfops
   • UNIX®: /opt/FileNet/BPF/bpfops
3. Extract the bp8_config.xml and log4j.xml files from the bp8ciops.jar file.
4. If you use Oracle for your Bp8Metastore database, edit the bp8_config.xml file to use the Oracle database service name instead of the Oracle database SID.
5. Optional: To encrypt the password of BPF Metastore database that is configured in the bp8_config.xml file at the node of <Bp8Operations>/<JDBC>/<Password>:
   1. Launch the Command Prompt (Windows® 2000/XP/2003) or shell console (Linux® or UNIX® platform - AIX, Solaris, and HP-UX), and then change the current directory to the folder which contains the bp8ciops.jar delivered with the fix pack.
   2. Ensure that the java command is reachable through the PATH environment variable.
   3. Run the following command to generate the encrypted password:
      
      java -jar bp8ciops.jar cm_user_password bpf_db_password
      
      The cm_user_password is the password of the user which is used to start BPF_Operations in Component Manager, and bpf_db_password is the password of BPF Metastore database. Please replace with your actual values.
      

      After running this command, the encrypted password will be displayed in Command Prompt/shell console, in the format encrypted{xxxxxxxxx}.

   4. Copy and paste the encrypted password, including the prefix encrypted{ and suffix }, to the extracted bp8_config.xml file to replace the password in plaintext.
6. Use WinZip or an equivalent utility to replace the bp8_config.xml and log4j.xml files in the bp8ciops.jar that was delivered with the fix pack with the files you extracted in step 3.
7. Replace the bp8ciops.jar that is currently installed on the BPF application server with the file that you updated in step 5.
8. If you installed P8PE-4.0.2-001.001 test fix or a later P8PE fix pack, navigate to the Connection Point that is used in your system and add the following text in the JRE Parameters field on the Advanced page:
   
   -Dfilenet.pe.cm.adaptor.single.dispatcher.BPF_Operations=true ‑Dfilenet.pe.cm.buffer.size=50 -Dfilenet.pe.eventlog.level=WARNING
9. Restart the Component Manager.
10. Verify that the BPF operations work correctly.
    
    If you use the sample Case Management application and have created workflow subscription on the Content Engine Case Management Documents document class(please refer to section "Creating workflow subscription on the Content Engine Case Management Documents document class (optional)" in BPF 4.1 Installation Guide), you can ensure that the BPF operations are working correctly as follows:
    1. In Workplace or FileNet Enterprise Manager, add a new document to the Case Management Documents document class.
    2. Set the DocEntryStatus and DocType values to 1.

    If the BPF operations are working correctly, BPF creates a new case and you can see it in the Index Inbasket.
    
    

Important: If you set the encrypted password in step 5, you must repeat steps 1 through 10 to refresh the encrypted password whenever the following passwords are changed:

• The password of BPF Metastore database
• The password of the user that is used to start BPF_Operations in Component Manager

Validate the BPF Web application

Before users access the BPF Web application, validate that the application is working:

1. Clear Internet Explorer caches by deleting Temporary Internet Files with all offline content on all BPF clients.
2. Launch BPF Web application and validate that the application is working correctly. For information about validating the BPF Web application, see "Logging on to a sample Business Process Framework Web application” in the IBM FileNet Business Process Framework Installation and Upgrade Guide.

Install inventory marker files

Starting with BPF-4.1.0-004, BPF provides two inventory marker files, also called tag files. The first tag file identifies the product name and the version number. In this release the file is named IBM_FileNet_Business_Process_Framework.4.1.0.swtag. The second tag file identifies the fix pack number, if applicable. In this release the file is named BPF.4.1.0.4.fxtag.

1. Go to the <BPF_installation_location> directory. By default, the <BPF_installation_location> is:
   
   • Windows: C:\Program Files\FileNet\BPF
   • UNIX: /opt/FileNet/BPF
2. Under the <BPF_installation_location> directory, create a directory named properties.
   
3. Under the  <BPF_installation_location>/properties directory, create a directory named version.
4. Under the  <BPF_installation_location>/properties/version directory, copy the two tag files. These files are included in this fix pack:
   IBM_FileNet_Business_Process_Framework.4.1.0.swtag
   BPF.4.1.0.4.fxtag
   

Important: Since BPF uninstaller does not uninstall files that are not laid down by BPF installer, to uninstall these two files, you need manually remove the <BPF_installation_location>/properties directory, including all subdirectories and files, after uninstalling the BPF product using BPF uninstaller.

Uninstalling this fix pack

You cannot uninstall the BPF-4.1.0-004 fix pack.

Product fix history

The following tables list the product fixes in this fix pack.

BPF-4.1.0-004

BPF-4.1.0-003

BPF-4.1.0-002

BPF-4.1.0-001

Contacting IBM support

For information about contacting IBM 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.

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.

   http://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 for IBM FileNet P8 Platform products:

1. Navigate to the Information Management support page (www.ibm.com/software/data/support).
2. Select FileNet Product Family.
3. On the FileNet Product Family support page, search for: FileNet fix packs.
4. Select the most appropriate link from the returned results.
5. Continue navigating through the returned pages until you find the fix pack you want.
6. Select the fix pack link.
   
   Selecting a fix pack opens the FileNet Fix Packs page. You will need to register at this page before you can continue to the fix pack download site.

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:

Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
3-2-12, Roppongi, Minato-ku, Tokyo 106-8711 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 and Windows 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 may be trademarks or service marks of others.