This i did long ago, thought of sharing it.
Pre-Patch steps:
1.Cold backup of Middle Tier.
2. Shutdown the application servers and backup the directory,
<ORACLE_HOME>/j2ee/home/
cp –R home home_bkp
3.startup the services.
Steps to upgrade
Upgrade
from 10.1.3.4.0d (patch 8284524, 8398280) and 10.1.3.4.1 does not require step
8 and step 9.
1- Make a backup copy of the xmlp-server-config.xml file located in
<application installation>/WEB-INF/ directory, where your application server unpacked the BI Publisher war or ear file.
Example:
In an Oracle AS/OC4J 10.1.3 deployment, the location is
<ORACLE_HOME>/j2ee/home/applications/xmlpserver/xmlpserver/WEB-INF/xmlp-server-config.xml
Note: Make sure the backup xml is outside the <ORACLE_HOME>/j2ee/home
2- Back up all the directories under the BI Publisher repository
(for example: {Oracle_Home}/xmlp/XMLP).
3.- If you are using Scheduling, back up your existing BI Publisher Scheduler
schema.
Take an export of BI schema(differs from customer to customer) and hotbackup of database.
4- Shut down BI Publisher.
Cd $ORACLE_HOME/j2ee/home
java -jar admin_client.jar deployer:oc4j:opmn://hostname:<request port>/home
oc4jadmin simple4u -stop xmlpserver
EG: java -jar admin_client.jar
deployer:oc4j:opmn://hostname:10522/home oc4jadmin *** -stop xmlpserver
10/10/23
00:53:32 Notification ==>Stopping manageable object:
oc4j:j2eeType=J2EEApplication,name=xmlpserver,J2EEServer=standalone
10/10/23
00:53:32 Notification ==>Stop completed for state manageable object:
oc4j:j2eeType=J2EEApplication,name=xmlpserver,J2EEServer=standalone
5- Undeploy the BI Publisher application ("xmlpserver") from your J2EE
application server.
EG: java
-jar admin_client.jar deployer:oc4j:opmn://hostname:10522/home oc4jadmin****
-undeploy xmlpserver
10/10/23
01:11:54 Notification ==>Application UnDeployer for xmlpserver STARTS.
10/10/23
01:11:55 Notification ==>Removing all web binding(s) for application
xmlpserver from all web site(s)
10/10/23
01:12:00 Notification ==>Application UnDeployer for xmlpserver COMPLETES.
Delete the xmlpserver directory else the deployment fails in next step.
6- Deploy the 10.1.3.4 xmlpserver.ear or xmlpserver.war to your application
server.
EG: java -jar
admin_client.jar deployer:oc4j:opmn://hostname:10522/home oc4jadmin ****
-deploy -file /u01/patches/oc4j/xmlpserver.ear -deploymentName xmlpserver
-bindAllWebApps
java -jar admin_client.jar
deployer:oc4j:opmn://hostname:10522/home oc4jadmin ***** -deploy -file /u01/patches/oc4j/xmlpserver.ear -deploymentName xmlpserver -bindAllWebApps
10/10/23
02:47:50 Notification ==>Application Deployer for xmlpserver STARTS.
10/10/23
02:47:50 Notification ==>Copy the archive to /u01/product/asmt_10131/j2ee/home/applications/xmlpserver.ear
10/10/23
02:47:51 Notification ==>Initialize /u01/product/asmt_10131/j2ee/home/applications/xmlpserver.ear
begins...
10/10/23
02:47:51 Notification ==>Unpacking xmlpserver.ear
10/10/23
02:47:55 Notification ==>Done unpacking xmlpserver.ear
10/10/23
02:47:55 Notification ==>Unpacking xmlpserver.war
10/10/23
02:48:13 Notification ==>Done unpacking xmlpserver.war
10/10/23
02:48:13 Notification ==>Initialize /u01/product/asmt_10131/j2ee/home/applications/xmlpserver.ear
ends...
10/10/23
02:48:13 Notification ==>Starting application : xmlpserver
10/10/23
02:48:13 Notification ==>Initializing ClassLoader(s)
10/10/23
02:48:13 Notification ==>Initializing EJB container
10/10/23
02:48:13 Notification ==>Loading connector(s)
10/10/23
02:48:13 Notification ==>Starting up resource adapters
10/10/23
02:48:13 Notification ==>Initializing EJB sessions
10/10/23
02:48:13 Notification ==>Committing ClassLoader(s)
10/10/23
02:48:13 Notification ==>Initialize xmlpserver begins...
10/10/23
02:48:13 Notification ==>Initialize xmlpserver ends...
10/10/23
02:48:13 Notification ==>Started application : xmlpserver
10/10/23
02:48:13 Notification ==>Binding web application(s) to site default-web-site
begins...
10/10/23
02:48:13 Notification ==>Binding xmlpserver web-module for application xmlpserver
to site default-web-site under context root xmlpserver
10/10/23
02:48:14 Notification ==>Initializing Servlet:
oracle.apps.xdo.service.report.ReportTemplateService for web application
xmlpserver
10/10/23
02:48:14 Notification ==>Initializing Servlet:
oracle.apps.xdo.servlet.XDOServlet for web application xmlpservr
10/10/23
02:48:15 Notification ==>Initializing Servlet:
oracle.apps.xdo.servlet.scheduler.quartz.ExtendedQuartzInitializerServlet for
web application xmlpserver
7- Copy the saved backup copy of the xmlp-server-config.xml file from step 1 to
the newly created BI Publisher
<application
installation>/WEB-INF/ directory, where your application server unpacked the
BI Publisher war or ear file.
Example:
In an Oracle AS/OC4J 10.1.3 deployment, the location is
<ORACLE_HOME>/j2ee/home/applications/xmlpserver/xmlpserver/WEB-INF/xmlp-server-config.xml
8- Copy ssodefaults.xml to the following directory. And replace [host]:[port]
with your server's information.
Default values for other properties can be updated depending on your configuration.
<ExistingRepository>\XMLP\Admin\Security
9- Copy database-config.xml to the following directory.
<ExistingRepository>\XMLP\Admin\Scheduler
10- Restart xmlpserver application or Application Server
Optional configuration:
If you use JNDI for Scheduler, update the following line in
{Oracle_Home}/xmlp/XMLP/Admin/Scheduler/quartz-config.properties.
OLD:
org.quartz.jobStore.driverDelegateClass=org.quartz.impl.jdbcjobstore.oracle.OracleDelegate
NEW:
org.quartz.jobStore.driverDelegateClass=org.quartz.impl.jdbcjobstore.StdJDBCDelegate
Restart xmlpserver and reconfigure Scheduler with JNDI connection.
11.Restart the oc4j container.
NOTE:
Make sure the customer is aware that you are redeploying the BI publisher, so some possible customization might be lost.
