Installing the fix pack

Transcription

1 Installing the fix pack To install the fix pack, complete the following tasks: 1. Installing the new and changed files 2. Installing the updated BPF Explorer 3. Updating your BPF Web application configuration 4. Applying eforms changes 5. Updating the BPF_Operations component 6. Validating the BPF Web application 7. Installing the inventory marker files List of new and changed files The BPF fix packs usually contain new and changed files for your BPF Web application. You need to install the files in the installation location and deployment location for your BPF Web application. The table below lists product files that have been added or changed cumulatively in all BPF fix packs. For information about installing these files, see Installing the new and changed files. BPF web application folder root \css \dtd \img\mime File name About.jsp Bp8AttachIFrameEntry.jsp Bp8Dialog.jsp Bp8Editor.jsp Bp8RemoteCallSingIn.jsp Bp8SSOSignout.jsp Bp8ViewerDocs.jsp Bp8ViewerFrameset.jsp Bp8ViewerModule.jsp Bp8WPDefaultAnswer.jsp ExtCommand.jsp Lookup.jsp SaveLayoutPopUp.jsp UserPreferences.jsp UserPrefs.jsp Bp8Styles.css case.dtd Bmp16.gif Bmp32.gif Default16.gif Default32.gif Doc16.gif Doc32.gif Gif16.gif Gif32.gif Htm16.gif Htm32.gif Jpg16.gif p. 1

2 BPF web application folder \inc \js \js\layout \plugins\custom \plugins\tabs\attachment \plugins\tabs\attachment\ui \plugins\tabs\attachment\xsl\include \plugins\tabs\attachment\xsl\list \plugins\tabs\eforms \plugins\tabs\table \plugins\tabs\table\xsl \plugins\tools\add_document\ui \plugins\tools\create_browse \plugins\tools\create_case File name Jpg32.gif Modca16.gif Msg16.gif Oft16.gif Pdf16.gif Pdf32.gif Pep32.gif Ppt16.gif Ppt32.gif Tif16.gif Tif32.gif Txt16.gif Txt32.gif Una16.gif Una32.gif Vcf16.gif Vcs16.gif Xls16.gif Xls32.gif Xml16.gif Xml32.gif InitUserPreferences.inc Bp8BusinessObjects.js Bp8CaseOperation.js Bp8ContextMenu.js Bp8Errors.js Bp8InitMain.js Bp8Util.js CreateCase.js FormActions.js FormUtil.js RemoteFunctions.js RemoteScripting.js assignroles.js BPFLayoutInitMain.js EventHandlers.js.template Bp8AttachmentsTab.jsp Bp8AttachmentsTab.jsp Bp8FavoriteAttachDocsIcons.xsl Bp8GetFormattedValue.xsl Bp8GetItemLinkURL.xsl ListViewContextMenu.xsl Bp8AttachTabSelectableListView.xsl Bp8DocumentForm.jsp SaveEFormDataMessage.jsp grid.htc TableTab.jsp list.xsl Bp8AddDocument.jsp CreateCase.jsp Bp8CreateCase.jsp p. 2

3 BPF web application folder \plugins\tools\reactivate_case \plugins\tools\split_case \UI-INF\jsp\modules\apps \UI-INF\jsp\ui \vbs \WEB-INF \WEB-INF\lib \WEB-INF\xsl\list \WEB-INF\xsl\include \xsl File name Bp8ReactivateCase.jsp SplitCaseResult.jsp Bp8MainModuleJSP.jsp Bp8SignInModuleJSP.jsp Bp8AttachIFrameEntry.jsp Bp8Main.jsp Bp8RemoteCallSingIn.jsp Bp8SignIn.jsp Bp8ViewerDocs.jsp Bp8Util.vbs Bp8Actions.xml Bp8CaseQueryLayout.xml Bp8CaseQueryLayout_TwoLines.xml Bp8ExtCommands.xml Bp8ExtTasks.xml Bp8Layout.xml user-preferences.xml bpfcm.jar bpfcmresources.jar bpfcustomlangresources.jar bpflangresources.jar bpfwa.jar serializer.jar xalan.jar xercesimpl.jar xml-apis.jar Bp8AttachDocsSelectableListView.xsl Bp8CustomSearchSelectableListView.xsl Bp8FavoriteAttachDocsSelectableListView.xsl Bp8AdoTransform.xsl Bp8AttachmentsPaging.xsl Bp8AttachmentsSorting.xsl Bp8CustomSearchIcons.xsl Bp8FavoriteAttachDocsIcons.xsl Bp8GetItemLinkURL.xsl ListViewContextMenu.xsl Bp8CaseProps.xsl Bp8Cases.xsl Bp8Filters.xsl Bp8MergeCase.xsl Bp8ReclassifyCase.xsl Bp8SplitCase.xsl Bp8Tool.xsl Installing the new and changed files p. 3

4 To install the new and changed files: 1. Replace the following JAR files for the Content Engine, Process Engine, Application Engine, and eforms components: Component Content Engine Process Engine Application Engine eforms Files Jace.jar javaapi.jar pe.jar peresources.jar 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 commons-httpclient jar eforms.jar eforms-resources.jar itext jar (for eforms version and earlier) itext jar (for eforms version and later) jai_codec.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: a. Copy one of the following files to the bpfops/lib folder in the BPF installation location: p8ciops.jar from the Workplace WEB-INF/lib folder ContentExtendedOps.jar from the C:\Program Files\FileNet\AE\router\lib folder on Windows or the /opt/filenet/ae/router/lib folder on UNIX b. Copy all other JAR files from the Workplace WEB-INF/lib folder to the WEB-INF/lib folder in the BPF installation location. c. If you are using eforms or later, copy the itext jar file from the WEB-INF/lib folder in Workplace to the WEB-INF/lib folder in the BPF installation location. Then remove the itext jar file from the BPF installation directory. p. 4

5 Important: You will also need to copy these JAR files to your BPF Web application deployment location as described in step Remove the earlier-version JAR files from WEB-INF/lib folder in the BPF installation location. 3. Download the fix pack and extract the files to a temporary folder on your local system. 4. 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 the List of new and changed files. 5. Back up the eforms-integration.xml file in the BPF configuration folder on your system. By default, the BPF configuration folder is: Windows: C:\Program Files\FileNet\Config\bpf UNIX: /opt/filenet/config/bpf 6. Copy the eforms-integration.xml file in the fix pack to the BPF configuration folder on your system. 7. Stop the application server on which your BPF Web application is running. 8. Use the Export Manifest option in BPF Explorer to back up the BPF Metastore configuration information. To access the Export Manifest option: a. Right-click Export and Import Management and select All tasks > Add All Objects to Export List. b. Right-click Export and Import Management again and select All tasks > Export XML Manifest. 9. Back up all files in the BPF Web application deployment location. Typically, the deployment location is different from the BPF installation home directory. If your application is deployed as a WAR or EAR file, back up the WAR or EAR file. 10. Update the BPF Web application files in the deployment location with the new and changed files from the fix pack. Application type Folder structure Instructions a. 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 the List of new and changed files. b. Copy any JAR files you replaced in step 1 to the /WEB-INF/lib folder in the deployment folder structure. WAR file a. Copy the WAR file to a temporary folder. In this procedure, the temporary folder is assumed to be C:\temp_war. b. Open a command window. c. Navigate to C:\temp_war and then run the following command to extract the WAR file contents: p. 5

6 jar -xvf bpf_app.war d. Delete the WAR file from the C:\temp_war folder. e. 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 the List of new and changed files. f. Copy any JAR files you replaced in step 1 to the C:\temp_war\WEB-INF\lib folder. EAR file a. Copy the EAR file to a temporary folder. In this procedure, the temporary folder is assumed to be C:\temp_ear. b. Open a command window. c. 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 d. Delete the EAR file from the C:\temp_ear folder. e. 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. f. Navigate to C:\temp_war and then run the following command to extract the WAR file contents: jar -xvf bpf_app.war g. Delete the WAR file from the C:\temp_war folder. h. 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 the List of new and changed files. i. Copy any JAR files you replaced in step 1 to the corresponding folders in the C:\temp_war\WEB-INF\lib folder. Important: If you use JBoss version 4.2.3, or later: Copy serializer.jar, xalan.jar, and xercesimpl.jar to the JBoss installation folder, which is usually <JBoss_HOME>/jboss-as/lib/endorsed. Remove serializer.jar, xalan.jar, xercesimpl.jar, and xml-apis.jar from the WEB- INF/lib folder in the BPF deployment location and the BPF installation location. p. 6

7 11. If you have the issue addressed by APAR PJ37750, and if you are upgrading from BPF-4.1 GA, BPF , BPF , BPF , or BPF : when eforms data is created in one time zone and later displayed in a different time zone, the date that is displayed is incorrect. This problem can occur when: The server on which BPF is running is in a different time zone from the clients accessing BPF. The clients are scattered in a wide range of time zones. To prevent this problem, you must: a. Ensure that you have applied he AE test fix P8AE-TF002 (or later fix pack) to Workplace (set eformsmapdatetogmtnoon=true) and copy the aeeforms.jar file to the BPF Web application. b. Add the following property to the bootstrap.properties file under the BPF configuration folder: eformsmapdatetogmtnoon=true By default, the BPF configuration folder is in the following location: Windows: C:\Program Files\FileNet\Config\bpf UNIX: /opt/filenet/config/bpf 12. 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 <bpfapp>\web-inf folder. If your application is deployed as an EAR or WAR file, update the web.xml file that you extracted to a temporary folder in step 10. To update the web.xml file: a. If you are upgrading from BPF-4.1 GA, BPF , or BPF , add the following elements after the last <servlet-mapping> element and before the <welcome-file-list> element: <!-- mime-mappings below --> <extension>doc</extension> <mime-type>application/msword</mime-type> <extension>docx</extension> <mime-type>application/msword</mime-type> <extension>xls</extension> <mime-type>application/vnd.ms-excel</mime-type> <extension>xlsx</extension> <mime-type>application/vnd.ms-excel</mime-type> <extension>xlsb</extension> p. 7

8 <mime-type>application/vnd.ms-excel</mime-type> <extension>xlsm</extension> <mime-type>application/vnd.ms-excel</mime-type> <extension>ppt</extension> <mime-type>application/vnd.ms-powerpoint</mime-type> <extension>pptx</extension> <mime-type>application/vnd.ms-powerpoint</mime-type> <extension>ppsx</extension> <mime-type>application/vnd.ms-powerpoint</mime-type> <extension>svg</extension> <mime-type>image/svg+xml</mime-type> <extension>xfdl</extension> <mime-type>application/vnd.xfdl</mime-type> <extension>xfdd</extension> <mime-type>application/vnd.xfdl.design</mime-type> b. If AE or later 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> Notes: This setting was new in BPF Before BPF , BPF contained a sessionid parameter in a URL. Beginning in BPF , this setting is provided to allow you to EITHER keep the sessionid parameter in the URL by setting its value to 0 OR remove this parameter from the URL by setting its value to 1. This setting should be set to 1 by default. p. 8

9 This setting will only take effect when AE or later version is applied. If the AE version is earlier than , you do not need to add this setting to the BPF web.xml file. You can refer to APAR PJ37346 fixed in AE for more information. c. If you are upgrading from BPF-4.1 GA or BPF and your BPF Web application needs to support clients with double-byte character sets, add the following code after the <contextparam> sections: <filter> <filter-name>encoding</filter-name> <description>utf-8 filter</description> <filter-class>com.filenet.bp8.apps.server.filter.encodingfilter</filterclass> <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> 13. If you have the issue addressed by APAR PJ39368, complete the following steps: a. Copy the SecurityFilter.xml file from the Workplace WEB-INF folder to the BPF web application WEB-INF folder. b. Modify the SecurityFilter.xml file by adding the lines <value>alert</value> and <value>><a href="</value> as shown below: <array key="expressions"> <value><\\s*img\\s* <\\s*script\\s*> \\s*javascript\\s*: (^ \\s+) on[a-za-z]*\\s*=</value> <value>script>.*\/script</value> <value> STYLE=xss:e</value> <value>><img SRC="</value> <value>alert</value> <value>><a href="</value> <value>onmouseover=</value> </array> c. Add the following lines to the web.xml file under the BPF web application WEB-INF folder before "<servlet id="servlet_3">": <filter> <filter-name>securitypluginfilter</filter-name> <filterclass>com.filenet.ae.toolkit.server.servlet.filter.securitypluginfil ter</filter-class> </filter> <filter-mapping> <filter-name>securitypluginfilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping> p. 9

10 14. 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>\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. 15. WAR and EAR file users only: Repackage the updated file structure into a new WAR or EAR file for redeployment: Application type WAR file Instructions a. Repackage the WAR file with the updated files in the C:\temp_war folder by executing the following command: jar -cvf bpf_app.war * b. Copy the WAR file to the BPF Web application deployment location. EAR file a. Repackage the WAR file with the updated files in the C:\temp_war folder by executing the following command: jar -cvf bpf_app.war * b. Copy the WAR file generated in the previous step from the C:\temp_war folder to the C:\temp_ear folder. c. Repackage the EAR file by executing the following command: jar -cvf bpf_app.ear * d. Copy the EAR file to the BPF Web application deployment location. 16. JBoss and WebSphere users 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 17. JBoss and WebSphere users only: Restart the application server on which BPF Web application is running. p. 10

11 18. WebLogic users only: Redeploy the BPF Web application. Installing the updated BPF Explorer To install the updated BPF Explorer: 1. Run the filenet_bpf_explorer_setup.exe program in the fix pack to uninstall BPF Explorer. 2. Run the filenet_bpf_explorer_setup.exe program in the fix pack again to install the updated BPF Explorer. If you are using Microsoft SQL Server for the Bp8Metastore database with a non-default instance, enter the instance information in the "SQL Server" field in the following format: Server_Name\Instance_Name. For more information about the setup program, see "BPF Explorer installation" in the IBM FileNet P8 Business Process Framework Installation Guide. Updating your BPF Web application configuration To upgrade the 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. (Installation documentation is available online at "Database security" in the "Planning and preparing for Business Process Framework installation" section, to determine if you need to edit the database scripts that are used to update the Metastore schema. "Loading the Business Process Framework Metastore" in the "Manually editing installation settings" section, for information on running the database scripts. Important: In releases prior to BPF , you could delete a company object (BUSINESS_UNIT_ID) even if user objects (USER_UNITS) still referenced that company. The 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. If you haven't done this before, you must manually reassign companies to these users after you apply the fix pack. a. 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) b. Edit the Step3 script to match your environment as needed: p. 11

12 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> entries with the real schemas of tables and views, stored procedures and functions of your BPF Metadatabase respectively. If your BPF Metastore is on Microsoft SQL, edit the Step3.mssql.Bp8.Metabase.1.0.sql script. Important: If the collation name of BPF Metastore database is set to SQL_Latin1_General_CP1_CI_AI, search for "SQL_Latin1_General_CP1_CI_AS" in the Step3.mssql.Bp8.Metabase.1.0.sql script and replace it with "SQL_Latin1_General_CP1_CI_AI". 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 entries 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:". c. 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 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. If your BPF Metastore is on DB2, run the Recreate.DB2.Bp8.Metabase.Triggers.sql file to fix logic problems in the BPF triggers (refer to APAR PJ37412): a. Open the DB2 Command Editor and log on as a BPF Metastore user. b. Change the Statement Termination Character You can change this character at the bottom of the Command Editor window. c. Click the Add button and select the Bp8Metastore database to be corrected. p. 12

13 d. Clear "User implicit credential," enter the username and password for the DB2 user who is the schema owner of your Bp8Metastore, and click OK. e. Open the Recreate.DB2.Bp8.Metabase.Triggers.sql file in the Command Editor using Selected > Open. f. Run the script using Selected > Execute. 3. Log in to BPF Explorer. 4. If you are upgrading from BPF-4.1 GA, BPF or BPF , update the Adhoc search definition options: a. In the console tree, expand the Application Settings node and click Web Application. b. 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. c. 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. 5. If you are upgrading from BPF-4.1 GA, BPF or BPF , and you customized the Attachment Panel Document List SQL statements for any inbaskets, perform the following steps for each of these inbaskets: a. In the console tree, expand the Inbasket Configurations node. b. Right-click the inbasket that you want to update and click Properties. c. Click the General tab. d. 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. 6. If you are upgrading from BPF-4.1 GA or BPF and you are using the sample Case Management application, change the inbasket type for the Indexer role: a. In the console tree, expand Inbasket Configuration node. b. Right-click the Matching Inbasket of the Indexer role and click Properties. p. 13

14 c. Click the General tab. d. From the Inbasket type list, select STANDARD. 7. If running a workflow's CE_Operations process displays problems with the eform version (APAR PJ39046), change the value of the "Save eforms form data synchronously" setting: a. Go to Applications Settings > Web Application. b. Set the value of the Save eforms form data synchronously setting to True. 8. If you have the issue addressed by APAR PJ39238 and need to disable the "Show Details" link in the error page, change the value of the following setting to "False": Applications Settings > Web Application > Display the Show Details link in the error page (Default: True). 9. If you have the issue addressed by APAR PJ40150, change the value of the following setting to "False": Applications Settings > Web Application > Save eforms data first when dispatching an eforms Case (Default: True). 10. If you have the issue addressed by APAR PJ40523, change the value of the following setting to "True": Applications Settings > Web Application > Display Short Name of user instead of Display Name/Full Name in the Audit tab and the bottom user information bar (Default: False). 11. If you have the issue addressed by APAR PJ41209, change the value of the following setting to "True" in BPF Explorer: Applications Settings > Web Application > Allow to query work items from inbox(0) queue instead of inbox for personal inbasket in browse mode (Default: False). TIP : The following cases describe the differences between the Inbox and the Inbox(0) user queues: Use Inbox queue to retrieve the inbox work items of the user that is currently logged on. Use Inbox(0) queue to retrieve inbox work items of all users. Use Inbox(0) queue and F_BoundUser system field in the query filter to retrieve inbox work items of a specific user (or users). 12. If you have the issue addressed by APAR PJ41299, change the value of the following setting to "True": Applications Settings > Web Application > Allow to attach documents to a Bp8 Case when the associated work item does not exist, locked by others or in the Delay queue for BPF_Operations::attachDoc (Default: False). Applying eforms changes If you upgrade eforms to eforms V or later, 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. Updating the BPF_Operations component p. 14

15 To update the BPF_Operations component: 1. Stop the 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 Microsoft SQL Server for your Bp8Metastore database with the non-default instance (as described in APAR PJ39488), edit the bp8_config.xml file: a. Add an instance node to the bp8_config.xml file extracted from the bp8ciops.jar file and configure it with the instance name. For example: <JDBC> <DBType>mssql</DBType> <!-- Database type -> <User>bp8</User> <!-- User name -> <Password>bp8</Password> <!-- User password -> <Database>Bp8Metastore</Database> <!-- Database name -> <Server>p8demo30</Server> <!-- Server -> <Instance>BPF</Instance> <!-- Instance name if using non-default instance -> <Port>1433</Port> <!-- Port -> </JDBC> 5. 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. 6. If you use Oracle RAC for your Bp8Metastore database, edit the bp8_config.xml file: a. Set the JDBC URL in the <URL> element. Ensure that the URL is written in one line without any break b. Specify the user and password in the <User> and <Password> elements. The settings in <Database>, <Server> and <Port> are ignored. Note: For non RAC environment, remove the URL element or leave it blank, and specify the parameters in <User>, <Password>, <Database>, <Server> and <Port> elements as usual. c. An example configuration is as below. You need to replace the values in blue bold with your real values. <Bp8Operations> <JDBC> <DBType>oracle</DBType> <URL> OTOCOL=TCP)(HOST=node1)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=node2)(PORT =1521)))(CONNECT_DATA=(SERVICE_NAME=oraclesvcname)(failover_mode=(type=sele ct)(method=basic)(retries=32)(delay=4)))) </URL> <User>bp8</User> <Password>bp8</Password> <Database>hfos</Database> p. 15

16 <Server>vm20</Server> <Port>1521</Port> </JDBC> <Settings> Optional: Encrypt the password of BPF Metastore database that is configured in the bp8_config.xml file at the node of <Bp8Operations>/<JDBC>/<Password>: a. Launch the command prompt (Windows) or shell console (Linux or UNIX platform on AIX, Solaris, and HP-UX), and then change the current directory to the folder that contains the bp8ciops.jar that is delivered with the fix pack. b. Ensure that your PATH environment variable is set to provide access to the java command. c. Run the following command to generate the encrypted password: java -jar bp8ciops.jar d. Enter and verify the following passwords when you are prompted: The password of the user that is configured to start BPF_Operations in Component Manager The password of the BPF Metastore database user Then the encrypted password will be displayed in Command Prompt/shell console, in the format encrypted{xxxxxxxxx}. e. Copy the encrypted password, including the prefix encrypted{ and suffix }, and paste it into the extracted bp8_config.xml file to replace the password in plain text. Note: Due to a limitation of Java versions prior to 6, two minor problems can occur when you run this tool: 1. The characters that you enter blink, displaying and disappearing quickly. 2. When you enter the password for the second time, you are prompted to enter the password again. You can ignore both issues. 8. Use an extraction 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 Replace the bp8ciops.jar that is currently installed on the BPF application server with the file that you updated in step If you installed P8PE test fix or a later P8PE fix pack, from the component manager in Process Task Manager on AE, select 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 p. 16

17 11. Restart the Component Manager. 12. Verify that the BPF operations work correctly. If you use the sample Case Management application and have created a workflow subscription on the Content Engine Case Management Documents document class, refer to the "Creating workflow subscription on the Content Engine Case Management Documents document class (optional)" section in the BPF 4.1 installation documentation. You can ensure that the BPF operations are working correctly as follows: a. In Workplace or FileNet Enterprise Manager, add a new document of the Case Management Documents document class. b. 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 6, you must repeat steps 1 through 10 to refresh the encrypted password whenever the following passwords are changed: The password of the BPF Metastore database user The password of the user that is configured to start BPF_Operations in Component Manager Validating the BPF Web application Before users access the BPF Web application, validate that the application is working. To 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 Guide. Installing the inventory marker files Starting with BPF , 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 swtag. The second tag file identifies the fix pack number, if applicable. In this release the file is named BPF fxtag. To install the inventory marker files: p. 17

18 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. Create a subdirectory with this path: <BPF_installation_location>/properties/version. 3. Under the <BPF_installation_location>/properties/version subdirectory, copy the two tag files from this fix pack: IBM_FileNet_Business_Process_Framework swtag BPF fxtag Important: The BPF uninstaller does not remove these two files. If you uninstall BPF and want to remove these files, you must manually remove the <BPF_installation_location>/properties directory, including all of the subdirectories and files. p. 18