My customer is running BPM Standard 8013 on AIX Servers. We decided to upgrade the COACH CUM Level in order to take advantages of all the new enhancements added into this FIX (JR54073) plus other FIXES.
The Installation was success with no issues in our TESTCASE Box afterward we continued working to update our ProcessCenter (PC) server, as you may know the installation was success with NO problems at all, but when the customer's development team had to update the ProcessDesigner (PD) to keep it synchronized they got some issues as follows:
1) The PD installation was success BUT it didn't include any FIX
2) They tried to work with Human Services + COACHES and started getting this error:
In case you can not open the image this is the text dialog for your review:
com.lombardisoftware.component.coaching.persistence.CoachNG; local class
incompatible stream classdesc serialVersionUID = 8529104104554740474
local class serialVersionUID = 1416081400037629903
When I realized this problem found the following issues:
a) The PD's workstations had the Installation Manager (IM) damaged pointing to some Windows Registry errors.
b) After some deep dive I found the Post Installation steps for JR54073 (COACH CUM) had some sample as follows:
Stand-alone server: ./upgradeProcessData.sh -profileName <profileName> -ifix JR53724
Network deployment environment: ./upgradeProcessData.sh -profileName <DMGRProfileName> -nodename <nodeName> -serverName <apptargetServerName> -ifix JR53724
The customer ran the command following the sample as indicated in the readme file but if was pointing to a previous COACH CUM Fix "JR53724"
*** Due to this issue we had to restore a BackUp taken from the BPM (PC) server. ***
After some research and help from BPM COACH Support and Development (L2 & L3) Teams I noted the Post Installation instructions were pointing to the previous COACH CUM (JR52724) then we ran the "upgradeProcessData.sh" again pointing to the right and latest fix (JR54073) and problem GONE !
This is the command used to Fix the problem:
./upgradeProcessData.sh -profileName DmgrCtr01 -nodeName Node01 -serverName BPMPC.AppTarget.Node01.0 -perfNodeName Node01 -perfServerName BPMPC.Support.Node01.0 -ifix JR54073
An extra issue was related with the Installation Manager (IM) then I reviewed the IM log and found some Windows registry errors due to this problems I decided to install IM again using a different location and this situation was addressed.
I hope this information helps other people on the field.