Example
This example details the required updates to change the Publisher context from xmlpserver
to /sales/xmlpserver
.
Perform these tasks:
Update the xmlpserver META-INF/application.xml File
Update the context-root of the META-INF/application.xml file.
-
Unzip the xmlpserver.ear file.
-
Navigate to META-INF/application.xml under the xmlpserver WAR.
-
Update the context-root to match you new context. In this example the context root is updated to /sales/xmlpserver:
<web> <web-uri>xmlpserver.war</web-uri> <context-root>/sales/xmlpserver</context-root> </web>
Update the xmlpserver WAR/WEB-INF/web.xml File
Under the xmplserver WAR/WEB-INF folder, update the web.xml file.
-
Navigate to the WAR/WEB-INF/web.xml file.
-
Update the following parameter values in the file:
<init-param> <!-- This is the root webdir for the xmlpserver application. Modify this if xmlpserver.ear is not deployed to its standard location. --> <param-name>xmlp-online-web-dir</param-name> <param-value>/sales/xmlpserver</param-value> </init-param> <init-param> <!-- Path to the ServiceGateway SOAP end point. Most likely this will be the path for services deployed with Axis. --> <param-name>service-endpoint</param-name> <param-value>/sales/xmlpserver/services/ServiceGateway</param-value> </init-param> <init-param> <!-- Path to report service web directory. --> <param-name>web-dir</param-name> <param-value>/sales/xmlpserver/report_service</param-value> </init-param>
Update the xmlpserver WAR/WEB-INF/weblogic.xml File
Under the xmplserver WAR/WEB-INF folder, update the weblogic.xml file.
-
Navigate to the WAR/WEB-INF/weblogic.xml file.
-
Update the cookie-path and context-root in the file:
<wls:session-descriptor> <wls:cookie-path>/sales/xmlpserver</wls:cookie-path> </wls:session-descriptor> <wls:context-root>sales/xmlpserver</wls:context-root>
Update the xmlp-server-config.xml File
Update an element in the xmlp-server-config.xml file.
-
Navigate to:
Oracle_Home/user_projects/domains/bi/config/fmwconfig/biconfig/bipublisher/Admin/Configuration/xmlp-server-config.xml
-
Update the following element in the file:
<property name="SAW_URL_SUFFIX" value="sales/analytics/saw.dll"/>
Update the analytics META-INF/application.xml File
Update the elements in the file to match your context-root.
-
Unzip the analytics.ear file.
-
Navigate to the META-INF/application.xml file.
-
Update the following elements to match your context-root:
<display-name>analytics</display-name> <module> <web> <web-uri>analytics.war</web-uri> <context-root>sales/analytics</context-root> </web> </module> <module> <web> <web-uri>analytics-ws.war</web-uri> <context-root>sales/analytics-ws</context-root> </web> </module> <module> <web> <web-uri>analytics.war</web-uri> <context-root>sales/analytics-bi-adf</context-root> </web> </module>
Update the instanceconfig.xml File
Update the instanceconfig.xml file.
-
Navigate to the instanceconfig.xml located at
[ORACLE_INSTANCE]\config\OracleBIPresentationServicesComponent\coreapplication_obips1\instanceconfig.xml
-
Update the <ServerBasedURL> and <WebURL> elements under <AdvancedReporting> in the file:
<AdvancedReporting> <ServerBaseURL>/sales/xmlpserver</ServerBaseURL> <WebURL>/sales/xmlpserver</WebURL> </AdvancedReporting>
Update the bipublisher and analytics Applications in WebLogic Server
Update the bipublisher and analytics applications in the Oracle WebLogic Server Administration Console.
-
Repackage the xmplserver.ear file.
-
Repackage the analytics.ear file.
-
Open your Oracle WebLogic Server Administration Console.
-
In the Change Center of the Administration Console, click Lock & Edit.
-
In the left pane of the Console, select Deployments. A table in the right pane displays all deployed Enterprise Applications and Application Modules.
-
In the table, select the bipublisher application.
-
Click Update.
-
Click Finish (do not change the source path).
-
Repeat Step 6 through Step 8 for the analytics application.
-
In the Change Center of the Administration Console, click Activate Changes and then click Release Configuration.