OVR Instaaltion
OVR Instaaltion
E1: OVR: Installing BI Publisher Server Instance 12.2.1.3.0 with Weblogic 12.2.1.3.0 for OVR
(Doc ID 2512616.1)
In this Document
Goal
Solution
References
APPLIES TO:
GOAL
How do you install BI Publisher Enterprise Server 12.2.1.3.0 with Weblogic 12.2.1.3.0 for use with JD Edwards EnterpriseOne
(E1) Oneview Reporting (OVR)?
SOLUTION
Note: The following are high level steps based on installing on a Weblogic Server:
1. If you have installed 11g in a previous install, uninstall your current RCU for 11g - Repository Creation Utility (RCU).
2. Go to https://edelivery.oracle.com.
3. Download Oracle Fusion Middleware 12c Infrastructure and REL: Oracle Fusion Middleware 12c Infrastructure 12.2.1.3.0.
4. Download Oracle Business Intelligence Publisher and DLP: Oracle Business Intelligence Publisher 12.2.1.3.0 (Oracle
Business Intelligence Publisher).
Note: You only need "Oracle Business Intelligence 12.2.1.3.0" from the cart, deselect the rest.
5. Install the correct JDK 1.8.x.
6. Install Middleware 12c Infrastructure 12.2.1.3.0.
Note: This includes RCU which can be found in \OracleHome\oracle.common\bin\rcu (This may not be accurate, but
should be close).
7. Install BI Publisher.
Windows OS and Weblogic
Install the MS C++ redistributable library from Microsoft (C++ redist from Microsoft site). You may need both 32bit and
64bit installed.
If during the Configuration progress the installation hangs and then errors, reference knowledge OBIEE 12c: Installation
Fails at Config Step: "Failed to build JDBC Connection object" (Doc ID 2319596.1) to apply the patch.
https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=83z1ultg0_952#REF 1/2
3/1/23, 6:47 PM Document Display
OCI Customers installing BI Publisher Server can use the OCI marketplace, for all other VMs or cloud environments,
customers can treat the installation as if it were a bare metal installation.
The below statement is to provide customers with a starting point in performance tuning, and memory allocation, this is only
meant as a starting point and understanding of BI Publisher memory requirements. Customers who need help with tuning in a
Hypervisor environment should consider outside consulting.
Customers running Virtual Devices, e.g. VMWARE and running into timeout and memory issues on the BIP/WLS side,
1. Per the BI Publisher (BIP) Install Certification, customers should allocate a minimum of 32 GB of RAM for BIP.
2. With the WLS Arguments you can start with something like, –Xms=2g and –Xmx=2g (8GB is too much) then start
increasing if more memory is needed on the WLS/BIP Server. Note: Typical rule is to not exceed 1/4 of your RAM, e.g.
16 GB of RAM then -Xmx=4g is max. Also, the value XX:MaxPermSize=xxx, is not read when using JDK 8, so this
argument can be removed and/or left out.
3. On the E1 side you can check the jdbj.ini runtime properties and make sure this is not too high, default is 60000ms for
timeout, e.g. holding the result for a long time, then this can affect memory.
REFERENCES
NOTE:2281660.1 - E1: OVR: BI Publisher User and Group setup in BI Publisher 12c for JD Edwards One View Reporting
NOTE:2319596.1 - OBIEE 12c: Installation Fails at Config Step: "Failed to build JDBC Connection object"
Didn't find what you are looking for?
https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=83z1ultg0_952#REF 2/2