Installing Oracle BI Publisher into a WLS Application Server

[Article based on:]

The following article describes Oracle BI Publisher installation process on a WLS 11g running on a UNIX server.

Components required for the installation can be found in “/manual” subdirectory of the BI Publisher installation folder.

The BI Publisher install media contains:




Font files


xmlpserver.war (for non-oc4j application servers)
xmlpserver.ear (for non-oc4j application servers)


xmlpserver.ear (for oc4j)


XMLP repository


Data source for demo reports.


Template Builder for Word Add-in


Installation steps


  1. Create an exploded archive directory.



    jar -xvf /<installation_dir>/manual/generic/xmlpserver.war

  2. In a browser, open the WebLogic Administration console (ex. http://hostname:7001/console).
  3. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit.
  4. In the left pane of the Administration Console, click Deployments.
  5. In the right pane, click Install

  1. Select xmlpserver.war directory and click Next
  2. Select “Install this deployment as an application” and click Next

  1. Select deployment target

  1. Select “I will make the deployment accessible from the following location” from Source accessibility.

  1. Click Finish. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
  2. Copy the XMLP repository directory from \manual on your installation media to your server, ex. /oracle/bipubhome/xmlpserver.war

    Note: If you are installing BI Publisher to work with OER, please copy XMLP directory supplied with OER.

  3. 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.


    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 or later, the file contains the following:

    <?xml version="1.0" encoding="UTF-8"?>

    <xmlpConfig xmlns="">


        <file path="${oracle.home}/xdo/repository"/>



    Note: If you are on version 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.


  4. 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="">


        <file path="/home/repository/XMLP"/>



    Save xmlp-server-config.xml after updating.


  5. 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:


    Example for WebSphere:

    <WebSphere dir>/AppServer/java/jre/lib/font

  6. Start the service: click Deployments, then xmlpserver.

    Start xmlpserver application.

  7. Launch BI Publisher:

    Open your browser to http://hostname:port/xmlpserver

    For example:


  8. Log in with user name “Administrator” and password “Administrator”.

    Important: Default Administrator password can be changed on the Account tab under Preferences.

  9. Remark: if you are installing BIP for OER, copy XMLP folder from OER for BIP; look for “reports” folder in OER installation, e.g.: /oracle/fmwhome/repository111/core/tools/solutions/reports

    Replace content of XMLP in destination folder, e.g. /oracle/bipubhome/xmlpserver.war.





OER Database Configuration

ORE database can be configured either automatically, using GUI provided by the system, or manually, based on the instruction provided bellow.

Database configuration GUI

GUI can be started from <repositoryxxx/common/bin>:

Good old BEA configuration screen prompts for options:

Current settings can be modified on the following screen:


  1. If database is already created, create new user, e.g. OER2.
  2. After configuration is finished, copy configurations files (, dbinfo.xml) to all locations:


Files generated by GUI


Files created by /oracle/fmwhome/repository111/common/bin/ in this location











Manual configuration

Manual configuration is based on the following files, located in <reposirotyxxx/weblogic/application/

File contain configuration of currently used data source:

Changing database password

Since password in the configuration is encrypted, encrypted version has to be provided. In order to encrypt password, PasswordEncryption utility has to be used.

Detailed instruction on how to encrypt password can be find at:

Password tool can be found in the following location:

“” script takes password as an input.

Additional notes:

  1. Configuration files location

The actual location of the configuration files can be found in config.xml at:




  1. Escape characters in password

Each reserved character in file should be escaped, e.g. ‘\=’

  1. Xml config file
  2. Error: Exception in thread “main” java.lang.NoClassDefFoundError: sun.misc.BASE64Encoder

If password encryption script returns the above error, include in classpath rt.jar, that can be found under /jre/lib directory