APAR PO06620 Installation Instructions

Transcription

1 IBM Corporation APAR PO06620 Installation Instructions IBM Counter Fraud Management IBM Counter Fraud Development

2 Table of Contents 1 Fix readme Abstract Contents Download this interim fix System requirements Prerequisite Supersedes Known issues Broken IBM Counter Fraud Management links Description Resolution Limitations SSL handshake errors Description Resolution Installation Overview Preparations Identifying the IBM Case Manager Object Stores for Counter Fraud Verifying IBM Case Manager Fix Pack 6 installation Verifying IBM Content Platform Engine Fix Pack 6 installation Creating a recovery point Preparing the interim fix installation files Unzipping the supplemental files Transferring interim fix files to the CFM Linux servers Backing up the IBM HTTPServer WebSphere plug-in configuration file Creating new ICFM System Properties Creating CF.ICM.SYS.TMPDIR Creating CF.ICM.DATA.CaseSearchStatus Changing CF.ICM.DATA.CaseSearchStatus Create new J2C aliases Page i

3 Creating CFM Creating CFMP Configuring JAAS Application logins Verifying CaseOperationsLogin properties Creating CaseOperationsLogin properties Upgrading the Messaging node Upgrading the Counter Fraud services applications Upgrading the CounterFraud_Engine application Upgrading the CounterFraud_FactConfig application Upgrading CounterFraud_PingEAR application Upgrading CounterFraud_DataImportEAR application Upgrading CounterFraud_DeployAgent_Cognos application Upgrading the Decision and Scoring node Upgrading CounterFraud_DeployAgent_SPSS application Upgrading the Case & Analysis node Upgrading the Counter Fraud Case Management plug-in Upgrading the Counter Fraud Case Manager-plugin Upgrading Counter Fraud Case Management Rest application Upgrading the Counter Fraud Case Management widgets Upgrading the Counter Fraud Systems Management Console Upgrading the SMC plug-in Upgrading CounterFraud_SMCEAR application Upgrading the Counter Fraud Case Manager Component Manager Upgrading the Counter Fraud Notification Service Upgrading CFCaseMgmtEventHandler Replacing the Counter Fraud Case Management solution Removing the solution template Create a backup copy solution Counter Fraud Alert Importing the Counter Fraud case management solution Configuring dashboard URLs Deploying a new solution Configuring security for IBM Case Manager solutions Updating IBM Case Manager roles Page ii

4 10.12 Updating the CFCaseMgmtOperations component queue Updating the JAAS CaseOperationsLogin module properties Restoring the IBM HTTPServer WebSphere plug-in configuration file Updating the Counter Fraud swidtag directory Table of Figures Figure 1: IBM Counter Fraud Management home page identifying broken links... 3 Figure 2: Web application log out error page... 3 Figure 3: Potential SSL handshake error... 4 Figure 4: IBM Knowledge Center - Upgrading Counter Fraud components... 6 Figure 5: Search for IBM Case Manger Fix Pack tag files... 7 Figure 6: Content Engine Startup Content (Ping Page)... 7 Figure 7: Extract APAR PO06620 installation files... 9 Figure 8: Extract destination path Figure 9: Launch CFM Case Manager Client Figure 10: CFM Case Manager login page Figure 11: CFM Case Client main page Figure 12: CFM System Properties summary page Figure 13: Add System Property page Figure 14:System Properties page Figure 15: Add System Property page Figure 16: WAS Global security page Figure 17: JAAS - J2C authentication data Figure 18: Create new J2C Alias page Figure 19: Save new J2C Alias page Figure 20: Refreshed JAAS - J2C authentication data page Figure 21: Refreshed JAAS - J2C authentication data page Figure 22: WebSphere Global security page Figure 23: WebSphere JAAS Applications logins page Figure 24: CaseOperationsLogin properties page Figure 25: comm.ibm.casemgmt.asa.ii... properties page Figure 26: filenet.vw.server.vwloginmodule properties page Figure 27: Map modules for CounterFraud_FactConfig Figure 28: IBM Counter Fraud Management launch page Figure 29:IDDN WebSphere enterprise applications page Figure 30: Decision and Scoring node enterprise applications page Figure 31: IBM Knowledge Center - Upgrading Case & Analysis node Figure 32:Manage Modules page for CFRestEAR.ear Figure 33: CFCaseMgmtWidgets.zip search results Figure 34: CFCaseMgmtWidgets directory contents Figure 35: IBM Case Manager Widget Packages page Page iii

5 Figure 36: Import custom widgets page Figure 37: Verify import package selection page Figure 38: Import widgets package results page Figure 39: CFCaseMgmtOperation.zip search results Figure 40: IBM Knowledge Center bread crumbs to Configuring the Component Manager Figure 41: Delete Component Manager queue Figure 42: CFCaseMgmtOperations Component Manager and queue Figure 43: NotificationService.properties search results Figure 44: CFCaseMgmtEventHandler search results Figure 45: CFCaseMgmtEventHandler directory contents Figure 46: TARGET object store contents Figure 47: CmAcmEventHandler page Figure 48: Exclusive checkout dialog box Figure 49: Check In Document dialog box Figure 50: Updated CodeModules table Figure 51: Replacing the Counter Fraud Case Management Solution Figure 52: Copy a solution page Figure 53: Updated Manage Solutions page Figure 54: IBM Case Manager DESIGN Solution Template page Figure 55: Solution template import results page Figure 56: Sample CFM Role assignments Figure 57: Process Configuration Console page Figure 58: Target Object Store page Figure 59: Process Configuration Console home page Figure 60: Process Configuration Component Queues page Table of tables Table 1: Stop IBM software products... 8 Table 2: Start IBM software products... 8 Table 3: File transfer destinations Table 4: Add System Property values Table 5: Add System Property values Table 6: J2C Alias attributes for CFM Table 7: J2C Alias attributes for CFMP Table 8: CaseOperationsLogin properties Table 9: com.ibm.casemgmt.asa.ii... Custom properties Table 10: User role to group mapping Table 11: Supplemental file transfer parameters Table 12: Copy a solution attributes Table 13: Solution template import URL prefix values Table 14: CFCaseMgmtOperations Component properties Table 15: Code Module properties page Page iv

6 1 Fix readme This document may be downloaded from the IBM Support web site: 2 Abstract This readme file is intended to help IBM Services consultants and other Service Providers to install IBM Counter Fraud Management (ICFM) V APAR PO06620 for cloud and on premise deployment environments. It directs the reader to the download site and provides information about prerequisites, known problems and restrictions for this release. 3 Contents Download this interim fix System requirements Prerequisite Supersedes Known issues Limitations Installation 4 Download this interim fix This APAR is available from the IBM Support Fix Central web site PO06620: IBM Counter Fraud Management Interim Fix 5 System requirements The official statements for hardware and software support are provided in IBM Counter Fraud Management detailed system requirements. Review new requirements for supported software, including base product fix packs (1505 tab Software Supported Software tab). Review the product license to ensure that you have the necessary authorizations to support your deployment topology and that you understand the usage restrictions for all software components that are included with the product. 6 Prerequisite IBM Counter Fraud Management IBM Counter Fraud Management APAR PO05499 IBM Counter Fraud Management APAR PO05616 Page 1

7 IBM Counter Fraud Management APAR PO06156 IBM Counter Fraud Management APAR PO06405 IBM Case Manager IBM Content Platform Engine IBM Content Navigator Supersedes None 8 Known issues Known problems, restrictions and solutions are documented in the form of individual technical notes. As problems are discovered and resolved, the IBM Counter Fraud Management Team updates the knowledge base. By searching the knowledge base, you can quickly find work arounds and solutions to problems. To view known issues and related support information. see the IBM Counter Fraud Management Support Portal and select to filter by version Broken IBM Counter Fraud Management links The IBM Counter Fraud Management default configuration directs HTTP and HTTPS messages to the IBM HTTPServer running on the Messaging node. The IBM HTTPServer uses the WebSphere plugin to reroute these messages to the back-end WebSphere Application Servers where the IBM Counter Fraud Management and Case Manager applications operate Description Unexpected changes to the WebSphere Plugin configuration file for the IBM HTTPServer were detected following the IBM Case Manager update to Fix Pack 6. The default HTTP and HTTPS URLs to the Case Manager applications fail. Page 2

8 Figure 1: IBM Counter Fraud Management home page identifying broken links Another manifestation of this problem occurs, when you use the Log Out function from the pulldown menu to end a web browser session with an IBM Case Manager application. Instead of returning to the application s Log in page, the web browser detects a page not found error. Figure 2: Web application log out error page Resolution The APAR installation procedure contains instructions: Page 3

9 1. At the start of the installation, to create a backup copy of the IBM HTTPServer WebSphere plug-in configuration file. Refer to Section Backing up the IBM HTTPServer WebSphere plug-in configuration file. 2. At the end of the installation procedure, to restore the IBM HTTPServer plug-in configuration file from the backup copy. Refer to section add the cross reference links. 9 Limitations The following items were discovered while system testing APAR PO SSL handshake errors This is an intermittent problem that may occur in some deployment environments Description From the Messaging node - WebSphere Administration Console, unable to restart the updated IBM Counter Fraud Management Enterprise Applications due to SSL handshake errors. Figure 3: Potential SSL handshake error Resolution 1. Restart the IBM software products on each node in the deployed IBM Counter Fraud Management topology using the IBM provided scripts The instructions to stop and start the IBM software products are located in this document under the heading Create Recovery Point. 2. Open a web browser and connect to the Messaging node WebSphere Administration Console and start the updated IBM the IBM Counter Fraud Management Enterprise Applications. 10 Installation This APAR contains enhancements to: 1. Provide the capability to report and update closed cases by adding a new system property CF.ICM.DATA.CaseSearchStatus to Systems Property Table CFCON.SYSTEM_PROPS in the Counter Fraud Data Base (CFDB) Use this property to provide a list of Case status values to override the default list which contains Initial, Triaging and Reviewing. 2. Improve security Overview The installation procedure requires the use of multiple tools and the systems administrator will be switching frequently between them. These tools are installed and configured on the ICFM Tools client. 1. IBM Content Navigator via the web browser. 2. IBM Content Engine Administration Console via the web browser. 3. IBM WebSphere Integrated System Console via the web browser. 4. Linux graphical desktop via VNC Viewer. 5. Linux terminal session via PuTTY. 6. File transfer Utility via WinSCP. Page 4

10 Unless explicitly directed by these instructions, all tasks should be initiated from the ICFM Tools client with the exceptions of creating full node backups or snapshots and rebooting the severs. Follow the instructions in this document to download the APAR installation file on the ICFM Tools Windows Client. The APAR install procedures are based on the procedures contained in the IBM Counter Fraud Management Knowledge Center under the topics: 1. Upgrading from ifix PO05499 to ifix PO Upgrading from version to version Most of the updates are made to IBM Case Manager components executing on the Case node (a.k.a Case server) and to the IBM Counter Fraud Management components on the Messaging node (a.k.a. Core server). There are some updates to DB2 objects on the Data server. Page 5

11 Figure 4: IBM Knowledge Center - Upgrading Counter Fraud components 10.2 Preparations This section contains the instructions for preparing to install APAR PO All steps must be completed before proceeding to Section Creating new ICFM System Properties. Page 6

12 Identifying the IBM Case Manager Object Stores for Counter Fraud Use the Filenet Process Management Tool to identify the names of the IBM Case Manager Object Store for the Counter Fraud solution. Two object stores are updated: the Design Object Store and the Target Object Store. Before proceeding, verify that you have backup copies IBM Case Manager Design and Target Object Stores for Counter Fraud. These object stores are updated during this APAR installation procedure Verifying IBM Case Manager Fix Pack 6 installation On the Case & Analysis node Use the commands below to verify IBM Case Manager Fix Pack 6 is installed on the Case & Analysis node. Do NOT proceed if this fix pack is not installed. You must install IBM Case Manager Fix Pack 6 before installing IBM Counter Fraud Management APAR PO Log in or switch to account root. 2. Navigate to the IBM Case Manager path. > cd /opt/ibm/filenet/casemanagement/swidtag 3. Search for IBM swidtag files. > find. -type f -name ibm.com* swidtag -print Figure 5: Search for IBM Case Manger Fix Pack tag files Note: There is a high probability that the IBM Counter Fraud Management WebSphere plugin configuration file has been altered during the ICM Fix Pack 6 installation. This problem was reported under the Known Issues heading earlier in this document. Refer to Known Issues section to resolve this problem before proceeding to the next step Verifying IBM Content Platform Engine Fix Pack 6 installation On the ICFM Tools client 1. Open a web browser If the web browser is configured to use the Counter Fraud Management Systems V page for its default page, then under the heading Case Manager (CM), select the link IBM Content Platform Engine (Ping Page). Otherwise enter the following URL in the browser: Figure 6: Content Engine Startup Content (Ping Page) Page 7

13 2. If the results do not match, then you must install this fix pack before proceeding to the next step Creating a recovery point On the ICFM Linux servers 1. Log in or switch to the root account. 2. Open a terminal window. 3. Stop the IBM software products executing on the ICFM Linux servers using the IBM supplied automation scripts. Table 1: Stop IBM software products ICFM node ICFM ICFM host name Automation Command server script Decision and Scoring Identity iddn.icfm.ibm.com ibmcfmiddn service ibmcfmiddn stop Case and Analysis Case case.icfm.ibm.com ibmcfmcase service ibmcfmcase stop Messaging Core core.icfm.ibm.com ibmcfmcore service ibmcfmcore stop Data Data data.icfm.ibm.com ibmcfmdata service ibmcfmdata stop 4. Shutdown each ICFM Linux server. 5. Take a snapshot or create a backup copy of each ICFM Linux server. 6. Restart each ICFM Linux server. 7. Log in or switch to the root account. 8. Open a terminal window. 9. Restart the IBM software products on each of the ICFM Linux servers using the IBM supplied automation scripts. Table 2: Start IBM software products Page 8

14 ICFM node ICFM ICFM host name Automation Command server script Data Data data.icfm.ibm.com ibmcfmdata service ibmcfmdata start Messaging Core core.icfm.ibm.com ibmcfmcore service ibmcfmcore start Case and Analysis Case case.icfm.ibm.com ibmcfmcase service ibmcfmcase start Decision and Scoring Identity iddn.icfm.ibm.com ibmcfmiddn service ibmcfmidddn start On the ICFM Tools client 10. Log in using account icfmmgr. 11. Shutdown the Windows client Open a command window and enter: shutdown /s /t Take a snapshot. 13. Restart the ICFM Tools client Preparing the interim fix installation files On the ICFM Tools client 1. Log in using account icfmmgr. 2. Open a command window. 3. Change directory cd c:\temp 4. Download the APAR installation zip file Other-IBMCFM-Multi-PO06620.zip. 5. Create directory. mkdir c:\temp\ other-ibmcfm-multi-po Change directory. cd c:\temp\ other-ibmcfm-multi-po Extract the c:\temp\po06620\ other-ibmcfm-multi-po06620.zip to folder c:\temp\ other- IBMCFM-Multi-PO Open Windows Explorer and select Extract from the toolbar. Figure 7: Extract APAR PO06620 installation files Page 9

15 7.2. Specify the destination directory. Figure 8: Extract destination path Unzipping the supplemental files Supplemental files are provided for reference only. You may use them as templates for IBM Case Manager and IBM Counter Fraud Management configuration tasks. The supplemental files may require editing because their values may not be appropriate for your deployment. For example: you may have to change the host names, the network domain, the port number, the user account or password values. 1. Navigate to C:\temp\ Other-IBMCFM-PO Extract file 1505Supplemental-PO06620.zip in the current directory. 3. Rename directory 1505Supplemental-PO06620 to supplemental Transferring interim fix files to the CFM Linux servers Transfer the installation files from the ICFM Tools client to the Messaging node and the IDDN node to stage them on the local filesystem for use later by product specific installation and configuration tools for IBM WebSphere Application Server, IBM Case Manager and IBM Content Navigator. Refer to the table below. Before transferring any files to the target ICFM server, verify the target path exists for the specified user account. If the target path does not exist, then create it using the Linux mkdir tool. Table 3: File transfer destinations Page 10

16 Source path Source file name c:\temp\ other-ibmcfm-multi-po- 6620\CFM\Applications\CounterFraud_S MCEAR.ear c:\temp\ other-ibmcfm-multi- PO06620\CFM\Services\ CounterFraud_DataImportEAR.ear c:\temp\ other-ibmcfm-multi- PO06620\CFM\Services\ CounterFraud_DeployAgent_Cognos.ear c:\temp\ other-ibmcfm-multi- PO06620\CFM\Services\ CounterFraud_DeployAgent_SPSS.ear c:\temp\ other-ibmcfm-multi- PO06620\CFM\Services\ CounterFraud_Engine.ear c:\temp\ other-ibmcfm-multi- PO06620\CFM\Services\ CounterFraud_FactConfig.ear c:\temp\ other-ibmcfm-multi- PO06620\CFM\Services\ CounterFraud_PingEAR.ear c:\temp\ other-ibmcfm-multi- PO06620\CFM\Client\CFCaseMgmt\CFCas emgmtwidgets.zip\cfcasemgmtwidgets\ CFCaseMgmtWidgetsEAR.ear c:\temp\ other-ibmcfm-multi- PO06620\CFM\Client\CFCaseMgmt\CFCas emgmtrestear.ear c:\temp\ other-ibmcfm-multi- PO06620\CFM\Client\CFCaseMgmt\CFCas emgmteventhandler.zip c:\temp\ other-ibmcfm-multi- PO06620\CFM\Client\CFCaseMgmt\CFCas emgmtoperaton.zip c:\temp\ other-ibmcfm-multi- PO06620\CFM\Client\CFCaseMgmt\Count erfraud_smcplugin.jar Target server Core Core Core IDDN Core Core Core Core Core Case Case Case Target account: group wasmgr: wasmgr wasmgr: wasmgr wasmgr: wasmgr wasmgr: wasmgr wasmgr: wasmgr wasmgr: wasmgr wasmgr: wasmgr wasmgr: wasmgr wasmgr: wasmgr icfmmgr: icfmmteam icfmmgr: icfmmteam icfmmgr: icfmmteam Target path Target file name /icfmdata/home/wasmgr/ other- IBMCFM-Multi- PO06620/CounterFraud_SMCEAR.ear /icfmdata/home/wasmgr/ other- IBMCFM-Multi-PO06620/ CounterFraud_DataImportEAR.ear /icfmdata/home/wasmgr/ other- IBMCFM-Multi-PO06620/ CounterFraud_DeployAgent_Cognos.ear /icfmdata/home/wasmgr/ other- IBMCFM-Multi-PO06620/ CounterFraud_DeployAgent_SPSS.ear /icfmdata/home/wasmgr/ other- IBMCFM-Multi-PO06620/ CounterFraud_Engine.ear /icfmdata/home/wasmgr/ other- IBMCFM-Multi-PO06620/ CounterFraud_FactConfig.ear /icfmdata/home/wasmgr/ other- IBMCFM-Multi-PO06620/ CounterFraud_PingEAR.ear /icfmdata/home/wasmgr/ other- IBMCFM-Multi- PO06620/CFCaseMgmtWidgetsEAR.ear /icfmdata/home/wasmgr/ other- IBMCFM-Multi- PO06620/CFCaseMgmtRestEAR.ear /icfmdata/home/icfmmgr/ other- IBMCFM-Multi- PO06620/CFCaseMgmtEventHandler.zip /icfmmgr/home/icfmmgr/ other- IBMCFM-Multi-PO06620/ CFCaseMgmtOperaton.zip /icfmmgr/home/icfmmgr/ other- IBMCFM-Multi-PO06620/ CounterFraud_SMCPlugin.jar Backing up the IBM HTTPServer WebSphere plug-in configuration file On the Messaging node and the Decision & Scoring node 1. Log in or switch to account wasmgr. 2. Navigate to the WebSphere plugin configuration file. > cd /opt/ibm/websphere/plugins/config/corewebserver 3. Create a date stamped backup copy. > cp -p plugin-cfg.xml plugin-cfg.xml.backup-yyyymmdd 10.3 Creating new ICFM System Properties This procedure creates two IBM Counter Fraud Management Systems Properties: Page 11

17 1. CF.ICM.SYS.TMPDIR 2. CF.ICM.DATA.CASESearchStatus Creating CF.ICM.SYS.TMPDIR This procedure creates a temporary directory for the CFCaseMgmtRestAPI to store data retrieved from IBM Case Manager. On the Case & Analysis node 1. Log in or switch to account root. 2. Create the CFCaseManagementRestEAR temporary directory > mkdir -pv /icfmdata/websphere/appserver/profiles/cmprofile/tmpdir 3. Change ownership. > cd /icfmdata > chown -R wasmgr:icfmmteam WebSphere 4. Change permission for tmpdir. > cd /icfmdata/websphere/appserver/profiles/cmprofile > chmod 0775 tmpdir > ls -alsh tmpdir On the ICFM Tools client 5. Use the CFM Case Manager Client to add a System Property. This is the preferred method because the Case Manager Client automatically assigns the value for PROP_ID, schema and table name. The alternative (not shown in these instructions) is to use the IBM Data Studio data wizard to add an entry to CFCONFIG.SYSTEM_PROPS table in the CFDB database. The data wizard generates an SQL insert statement. 6. Open a web browser to launch the default page that is set to Counter Fraud Management Systems V Page 12

18 Figure 9: Launch CFM Case Manager Client 7. From the Counter Fraud Management System V launch page, select the CFM Case Manager Client. Figure 10: CFM Case Manager login page 7.1. Provide the User name value of filenet Provide the Password value Press the Login button. Page 13

19 Figure 11: CFM Case Client main page 8. From the left margin, select the icon for IBM Counter Fraud Management System Console Feature. On the resulting page, select the System Properties tab. Figure 12: CFM System Properties summary page 9. Press the Add button to launch the wizard to add a System Property Page 14

20 Figure 13: Add System Property page 10. From the table below, supply the values for the System Property attributes. Table 4: Add System Property values Attribute Name Description Stereotype Value Enable value encoding Value CFCaseMgmtRestEAR temporary directory CFCaseMgmtRestEAR temporary directory CF.ICM.SYS.TMPDIR /icfmdata/websphere/appserver/profiles/cmprofile/tmpdir No (do not select the check box) Note: The values for the path name was selected for consistency with the naming conventions for data and log files. The directory name maps to the stereotype. 11. Press the Add button. Figure 14:System Properties page Page 15

21 Creating CF.ICM.DATA.CaseSearchStatus This step is optional. If using the out-of-the-box Case Manager status values are acceptable, then skip this step. The CF.ICM.DATA.CaseSearchStatus system property value is a string of one or more Case Manager status codes. The status codes specified may be locally defined or a combination of locally defined and Case Manager out-of-the box status codes. The Counter Fraud Management application detects the presence of this system property and searches the string for a match during case selection. On the ICFM Tools client This procedure resembles the prior procedure so there are no screenshots. 1. Open a web browser to launch the default page that is set to Counter Fraud Management Systems V From the Counter Fraud Management System V launch page, select the CFM Case Manager Client. 3. Provide the User name value of filenet. 4. Provide the Password value. 5. Press the Login button. 6. From the left margin, select the icon for IBM Counter Fraud Management System Console Feature. On the resulting page, select the System Properties tab. 7. Press the Add button to launch the wizard to add a System Property. Figure 15: Add System Property page 8. From the table below, supply the values for the System Property attributes Table 5: Add System Property values Attribute Name Description Stereotype Value CaseSearchStatus CaseSearchStatus CF.ICM.DATA.CaseSearchStatus Page 16

22 Attribute Value Enable value encoding Value <any combination of out-of the box and local Case Manager status values.> Example: Initial, Triage, Open, Closed No (do not select the check box) 9. Press the Add button Changing CF.ICM.DATA.CaseSearchStatus The CF System Properties editor does not have edit in place capabilities. Delete the CF.ICM.DATA.CaseSearchStatus property. Then add the CF.ICM.DATA.CaseSearchStatus system property following the instructions in the prior step Create new J2C aliases This procedure creates two J2C aliases for secure network communications between IBM WebSphere applications and external enterprise applications. 1. CFM 2. CFMP Creating CFM On the ICFM Tools client Use the IBM WebSphere Administration Console to create J2C Alias CFM . 1. Open a web browser to launch the default page (previously shown) and select the link Core WebSphere Application Server Admin Console. 2. Log in with User ID: wasmgr and enter the password. Figure 16: WAS Global security page Page 17

23 3. Navigate to Security Global security. 4. Inside the Global security pane, under the Authentication heading, expand the twisty next to Java Authentication and Authorization Service. 5. Select the link J2C authentication data. Figure 17: JAAS - J2C authentication data 6. Press the New button to launch the wizard to add an alias. Figure 18: Create new J2C Alias page Page 18

24 7. Enter the attribute values from the table below. Table 6: J2C Alias attributes for CFM Attribute Alias User ID Password Description Value CFM filenet The default vale is CounterFraud1. Case Management Notification Service 8. Press the Apply button. Figure 19: Save new J2C Alias page Page 19

25 9. Press the Save link. The Global Security > JAAS J2C authentication data page is returned. There is a new row in the table for Alias CFM . Figure 20: Refreshed JAAS - J2C authentication data page Page 20

26 Creating CFMP8 On the ICFM Tools client Use the IBM WebSphere Administration Console to create J2C Alias CFMP8. This step is a continuation of the prior step that created J2C Alias CFM 1. Press the New button, to launch the wizard to create an alias. 2. Enter the attribute values from the table below. Table 7: J2C Alias attributes for CFMP8 Attribute Alias User ID Password Description Value CFMP8 filenet The default vale is CounterFraud1. Case Management Notification Service 3. Press the Apply button. 4. On the Global Security > JAAS J2C authentication data > CFMP8 page, press the Save link. Figure 21: Refreshed JAAS - J2C authentication data page Page 21

27 The Global Security > JAAS J2C authentication data page is returned. There is a new row in the table for Alias CFMP Configuring JAAS Application logins On the ICFM Tools client Use the IBM WebSphere Administration Console to configure JAAS Application logins. 1. Open a web browser to launch the default page (previously shown) and select the link Core WebSphere Application Server Admin Console. 2. Log in with User ID: wasmgr and enter the password. 3. Navigate to Security Global security. Page 22

28 Figure 22: WebSphere Global security page 4. Inside the Global security pane, under the Authentication heading, expand the twisty next to Java Authentication and Authorization Service. 5. Select the link J2C application login. Figure 23: WebSphere JAAS Applications logins page 6. Search Application logins table for entry CaseOperationsLogin If the entry exists, select the link and verify the settings If the entry does not exist, then you must create the entry. Page 23

29 Verifying CaseOperationsLogin properties 1. The entry in the table is the hypertext link, select it. Figure 24: CaseOperationsLogin properties page 2. The property values should match the entries in the table below. Table 8: CaseOperationsLogin properties JAAS Application login properties Alias CaseOperationsLogin JAAS login modules Module class name Authentication Strategy com.ibm.casemgmt.asa.ii.components.authentication.caseopsloginmodule Required 1 filenet.vw.server.vwloginmodule Required 2 3. There are two JAAS login modules in the table and their names also hypertext links to their respective properties page. 4. Select the hypertext link com.ibm.casemgmt.asa.ii.components.authentication.caseopsloginmodule. Module Order Page 24

30 Figure 25: comm.ibm.casemgmt.asa.ii... properties page 4.1. Verify the value for Module class name is com.ibm.casemgmt.asa.ii.components.authentication.caseopsloginmodule 4.2. Verify there is a check mark in the check box next to Use login module proxy 4.3. Verify the value for authentication strategy is REQUIRED Verify the entries in the Custom properties table. Table 9: com.ibm.casemgmt.asa.ii... Custom properties Name resturl ce_url debug Value true Note: The debug attribute value true enables debugging and it degrades performance. It is imperative that change this value to false after testing this APAR. 5. Return to the prior page and select the hypertext link filenet.vw.server.vwloginmodule. Page 25

31 Figure 26: filenet.vw.server.vwloginmodule properties page 5.1. Verify the value for Module class name is filenet.vw.server.vwloginmodule 5.2. Verify there is a no check mark in the check box next to Use login module proxy 5.3. Verify the value for authentication strategy is REQUIRED Verify the entries in the Custom properties table is empty Creating CaseOperationsLogin properties Use the alias names and properties reference in the prior section to create the CaseOperationsLogin alias Upgrading the Messaging node The Messaging node provides the run time environment for the Counter Fraud services applications that coordinate events and alerts between counter fraud components Upgrading the Counter Fraud services applications The following WebSphere J2EE applications are updated. 1. CounterFraud_Engine 2. CounterFraud_FactConfig 3. CounterFraud_Ping 4. CounterFraud_DataImportEAR 5. CounterFraud_DeployAgent_Cognos Upgrading the CounterFraud_Engine application 1. Navigate to the Enterprise Applications page. 2. Select CounterFraud_Engine. 3. Press the Update button to advance to the application update page. 4. Under Specify the EAR, WAR, JAR, RAR or SAR module to upload or install, ensure that the application to be updated is CounterFraud_Engine. 5. Select the Replace the entire application. 6. Ensure that the application to be updated refers to the CounterFraud_Engine. 7. Click Replace the entire application. 8. Under the heading Specify the path to the replacement ear file, select either Local file system or Remote file system. Page 26

32 8.1. The local file system path (where the web browser executes) is: c:\tmp\ other-ibmcfm-multi- PO06620\CFM\Services\ CounterFraud_Engine.ear 8.2. The remote file system path where a WAS node agent executes. If you select this options, press the browse button and select the WAS node where the APAR install files were placed and then navigate it to them Press the Next button to advance to the application update options page. 9. Select FAST PATH and press the Next button. 10. Press the Next button to advance past the Select installation options page. 11. On the Map module to servers page, select all of the modules. Then specify WebSphere:cell=CoreCell,node=CoreWebNode,server=CoreWebServer and WebSphere:cell=CoreCell,cluster=ICFMCluster. 12. Press the Apply button. 13. Verify all the entries in the check box are correct. 14. Press the Next button. 15. Review the entries on the Summary page and press the Finish button to update the ear file or the Previous button to correct any entries. 16. The replacement wizard creates an update log page. Review all messages written to this page. 17. Press the Save link to update the master configuration files and return to the Enterprise Applications page. 18. Select CounterFraud_Engine. 19. Press the Start button. Wait for the status icon to turn green Upgrading the CounterFraud_FactConfig application On the ICFM Tools client 1. Open the web browser and from the default page select the link for Core WebSphere Application Server Admin Console or enter URL: Login using account wasmgr. 2. Navigate to Applications Application Types WebSphere enterprise applications 3. Select the CounterFraud_FactConfig checkbox and press the Stop button. 4. After the service stops, select the CounterFraud_FactConfig checkbox and press the Export button. Save the exported CounterFraud_FactCong.ear file on the ICFM Tools client in directory c:\temp\ other- IBMCFM-Multi-PO06620/WAS-exports. Press the Back button. 5. Select the CounterFraud_FactConfig checkbox and press the Uninstall button followed by pressing the OK button and Save to master configuration link. 6. From the Enterprise application page, press the Install button Select the Local file system and then press the Browse button and navigate to c:\temp\ other- IBMCFM-Multi-PO06620\CFM\Services\CounterFraud_FactConfig.ear and press the Open button followed by the Next button Press the Next button twice to advance to the Map modules to servers panel. Page 27

33 Figure 27: Map modules for CounterFraud_FactConfig 6.3. Select the check boxes for all modules and in the Clusters and servers panel, select the deployment target values. WebSphere:cell=CoreCell,Node=CoreWebNode,server=CoreWebServer WebSphere:cell=CoreCell,cluster=CMCluster WebSphere:cell=CoreCell,cluster=ICFMCluster 6.4. Press the Apply button Press the Next twice and then press the Finish button Press the Save directly to master configuration. 7. Map the application defined roles to groups in the directory Navigate to Applications Application Types WebSphere enterprise applications Select CounterFraud_FactConfig Select Security role to user/group mapping Verify the entries resemble table below, then press the OK button. Table 10: User role to group mapping Role LDAP Group Administrator CFAdministrators Manager CFManagers Worker CFWorkers User CFUsers 8. Start the CounterFraud_FactConfig application Navigate to Applications Application Types WebSphere enterprise applications Select the check box next to CounterFraud_FactConfig Press the Start button Upgrading CounterFraud_PingEAR application 1. Navigate to the Enterprise Applications page. 2. Select CounterFraud_PingEAR. 3. Press the Update button to advance to the application update page. Page 28

34 4. Under Specify the EAR, WAR, JAR, RAR or SAR module to upload or install, ensure that the application to be updated is CounterFraud_PingEAR. 5. Select the Replace the entire application. 6. Ensure that the application to be updated refers to the CounterFraud_PingEAR. 7. Click Replace the entire application. 8. Under the heading Specify the path to the replacement ear file, select either Local file system or Remote file system The local file system path (where the web browser executes) is: c:\tmp\ other-ibmcfm-multi- PO06620\CFM\Services\ CounterFraud_PingEAR.ear 8.2. The remote file system path where a WAS node agent executes. If you select this options, press the browse button and select the WAS node where the APAR install files were placed and then navigate it to them Press the Next button to advance to the application update options page. 9. Select FAST PATH and press the Next button. 10. Press the Next button to advance past the Select installation options page. 11. On the Map module to servers page, select WebSphere:cell=CoreCell,node=CoreWebNode,server=CoreWebServer and WebSphere:cell=CoreCell,cluster=ICFMCluster. 12. Press the Apply button. 13. Verify the entries in the check box are correct. 14. Press the Next button. 15. Review the entries on the Summary page and press the Finish button to update the ear file or the Previous button to correct any entries. 16. The replacement wizard creates an update log page. Review all messages written to this page. 17. Press the Save link to update the master configuration files and return to the Enterprise Applications page. 18. Select CounterFraud_PingEAR. 19. Press the Start button. Wait for the status icon to turn green Upgrading CounterFraud_DataImportEAR application 1. Navigate to the Enterprise Applications page. 2. Select CounterFraud_DataImportEAR. 3. Press the Update button to advance to the application update page. 4. Under Specify the EAR, WAR, JAR, RAR or SAR module to upload or install, ensure that the application to be updated is CounterFraud_DataImportEAR. 5. Select the Replace the entire application. 6. Ensure that the application to be updated refers to the CounterFraud_DataImportEAR. 7. Click Replace the entire application. 8. Under the heading Specify the path to the replacement ear file, select either Local file system or Remote file system The local file system path (where the web browser executes) is: c:\tmp\ other-ibmcfm-multi- PO06620\CFM\Services\ CounterFraud_DataImportEAR.ear 8.2. The remote file system path where a WAS node agent executes. If you select this options, press the browse button and select the WAS node where the APAR install files were placed and then navigate it to them Press the Next button to advance to the application update options page. 9. Select FAST PATH and press the Next button. 10. Press the Next button to advance past the Select installation options page. 11. On the Map module to servers page, select WebSphere:cell=CoreCell,cluster=DataCluster. 12. Press the Apply button. 13. Verify the entries in the check box are correct. 14. Press the Next button. 15. Review the entries on the Summary page and press the Finish button to update the ear file or the Previous button to correct any entries. 16. The replacement wizard creates an update log page. Review all messages written to this page. Page 29

35 17. Press the Save link to update the master configuration files and return to the Enterprise Applications page. 18. Select CounterFraud_DataImportEAR. 19. Press the Start button. Wait for the status icon to turn green Upgrading CounterFraud_DeployAgent_Cognos application 1. Navigate to the Enterprise Applications page. 2. Select CounterFraud_DeployAgent_Cognos. 3. Press the Update button to advance to the application update page. 4. Under Specify the EAR, WAR, JAR, RAR or SAR module to upload or install, ensure that the application to be updated is CounterFraud_DeployAgent_Cognos 5. Select the Replace the entire application. 6. Ensure that the application to be updated refers to the CounterFraud_DeployAgent_Cognos. 7. Click Replace the entire application. 8. Under the heading Specify the path to the replacement ear file, select either Local file system or Remote file system The local file system path (where the web browser executes) is: c:\tmp\ other-ibmcfm-multi- PO06620\CFM\Services\ CounterFraud_DeployAgent_Cognos.ear 8.2. The remote file system path where a WAS node agent executes. If you select this options, press the browse button and select the WAS node where the APAR install files were placed and then navigate it to them Press the Next button to advance to the application update options page. 9. Select FAST PATH and press the Next button. 10. Press the Next button to advance past the Select installation options page. 11. On the Map module to servers page, select WebSphere:cell=CoreCell,node=CoreWebNode,server=CoreWebServer and WebSphere:cell=CoreCell,cluster=CognosGWCluster. 12. Press the Apply button. 13. Verify the entries in the check box are correct. 14. Press the Next button. 15. Review the entries on the Summary page and press the Finish button to update the ear file or the Previous button to correct any entries. 16. The replacement wizard creates an update log page. Review all messages written to this page. 17. Press the Save link to update the master configuration files and return to the Enterprise Applications page. 18. Select CounterFraud_DeployAgent_Cognos. 19. Press the Start button. Wait for the status icon to turn green Upgrading the Decision and Scoring node The following WebSphere J2EE applications are updated: 1. CounterFraud_DeployAgent_SPSS Upgrading CounterFraud_DeployAgent_SPSS application On the Decision and Scoring node 1. From the Counter Fraud Management System V launch page, select the IDD WebSphere Application Server Admin Console. Page 30

36 Figure 28: IBM Counter Fraud Management launch page If you do not use the launch pages, then open a web browser and enter: 2. Log in with User ID: wasmgr and supply the password value. 3. Navigate to Applications Application Types WebSphere enterprise applications. Figure 29:IDDN WebSphere enterprise applications page Page 31

37 Figure 30: Decision and Scoring node enterprise applications page 4. Select the enterprise applications. 5. Select CounterFraud_DeploymentAgent_SPSS 6. Select EXPORT to export a backup copy of the current version for each file of the three ear files, to the local file system where the web browser was launched. In this scenario, it is the local file system of the ICFM Tools client. 7. In the pop-up window, select the link to download the EAR file to the ICFM Tools Windows Client Create a new directory call zbackup under c:\temp\po Save each exported ear file to c:\temp\po06620\zbackup 8. Press the Back button to return to the Enterprise Applications page. 9. Select the enterprise applications. 10. Select CounterFraud_DeployAgent_SPSS. 11. Press the Stop button and wait for the Application Status icon to turn red for each selected application. 12. Select CounterFraud_DeployAgent_SPSS.ear. 13. Press the Update button to advance to the application update page. 14. Under Specify the EAR, WAR, JAR, RAR or SAR module to upload or install: 15. Ensure that the application to be updated is CounterFraud_DeployAgent_SPSS.ear. 16. Click Replace the entire application. 17. Under the heading Specify the path to the replacement ear file, select either Local file system or Remote file system The local file system path (where the web browser executes) is: c:\tmp\ other-ibmcfm-multi- PO06620\CFM\Server\CounterFraud_DeployAgent_SPSS.ear The remote file system path where a WAS node agent executes. If you select this options, press the browse button and select the WAS node where the APAR install files were placed and then navigate it to them Press the Next button to advance to the application update options page. 18. Select FAST PATH and press the Next button. 19. Press the Next button to advance past the Select installation options page. 20. On the Map module to servers page, select WebSphere:cell=IddnCell,node=IddnWebNode,server=IddnWebServer and WebSphere:cell=IddnCell,cluster=SPSS. 21. Press the Apply button. 22. Verify the entries in the check box are correct. Page 32

38 23. Press the Next button. 24. Review the entries on the Summary page and press the Finish button to update the ear file or the Previous button to correct any entries. 25. Select the Save directly to master configuration. 26. Select CounterFraud_DeployAgent_SPSS and press the Start button Upgrading the Case & Analysis node Before proceeding, we recommend you review the instructions in the IBM Counter Fraud Management Knowledge Center for Upgrading the Case & Analysis node. The URL to the external IBM Knowledge Center is: The URL to the Internal IBM Knowledge Center is: Search for the topic Upgrading the Case & Analysis node. Change the viewing mode to Show in Table of Contents. Figure 31: IBM Knowledge Center - Upgrading Case & Analysis node. The instructions that follow make frequent references to the topics in the IBM Knowledge Center. This APAR adds steps that are not in the Knowledge Center. Below is the revised installation procedure for Upgrading the Case & Analysis node. Page 33

39 Upgrading the Counter Fraud Case Management plug-in Overview: 1. Uninstalling the Counter Fraud Case Manager plug-in. 2. Upgrading the Counter Fraud Case Management REST application. 3. Upgrading the Counter Fraud Case Management widgets Upgrading the Counter Fraud Case Manager-plugin On the ICFM Tools client 1. Open the web browser and from the default page select the link for IBM Case Manager Administrative Desktop or enter URL: 2. Follow the instructions in the Knowledge Center to use the IBM Content Navigator remove the Counter Fraud Case Management plug-in from the Case Management Design Object Store Upgrading Counter Fraud Case Management Rest application On the Case & Analysis node Backup the following CFCaseMgmtRest application configuration files because they will be restored later in this procedure. 1. configuration.properties 2. NotificationService.propeties 3. log4j.xml 1. Switch or log in using account wasmgr. 2. Navigate to the directory containing the files. > cd /opt/ibm/websphere/applicationserver/profiles/cmprofile/installedapps/corecell > cd CFCaseMgmtRestEAR.ear/CFCaseMgmtRest.war/WEB-INF > mkdir /tmp/po06620 > cp -p log4j.xml /tmp/po06620/log4j.xml > cd classes > cp -p configuration.properties /tmp/po06620/configuration.properties > cp -p NotificationService.properties /tmp/po06620/notificationservice.properties On the ICFM Tools client 3. Open the web browser and from the default page select the link for Core WebSphere Application Server Admin Console or enter URL: 4. Login using account wasmgr. 5. Navigate to Applications Application Types WebSphere enterprise applications 6. Select the CFCaseMgmtRestEAR checkbox and press the Stop button. 7. After the service stops, select the CFCaseMgmtRestEAR checkbox and press the Export button Save the exported CFCaseMgmtEAR.ear file on the ICFM Tools client in directory c:\temp\ other- IBMCFM-Multi-PO06620/WAS-exports. Press the Back button. 8. Replace the CFCaseMgmtRestEAR application Select the CFCaseMgmtRestEAR checkbox and press the Update button Press the Browse button to specify the path to the replacement EAR file Enter the path: c:\temp\ other-ibmcmf-multi- PO06620\CFM\Client\CFCaseMgmt\CFCaseMgmtRestEAR.ear 8.2. Press the Next button twice to advance to the Map modules to servers panel. Page 34

40 Figure 32:Manage Modules page for CFRestEAR.ear Select the CFCaseMgmtRest module check box In the Clusters and servers panel, select the deployment target values. WebSphere:cell=CoreCell,Node=CoreWebNode,server=CoreWebServer WebSphere:cell=CoreCell,cluster=CMCluster 8.3. Press the Next twice and then press the Finish button Press the Save directly to master configuration Upgrading the Counter Fraud Case Management widgets This APAR contains updated Counter Fraud Case Management widget files. The instructions to update the Counter Fraud Case Management widgets are provided in the IBM Knowledge Center for Counter Fraud Management The URL to the external IBM Knowledge Center is: The URL to the Internal IBM Knowledge Center is: Search for the topic Upgrading Counter Fraud Case Management widgets. On the Case & Analysis node 1. Login or switch to account root. 2. Search the file system for all instances of CFCaseMgmtWidgets.zip. > find / -type f -name CFCaseMgmtWidgets.zip -print Page 35

41 Figure 33: CFCaseMgmtWidgets.zip search results 3. Replace CFCaseMgmtWidgets.zip in /opt/ibm/cfmdeveloperbucket Create a date stamped backup by renaming file CFCaseMgmtOperation.zip > cd /opt/ibm/cfmdeveloperbucket > mv -f CFCaseMgmtWidgets.zip CFCaseMgmtWidgets.zip.backup-yyyymmdd 3.2. Copy the replacement CFCaseMgmtWidgets.zip file from the staging directory to the target directory. > cp -p /icfmdata/home/icfmmgr/ other-ibmcfm-multi-po06620/cfcasemgmtwidgets.zip /opt/ibm/cfmdeveloperbucket 3.3. Set the file ownership and file permission attributes. > chown icfmmgr:icfmteam CFCaseMgmtWidgets.zip > chmod 0644 CFCaseMgmtWidgets.zip 4. Replace CFCaseMgmtWidgets.zip in /opt/ibm/icfm 4.1. Create a date stamped backup by renaming directory CFCaseMgmtWidgets and file CFCaseMgmtOperation.zip. > cd /opt/ibm/icfm > mv CFCaseMgmtWidgets CFCaseMgmtWidgets.backup-yyyymmdd > mv -f CFCaseMgmtWidgets.zip CFCaseMgmtWidgets.zip.backup-yyyymmdd 4.2. Copy the replacement CFCaseMgmtWidgets.zip file from the staging directory to /opt/ibm/icfm > cp -p /icfmdata/home/icfmmgr/ other-ibmcfm-multi-po06620/cfcasemgmtwidgets.zip /opt/ibm/icfm 4.3. Set the file ownership and file permission attributes. > chown icfmmgr:icfmteam CFCaseMgmtWidgets.zip > chmod 0644 CFCaseMgmtWidgets.zip 4.4. Unzip CFCaseMgmtEventHandler.zip into directory /opt/ibm/icfm/cfcasemgmtwidgets. > unzip CFCaseMgmtEventHandler.zip -d /opt/ibm/icfm/cfcasemgmtwidgets 4.5. Set the file ownership and file permission attributes. > cd /opt/ibm/icfm/cfcasemgmtwidgets > ls -alsh CFCaseMgmtWidgets > chown -R icfmmgr:icfmmteam /opt/ibm/icfm/cfcasemgmtwidgets > chmod 644 CFCaseMgmt*ar > ls -alsh Page 36

42 Figure 34: CFCaseMgmtWidgets directory contents On the ICFM Tools client 5. Extract in place c:\temp\ other-ibmcfm-multi- PO06620\CFM\Client\CFCaseMgmt\CFCaseMgmtWidgets.zip. The extract creates a new directory c:\temp\ other-ibmcfm-multi- PO06620\CFM\Client\CFCaseMgmt\ CFCaseMgmtWidgets. The files in this directory will be used later in this procedure to install CFCaseMgmtWidgetsEAR.ear using the WebSphere Integrated Solutions Console Create a new directory for storing WebSphere Enterprise Applications that are exported using the WebSphere Integrated Systems Console. > Open a command window. > mkir c:\temp\ other-ibmcfm-mulit-po06620\was-exports > exit 6. ICFM Knowledge Center step 2: Open a web browser use this URL to bypass the IBM HTTPServer WAS plugin and launch the IBM Case Manager Administration Client Log in with user account filenet and supply the password value. 7. ICFM Knowledge Center step 3: Navigate to Object Stores Design Object Store Widget Packages. Page 37

43 Figure 35: IBM Case Manager Widget Packages page If there is an entry in the table for the IBM Counter Fraud Widget Package, then follow the steps below to remove the IBM Counter Fraud Widget Package Select the row containing the information for the IBM Counter Fraud Management Widget package From the Action pulldown menu, select Delete Custom Widgets From the Delete Custom Widgets page, press the Finish button to confirm the removal of this custom widgets package From the refreshed Delete Custom Widgets page, verify the package was removed and press the Close button. 8. ICFM Knowledge Center step 4: press the Import Custom Widget button. Figure 36: Import custom widgets page 8.1. Press the Browse button to navigate and select file c:\temp\ other-ibmcfm-multi- PO06620\CFM\Client\CFCaseMgmt\CFCaseMgmtWidgets.zip Press the Next button to proceed to the page to verify the selection. Page 38

44 Figure 37: Verify import package selection page 9. ICFM Knowledge Center step 5: Accept the default options for Replace if already imported and Register custom widgets package. Press the Finish button. Figure 38: Import widgets package results page 9.1. Verify the widgets package was added and press the Close button to return to the Widgets packages page Log off. 10. ICFM Knowledge Center step 6: open a web browser and select from the Counter Fraud Management Systems V page, Core WebSphere Application Server Admin Console Log in with account wasmgr and provide the password value. Page 39

45 11. ICFM Knowledge Center step 7: navigate to Applications Application Types WebSphere enterprise applications. 12. ICFM Knowledge Center step 8: select CFCaseMgmtWidgetsEAR and press the Stop button. 13. ICFM Knowledge Center step 9: select the CFCaseManagementWidgetsEAR entry and press the Export button To download, select CFCaseMgmtWidgetsEAR.ear A pop window appears. Select the Save File radio button and press the OK button Navigate to c:\temp\ other-ibmcfm-multi-po06620\was-exmorts and press the Save button Press the Back button. 14. ICFM Knowledge Center step 10: uninstall the CFCaseMgmtWidgetsEAR application Press Save to update the master configuration. 15. ICFM Knowledge Center step 11: install the CFCaseMgmtWidgetsEAR application From the Enterprise application page, press the Install button Select the Local file system and then press the Browse button and navigate to c:\temp\ other- IBMCFM-Multi-PO06620\CFM\Client\CFCaseMgmt\CFCaseMgmtWidgetsEAR.ear and press the Open button followed by the Next button Press the Next button twice to advance to the Map modules to servers panel Select the check boxes for all modules and in the Clusters and servers panel, select the deployment target values. WebSphere:cell=CoreCell,Node=CoreWebNode,server=CoreWebServer WebSphere:cell=CoreCell,cluster=CMCluster Press the Next twice and then press the Finish button Press the Save directly to the master configuration. 16. Press the Save directly to master configuration. 17. Select CFCaseMgmtWidgetsEAR. 18. Press the Start button. Wait for the status icon to turn green Upgrading the Counter Fraud Systems Management Console The Counter Fraud Systems Management Console feature has two main components. An IBM Case Navigator plugin: CounterFraud_SMC.jar A WebSphere Enterprise Application: CounterFraud_SMCEAR.ear Upgrading the SMC plug-in This APAR contains updated Counter Fraud System Management Console plug-in. The instructions are provided in the IBM Knowledge Center for Counter Fraud Management The URL to the external IBM Knowledge Center is: The URL to the Internal IBM Knowledge Center is: Search for the topic Upgrading the Counter Fraud System Management Console. Follow the instructions in the Knowledge Center to use IBM Content Navigator to replace the existing plug-in. Page 40

46 Upgrading CounterFraud_SMCEAR application 1. Navigate to the Enterprise Applications page. 2. Select CounterFraud_SMCEAR. 3. Press the Update button to advance to the application update page. 4. Under Specify the EAR, WAR, JAR, RAR or SAR module to upload or install, ensure that the application to be updated is CounterFraud_SMCEAR. 5. Select the Replace the entire application. 6. Ensure that the application to be updated refers to the CounterFraud_SMCEAR. 7. Click Replace the entire application. 8. Under the heading Specify the path to the replacement ear file, select either Local file system or Remote file system The local file system path (where the web browser executes) is: c:\tmp\ other-ibmcfm-multi- PO06620\CFM\Applications\ CounterFraud_SMCEAR.ear 8.2. The remote file system path where a WAS node agent executes. If you select this options, press the browse button and select the WAS node where the APAR install files were placed and then navigate it to them Press the Next button to advance to the application update options page. 9. Select FAST PATH and press the Next button. 10. Press the Next button to advance past the Select installation options page. 11. On the Map module to servers page: Select the check boxes for all modules In the Clusters and servers panel, select the deployment target values. WebSphere:cell=CoreCell,cluster=CMCluster WebSphere:cell=CoreCell,node=CoreWebNode,server=CoreWebServer Press the Apply button. 12. Press the Next button twice and the Finish button. 13. Press the Save directly to master configuration. 14. Select the check box next to CounterFraud_SMCEAR and press the Start button Upgrading the Counter Fraud Case Manager Component Manager This procedure is required because APAR PO06620 contains updated files in the CFCaseMgmtOpertion.zip file for the Component Manager. The URL to the external IBM Knowledge Center is: The URL to the Internal IBM Knowledge Center is: Search for the topic Configuring the Component Manager. On the Case & Analysis node 1. Log in or switch to account root. 2. Search the filesystem for all instances CFCaseMgmtOperation.zip. > find / -type f -name CFCaseMgmtOperation.zip -print Page 41

47 Figure 39: CFCaseMgmtOperation.zip search results 3. Replace the files in the IBM Counter Fraud Management directory Navigate to the target directory /opt/ibm/icfm > cd /opt/ibm/icfm 3.2. Create a date stamped backup by renaming file CFCaseMgmtOperation.zip > mv -f CFCaseMgmtOperation.zip CFCaseMgmtOperation.zip.backup-yyyymmdd 3.3. Copy the replacement CFCaseMgmtOperation.zip file from the staging directory to /opt/ibm/icfm > cp /icfmdata/home/icfmmgr/ other-ibmcfm-multi-po06620/cfcasemgmteventhandler.zip /opt/ibm/icfm 3.4. Set the file ownership and file permission attributes. > chown icfmmgr:icfmmteam CFCaseMgmtOperation.zip > chmod 0644 CFCaseMgmtOperation.zip 4. Replace the component manager directory Rename component manager directory. > cd /opt/ibm/icfm > mv compmgr compmgr.backup-yyyymmdd 4.2. Create a new component manager directory and set the ownership attributes. > mkdir compmgr > chown icfmmgr:icfmgr compmgr 4.3. Unzip the CFCaseMgmtOperaton.zip file into the component manager directory. > cd /opt/ibm/icfm > unzip CFCaseMgmtOperaton.zip -d /opt/ibm/icfm/compmgr 4.4. Set the file ownership and file permission attributes. > chown -fr icfmmgr:icfmmteam /opt/ibm/icfm/compmgr 5. Replace the Component Manager s log4j.xml file with the supplemental versions file shipped with APAR. The supplement version log4j.xml places file CFCaseMgmtOperation.log in the same directory where the other IBM Case Management log files reside. The directory path is: /icfmlog/filenet/casemanager/logs Log in or switch to account icfmmgr Navigate to the target directory. > cd /opt/ibm/icfm/compmgr/config 5.3. Rename the original log4j.xml file. > mv log4j.xml log4j.xml.original Page 42

48 5.4. Use a file transfer tool to load the designated supplemental files distributed with this APAR that reside on the ICFM Tools client. Table 11: Supplemental file transfer parameters Source Target Source Target File 01 = log4j.xml c:\temp\ other-ibmcfm\multi-po06620\supplemental\ config\1505supplementalcompmgr-log4j.xml /opt/ibm/icfm/compmgr/config/1505supplemental-compmgr-log4j.xml File 02 = taskman.properties c:\temp\ other-ibmcfm\multi-po06620\supplemental\ config\1505supplementaltaskman.properties /opt/ibm/filenet/webclient/router/1505supplemental-taskman.properties 5.5. Rename file 1505Supplemental-compmgr-log4j.xml, reformat it for Linux, set file owner ship and file permission. > mv 1505Supplemental-compmgr-log4j.xml log4j.xml > dos2unix log4j.xml > chown icfmmgr:icfmmteam log4j.xml > chmod 0644 log4j.xml Note: The new log4j.xml places file CFCaseMgmtOperation.log in the same directory where the other IBM Case Management log files reside. The directory path is: /icfmlog/filenet/casemanager/logs Navigate to the log file directory and create CFCaseMgmtOperations.log. > cd /icfmlog/filenet/casemanager/logs > /bin/touch CFCaseMgmtOperations.log 5.7. Set the file ownership and file permission attributes. > chown icfmmgr:icfmmteam CFCaseMgmtOperations.log > chmod 0664 CFCaseMgmtOperations.log 6. There is no need to replace /opt/ibm /FileNet/WebClient/Router/taskman.login.config. The existing file contains the required statements. 7. Replace the taskman properties file because it does not have the Component Manager Java runtime files Create a date stamped backup of taskman.properties. > cd /opt/ibm/filenet/webclient/router > cp -p taskman.properties taskman.properties.backup-yyyymmdd 7.2. Rename file 1505Supplemental-compmgr-log4j.xml, reformat it for Linux, set file ownership and file permission. > mv 1505Supplemental-taskman.properties > dos2unix taskman.properties > chmod 0644 taskman.properties 8. Follow the instructions in the IBM Counter Fraud Management Knowledge Center to complete this procedure. This procedure requires: Page 43

49 8.1. Execution under the root account A graphical user interface (X-widows). Figure 40: IBM Knowledge Center bread crumbs to Configuring the Component Manager On the ICFM Tools client 9. Launch the VNC Viewer and select the connection to the Case & Analysis node The VNC Viewer connection is configured to communicate with the Case & Analysis node through TCP port The VNC Server on the ICFM Case & Analysis node is configured to assign the root account to TCP port If the VNC Server on the ICFM Case & Analysis node presents a password challenge, you must enter the root account s password From the VNC Viewer, the graphical Linux desktop for the root account is visible Open a terminal session. 10. ICFM Knowledge Center step 4: start the Component Manager (PTM = Process Task Manager) Navigate to the runtime directory and start the Component Manager. > cd /opt/ibm/filenet/webclient/router > /opt/ibm/filenet/webclient/router/routercmd.sh 11. ICFM Knowledge Center step 5: verify the Content Engine URI and Service user are correct. 12. Delete the CFM.CaseMgmtOperations component manager because the Component Manager configuration files are out of date. Page 44

50 Figure 41: Delete Component Manager queue 13. ICFM Knowledge Center step 6: Create the CFM.CaseMgmtOperations component manager. 14. ICFM Knowledge Center step 7: Create the CFCaseMgmtOperations component queue. 15. Skip ICFM Knowledge Center step 8: Add Required Libraries. The libraries were updated earlier in this procedure when the 1505Supplemental-taskman.properties file was renamed to taskman.properties. 16. ICFM Knowledge Center step 9: verify the Java Security properties are correct and press the Apply button. 17. ICFM Knowledge Center step 10: start the Component Manager Page 45

51 Figure 42: CFCaseMgmtOperations Component Manager and queue Upgrading the Counter Fraud Notification Service On the Case & Analysis node This procedure replaces the password values from the NotificationService.properties file with the previously created J2C Aliases. It also updates the Counter Fraud applications that use the Notification Service to use the J2C Aliases. The following properties are removed from the NotificationServices.properties file. p8_login_user=<adminuser> p8_login_password=<password> _LOGON_ID= _LOGON_PASSWORD= The replacement properties added by this PMR are: p8_alias=cfmp8 _ALIAS=CFM The values assigned to these properties are the default names for the J2C Aliases that must be created for the Case & Analysis node. You may use alternative names but their use requires updates to the NotificationService.properties file. 1. If you have not created the two new J2C aliases following the instructions in a previous section of this document, then you must create them now. The aliases must exist before updating the NotificationService.properties file. 2. Log in or switch to account root. 3. Search the filesystem for all instances NotificationService.properties. Page 46

52 > find / -type f -name NotificationService.properties -print Figure 43: NotificationService.properties search results 4. Update /opt/ibm 4.1. Change to the target directory. > cd /opt/ibm 4.2. Create a date stamped backup by renaming file NotificationServices.properties. > mv -f NotificationServices.properties to NotificationServices.properties.backup-yyyymmdd 4.3. Use a file transfer too to load the replacement NotificationServices properties from the APAR installation media located on the ICFM Tools Client in folder C:\temp\ Other-IBMCFM-Multi- PO06620\CFM\Client\CFCaseMgmt. 5. Update /opt/ /CFCaseMgmtRest.war/WEB-INF/Classes Change to the target runtime directory. > cd /opt/ibm/websphere/appserver/profiles/cmprofile/installedapps/corecell/ CFCaseMgmtRestEAR.ear/CFCaseMgmtRest.war/WEB_INF/classes NotificationService.properties 5.2. Create a date stamped backup by renaming file NotificationService.properties > mv -f NotificationService.properties NotificationService.properties.backup-yyyymmdd 5.3. Use a file transfer tool to load the replacement NotificationServices.properties file from the APAR installation media located on the ICFM Tools client in folder C:\temp\ Other-IBMCFM-Multi- PO06620\CFM\Client\CFCaseMgmt. 6. Update /opt/ibm/websphereappserver/profiles/cmprofiles/properties 6.1. Change to the target runtime directory. > cd /opt/ibm/websphereappserver/profiles/cmprofile/properties 6.2. Create a date stamped backup by renaming file NotificationService.properties > mv -f NotificationService.properties NotificationService.properties.backup-yyyymmdd 6.3. Use a file transfer tool to load the replacement NotificationServices.properties file from the APAR installation media located on the ICFM Tools client in folder C:\temp\ Other-IBMCFM-Multi- PO06620\CFM\Client\CFCaseMgmt. Page 47

53 10.9 Upgrading CFCaseMgmtEventHandler This APAR contains updated Counter Fraud Case Management event handler files. The instructions to update the Counter Fraud Case Management Event Handler are provided in the IBM Knowledge Center for Counter Fraud Management The URL to the external IBM Knowledge Center is: The URL to the Internal IBM Knowledge Center is: Search for the topic Upgrading the Intelligent Investigation event handler. On the Case & Analysis node 1. Login or switch to account root. 2. Search the file system for all instances of CFCaseMgmtEventHandler. > find / -type f -name CFCaseMgmtEventHandler* -print Figure 44: CFCaseMgmtEventHandler search results 3. Rename the zip file and the event subdirectory under /opt/ibm/icfm. > cd /opt/ibm/icfm > mv CFCaseMgmtEventHandler.zip CFCaseMgmtEventHandler.zip.backup-yyyymmdd > mv event event.backup-yyyymmdd 4. Copy the replacement CFCaseMgmtEventHandler.zip file from the staging directory to /opt/ibm/icfm > cp /icfmdata/home/icfmmgr/ other-ibmcfm-multi-po06620/cfcasemgmteventhandler.zip /opt/ibm/icfm 5. Unzip CFCaseMgmtEventHandler.zip into the directory /opt/ibm/icfm/cfmcasemgmteventhandler. > unzip CFCaseMgmtEventHandler.zip -d /opt/ibm/icfm/cfcasemgmteventhandler > ls -alsh /opt/ibm/icfm/cfcasemtmteventhandler Page 48

54 Figure 45: CFCaseMgmtEventHandler directory contents On the ICFM Tools client 6. Extract all the files in c:\temp\ other-ibmcfm-multi- PO06620\CFM\Client\CFCaseMgmt\CFCaseMgmtEventHandler.zip. The extract creates a new directory CFCaseMgmtEventHandler. The files in this directory will be used later in this procedure. 7. Open a web browser use this URL to bypass the IBM HTTPServer WAS plugin and launch the Administration Console for Content Engine (ACCE): 8. Log in with user account filenet and supply the password value. 9. Navigate to Object Stores TARGET Browse Code Modules. Figure 46: TARGET object store contents 10. From the table, select the entry for Containment Name CmAcmEventHandler. Page 49

55 Figure 47: CmAcmEventHandler page 11. Select the Actions tab and from the pulldown menu select Checkin, checkout, cancel and then select Exclusive Checkout. Figure 48: Exclusive checkout dialog box 12. In the Exclusive Checkout document dialog box, select CFCaseMgmtEventHandler and press the Checkout button. 13. Select the Actions tab and from the pulldown menu select Checkin, checkout, cancel and then select Checkin. Figure 49: Check In Document dialog box Page 50

56 14. Use the Add button to add the jar files from the directory c:\temp\ other-ibmcfm-multi- PO06620\CFM\Client\CFCaseMgmt\CFCaseMgmtEventHandler Select file CFCaseMgmtEventHandler.jar and press the Add Content button Select file commons-pool jar and press the Add Content button Select file JSON4J_Apache.jar and press the Add Content button. 15. Select the check box next to Update all Action class instances that reference earlier version of this Code Module class. 16. Press the Check In Major Version button. 17. Close the CMAsaEventHandler tab. 18. Press the Refresh button under the CodeModules tab. Figure 50: Updated CodeModules table Page 51

57 18.1. Review the table entry for CMAsaEventHandler. Notice the Date Created value is the current date and the Version number increased. 19. Close the CodeModules tab Replacing the Counter Fraud Case Management solution Before proceeding, we recommend you review the instructions in the IBM Counter Fraud Management Knowledge Center for Replacing the Counter Fraud Case Management Solution. The URL to the external IBM Knowledge Center is: The URL to the Internal IBM Knowledge Center is: Search for the topic Replacing the Counter Fraud Case Management Solution. Change the viewing mode to Show in Table of Contents. Figure 51: Replacing the Counter Fraud Case Management Solution Removing the solution template Create a backup copy solution Counter Fraud Alert 1. From the Counter Fraud Management System V launch page, select IBM Case Manager Builder or enter 2. Login in using account FileNet. 3. Select solution Counter Fraud Alert. 4. From the grey bar at the bottom of the tile, select Copy. Page 52

58 Figure 52: Copy a solution page Table 12: Copy a solution attributes Attribute Name Solution prefix Description Validate solution before copying Value Backup Counter Fraud Alert APAR APAR PO06620 backup copy of Counter Fraud Alert before replacing it Check mark in the box 5. Supply the values in the pop-up window and press the OK button. Page 53

59 Figure 53: Updated Manage Solutions page 1. From the default home page, select IBM Case Manager Administration Desktop or enter Log in using account filenet and supply the password. 2. Navigate to CFM Object Stores DESIGN Solution Templates. Figure 54: IBM Case Manager DESIGN Solution Template page 3. If the solution template exists, select Counter Fraud solution template and the Action button. From the pulldown menu, select Delete. 4. Verify the correct template is selected and press Finish Importing the Counter Fraud case management solution 1. From the default home page, select IBM Case Manager Administration Desktop or enter Page 54

60 1.1. Log in using account filenet and supply the password. 2. Navigate to CFM Object Stores DESIGN Solutions press Import. 3. From the pulldown menu, select Import Solution and From Solution Package. 4. Press Browse and navigate to the solution template file distributed with this APAR. The should be C:\temp\ Other-IBMCFM-Multi-PO06620\CFM\Client\CFCaseMgmt Solution\Counter_Fraud_Altert_Management_solution.zip. Press Next. 5. Select the Continue if solution exists check box if applicable. 6. For each Mapping service, change the Target Value URL prefix to the correct protocol, host name and port number for the deployment environment. The table below provides guidance. Table 13: Solution template import URL prefix values Mapping Mapping Service Source Value for Name Service 1 12MonthAssessmentSummary.WebSiteDisplayer0. default.websitedisplayerurl 2 AnalysisFlowDashboard.WebSiteDisplayer4.default.webSisteDisplayerUrl 3 AssessmentActivityDashboard.WebSiteDisplayer0. default.websitedisplayerurl 4 AssessmentResultsDashboard.WebSiteDisplayer1.d efault.websitedisplayerurl 5 AssessmentTrendsDashboard.WebSiteDisplayer2.d efault.websitedisplayerul 6 AssessmentsbyObjectType.WebSiteDisplayer2.defa ult.websitedisplayerurl 7 CaseGenerationDashboard.WebSiteDisplayer5.defa ult.websitedisplayerurl 8 ContentAnalytics.WebSiteDisplayer16.default.weSi tedisplayerurl 9 EntityResume.WebSisteDisplayer3.default.webSite DisplayerUrl 10 InvDashboard.WebSiteDisplayer0.default.webSiteD isplayerurk 11 LinkAnalysis.WebSiteDisplayer17.default.webSiteDi splayerurl 12 OperationalDashboard.WebSiteDisplayer2.default. websitedisplayerurl Target Value URL prefix way/servlet/gateway?b... way/servlet/gateway?b... way/servlet/gateway?b... way/servlet/gateway?b... way/servlet/gateway?b... way/servlet/gateway?b... way/servlet/gateway?b way/servlet/gateway?b... InvDashboard.WebSiteDisplayer0.default.we bsitedisplayerurl OperationalDashboard.WebSiteDisplayer2.de fault.websitedisplayerurl 7. Press the Next button. 8. Use the default values for User and Group, press the Finish button. Page 55

61 Figure 55: Solution template import results page 9. Press the Close button Configuring dashboard URLs 1. From the default home page, select the link IBM Case Manager builder or enter 2. Follow the instructions from the Knowledge Center to verify and correct the URL s for the solution pages for: 2.1. Step Step Step Step 7 3. Save all changes and Close the editor. 4. From the copied solution tile, press Commit. 5. from the copied solution tile, press Deploy Deploying a new solution 1. Follow the instructions in the IBM Knowledge Center for Backing up the target environment before deploying solutions. 2. Follow the instructions in the IBM Knowledge Center to deploy the solution using the IBM Case Administration client. Select the link Deploying a solution with IBM Case Manager Configuring security for IBM Case Manager solutions Before proceeding, we recommend you review the instructions in the IBM Counter Fraud Management Knowledge Center for Configuring security for IBM Case Manager solutions. The URL to the external IBM Knowledge Center is: Page 56

62 The URL to the Internal IBM Knowledge Center is: Updating IBM Case Manager roles The IBM Case Manager Role Selector behavior changed slightly after Fix Pack 6 installation for the Administrator role and the Supervisor role. They do not show all defined roles. The work around is to assign the roles that are missing from the pulldown menu to the group or user account that is retrieved from the directory. Figure 56: Sample CFM Role assignments Updating the CFCaseMgmtOperations component queue This procedure creates the interfaces between the IBM Case Manager workflow system and the IBM Counter Fraud Management application components. The URL to the external IBM Knowledge Center for IBM Case Manager is: Note: The URL points to the IBM Case Manager for Investigations product, however the instructions are the same for IBM Case Manager The URL to the external IBM Knowledge Center for Counter Fraud Management is: The URL to the Internal IBM Knowledge Center for Counter Fraud Management is: Page 57

63 Search for the topic Configuring the Component Manager. On the ICFM Tools Client 1. Launch a new web browser session and from the default Counter Fraud Management Systems page, select the hypertext link Administration Console for Content Engine The URL is 2. Login using account filenet and supply the password value. 3. Navigate to Workflow system folder. Under Domain: CFM Object Stores TARGET Figure 57: Process Configuration Console page 4. From the Object Stores table, select the hypertext link TARGET. Figure 58: Target Object Store page Page 58

64 5. Open the Administrative folder. Right click on the Workflow System folder and select Configure Workflow Settings. This launches a Java in pop-up window and starts the Process Configuration Console. Figure 59: Process Configuration Console home page 6. Expand the twisty next to TARGET-OSDBUSER. Right click on CFM[1] and select Connect. Figure 60: Process Configuration Component Queues page 7. Expand the twisty next to Component Queues. Right click on CFCaseMgmtOperations and select Properties Page 59

65 8. Select the Adapter tab. Edit the properties using the values from the table below. Table 14: CFCaseMgmtOperations Component properties Adapter User Name Password Configuration Context Java Component filenet <password value> CaseOperationsLogin 9. Then press the Configure button. 10. Edit the properties using the values from the table below. The Jar File value is CFCaseMgmtOperations.jar Table 15: Code Module properties page Java Class Available Methods Page 60