This chapter covers the following topics:
Each time a new patch is delivered, it has to be copied into the correct directory, and the new applications will have to be deployed to all the Managed Servers. Perform the following procedure to copy and extract the ZIP files.
To copy the class files, run the script InitialEngineSetup.sh in the folder WLST_scripts.
Log in to the machine where EBS is installed with username as APPL manager user or APPL TOP owner.
Set the environment variable $MSC_TOP to the path where you copied the patch.
Example:
/slot/ems4928/appmgr/apps/apps_st/appl/msc/12.0
For 12.2.3, if using Online Patching, there will be two APPL_TOPs, RUN tier and PATCH tier. Compare the ZIP files for both RUN and PATCH tier, and use the higher version for deployment.
For example, fs1 is assigned to one tier, either RUN or PATCH. Use the command ident /u01/R122_EBS/fs1/EBSapps/appl/msc/12.0.0/dist/orp/engine.zip to obtain the file version.
Set the environment variable $JAVA_TOP to the path having Java classes.
Example:
/slot/ems2947/appmgr/apps/apps_st/comn/java/classes
Create a folder named ORPTEMP in a user-defined directory (for example: /tmp/ORPTEMP) on the host machine where WebLogic is installed. This folder is referred to as ORPTEMP.
Copy the following ZIP files to the folder ORPTEMP.
RPAdmin.zip
ui.zip
engine.zip
Extract all the ZIP files in the same folder. Each unzipped file contains a respective EAR file.
The EAR files will be selected from this location for deployment.
For release 12.2 and later, there are two $MSC_TOP directories that require the following updates:
Copy the class files to $JAVA_TOP (oracle/apps/msc) locations on both the APPL_TOP directories.
The patching process does not update this directory. Refer to the patch readme for each release for specific manual updates that may be required to these directories.
Perform the following procedure to redeploy the Engine Application.
In order to redeploy the Engine Application, open the WebLogic interface for Engine Domain according to the procedure in Starting the Engine Admin Server.
Click Lock & Edit from the Change Center region in top left corner to change the domain configuration.
Select Deployments from the Domain Structure region.
Select the application you want to redeploy, and click Stop. Select Force Stop Now.
Click Yes to stop the application.
Select the application you want to redeploy, and click Delete.
Click Yes to delete the application.
Follow the procedure in the section Deploying and Starting Engine Application to deploy the Engine Application.
From Change Center region, click Activate Changes.
Perform the following procedure to redeploy the User Interface (UI) Application.
In order to redeploy the Engine Application, open the WebLogic UI for Engine Domain according to the procedure mentioned in Starting the User Interface Admin Server.
Select Deployments from the Domain Structure region.
Select the application you want to redeploy, and click Stop. Select Force Stop Now.
Click Yes to stop the application.
Select the application you want to redeploy, and click Delete.
Click Yes to delete the application.
Perform the procedure in Deploying and Starting the User Interface Application to deploy the User Interface Application.
After you deploy a new engine EAR file, delete the old binary files described in the following procedure. You cannot use them to load the plans.
In <WLS_HOME>, navigate to directory user_projects/domains/<ENGINEDOMAINNAME>/output.
Example:
/slot/ems3157/appmgr/user_projects/domains/testenginedomain/output
Delete the contents of the output folder.