14.1.3 Installing standalone Process Designer
We can examine the Record Claim task workflow using the standalone Process Designer Java applet. To use this Java applet, we have to download IBM Content Foundation Content Engine. We have downloaded the Windows version of IBM Content Foundation Content Engine v5.5.0. This is installed, as shown in Figure 14.54:
Figure 14.54: The downloaded Windows version of IBM Content Foundation Content Engine v5.5.0 is installed
The splash screen for the IBM Content Foundation Content Platform Engine 5.5.0.0 installation is shown in Figure 14.55:
Figure 14.55: The splash screen for the IBM Content Foundation Content Platform Engine 5.5.0.0 installation
The highlighted, I accept… option, is selected after reading the scrollable Program License Agreement, as shown in Figure 14.56:
Figure 14.56: The highlighted, I accept… option, is selected after reading the Program License Agreement
The NET Clients and Tools installation tick boxes are selected as shown in Figure 14.57:
Figure 14.57: The NET Clients and Tools installation tick boxes are selected and then Next selected
The default Windows Installation Directory and JRE path are left and Next clicked as shown in Figure 14.58:
Figure 14.58: The default Windows Installation Directory and JRE path are left and Next clicked
The CCL server URL: is updated as highlighted in Figure 14.59 to http://ecmukdemo22:9080/wsi/FNCEWS40MTOM/:
Figure 14.59: The CCL server URL is updated as highlighted in the full URL above, http://ecmukdemo22:9080/wsi/FNCEWS40MTOM/
Click Next and enter the Linux Content Engine Server URL, (http://ecmukdemo22:9080/wsi/FNCEWS40MTOM/) for the WcmApiConfig.properties file, as shown in Figure 14.60:
Figure 14.60: Enter the Linux Content Engine Server URL for the WcmApiConfig.properties file and click Next
Note: This can be validated using http://ecmukdemo22:9080/wsi/FNCEWS40MTOM in an Internet browser on the Windows server to see the WSDL output.
The Installation summary page is displayed, showing the required disk space, as shown in Figure 14.61:
Figure 14.61: The Installation summary page is displayed, showing the required disk space
After clicking the Install button, the installation status is displayed as shown in Figure 14.62:
Figure 14.62: The installation status is displayed
The .NET configuration status is shown in Figure 14.63:
Figure 14.63: The .NET configuration status is shown
The Installation Complete window is displayed, and the Done button clicked as shown in Figure 14.64:
Figure 14.64: The Installation Complete window is displayed, and the Done command button clicked
Click Done, then navigate to C:\Program Files (x86)\IBM\FileNet\ContentEngine\tools\PE and edit the pedesigner.bat Windows shell script command file as shown in Figure 14.65. Change all occurrences of:
Program Files (x86)
To:
PROGRA~2
Note: Run notepad.exe as the Windows administrator.
Figure 14.65: Navigate to C:\Program Files (x86)\IBM\FileNet\ContentEngine\tools\PE and edit the pedesigner.bat file
The notepad edit program’s Find and Replace is used to update the pedesigner.bat file as shown in Figure 14.66:
Figure 14.66: The notepad edit program’s Find and Replace is used to update the pedesigner.bat file
The updated pedesigner.bat file is shown in Figure 14.67, with the changed text highlighted:
Figure 14.67: The updated pedesigner.bat file is shown with the changed text highlighted
The pedesigner.bat file is saved after selecting All Files (.) type as shown in Figure 14.68:
Figure 14.68: The pedesigner.bat file is saved after selecting All Files (.) type
The notepad edit program’s Find and Replace is used to update the cpetoolenv.bat file as shown in Figure 14.69 and Figure 14.70:
Figure 14.69: The notepad edit program’s Find and Replace is used to update the cpetoolenv.bat file
The highlighted directory, Program Files (x86) with spaces is changed to the DOS short form, Progra~2 as shown in Figure 14.70:
Figure 14.70: The highlighted, “Program Files (x86)” with spaces is changed to the DOS short form, “Progra~2”
Edit cpetoolenv.bat and change the highlighted text to append the \JRE sub-directory as shown in Figure 14.71:
Figure 14.71: Edit cpetoolenv.bat and change the highlighted text to append the \JRE sub-directory
Run pedesigner.bat in a cmd.exe command window, passing in the connection point, as shown in Figure 14.72:
Figure 14.72: Run pedesigner.bat in a cmd.exe command window, passing in the connection point, CP1
cd c:\PROGRA~2\IBM\FileNet\ContentEngine\tools\PE
pedesigner.bat CP1
Enter the Process Designer login and password. This must be in the Fully Qualified Domain Name format of cn=P8Admin, cn=localhost as shown in Figure 14.73:
Figure 14.73: Enter the Process Designer FQDN in the format of cn=P8Admin, cn=localhost
The IBM FileNet P8, Content Platform Engine, Java applet Process Designer workbench is loaded as shown in Figure 14.74:
Figure 14.74: The IBM FileNet P8, Content Platform Engine, java applet Process Designer workbench is loaded
The File | Solution | Edit menu item is selected to start the load for the Auto Claims solution, as shown in Figure 14.75:
Figure 14.75: The File | Solution | Edit menu item is selected to start the load for the Auto Claims solution
Select the DOS1 Object Store and click Open as shown in Figure 14.76:
Figure 14.76: Select the DOS1 Object Store and click Open
Double click to move down the folder levels as shown in the drop-down as highlighted in Figure 14.77:
Figure 14.77: Double click to move down the Folder levels as shown in the drop-down as highlighted
The Auto Claims Folder is opened as shown in Figure 14.78 and the Solution Definition XML file is selected:
Figure 14.78: The Auto Claims Folder is opened and the Solution Definition XML file is selected
Click Open and select General Claim from the drop-down, as shown in Figure 14.79:
Figure 14.79: Click Open and Select General Claim from the drop-down
Select AC_RecordClaim from the list of Task Workflows as shown in Figure 14.80:
Figure 14.80: Select AC_RecordClaim from the list of Task Workflows
Select the Get Policy Data step as highlighted in Figure 14.81. This shows the origin of the error message(shown earlier, in Figure 14.52):
Figure 14.81: Select the Get Policy Data step as highlighted
The DemoDB Database Connection Alias can be seen as highlighted in Figure 14.82, with the Stored Procedure named GetPolicyData and its list of parameters:
Figure 14.82: The DemoDB Database Connection Alias, with the Stored Procedure, GetPolicyData
The full list of Parameters is shown in Figure 14.83:
Figure 14.83: The full list of parameters, for the Stored Procedure, GetPolicyData