1. Ifix dependencies:

Process Center/Process Server:
a) Pre-requisites:
Direct Pre-requisites:
JR42342
IC74897

Indirect Pre-requisites:
JR42342 pre-requisites JR42330
JR42330 pre-requisites JR42232 and JR42280
JR42280 pre-requisites JR42012
IC74897 pre-requisites JR42232, JR41908 and JR42356
JR42356 pre-requisites JR42232
JR42232 pre-requisites JR42220, JR42280 and JR42012


Process Designer:
Direct Pre-requisites:
JR42280

Indirect Pre-requisites:
JR42280 pre-requisites JR42012

2. Interim fix Installation Manager Install Order: 
Process Server/Center Install Order is:

JR42012
JR42280
JR42220
JR42232
JR42356
JR41908
IC74897
JR42330
JR42342
JR42522

Process Designer install order is:
JR42012
JR42280
JR42522

3. Interim fix Installation Manager Install Instructions: 
http://www-01.ibm.com/support/docview.wss?uid=swg21417656

4. Post Installation Manager Install Instructions:
(these need to be run once after all the fixes have been installed using Installation Manager.)

4.1. Run bpmprofileupgrade on PC/PS:
For Standalone:
Backup the stand-alone profile using the backupConfig command.
Run the backupConfig command from the profile_root/bin directory.
On Linux and UNIX, the syntax is backupConfig.sh backup_file_name -profileName <stand-alone_profile_name>
On Windows, the syntax is backupConfig.bat backup_file_name -profileName <stand-alone_profile_name>

Change directories to <target_install_root> for  the profile you wish to update and run one of the following commands as appropriate for your platform:
Windows: bin\ws_ant.bat -f util\BPMProfileUpgrade.ant -profileName <profile_name> -Dupgrade=true
Linux/Unix: bin/ws_ant.sh -f util/BPMProfileUpgrade.ant -profileName <profile_name> -Dupgrade=true
Where <profile_name> is the name of the stand-alone profile.

For Clusters:
Backup the deployment manager profile using the backupConfig command.
Run the backupConfig command from the profile_root/bin directory.
On Linux and UNIX, the syntax is backupConfig.sh <backup_file_name> -profileName <deployment_manager_profile_name>
On Windows, the syntax is backupConfig.bat <backup_file_name> -profileName <deployment_manager_profile_name>

Depending on the platform, run one of the following commands for each cluster:
Windows
For English locales: bin\ws_ant.bat -f util\BPMProfileUpgrade.ant -profileName <profile_name> -Dupgrade=true  -Dcluster=<cluster_name>
For non-English locales: bin\ws_ant.bat -f util\BPMProfileUpgrade.ant -profileName <profile_name> -Dupgrade=true "-Dcluster=<cluster_name>"
Linux Unix bin/ws_ant.sh -f util/BPMProfileUpgrade.ant -profileName <profile_name>  -Dupgrade=true -Dcluster=<cluster_name> where <profile_name> is the name of the deployment manager profile and <cluster_name> is the name of the cluster.


4.2. Update Database:
Backup the BPM and Performance Data Warehouse databases.
(This is Mandatory)

Run the upgrade_7x command to update the database by following step one in this section:
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5m1/topic/com.ibm.wbpm.imuc.doc/upgrade/topic/upgrading_existing_dbs_751.html
for example:
Standalone server: ./upgrade_7x.sh -profileName <profileName>
Network deployment environment: ./upgrade_7x.sh -profileName <DMGRProfileName> -nodename <nodeName> -serverName <apptargetServerName>
Please see Step 1 in http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5m1/topic/com.ibm.wbpm.imuc.doc/upgrade/topic/upgrading_existing_dbs_751.html for details.



>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
5. Post Install instructions:
(before starting servers)

NOTE: ANY POST INSTALL MANUAL INSTRUCTIONS FROM PRE-REQUISITE FIXES (e.g. changing xml Configuration) ARE NOT INCLUDED IN THIS INSTALL README. THOSE NEED TO BE DONE BY FOLLOWING THE APAR README/MORE INFO TEXT OF THAT PRE-REQUISITE.

- Copy the following XML from below and add it to the 100Custom.xml under <properties> tag:
	
100Custom location:
Standalone Profiles:
Profile_home\config\cells\<~cellname~>\nodes\<~nodename~>\servers\<~servername~>\<~process-center/server~>\config\100Custom.xml
Clusters:
DMGR_home\config\cells\<~cellname~>\nodes\<~nodename~>\servers\<~servername~>\<~process-center/server~>\config\100Custom.xml
(After making the changes to 100Custom.xml in the DMGR profile, make sure the changes get carried to the nodes by doing a force synchronize and restarting the DMGR)

xml snippet to copy to 100Custom.xml:

server merge="mergeChildren">
<repository merge="mergeChildren">
<branch-context-max-cache-size>64</branch-context-max-cache-size>
</repository>
<persistence-service merge="mergeChildren">
<handler type="Snapshot" is-thread-safe="true" class-name="com.lombardisoftware.server.ejb.persistence.PSDefaultHandler" merge="replace">
<dao is-thread-safe="true" class-name="com.lombardisoftware.server.ejb.persistence.dao.SnapshotDAO" />
<jms-cache-to-notify-on-update>DefaultMessageRoutingCache</jms-cache-to-notify-on-update>
<jms-cache-to-notify-on-update>NamedSnapshots</jms-cache-to-notify-on-update>
</handler>
<handler type="BPD" library-object-type="25" is-thread-safe="true" class-name="com.lombardisoftware.server.ejb.persistence.BPDPersistenceHandler" merge="mergeChildren">
<dao is-thread-safe="true" class-name="com.lombardisoftware.server.ejb.persistence.dao.BPDTransferDataHelperDAO" />
<object-to-notify-on-update>com.lombardisoftware.server.ejb.psapi.BusinessDataAliasesCacheUpdateHandler</object-to-notify-on-update>
</handler>
</persistence-service>
</server>

NOTE: please open the xml file in a browser after saving it- to make sure there are no special characters in it.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
6. Uninstall Instructions:
a) Stop all servers
b) Backup the BPM and Performance Data Warehouse databases.
c) Uninstall runtime interim fix and pre requisite packages using IBM Installation Manager.  
Prerequisite fixes and other fixes in the installation order can be uninstalled at the same time as the interim fix. 
Note that some of the pre-requisite fixes have runtime as well as process designer fix packages. 
Process Designer fix packages will also need to be uninstalled if server packages are being uninstalled.

d) Optional: Run only if Profile upgrade was run in "4. Post Installation Manager Install Instructions".
If the profile was backed up using the backupConfig command, then use the restoreConfig command to restore the stand-alone profile or all profiles in a network deployment environment.  
The "restoreConfig" command can be used to restore a profile.  See the following documentation section:
http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/rxml_restoreconfig.html

If the backupConfig command was not used then run the BPMProfileUpgrade command to restore applications (but not configuration files changes, 

if the interim fix changed configuration files) to their prior state.
- For a stand-alone environment, follow step two in this section:
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5m1/topic/com.ibm.wbpm.imuc.doc/topics/tmig_upgrading_bpm_errors.html
- For a network deployment environment, follow step three in this section for each cluster:
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5m1/topic/com.ibm.wbpm.imuc.doc/topics/tmig_upgrading_bpm_nd_clusters.html

e) Optional: Run only if upgrade_7x was run in "4. Post Installation Manager Install Instructions".
Run the upgrade_7x command to update the database with the reverted artifacts by following step one in this section:
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5m1/topic/com.ibm.wbpm.imuc.doc/upgrade/topic/upgrading_existing_dbs_751.html
f) Start the stand-alone server or network deployment environment.