13.2.2 Configuring the development environment by running the following tasks
The IBM Case Manager development environment is set up using the configmgr application as shown in the following steps:
- Update the Content Platform Engine Client Connector files.
Important: Ensure you restart IBM Case Manager configuration tool before continuing to the next task. - Configure the Case Management Object Stores.
- Create Case Manager Applications.
- Deploy the Case Manager API.
- Register the IBM Case Manager Services Plug-in.
- Deploy Case Manager Builder.
- Deploy and Register Widgets Package, specifically the ICMClient widget package. (\configure\deploy\ICMClient.zip)
- Register the IBM Case Manager Administration Client Plug-in.
- Register Project Area.
- Configure Business Rules. Run this task only if your environment uses business rules.
The Tasks highlighted were run for our installation of IBM Case Manager as shown in Figure 13.66:
Figure 13.66: The Tasks highlighted were run for our installation of IBM Case Manager
Restart IBM Case Manager server and the IBM Content Platform Engine server web applications (AppSrv01 and AppSrv02).
Note: Before accessing IBM Case Client, clear the browser cache.
Below, we display just a few of the installation screens specific to our environment on the ECMUKDEMO22 server we are using. A full set of screens is available by downloading the installation of the Case Manager Version 5.3.3, see pages 450 to page 465, pages 476 to page 481 and pages 495 to page 506. This is in the downloaded document, CaseManagerInstallationonRHEL8.0_V3.docx, from the URL: https://doi.org/10.13140/RG.2.2.21708.16001. (Ignore the Content navigator configurations, which are all completed from the configuration manager in the latest release.). The IBM Case Manager configuration tool is run, as shown in Figure 13.67 to select the Target Object store, TOS1, from the detected drop-down list:
Figure 13.67: The IBM Case Manager configuration tool is run to using the Target Object store, TOS1
The Define the Default Project Area task is configured and run to associate the IBM Filenet P8 Workflow system CP2 connection point to the IBM Case Manager, Default Project Area as shown in Figure 13.68:
Figure 13.68: The “Define the Default Project Area” task is configured and run for the Workflow CP2 connection point
After restarting the IBM WebSphere Application Server, AppSrv01 and AppSrv02 profiles, we can see the deployed and running CaseBuilder, CaseForms, CaseManager, ICMClient and navigator web applications on the AppSrv02 profile as shown in Figure 13.69:
Figure 13.69: The running CaseBuilder, CaseForms, CaseManager, ICMClient and navigator web applications
It is now possible to log into the IBM CaseManager Case Builder web application using the URL http://ecmukdemo22:9081/CaseBuilder/login/login.jsp as shown in Figure 13.70:
Figure 13.70: Log into the IBM CaseManager Case Builder web application using the URL http://ecmukdemo22:9081/CaseBuilder/login/login.jsp
The Add a solution wizard is selected using the + icon on the right side of the IBM Case Builder main screen, as shown in Figure 13.71:
Figure 13.71: The Add a solution wizard is selected using the + icon of the IBM Case Builder main screen
The ASBTest Case Management solution is created for saving as shown in Figure 13.72:
Figure 13.72: The ASBTest Case Management solution is created for saving
The Saved ASBTest Case Manager solution is displayed as shown in Figure 13.73:
Figure 13.73: The Saved ASBTest Case Manager solution is displayed
The ASBTest Case Manager solution is deployed successfully, as shown in Figure 13.74:
Figure 13.74: The ASBTest Case Manager solution is deployed successfully
Conclusion
In this chapter, we outlined the installation procedures for the installation and configuration of IBM Content Navigator server and the installation of IBM Case Manager 5.3.3.
In the next chapter, we describe the import of an IBM Case Manager solution, using the Auto Claims example.