cpe5.1 Archives - iparagons blog

IBM Case Manager Client Case History tab is slow sometimes

November 6, 2018

Case history tab is slow sometimes in case management software (ICM), when viewing the History tab in the Case Information widget in IBM Case Manager Client, if the case has a large number of case history records associated with it and the Event table in Content Engine has a large number of records, the views might load very slowly. Sometimes the following timeout error occurs, with very slow responses:

The case history is unavailable because of the following error: timeout exceeded (CDEWG5206E).

Problem

Open a case in the IBM Case Manager Client and click to the History tab in the Case Information widget. As you change the views, such as “Show Summary/All” and “for All/Case/Comments/etc.”, they load very slowly, for example, nearly in one minute. Below is the screenshot of problem description:

Cause

The information displayed on the History tab is stored in the Event table in the Content Engine database. The Event table index might not have been updated or configured to fit your environment needs. This causes a database performance problem.

Environment

ICM 5.1.1.x / 5.2.1.x ? 5.3.x
WAS 7.x / WAS 8.x
CPE 5.1.x / 5.2.x

Solution

Stop IBM FileNet P8 Services.
In the Content Engine Platform database (Target OS Schema), create one new index with the following definition:

DB2:

CREATE UNIQUE INDEX I_CASE_FOLDER
ON db2admin.EVENT (U88E7_CMACMCASEFOLDER ASC, AUDIT_SEQUENCE DESC)
INCLUDE (OBJECT_CLASS_ID, SOURCE_OBJECT_CLASS_ID, HOME_ID)
COMPRESS NO ALLOW REVERSE SCANS

Oracle:

CREATE INDEX I_CASE_FOLDER ON EVENT
(U88E7_CMACMCASEFOLDER ASC, AUDIT_SEQUENCE ,OBJECT_CLASS_ID, SOURCE_OBJECT_CLASS_ID, HOME_ID)
LOGGING
TABLESPACE USERS
PCTFREE 10
INITRANS 2
MAXTRANS 255
STORAGE (
INITIAL 64K
NEXT 1M
MINEXTENTS 1
MAXEXTENTS UNLIMITED
PCTINCREASE 0
BUFFER_POOL DEFAULT
)
COMPRESS REVERSE ;

Once done. Start IBM FileNet P8 Services.
Test ICM Client and click on history tab in Case Information Widget again. Now there will be no delay and Case History will be shown timely as mentioned below:

For further details, please visit this tech note http://www-01.ibm.com/support/docview.wss?uid=swg21587662

IBM Content Platform Engine (CPE)

How to Change Bootstrap User Password – IBM CPE 5.x above

July 31, 2018

The Directory Service user account and password are normally used in two product components: FileNet Enterprise Manager (FEM), and the application server. A coordinated update procedure should be followed when there is a need to change the user account and/or password. This procedure applies to FileNet Content Engine 5.x and above.

These steps are required to do for IBM FileNet P8 so in 5.1 environment we use FileNet Enterprise Manager (FEM) while in 5.2, You have to use Administration Console for Content Platform Engine (ACCE). Following is the complete step by step procedure to change bootstrap user password cpe 5.1:

Backup the Engine-##.ear file, where ws denotes WebSphere, wl denote WebLogic, and jb denotes JBoss. You can then revert to last good known EAR file in case changing the password fails.
Path: /opt/IBM/FileNet/ContentEngine/tools/configure/profiles/CEConfig/ear/Engine-ws.ear
On the server containing Content Engine, start the Configuration Manager.
a. Load the Configuration Manager profile that describes your installation.
Path: /opt/IBM/FileNet/ContentEngine/tools/configure/./configmgr_cl gui (To Load Configuration Profile)
b. Click Configuration Bootstrap Properties. Do not change anything yet. The Bootstrap user password is the field you will change later in this procedure.
c. Leave this window open while doing the following steps.
Log in to Enterprise Manager (FEM) as GCD administrator gcd_admin.

a. In Enterprise Manager, right-click the Root Folder, and then click Properties.
b. Click the Directory Configuration tab.
c. Select the row that represents the configuration parameters pointing to the LDAP location that the Content Engine system user belongs to, and click Edit.
d. When the Modify Directory Configuration dialog box opens, view the value for the Directory Service User account.

4. Locate the value for the Directory Service (AD) User account. This should be the same value as described in step 3d.
a. Navigate to the authentication provider panel containing the ID and password for the Directory Service User account.
WebLogic: this will be the value of the Principal field in the Authentication Provider for the WebLogic domain containing Content Engine.
WebSphere: this will be the bind user account in the Profile containing Content Engine. JBoss: the Directory Service User account is contained in the login-config.xml file.

b. Do not change anything yet. Leave the console open while doing the remaining steps.
5. Log in to your directory server (AD).
a. Navigate to the location containing the account for the Content Engine system user.
b. Change its password.
c. Save and apply.
6. Return to Enterprise Manager Dialog box.
a. Change the Directory Service User’s password to the new password.
b. Click Apply and OK to close the dialog box.
7. Return to the window containing Configuration Manager.
a. In the Configure Bootstrap Properties task, set the Bootstrap Operation property to Modify Existing.
b. Confirm that the Bootstrapped EAR file property contains the path to the bootstrap file you need to edit.
Path: /opt/IBM/FileNet/ContentEngine/tools/configure/profiles/CEConfig/ear/Engine-ws.ear
c. Change the Bootstrap user password. Use Configuration Manager’s features to save and run the task.
d. Run Configuration Manager’s Deploy Application.

8. Restart the application server or machine.
9. Verify the change by logging on to Enterprise Manager as a GCD administrator (gcd_admin) and performing a user and group look up.
Open FEM–Edit–Provide New Password in the Password
Field-Apply-OK-Connect
10. If you are using p8admin to connect to CE, you need to retype the new
password on the Process Engine Process Task Manager (PE PTM) Security
tab and on the AE/XT PTM for component manager (General Tab).
Path: /opt/IBM/FileNet/ProcessEngine/./vwtaskman

11. To Change password for ICMSupportOperations component properties file
Path: /opt/IBM/FileNetWebClient/Router/./routercmd.sh
Change these passwords one by one.
11.1 CE_Operations–Advanced Tab–Change Password
11.2 ICM_SupportOperations–Advanced Tab–Change Password
11.3 RM_Operations–Advanced Tab–Change Password
11.4 RM_Workflowutil–Advanced Tab–Change Password
12. If p8admin is used for the JAAS credentials configuration of a component
adaptor, you need to reenter the password.

Path: Login to WorkplaceXT-Tools-Administration-Process Configuration Console-Right Click on PE_1-Connect-Component Queues-Adaptor Tab-Change Password-Commit the Changes.
12.1 CE_Operations-Adaptop Tab-Change Password
12.2 ICM_SupportOperations Adaptop Tab-Change Password
12.3 RM_Operations– Adaptop Tab-Change Password
12.4 RM_Workflowutil– Adaptop Tab-Change Password
12.5 WS_Request– Adaptop Tab-Change Password
13. Reboot the Application Server or machine.
14. Verify the Changes.

Please visit this ibm tech note for details: http://www-01.ibm.com/support/docview.wss?uid=swg21442694.

In case of failure or password change activity unsuccessful, you can revert back as mentioned here:

Connect to GCD schema.

Revert back Active Directory (AD) Bootstrap User Password.

Stop Application Server Services.

select * from FNGCD order by 1;

select LAST_EPOCH_ID from FNGCD where EPOCH_ID=0;

UPDATE FNGCD SET EPOCH_ID=EPOCH_ID * -1 where EPOCH_ID=109;

Note: Change EPOCH_ID value as per your environment.

COMMIT;

Restart Services.

Note: If your environment is on CPE 5.5.0, IBM Would not allow to change password for bootstrap user account because workflow system unable to start after changing password. For details please review: https://www-01.ibm.com/support/docview.wss?uid=ibm10739669 . In 5.5.1 environment you can easily change bootstrap user’s password using ACCE.

Please advise users – Do not change the password of bootstrap user in CPE 5.5.0.

If the customer has already changed the password, there are two ways to recover:

a) Change the password of the bootstrap user back to original value.

b) Upgrade the CPE 5.5.0 to 5.5.1. In CPE 5.5.1 users is able to change the password of bootstrap users using ACCE.

IBM Content Platform Engine (CPE)

Upgrading IBM CPE 5.1.x to CPE 5.2.1

July 27, 2018

If your FileNet P8 upgrade starts at version 5.2.0, then you are upgrading Content Platform Engine. If your upgrade starts at version 4.5.1, 5.0, or 5.1, then you are upgrading Content Engine and Process Engine.

If you’re using IBM Case Manager (ICM) in your environment and you want to retain cases history or old data as well than you’ve to move workflow system or isolated region to targetos schema if both source and destination are not in same one. Than before upgrading, please first go through following links to move isolated regions and workflow systems first. This task must be completed before upgrading CPE.

https://iparagons.com/blog/2018/07/27/moving-workflow-system-or-process-engine-isolated-regions-5-1-x/

http://www-01.ibm.com/support/docview.wss?uid=swg27036552

Mount the media of FN CPE 5.2.1 to any temp directory and extract it on the server where you want to upgrade.
Here is the Knowledge centre url that needs to be follow for complete upgrade activity:
https://www.ibm.com/support/knowledgecenter/en/SSNW2F_5.2.1/com.ibm.p8.install.doc/p8pup007.htm

Simply follow complete procedure step by step as mentioned:

If your system includes IBM FileNet Content Federation Services for Content Integrator, you must shut down the CFS Exporter before upgrading Content Platform Engine.
You must stop the IBM Content Search Services index dispatcher before upgrading Content Platform Engine.
You will restart the dispatcher after completing the upgrade of IBM Content Search Services.

Open FEM and do the following to stop CSS index dispatcher:

In the navigation pane, select the domain icon.
In the edit pane, click the Text Search Subsystem tab and clear the Enable indexing check box.
Click Save to save your changes.

If you are upgrading an existing application server instance, you must remove the existing FileNetEngine application from the web application server to undeploy or uninstall the application EAR file. Removing the existing version ensures a clean deployment of the upgraded version of the Content Platform Engine EAR file.

Use the administrative console to undeploy the FileNetEngine application, Engine-ws.ear. The application server needs to be running when you undeploy the FileNetEngine application.

If you are upgrading to a different application server but using an existing profile, make a copy of the current configuration profile directory.

Path: /opt/IBM/FileNet/ContentEngine/tools/configure/profiles

If you are upgrading FileNet P8 from version 5.0 or 5.1, stop all Process Engine and related software and do a backup before doing the upgrade.

Process Simulator

Case Analyzer

Component Manager

Application Engine

Process Service

Process Task Manager Process Engine

IBM Case Manager

If you are upgrading FileNet P8 from version 5.0 or 5.1, stop all Content Engine-related services and applications and do a backup before doing the upgrade.

Stop the following components (if they are running).

Content Engine Content Engine

Configuration Manager Content Engine

Enterprise Manager Windows system

Rendition Engine Rendition Engine

FileNet Deployment Manager Windows system

.NET client applications Windows systems

Check your JDBC driver version. If a JDBC 4.0 driver is not already configured for use in your application server, you must replace your existing JDBC drivers with a 4.0 version before you upgrade.
You must clear the cache for the web application server to remove the currently deployed Content Platform Engine (Content Engine, if you are upgrading from a version prior to 5.2) data to prevent conflicts with the upgraded version.
Stop the application server instances that host the FileNetEngine application.
Delete the cache files for your web application server.

Path: WAS_HOME/profiles/profilename/temp/nodename/servername/FileNetEngine/*.*

Note: Upgrading Content Platform Engine software is a multistep process. (If you are upgrading FileNet P8 from a version prior to 5.2, you upgrade Content Engine and Process Engine software.)

Run the Content Platform Engine(CPE) 5.2.1 installer either interactively or silently. When the installation completed close the installer.
You must install IBM Case Foundation if you need full workflow processing capabilities. You can install IBM Case Foundation either interactively or silently.
Run the Case Foundation(CF) 5.2.1 installer either interactively or silently. When the installation completed close the installer.
You must apply any updates, fix packs, or interim fixes for the Content Platform Engine software that have been released for both CPE 5.2.1.* and CF 5.2.1.*.
grant permissions to the Configuration Manager user

chmod -R 777 ce_install_path/tools/configure

You can configure your upgraded Content Platform Engine instances with Configuration Manager. You must upgrade the Content Platform Engine bootstrap properties for the upgraded Content Platform Engine instance. A single Content Platform Engine application instance equates to one deployed application on your application server. You can complete this task either interactively or silently.

Creating an upgrade configuration profile and complete the wizard.

Chossing licenses

You must provide licensing information about your installed products so that IBM License Metric Tool can make the correct product license association.

You must configure the login modules, which provide authentication information for Content Platform Engine.
You must create JDBC data sources for each database that Process Engine uses. Content Platform Engine and the peupgrade tool use this data source information to connect to and update the database.
You must provide the bootstrap and text extraction property values to upgrade Content Platform Engine or Content Engine.
You must deploy the upgraded Content Platform Engine on the web application server. Deploying makes the Content Platform Engine application available for use.
Start the application server instance if it is not already running.
Run ce_install_path\tools\configure\configmgr and deploy Application task.

Completing Content Platform Engine post-deployment steps

You can verify that the Content Platform Engine deployment was successful by accessing the FileNet P8 System Health page and the Content Platform Engine Startup Context (Ping Page).
http://server:port/FileNet/Engine
Enabling Java applet support for Administration Console for Content Platform Engine on WebSphere Application Server 8.

Log on to the WebSphere administration console.
Disable HttpOnly session cookies, either globally or for just your deployed Content Platform Engine application:
To disable HttpOnly globally, either for single sign-on (SSO) or for secure sockets layer (SSL):
To disable HttpOnly for SSO:
Navigate to Security > Global security > Authentication > Web and SIP security > Single sign-on (SSO)
Under General Properties, clear the Set security cookies to HTTP Only to help prevent cross-site scripting attacks check box and click Apply.
To enable cookies and disable HttpOnly settings at the server level setting when using SSL:
Navigate to Servers > Server Types > WebSphere application servers.
Select the server where FileNetEngine is deployed.
Click Session Management.

Under General properties, select the Override session management check box and click Apply.
Click the Enable cookies link under Session tracking mechanism.
Clear the box Set session cookies to HTTP Only to help prevent cross-site scripting attacks check box.

To disable HttpOnly and enable cookies for the deployed Content Platform Engine application:
Navigate to Applications > Application Types > WebSphere enterprise applications > FileNetEngine > Manage Modules > acce > Session Management.
Under General properties, select the Override session management check box and click Apply.
Under Session tracking mechanism, click the Enable cookies link.
Under General properties, clear the Set session cookies to HTTP Only to help prevent cross-site scripting attacks check box and click Apply.
Save your settings and restart WebSphere Application Server.

Checking the automatic upgrade status for Content Platform Engine data
http://server_name:port/FileNet/AutomaticUpgradeStatus

Note: This task must be completed if it is not you have to wait until or unless it’s status completed or Ready.

Creating an index on the IBM Content Search Services index requests table
The automatic upgrade of Content Platform Engine data (Content Engine data if you are upgrading FileNet P8 from a version prior to 5.2.0) includes the creation of a new index on the IBM Content Search Services index requests table. However, if the table is too large, the automatic upgrade cannot build the index. In which case you need to build it manually.

Completing the Process Engine upgrade (from version 5.1 or earlier)

Note: If you are upgrading FileNet P8 from version 5.1 or earlier, complete the following tasks to upgrade the Process Engine database.

Creating the Process Engine upgrade properties file and starting the upgrade interactively
cpe_install_directory/tools/PE/peupgrade -Y username + password

You have to provide now target object store database connection info in this wizard to successfully completion of this task after that review the summary.
Click Finish to save the information to the output file and to start the upgrade.

Verifying the successful upgrade of workflow systems
http://server:port/peengine/IOR/ping

Installing the latest Content Platform Engine client files on other FileNet P8.
Install CPE Client 5.2.1 and complete the wizard.
You must also redeploy any components that are web-application-server-based, such as Application Engine, Workplace XT, or IBM Enterprise Records, after you install the Content Platform Engine client files on the associated machines.

WorkplaceXT
IER
Case Manager
Content Navigator.

Upgrading Content Search Services (CSS 5.2.1)

If you’re using Content Search Services in your environment than install the CSS 5.2.1.* on the same server.
Complete the upgrade installation windows by using the values from your worksheet.

Earlier, we’ve stopped Index dispatcher before start of this exercise. To start the index dispatcher:
http://CPE_Server:port/acce CPE_Server is the name of the system where Content Platform Engine is deployed

In the navigation pane, select the domain icon.

In the edit pane, click the Text Search Subsystem tab and select the Enable indexing check box.

Click Save to save your changes.

You can verify that the IBM Content Search Services upgrade was successful by using Administration Console for Content Platform Engine to create a search index job and checking to see whether the job returns the correct index objects.

Just search a document from acce console using SQL mode like;
SELECT THIS, ID FROM DOCUMMENT WHERE ID = ‘{}’;

If search returns results correctly than it means CSS upgraded successfully.

Test your environment completely.

Process Engine (PE)

Moving Workflow System or Process Engine Isolated Regions 5.1.x

July 27, 2018

You can move isolated region to a new workflow system or Process Engine database or schema. You can move the isolated regions to correct IBM Case Manager environments where the isolated region and the Content Platform Engine target object store are not stored in the same database and schema. You can also reorganize existing isolated region data by moving the isolated region to a new database or schema.

For IBM Case Manager 5.0 or 5.1 systems that are not in compliance with the common database or schema requirement (that is, the isolated region and the Content Platform Engine target object store are not stored in the same database and schema), move the Process Engine isolated regions into a Content Engine object store before you upgrade to Content Platform Engine 5.2.

Restriction to Move Isolated Region to a New Workflow System:

You cannot move an isolated region from the database and schema of one workflow system to an existing workflow system database and schema that already contains an isolated region. If you want to move
multiple isolated regions to a new database and schema, you must do so in the same operation in one run.

These steps are only required if you want to retain ibm case manager (ICM) older data so that it will be available in new environment. Because process region and the content platform engine (CPE) target object stores are not stored in the same database or schema.

Note: Before doing this activity please make sure you’ve proper backup of your PE and Target OS database.

Stop All IBM FileNet P8 services except database.
Open and follow help pdf file. This file will tell you what changes you need to do.
This is the tech note link of pdf file.http://www-01.ibm.com/support/docview.wss?uid=swg27036552
First of all install and update JDK 1.6.24 to 1.8.102 on the ACM app server because in my environment it doesn’t work for JDK1.6.24 when we run the rmove.sh and rdel.sh commands.
Also use regmove.jar file into your CLASSPATH environmental variable.
Make essential changes in .bash_profile file like; CLASSPATH and JAVA_HOME as perlatest java version.Just move regmove directory to somewhere temp directory on Linux.
Please make necessary changes in relevant files that are placed in directory regmove. rmove.sh, rdel.sh, region_move.properties, and region_delete.properties. I’ve already amended these files according to my environment.
Run the following commands to give permission to run both of scripts

sed -i -e ‘s/\r$//’ rmove.sh

sed -i -e ‘s/\r$//’ rdel.sh

rmove.sh will run first.

Once its completed. Check the schemas both PE and Target Object Stores.
Run rdel.sh file than.

Start the IBM FileNet P8 services.
Corresponding isolated regions and connection points also need to be created or modified in the P8 domain to make the system functional after the move. Use the process task manager (PTM) to configure a new process engine server or virtual server to connect to the moved database.

Check the Health Page to make sure all of the components are running smoothly or not.

http://servername:9080/P8CE/Health

Once done, do complete testing of FileNet P8 system including icm, icn, ier, and other applications. Relevant jar files scripts, links, and screenshots can be download from here.

cpe5.1