How to Apply a Hotfix for MSCM

WFM Hot Fix – Deploy .ear file

To prepare for applying the Hot Fix

1. Backup the appropriate databases
2. Backup important application files (ex. lsfprod/law/system) app server:
   1. ssokeystore
   2. ssotruststore
   3. authen.dat
   4. install.cfg
   5. lsservice.properties
3. Backup Ldap
   1. Get the instance name (ex. lsfprod-389)
   2. At the command prompt, browse to C:\
   3. Type: dsdbutil enter
   4. Type: active instance lsfprod-389 enter
   5. Type: ifm enter
   6. Type: create full D:/lsfprod/TEMP/ldapbackup/20160428
      
      

APPLICATION DEPLOYMENT

4. Logon as an administrator WEBLOGIC server.
5. Backup your current directory where the application is deployed (ex. workbrain_20160502)
6. Since you backed up the current Weblogic deployment directory, create a directory with the original name (ex. workbrain)
7. Open a command prompt and browse to the directory where the application is deployed
   ex. cd $WB_HOME/deployments/production/workbrain
8. Copy the EAR File to deployment directory (ex. $WB_HOME/deployments/production/workbrain
9. Expand the EAR file in the deployment directory, using the jar tool:
   jar xvf workbrain.ear
10. Delete the EAR File
    rm workbrain.ear
11. Create a directory named war
    mkdir war
12. Move the workbrain.war file into the war directory:
    mv workbrain.war war
13. Select the war directory and expand the war file:
    cd war
    jar xvf workbrain.war
14. Delete the war file:
    rm workbrain.war
15. Edit the application.xml file found in the deployment_directory/workbrain/META-INF
16. Change the line from:
    <web-uri>workbrain.war</web-uri>
    to:
    <web-uri>war</web-uri>
17. For the process of deploying as non-root context, select the deployment_directory/workbrain/META-INF directory, edit the application.xml file, and modify for the application non-root context:

<module id=”WebModule_1066144042227″>
<web>
<web-uri>war</web-uri>
<context-root>/workbrain</context-root>
</web>
</module>
<module id=”WebModule_1066144042228″>
<web>
<web-uri>lib/axis.war</web-uri>
<context-root>/workbrain/axis</context-root>
</web>
</module>

NOTE: Make sure that you copy over any custom .jar files. Compare your previously deployed directories (the directory you backed up in step 5) to the new deployment for any custom .jar files.

18. In the Administration Console, select Deployments in the left panel, and click Install in the right panel.The Install Application Assistant – Locate deployment to install and prepare for deployment page is displayed.
    
19. Select the folder where the application was exploded.
20. Click Next The Install Application Assistant – Choose targeting style page is displayed.
    
21. Leave the default Install this deployment as an application option selected.
22. Click Next. The Install Application Assistant – Select deployment targets page is displayed.
    
    
23. Select the managed server.
24. Click Next. The Install Application Assistant – Optional Settings page is displayed.
    
25. Select Copy this application onto every target for me.
26. Click Next. The Install Application Assistant – Review your choices and click Finish page is displayed.
    
27. Leave the default Yes, take me to the deployment’s configuration screen option selected.
28. Click Finish. The Install Application Assistant – Settings for My App page is displayed.
    
    
29. Confirm that all settings are correct.
30. Click Save.
31. Click Activate Changes in the left panel.
32. Click Deployment in the left panel.
    
33. In the right panel, select the deployed application check box.

The Start Application Assistant page is displayed

34. Click Yes.Note:Before you start your deployment, make sure that your managed server is running (<domain_name>/Environment/Servers/<managed_server>/control).