http://<hostname>:<port>/xmlpserver/
and the default port is 9704.Data Source Name: Insight
Driver Type: Oracle 11g
Database Driver Class: oracle.jdbc.OracleDriver
Connection String: jdbc:oracle:thin:@<hostname>:<port>:<sid>
User name: <RCU_PREFIX>_soainfra
Password: password specified in RCU when creating users.
values: the username and password for schemas created by RCU during installation
A clarifier is essential as RCU will be run for BI Publisher and any SOA or OSB that Insight integrates to.
ORACLE_HOME
on the WebLogic server.Shared Folders/Oracle Integration Insight Reports
is created.Navigate to Security > Credentials in the Enterprise Manager Fusion Manager Control.
Figure 4-2 Enterprise Manager Fusion Middleware Control Credentials Screen
Expand oracle.soa.insight
and select INSIGHT_BIP_CONNECTION_KEY. If oracle.soa.insight
does not exist, click Create Map to create it, and then create the key INSIGHT_BIP_CONNECTION_KEY using Create Key.
Click Edit to enter or edit the user name and password. These credentials are for the BI Publisher.
The Edit Key Dialog opens. Enter the following details:
Figure 4-3 Edit Key Dialog
User Name: enter the user name you want to use to log in to BI Publisher. This is a mandatory field.
Password: enter a password to log in to BI Publisher. This is a mandatory field.
Confirm Password: re-enter the password you entered in the above step. This is a mandatory field.
Description: enter a suitable description for the key. This is an optional field.
Click OK.
Figure 4-4 ConfigMBean:InsightConfigBean
The BiUserServerName
field is unused and the BiServerPassword
contains INSIGHT_BIP_CONNECTION_KEY, which is the default value.
BiServerPassword
— The CSF Password Credential Key for the BI Publisher Server. The key should be INSIGHT_BIP_CONNECTION_KEY as created in the Credential Store.
BiServerUrl
— URL of the BI Publisher Server. Enter a value similar to http://<host:port>/
. Do not forget to include the port number in the URL. The integration will automatically append xmlpserver/ to the end of this URL, so only the protocol, host and port are included
BiServerUsername
— this attribute is not used.
The configuration must be validated by logging in to the Insight application. You will see reports when you navigate to Reports. The reports will start generating the data when you have created and activated models.