Oracle Business Intelligence Publisher Installation Guide Release 10.1.3.3.2 Part Number E11867-01 | ![]() Contents | ![]() Previous | ![]() Next |
The BI Publisher install media contains:
BI Publisher server application
BI Publisher runtime libraries
BI Publisher fonts
BI Publisher desktop tools
Documentation: User’s Guide, Javadocs, demos, and samples
Individual components are located as follows:
Directory | Component |
---|---|
manual\fonts | Font files |
manual\generic | xmlpserver.war (for non-oc4j application servers) xmlpserver.ear (for non-oc4j application servers) |
manual\oc4j | xmlpserver.ear (for oc4j) |
manual\XMLP | XMLP repository |
manual\XMLP\DemoFiles | Data source for demo reports. |
manual\XMLP\Tools | Template Builder for Word Add-in |
The server application allows you to create, manage and schedule reports. You must perform the following steps as described in this document to deploy Oracle BI Publisher manually:
Deploy BI Publisher on the application server.
Configure the BI Publisher repository and install fonts.
Perform postinstallation tasks:
Create the BI Publisher scheduler schema on the database server (required to send and schedule reports).
Set up the BI Publisher Demo Reports
BI Publisher is a pure J2EE application and has been extensively tested on:
Oracle AS 10.1.3
OC4J Standalone 10.1.3
Apache Tomcat 5.5
IBM WebSphere 6.0, 6.1
Sun Java System Web Server 6.1, 7.0
BEA WebLogic 8.1, 9.2
Depending on how you have installed Oracle Application Server or OC4J, there are several methods you can use to deploy BI Publisher. Oracle recommends using Oracle Application Server Control to deploy Java applications. The following steps use the admin_client.jar file to deploy BI Publisher on Oracle AS 10.1.3 or OC4J 10.1.3. Please refer to the Oracle Containers for J2EE Deployment Guide to see which deployment method is best for your installation.
Deploy the xmlpserver.ear to your OC4J instance.
Syntax:
java -jar admin_client.jar deployer:oc4j:opmn://<host>:<OPMN_Request_port>/<instance_name> oc4jadmin<oc4jadmin_Password> -deploy -file xmlpserver.ear -deploymentName xmlpserver -bindAllWebApps
Example:
C:\product\10.1.3.1\OracleAS_1\jdk\jre\bin\java -jar admin_client.jar deployer:oc4j:opmn://localhost:6005/home oc4jadmin oc4jadmin -deploy -file C:\Temp\BIP_101332\manual\oc4j\xmlpserver.ear -deploymentName xmlpserver -bindAllWebApps
Launch the BI Publisher application.
Open your browser to http://hostname:port/xmlpserver
For example:
http://localhost:8888/xmlpserver
If you see the login page, proceed to Configuring the BI Publisher Repository and Installing Fonts.
Note: To generate documents in the widest range of locales, when starting Oracle Containers for J2EE please specify the following arguments to the Java Virtual Machine:
-Dfile.encoding=UTF-8 -Duser.language=en -Duser.country=US
This enables the BI Publisher installation to generate documents in all the supported locales and languages regardless of the language and locale of the server operating system.
Example:
C:\Java\jdk1.5.0_06\bin\java -Dfile.encoding=UTF-8 -Duser.language=en -Duser.country=US -jar C:\OC4J\j2ee\home\oc4j.jar
There are several approaches available to deploy applications to the Tomcat servlet container. Please see the Apache Tomcat Application Developer’s Guide to determine which method is appropriate for your installation. The following steps use the Tomcat Web Application Manager to deploy BI Publisher on Apache Tomcat 5.5:
Important: Apache Tomcat deployments of BI Publisher require that folder and file names use ASCII characters only. Any non-ASCII character will be displayed incorrectly.
Open the Tomcat home page.
Select Tomcat Manager and log in.
From the Tomcat Web Application Manager page, under the Deploy region, browse for and select the manual\generic\xmlpserver.war from your install media. Select the Deploy button.
Ensure the xmlpserver application successfully deployed. If successful, /xmplserver will appear on the Tomcat Web Application Manager page under the list of Applications.
Open your browser, http://hostname:port/xmlpserver to see the login page.
For example: http://localhost:8080/xmlpserver
If you see the login page, proceed to Configuring the BI Publisher Repository and Installing Fonts.
This section describes one example of how to deploy the BI Publisher application to the IBM WebSphere 6.0 or 6.1 application server. Refer to your WebSphere documentation for the appropriate procedure to install into your environment.
Access the WebSphere Administrative Console, select Install New Application.
Choose the manual/generic/xmlpserver.ear file from your installation media.
Select the Generate Default Bindings checkbox and click Next.
On the Select installation options page, select the Distribute application checkbox and the Create MBeans for resources checkbox.
On the Map modules to servers page, select xmlpserver.war.
On the Map virtual hosts for Web modules page select xmlpserver.war.
On the Summary screen, review your selections, and select Finish.
You will see the deployment status on the screen. Once you see the success message, select the Save to Master Configuration link.
Restart BI Publisher.
From the WebSphere Administration Console, select the Enterprise Applications link, choose "xmlpserver" and click the Stop button. Once stopped, choose "xmlpserver" and click the Start button.
Launch BI Publisher:
Open your browser to http://hostname:port/xmlpserver to see the login page.
For example: http://localhost:8080/xmlpserver
If you see the login page, proceed to Configuring the BI Publisher Repository and Installing Fonts.
This section describes one example of how to deploy the BI Publisher application. Follow the guidelines in your Sun Java System Web Server 6.1 documentation for the appropriate method for your installation.
Important: To successfully deploy BI Publisher on Sun Java System Web Server 6.1 you must perform the predeployment and postdeployment configuration steps described in this section:
Before you deploy, you must ensure that the maxUploadSize property is set appropriately as described in Step 1.
After you deploy, you must configure the system.xml file as described in Step 11.
The xdoparser.jar files include files from the W3C org.w3c.dom package that are excluded from the same package included with the Sun Java System Web Server system jar files. To ensure these files are loaded from the xdoparser.jar file, you must configure the server.xml file to load the xmlparser.jar files first.
Note: The Sun Web Server on Windows platform blocks any URI that contains a tilde "~" character. To allow URIs that contain a tilde, you must edit the obj.conf. The obj.conf file is located in the <instance_dir>/config directory. Edit the file as follows:
<Object name="default">
...
PathCheck fn="nt-uri-clean" tildeok=""
...
</Object>
By default, the tildeok parameter is not present. You must add this manually. For more information, see the Sun Web Server 6.1 configuration file reference:
http://docs.sun.com/source/817-1834-10/crobjsaf.html#wp18466.
Ensure the maxUploadSize property is set appropriately to handle the size of the BI Publisher WAR file. It is recommended that you set the maxUploadSize property to 100 megabytes.
To set the maxUploadSize property:
In the <WebServer-install-dir>/bin/https/webapps/admin-app/WEB-INF/web.xml, add the following parameter:
<init-param>
<param-name>maxUploadSize</param-name>
<param-value>100000000</param-value>
</init-param>
For example:
<servlet-name>webappdeploy</servlet-name>
<servlet-class>com.sun.web.admin.servlets.DeployServlet</servlet-class>
<init-param>
<param-name>maxUploadSize</param-name>
<param-value>100000000</param-value>
</init-param>
Restart the application server.
In a browser, open the Admin Console of the Sun Java System Web Server 6.1.
Select a Server from the list and click Manage.
Select the Virtual Server Class tab.
Select a Class from the list and click Manage.
From the Select a Virtual Server drop-down list, choose your server and click Manage.
Select the Web Applications tab.
On the Deploy Web Application page, browse for and select manual\generic\xmlpserver.war (non-oc4j version) from your install media. In the Application URI field, enter /xmlpserver then click OK.
Please note where this WAR file deployed, indicated in the Installation Directory field.
Click OK to deploy the application. A message appears informing that you must apply the changes. Click Apply in the top right corner, then click Apply Changes.
Configure the Sun Java System Web Server server.xml file to load the xdoparser.jar files first:
Open <WebServer-install-dir>/<https-name-of-webserver-instance>/config/server.xml
Add the following class path as the first entry for the serverclasspath attribute value in the <JAVA> tag:
<WebServer-install-dir>/<https-name-of-webserver-instance>/webapps/<https-name-of-web-server-instance>/xmlpserver/WEB-INF/lib/xdoparser.jar
Example from server.xml:
<JAVA javahome="C:/Sun/WebServer6.1/bin/https/jdk"
serverclasspath="C:/Sun/WebServer6.1/https-xmlphost/webapps/https-xmlphost/xmlpserver/WEBINF/lib/xmlparserv2-904.jar;C:/Sun/WebServer6.1/https-xmlphost/webapps/https-xmlphost/xmlpserver/WEBINF/lib/xdoparser.jar;C:/Sun/WebServer6.1/bin/https/jar/webserv-rt.jar;${java.home}/lib/tools.jar;C:/Sun/WebServer6.1/bin/https/jar/webserv-ext.jar;C:/Sun/WebServer6.1/bin/https/jar/webserv-jstl.jar;C:/Sun/WebServer6.1/bin/https/jar/ktsearch.jar"
classpathsuffix="" envclasspathignored="true"
nativelibrarypathprefix="" debug="false" debugoptions="-Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=n" dynamicreloadinterval="-1">
Launch the BI Publisher application:
Open your browser to http://hostname:port/xmlpserver to see the login page.
For example: http://localhost:8080/xmlpserver
If you see the login page, proceed to Configuring the BI Publisher Repository and Installing Fonts.
This section describes one example of how to deploy the BI Publisher application. Follow the guidelines in your Sun Java System Web Server 7.0 documentation for the appropriate method for your installation
Note: The Sun Web Server on Windows platform blocks any URI that contains a tilde "~" character. To allow URIs that contain a tilde, you must edit the obj.conf. The obj.conf file is located in the <instance_dir>/config directory, for example: C:\Program Files\Sun\WebServer7\<https-hostname>\config\obj.conf.
Edit the file as follows:
<Object name="default">
...
PathCheck fn="nt-uri-clean" tildeok=""
...
</Object>
By default, the tildeok parameter is not present. You must add this manually. For more information, see your Sun Web Server 7.0 configuration file reference (http://docs.sun.com/app/docs/doc/819-2630).
In a browser, open the Admin Console of the Sun Java System Web Server 7.0.
Select the Virtual Servers tab under Configurations.
Select the virtual server, into which you will deploy the BI Publisher application.
Select the Web Applications tab, and then click New.
Browse for and select manual\generic\xmlpserver.war (non-oc4j version) from your install media. (Optionally, you can also specify a Web application archive located on the server.)
In the Application URI field, enter /xmlpserver then click OK.
Enable the application.
Click Deployment Pending.
Click the Deploy button to deploy the BI Publisher application.
Launch the BI Publisher application:
Open your browser to http://hostname:port/xmlpserver to see the login page.
For example: http://localhost:8080/xmlpserver
If you see the login page, proceed to Configuring the BI Publisher Repository and Installing Fonts.
This section describes one example of how to deploy the BI Publisher application to the BEA WebLogic 8.1 application server. Refer to your WebLogic documentation for the appropriate procedure to install into your environment.
Important: Do not use JRockit SDK 1.4.2_08 (bundled with WebLogic 8.1). The RandomAccessFile class included with JRockit inhibits the proper generation of HTML, RTF and Excel outputs in BI Publisher reports. Instead, use Sun SDK 1.4.2 or later.
Note: Use of exploded archive directories: Do not deploy xmlpserver.ear (or xmlpserver.war) on WebLogic by uploading it from the WebLogic console because the console deploys the application (or Web module) in an archived file format. This is problematic to BI Publisher configuration because you must update WEB-INF/xmlp-server-config.xml manually after the deployment. To workaround this issue, use an "exploded archive" directory. To create an exploded archive directory, you manually unpack the xmlpserver.ear and xmlpserver.war using a jar command. For more information, see your WebLogic documentation.
Create an exploded archive directory.
mkdir C:\BIPub\xmlpserver.war
cd C:\BIPub\xmlpserver.war
jar -xvf manual\generic\xmlpserver.war
In a browser, open the WebLogic Administration console (for example:http://hostname:7001/console).
Click <domain name>/Deployments/Web Application Modules from the left tree pane.
Select Deploy a new Web Application Module.
Select C:\BIPub\xmlpserver.war as the Target Module and click Deploy.
WebLogic automatically deploys and starts up the BI Publisher server.
Open your browser to http://hostname:port/xmlpserver to see the login page.
For example: http://localhost:8080/xmlpserver
If you see the login page, proceed to Configuring the BI Publisher Repository and Installing Fonts.
This section describes one example of how to deploy the BI Publisher application to the BEA WebLogic 9.2 application server. Refer to your WebLogic documentation for the appropriate procedure to install into your environment.
Note: Use of exploded archive directories: Do not deploy xmlpserver.ear (or xmlpserver.war) on WebLogic by uploading it from the WebLogic console because the console deploys the application (or Web module) in an archived file format. This is problematic to BI Publisher configuration because you must update WEB-INF/xmlp-server-config.xml manually after the deployment. To workaround this issue, use an "exploded archive" directory. To create an exploded archive directory, you manually unpack the xmlpserver.ear and xmlpserver.war using a jar command. For more information, see your WebLogic documentation.
Create an exploded archive directory.
Example:
mkdir C:\BIPub\xmlpserver.war
cd C:\BIPub\xmlpserver.war
jar -xvf manual\generic\xmlpserver.war
In a browser, open the WebLogic Administration console (for example:http://hostname:7001/console).
If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit.
In the left pane of the Administration Console, click Deployments.
In the right pane, click Install.
Select C:\BIPub\xmlpserver.war and click Next.
Select "Install this deployment as an application" and click Next.
Select "I will make the deployment accessible from the following location" from Source accessibility.
Click Finish.
To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
Perform the configurations described in Configuring the BI Publisher Repository and Installing Fonts.
Start the service: click Deployments, then xmlpserver.
After deploying BI Publisher in your application server, you must set up the BI Publisher repository and install the font files.
To set up the repository, copy the xmlp repository directory to a location on your server, then edit the configuration file to point to the saved location as follows:
Copy the XMLP repository directory from \manual on your installation media to your server.
Open the xmlp-server-config.xml file located in the
<application installation>/WEB-INF/ directory, where your application server unpacked the war or ear file.
Example:
In an AS/OC4J 10.1.3 deployment, the location is <ORACLE_HOME>/j2ee/home/applications/xmlpserver/xmlpserver/WEB-INF/xmlp-server-config.xml
If you are on BI Publisher version 10.1.3.3.1 or later, the file contains the following:
<?xml version="1.0" encoding="UTF-8"?>
<xmlpConfig xmlns="http://xmlns.oracle.com/oxp/xmlp">
<resource>
<file path="${oracle.home}/xdo/repository"/>
</resource>
</xmlpConfig>
Note: If you are on version 10.1.3.3 of BI Publisher, the <file path> element will appear as follows:
<file path="%s_Reports_Path%"/>. Replace the "%s_Reports_Path%" string with the file path to the location where you copied the XMLP repository directory on your server, as described in the next step.
Replace ${oracle.home}/xdo/repository with file path to the location where you copied the XMLP repository directory on your server.
For example, if you copied the repository directory to/home/repository/XMLP, update the xmlp-server-config.xml file as follows:
<?xml version="1.0" encoding="UTF-8"?>
<xmlpConfig xmlns="http://xmlns.oracle.com/oxp/xmlp">
<resource>
<file path="/home/repository/XMLP"/>
</resource>
</xmlpConfig>
Save xmlp-server-config.xml after updating.
Copy the font files from the manual\fonts on the install media to the fonts directory of the Java Runtime Environment used by your J2EE container/application server.
Example for Apache Tomcat:
C:\Program Files\Java\jre1.5.0_07\lib\fonts
Example for Oracle Application Server or OC4J:
<ORACLE_HOME>…\jdk\jre\lib\fonts
Example for WebSphere:
<WebSphere dir>/AppServer/java/jre/lib/font
Restart your application server.
Launch BI Publisher:
Open your browser to http://hostname:port/xmlpserver
For example:
http://localhost:8888/xmlpserver
Log in with user name "Administrator" and password "Administrator".
Important: Please change the Administrator password on the Account tab under Preferences.