This chapter contains information about installing and managing Oracle Business Intelligence components on IBM WebSphere. This chapter includes the following sections:
Introduction to Oracle Business Intelligence on IBM WebSphere
Differences Installing and Configuring Oracle Business Intelligence on IBM WebSphere
Upgrading Oracle Business Intelligence to Run on IBM WebSphere
Troubleshooting Oracle Business Intelligence on IBM WebSphere
Oracle Business Intelligence provides a full range of business intelligence capabilities that allow you to collect up-to-date data from your organization, present the data in easy-to-understand formats, and deliver data in a timely fashion to the employees in your organization. These capabilities enable your organization to make better decisions, take informed actions, and implement more-efficient business processes.
This section includes the following topics for using Oracle Business Intelligence on IBM WebSphere:
For complete information on Oracle Business Intelligence, see the documentation at the following location:
http://docs.oracle.com/cd/E23943_01/bi.htm
Many of the features of Oracle Business Intelligence behave the same, regardless of whether you install Oracle Business Intelligence on WebLogic Server or on IBM WebSphere. The following list outlines these features:
Analyses, Dashboards, Actions, Agents, Conditions, KPIs, Scorecards, BI Composer, Oracle Business Intelligence Mobile, Oracle Real-Time Decisions, and Marketing Server — You use the feature in the same way on both WebLogic Server and IBM WebSphere.
Actions — You use actions that involve web services in the same way on both WebLogic Server and IBM WebSphere. Actions that involve Enterprise Java Beans (EJB) require manual configuration, as described in Section 10.2.9, "Configuring for Actions that Invoke a Java Method on IBM WebSphere."
Map Views — You use the feature in the same way on both WebLogic Server and IBM WebSphere, but you must manually configure Oracle Fusion Middleware MapViewer, as described in Section 10.2.8, "Configuring for Map Views in Oracle Business Intelligence on IBM WebSphere."
Oracle BI Publisher — You use the feature in nearly the same way on both WebLogic Server and IBM WebSphere, but manual configuration is required as described in Section 10.2.3, "Configuring for BI Publisher on IBM WebSphere." Scheduling is available for reports using ActiveMQ as a provider, rather than the WebLogic JMS queues. For information on ActiveMQ, see "Scheduler Configuration Reference" in Oracle Fusion Middleware Administrator's Guide for Oracle Business Intelligence Publisher.
System Management — Features including starting, stopping and configuring Oracle Business Intelligence using Fusion Middleware Control, and using the Catalog Manager. Monitoring metrics, using the Log Viewer, and moving from test to production are not available in this release.
Single Sign On and Secure Socket Layers — You use the feature in the same way on both WebLogic Server and IBM WebSphere, but manual configuration is required as described in Section 10.2.7.2, "Configuring SSO for Oracle Business Intelligence on IBM WebSphere" and Section 10.2.7.3, "Configuring SSL for Oracle Business Intelligence on IBM WebSphere."
Oracle BI Web Services — You use the feature in the same way on both WebLogic Server and IBM WebSphere with the exception of Oracle Business Intelligence Metadata Web service and Web Services for SOA, which are not available for IBM WebSphere.
High-Availability — You use the feature in the same way on both WebLogic Server and IBM WebSphere, but manual configuration is required as described in Section 10.2.11, "Configuring for Scaling the Deployment of Oracle Business Intelligence on IBM WebSphere."
Upgrading — You can upgrade Oracle Business Intelligence if you have an installation on Oracle WebLogic Server, as described in Section 10.4, "Upgrading Oracle Business Intelligence to Run on IBM WebSphere."
Oracle BI for Microsoft Office — You use the feature in nearly the same way on both WebLogic Server and IBM WebSphere, but manual configuration is required as described in Section 10.2.10, "Configuring for Oracle BI for Microsoft Office on IBM WebSphere."
The following list describes the limitations of Oracle Business Intelligence on IBM WebSphere for this release:
Windows, Solaris, and SLES/SUSE platforms are not supported.
IBM WebSphere Application Server Standalone is not supported.
The Sample Application for Oracle Business Intelligence is not supported. The SampleAppLite application is supported.
The following features are not available with IBM WebSphere for this release: Full-text catalog search, multitenancy, Financial Reporting, Calculation Manager, Smart View integration, Essbase Administration Services and Analytic Provider Services, Oracle BI Services for SOA, and Oracle WebCenter Portal integration. The IBM WebSphere integration is not available for an Exalytics In-Memory Machine.
You can use Oracle Business Intelligence components on IBM WebSphere without having WebLogic Server installed, with one exception. If you plan to upgrade from an earlier version of Oracle Business Intelligence, then you must have Oracle Business Intelligence on both WebLogic Server and IBM WebSphere for Release 11g, as described in Section 10.4, "Upgrading Oracle Business Intelligence to Run on IBM WebSphere."
Use the first three chapters of this guide for basic information on installing and configuring Oracle Business Intelligence on IBM WebSphere. This section provides procedures that outline the differences between installing and configuring Oracle Business Intelligence on IBM WebSphere instead of on Oracle WebLogic Server:
Configuring Oracle Business Intelligence in a New IBM WebSphere Cell
Configuring for Security of Oracle Business Intelligence on IBM WebSphere
Configuring for Map Views in Oracle Business Intelligence on IBM WebSphere
Configuring for Actions that Invoke a Java Method on IBM WebSphere
Configuring for Oracle BI for Microsoft Office on IBM WebSphere
Configuring for Scaling the Deployment of Oracle Business Intelligence on IBM WebSphere
Installing Oracle Business Intelligence on IBM WebSphere is similar to installing on Oracle WebLogic Server. When installing on IBM WebSphere, you use the Software-Only installation type to create an IBM WebSphere cell rather than a domain in WebLogic Server.
This section contains the following topics:
Keep the following points in mind as you prepare for installation:
Ensure that an appropriate version of IBM WebSphere is installed, as specified in the certification document.
See Section 2.1, "Task 1: Review the System Requirements and Certification Information" for details on the certification document.
Ensure that you use the Repository Creation Utility to configure the BIPLATFORM and MDS schemas that Oracle Business Intelligence uses.
For information, see "Create Database Schemas Using the Repository Creation Utility (RCU)" in Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.
Do not install Oracle Business Intelligence into an existing IBM WebSphere cell, which can decrease system security.
Install IBM WebSphere and Oracle Business Intelligence on the same host.
Table 10-1 provides a summary of the procedure for intalling Oracle Business Intelligence on IBM WebSphere using the Software Only install type. For complete information on this install type, see "Software Only Install" in Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.
Table 10-1 Summary of Software Only Install Procedure
| Screen | Actions |
|---|---|
|
None |
Start Oracle Business Intelligence 11g Installer. |
|
Welcome |
Click Next to continue |
|
Install Software Updates |
Specify your My Oracle Support account information and software update preferences. Click Next to continue. |
|
Select Installation Type |
Click Software Only Install. Select this option to copy the software binary files to the target computer. You do not configure the components until after the installation finishes. Click Next to continue. |
|
Prerequisite Checks |
Click Next to continue. |
|
Specify Installation Location |
Specify the Oracle Middleware Home location for IBM WebSphere and the Oracle Business Intelligence Home location. For information on the directory in which IBM WebSphere is installed, see Section 2.4.2.3, "About the WAS_HOME Directory Path." The locations for the Fusion Middleware Home and the Oracle Home must not be within the directory in which IBM WebSphere is installed. Click Next to continue. |
|
Application Server |
Review and confirm that the IBM WebSphere application server and its location are automatically selected. Click Next to continue. |
|
Security Updates |
Specify your My Oracle Support account information and security update preferences. Click Next to continue. |
|
Summary |
Verify the information on this screen. Click Back to change the information in a previous screen. Click Save to save the settings for the installation in a response file. Click Install to begin the installation |
|
Installation Progress |
When the installation is 100% complete, click Next to continue |
|
Complete |
Click Finish to exit Oracle Business Intelligence 11g Installer. |
To configure Oracle Business Intelligence on IBM WebSphere, you use the Configuration Assistant, similar to how you configure on Oracle WebLogic Server. The Configuration Assistant creates an IBM WebSphere cell, configures the BI_PLATFORM and MDS database schemas, and configures the Oracle Business Intelligence system.
The following procedure describes how to use the Configuration Assistant for Oracle Business Intelligence on IBM WebSphere.
To configure Oracle Business Intelligence software on IBM WebSphere:
Set the environment variable and run the Configuration Assistant using commands such as the following ones:
setenv WAS_HOME <install-directory>
ORACLE_HOME/bin/config.sh
Configure a new Oracle Business Intelligence system, with a cell and appropriate user name and password.
You cannot scale out or extend the system using the Configuration Assistant.
At the end of the configuration process, all processes should be running. See Section 10.5.1, "Verifying the Configuration of Oracle Business Intelligence on IBM WebSphere" for information on viewing running processes.
After running the Configuration Assistant, perform the following steps to complete the configuration:
Log into the IBM WebSphere Administrative Console.
Navigate to Servers, Server Types, and WebSphere Application Servers.
Click on the server to which you must apply the custom property, which is usually biserver1.
Under Configuration and Container settings, click Web Container Settings, then click Web container.
Under Configuration and Additional Properties, click Custom Properties.
On the Custom Properties page, click New.
On the Settings page, enter com.ibm.ws.webcontainer.invokeFilterInitAtStartup as the name of the property to added in the Name field and enter true in the Value field.
Note that some properties are case-sensitive.
Click OK.
Click Save in the Messages box that is displayed.
Restart the server so that the custom property can take effect.
BI Publisher is installed and primarily configured as part of the process of installing and configuring Oracle Business Intelligence. You must perform additional procedures as described in the following topics:
To manually configure for BI Publisher on IBM WebSphere:
Stop the processes for IBM WebSphere as described in Section 10.2.5, "Starting and Stopping Components on IBM WebSphere."
In a text editor, open the following file:
user_projects/domains/bifoundation_cell/bifoundation_cell_dmgr0/config/cells/bifoundation_cell/fmwconfig/system-jazn-data.xml
Locate the app-role section of the file and add an entry for the wasadmin user, as shown in the following example:
<app-role>
<name>BIAdministrator</name>
<display-name>BI Administrator Role</display-name>
<guid>BB2BA241CC0411E1BF58057424DD2C21</guid>
<class>oracle.security.jps.service.policystore.ApplicationRole</class>
<members>
<member>
<class>weblogic.security.principal.WLSGroupImpl</class>
<name>BIAdministrators</name>
</member>
<member>
<class>weblogic.security.principal.WLSUserImpl</class>
<name>wasadmin</name>
</member>
</members>
</app-role>
Ensure that you add the wasadmin line for the WLSUserImpl class, and not for the WLSGroupImpl class.
Save and close the file.
Display the Administration page for BI Publisher by entering the following URL:
http://host-name:port-num/xmlpserver
Select Administration and Server Configuration. Select Oracle BI EE Catalog for Catalog Type and select Apply.
Configure for ActiveMQ, as described in "Configuring BI Publisher for ActiveMQ" in Oracle Fusion Middleware Administrator's Guide for Oracle Business Intelligence Publisher.
Restart the processes for IBM WebSphere as described in Section 10.2.5, "Starting and Stopping Components on IBM WebSphere."
When you use BI Publisher on IBM WebSphere, you must use the Administration page to specify the Oracle BI Presentation Catalog. You must always use the following procedure when using the Administration page on IBM WebSphere.
To use the Administration page of BI Publisher on IBM WebSphere:
Log in to BI Publisher on the managed server that is running on the same host computer as the OracleAdminServer and the Dmgr for IBM WebSphere.
The managed server is likely named bi_server1.
Click Administration and make the appropriate changes.
Click Apply.
In the IBM WebSphere Administration console, click System Administration, then Nodes.
Select all the scaled-out nodes for Oracle Business Intelligence.
Click Full Resynchronize button and watch for that to succeed.
Click Applications, Application Types, and WebSphere enterprise applications.
Select bipublisher_11.1.1 in the application list.
Click Stop and watch for the application to show as "Stopped" in the list
Select bipublisher_11.1.1 in the application list.
Click Start and watch for the application to show as "Started" in the list.
The administration changes are saved and replicated to all nodes of the cluster for Oracle Business Intelligence.
Oracle RTD is installed and primarily configured as part of the process of installing and configuring Oracle Business Intelligence. You must perform additional procedures as described in the following topics:
Then, depending on your system configuration and requirements, you may need to perform the following procedures:
To enable Oracle RTD Inline Services to be deployed in Oracle Real-Time Decisions Studio, you must disable parent class loading in the IBM WebSphere Administration Console, as described in the following procedure. If you want to use SSL with Oracle RTD, then see Section 10.2.7.3, "Configuring SSL for Oracle Business Intelligence on IBM WebSphere."
To manually configure for Oracle RTD on IBM WebSphere:
In the IBM WebSphere Administration console, select Applications, Application Types, WebSphere enterprise applications, Oracle RTD, and Class loading and update detection.
Select Classes loaded with local class loader first (parent last).
Save your change.
Oracle RTD automatically supports certain specific web service policies. If you define your own server-wide web policy sets, you must configure constraints for those policy sets. If you do not do so, the Oracle RTD client-side tools may not work correctly, such as content panes not appearing on Decision Center logins.
Note:
If the Oracle RTD client-side files are configured on a separate machine to the server, you must configure the constraints for user-defined web policy sets on both client and server machines.
You can configure the policy set constraints either in Fusion Middleware Control or through using wsadmin commands.
General information about configuring policy set constraints is available in "Specifying Run-time Constraints in Policy Sets" in Oracle Fusion Middleware Security and Administrator's Guide for Web Services, and detailed instructions appear in "Using Fusion Middleware Control."
Specifically for Oracle RTD, follow the instructions in "Using Fusion Middleware Control," and in the Enter Constraint page, perform the following steps:
Select the options Enabled and !(NOT) Operator.
For HTTP Header Name, enter rtd_scope.
For HTTP Header Value, enter internal.
General information about entering wsadmin commands is available in Section 3.1.3, "Using the Oracle Fusion Middleware wsadmin Commands."
The wsadmin commands dealing with policy sets appear in the wsmManage category. For more information, see Section 8.5, "Using the Web Services wsadmin Commands" and Section 8.5.3, "wsmManage wsadmin Commands."
Specifically for Oracle RTD, on initial creation of the policy set, you must include the following line:
wsmManage.setPolicySetConstraint("!HTTPHeader('rtd_scope', 'internal')")
If the policy set has already been created, modify the policy set as follows, after replacing <YourPolicySet> with your particular policy set name:
wsmManage.beginRepositorySession()
wsmManage.modifyPolicySet('<YourPolicySet> ')
wsmManage.setPolicySetConstraint("!HTTPHeader('rtd_scope', 'internal')")
wsmManage.commitRepositorySession()
To install Oracle RTD client-side files, perform the procedures described in "Installing Oracle RTD Client-Side Files" in Oracle Fusion Middleware Administrator's Guide for Oracle Real-Time Decisions.
If you want to use the two example Inline Services, CrossSell and DC_Demo, that are included with Oracle Real-Time Decisions, perform the procedures described in "Populating the Example Data Tables (Optional)" in Oracle Fusion Middleware Administrator's Guide for Oracle Real-Time Decisions.
The following procedure shows the sequence that you must use to stop and start the various components that allow Oracle Business Intelligence to run in the cell. See Section 2.7, "Task 7: Start the IBM WebSphere Servers" for additional information on starting processes.
Note:
You can include the commands for starting and stopping components in a script that is appropriate for the operating system. Running a script is more convenient than entering each command separately each time.
The steps in the following procedure assume that the user_projects directory is under the MW_HOME/user_projects directory. However, the user_projects directory can be located under WAS_HOME/user_projects or another directory that was selected when Oracle Business Intelligence was installed.
To start and stop components on IBM WebSphere:
Log into the Administration node for Oracle Business Intelligence and open a terminal window.
Stop all components by entering the following commands:
MW_HOME/instances/instance1/bin/opmnctl stopall MW_HOME/user_projects/domains/bifoundation_cell/bifoundation_cell_node0/bin/stopServer.sh bi_server1 -username user_name -password password MW_HOME/user_projects/domains/bifoundation_cell/bifoundation_cell_node0/bin/stopServer.sh bi_server1 -username user_name -password password MW_HOME/user_projects/domains/bifoundation_cell/bifoundation_cell_node0/bin/stopServer.sh OracleAdminServer -username user_name -password password MW_HOME/user_projects/domains/bifoundation_cell/bifoundation_cell_node0/bin/stopNode.sh -username user_name -password password MW_HOME/user_projects/domains/bifoundation_cell/bifoundation_cell_dmgr/bin/stopManager.sh -username user_name -password password
Start the Deployment Manager by entering the following command:
MW_HOME/user_projects/domains/bifoundation_cell/bifoundation_cell_dmgr/bin/startManager.sh -username user_name -password password
Start the node by entering the following command:
MW_HOME/user_projects/domains/bifoundation_cell/bifoundation_cell_node0/bin/startNode.sh -username user_name -password password
Start the OracleAdminServer server by entering the following command:
MW_HOME/user_projects/domains/bifoundation_cell/bifoundation_cell_node0/bin/startServer.sh OracleAdminServer -username user_name -password password
Start the Managed Server by entering the following command:
MW_HOME/user_projects/domains/bifoundation_cell/bifoundation_cell_node0/bin/startServer.sh bi_server1 -username user_name -password password
Restart OPMN components by entering the following commands:
MW_HOME/instances/instance1/bin/opmnctl startall MW_HOME/instances/instance1/bin/opmnctl status
When you install Oracle Business Intelligence with IBM WebSphere, you use different port numbers to access various components than you use on WebLogic Server. Port numbers can also differ between SSL and non-SSL environments and in scaled-out environments. See Chapter 3, "Managing Oracle Fusion Middleware on IBM WebSphere" and the documentation for IBM WebSphere for information on locating ports for various processes such as Fusion Middleware Control and the IBM WebSphere Administration Console.
Table 10-2 describes port numbers that are generally assigned and the URLs for accessing the components.
Table 10-2 Typical Port Numbers and URLs for Components
| Component | Non-SSL Port Number | SSL Port Number | URL |
|---|---|---|---|
|
Oracle BI Presentation Services |
9704 |
9804 |
http://host-name:port-num/analytics or https://host-name:port-num/analytics |
|
Oracle BI Publisher |
9704 |
9804 |
http://host-name:port-num/xmplserver or https://host-name:port-num/xmplserver |
|
Fusion Middleware Control |
9002 |
9003 |
http://host-name:port-num/em or https://host-name:port-num/em |
|
IBM WebSphere Administration Console |
Not available |
9043 or 9045 |
https://host-name:port-num/ibm/console |
You must ensure that you implement appropriate security when using Oracle Business Intelligence on IBM WebSphere. This section contains the following topics on security:
Configuring SSO for Oracle Business Intelligence on IBM WebSphere
Configuring SSL for Oracle Business Intelligence on IBM WebSphere
Ensure that you are familiar with the information on security that is provided in the documentation for IBM WebSphere and for Oracle Business Intelligence. If you use Oracle Business Intelligence, then see Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition. If you use Oracle RTD, then see "Security for Oracle Real-Time Decisions" in Oracle Fusion Middleware Administrator's Guide for Oracle Real-Time Decisions.
When you install Oracle Business Intelligence with IBM WebSphere, the system is installed using an XML-based identity store that is not secure. This identity store allows for easy configuration of an instance of Oracle Business Intelligence that is running after installation. You can use Oracle BI Presentation Services, but with restricted access. You must use an LDAP-based identity store to access more features of Oracle Business Intelligence while securing the system.
After you install Oracle Business Intelligence with IBM WebSphere, you must configure an LDAP-based identity store such as Oracle Internet Directory or Microsoft Active Directory, as described in the following sections.
The following sections describe how to configure Oracle Internet Directory or Microsoft Active Directory as the external identity store for use when authenticating and authorizing access to Oracle Business Intelligence and the IBM WebSphere Administration Console Web interface. The steps are similar for the two types of identity store, as described in the following list:
Step 1: Ensuring the Prerequisites for the Identity Store on IBM WebSphere
Step 2: Configuring Required Users and Groups in the Provider for IBM WebSphere
Step 3: Creating the Properties File for the Identity Store on IBM WebSphere
Step 4: Updating the BISystemUser Credential on IBM WebSphere
Step 5: Reassociating Oracle Business Intelligence with the Identity Store on IBM WebSphere
Before you begin configuring the identity store, ensure that the following are true:
You have installed Oracle Business Intelligence on IBM WebSphere using the instructions in this chapter.
You have administrator access to a computer that has an installed Oracle Internet Directory or Active Directory instance on which you can create groups and users.
The "wasadmin" user exists in the LDAP-based identity store with which you are reassociating.
See "Configuring Alternative Authentication Providers" in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition for information on configuring Oracle Internet Directory or Active Directory as authentication providers.
To create the properties file for the LDAP-based identity store on IBM WebSphere:
Log into the Administration node for Oracle Business Intelligence and open a terminal window.
Create a .properties file that can provide the details for the identity store to IBM WebSphere and the JPS subsystem.
Save your changes to the file.
The following examples provide sample properties files that you can create. You must modify the user and group search base properties based on the information that you gathered in Section 10.2.7.1.2, "Step 2: Configuring Required Users and Groups in the Provider for IBM WebSphere.". You must modify the following values as appropriate:
user.search.bases — The container within which users are found.
group.search.bases — The container within which groups are found.
subscriber.name — The root directory for this subscription.
ldap.host — The host name of the instance for the identity store.
ldap.port — The port number on which the instance for the identity store is available.
admin.id — The full distinguished name of the user who binds to the service for the identity store. For example, cn=orcladmin
admin.pass — The password of the user who binds to the service for the identity store.
The following example shows a properties file for use with Oracle Internet Directory.
user.search.bases=cn=Users,dc=us,dc=oracle,dc=com
group.search.bases=cn=Groups,dc=us,dc=oracle,dc=com
subscriber.name=dc=us,dc=oracle,dc=com
ldap.host=myserver.example.com
ldap.port=3060
# admin.id must be the full DN of the user in the LDAP
admin.id=cn=orcladmin
admin.pass=password-name
user.filter=(&(uid=%v)(objectclass=person))
group.filter=(&(cn=%v)(objectclass=groupofuniquenames))
user.id.map=:uid
group.id.map=:cn
group.member.id.map=groupofuniquenames:uniquemember
ssl=false
# primary.admin.id indicates the user you want to be the primary
# administrative user on WebSphere. It should be a user under user.search.bases.
# later you need to use this user's user name and password to manage or
# start/stop the server.
primary.admin.id=wasadmin
# optional, default to "OID"
idstore.type=OID
# other, optional identity store properties can be configured in this file.
username.attr=cn
The following example shows a properties file for use with Active Directory.
user.search.bases=cn=Users,dc=smartinc,dc=com
group.search.bases=cn=Builtin,dc=smartinc,dc=com
subscriber.name=dc=smartinc,dc=com
ldap.host=ad.smartinc.com
ldap.port=389
# admin.id must be the full DN of the user in the LDAP
admin.id=cn=admin,cn=Users,dc=smartinc,dc=com
admin.pass=password-name
user.filter=(&(samaccountname=%v)(objectclass=user))
group.filter=(&(samaccountname=%v)(objectclass=group))
user.id.map=:samaccountname
group.id.map=:cn
group.member.id.map=group:member
ssl=false
# primary.admin.id indicates the user you want to be the primary
# administrative user on WebSphere. It should be a user under user.search.bases.
# later you need to use this user's user name and password to manage or
# start/stop the server.
primary.admin.id=wasadmin
# optional, default to "OID"
idstore.type=ACTIVE_DIRECTORY
# other, optional identity store properties can be configured in this file.
username.attr=cn
When you install Oracle Business Intelligence, the file-based identity store assigns the BISystemUser a password. You must use a command in IBM WebSphere for the new identity store to recognize the user name and password for the BISystemUser.
To update the BISystemUser credential on IBM WebSphere:
From a terminal window on the computer on which IBM WebSphere is running, enter the following commands:
setenv WAS_HOME IBM_WebSphere_install_dir cd MW_HOME ./Oracle_BI1/common/bin/wsadmin.sh -connType SOAP -host localhost -port 8879 wsadmin> Opss.updateCred(map="oracle.bi.system",key="system.user",user="BISystemUser",password="password-name")
Note:
When you enter the wsadmin.sh command, the system prompts you for the user name and password. These commands assume that the SOAP port is 8879. You can verify port numbers by viewing the AboutThisProfile.txt file in the following directory:
MW_HOME/user_projects/domains/bifoundation_cell/bifoundation_cell_dmgr0/logs/AboutThisProfile.txt
See Chapter 3, "Managing Oracle Fusion Middleware on IBM WebSphere" for additional information on ports.
You must reassociate Oracle Business Intelligence with the identity store so that information about users is available to Oracle Business Intelligence.
To reassociate Oracle Business Intelligence with the identity store on IBM WebSphere:
In the same terminal window in which you updated the BISystemUser credential, enter the following commands:
wsadmin> Opss.configureIdentityStore(propsFileLoc="/<dir-name>/ldap.properties") wsadmin> quit
If you use Oracle RTD on IBM WebSphere, then to ensure that Oracle RTD functions properly, you must associate the Oracle RTD role "users" with all authenticated users and groups (which includes the user "wasdmin"), as described in the following steps:
In the IBM WebSphere Administration console, select Applications, Application Types, WebSphere enterprise applications, and OracleRTD.
Edit the OracleRTD application and select Security role to user/group mapping.
Select the Role users, click Map Special Subjects, and select All Authenticated in Application's Realm.
Click OK twice and save your changes.
Restart the processes for IBM WebSphere and OPMN as described in Section 10.2.5, "Starting and Stopping Components on IBM WebSphere."
Note:
You must also remap the "wasadmin" user if you plan to use map views. For information, see Section 10.2.8, "Configuring for Map Views in Oracle Business Intelligence on IBM WebSphere."
You must use the syncNode command to force a configuration synchronization to occur between the node and the Deployment Manager (dmgr) for the cell in which the node is configured. You must also restart processes to allow the system to recognize and activate the new security settings.
Note:
Run the commands as shown in the following steps. The user name and password in all of these commands are for the currently configured IBM WebSphere administrator and not for the one in the new identity store configuration.
To synchronize the configuration on IBM WebSphere:
Log into the Administration node for Oracle Business Intelligence and open a terminal window.
Stop all components as described in Section 10.2.5, "Starting and Stopping Components on IBM WebSphere."
Start all components as described in Section 10.2.5, "Starting and Stopping Components on IBM WebSphere."
Perform the following steps for synchronization:
Stop the node using the following command:
MW_HOME/user_projects/domains/bifoundation_cell/bifoundation_cell_node0/bin/stopNode.sh -username user_name -password password
Manually synchronize the node by running the syncNode.sh command from the profile_root/bin directory, using the following syntax:
MW_HOME/user_projects/domains/bifoundation_cell/bifoundation_cell_node0/bin/syncNode.sh DMGRT_host_name DMGRT_SOAP_prt -username user_name -password password
Start the node using the following command
MW_HOME/user_projects/domains/bifoundation_cell/bifoundation_cell_node0/bin/startNode.sh -username user_name -password password
After all processes have restarted, ensure that you can log into the IBM WebSphere Administration Console and Oracle Business Intelligence using the new user details from the identity store. That is, log in with the user that is specified in the primary.admin.id value of the properties file.
For additional information on starting processes, see Section 10.2.5, "Starting and Stopping Components on IBM WebSphere."
See "Refreshing User GUIDs" in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition for information on updating any metadata references to user GUIDs in the Oracle BI repository and in the Oracle BI Presentation Catalog.
Note:
Unless otherwise indicated, the information in this section applies to Oracle BI Enterprise Edition, Oracle BI Publisher, and Oracle Real-Time Decisions.
You can use Oracle Single Sign-On with Oracle Business Intelligence on IBM WebSphere by relying on Oracle Access Manager 11g for authentication and authorization of its users. Figure 11-2 describes this process.
The SSO configuration requires the following components, typically on two host computers:
Host Computer #1
Oracle Business Intelligence 11g
IBM HTTP Server 7
WebGate 10g
Host Computer #2
Oracle Access Manager (OAM) 11g
Oracle Internet Directory (OID) 11g
If you plan to use Oracle Single Sign-On with Oracle Business Intelligence on IBM WebSphere, then you must configure it manually, as described in the following sections:
Step 1: Installing and Configuring Oracle Business Intelligence on IBM WebSphere
Step 3: Configuring Oracle Access Manager and Oracle Internet Directory on IBM WebSphere
Step 4: Registering the WebGate Agent with Oracle Access Manager on IBM WebSphere
Step 5: Updating the Application Policy for Oracle Business Intelligence on IBM WebSphere
Step 7: Configuring IBM WebSphere for SSO in Oracle Access Manager and IAP
Step 8: Configuring the Logout for Oracle Business Intelligence on IBM WebSphere
Step 9: Updating Oracle Business Intelligence for SSO on IBM WebSphere
You must install and configure Oracle Business Intelligence on the first host computer, as described in Section 10.2.1, "Installing Oracle Business Intelligence on IBM WebSphere" and Section 10.2.2, "Configuring Oracle Business Intelligence in a New IBM WebSphere Cell."
You must install and configure the IBM HTTP Server on the first host computer to work in front of IBM WebSphere to receive all web requests and route them to the Oracle Business Intelligence instance that is integrated with IBM WebSphere.
To configure the IBM HTTP Server for IBM WebSphere:
Install the IBM HTTP Server, and take note of the Server Name and the HTTP Port.
For detailed installation instruction, refer to IBM HTTP Server documentation.
Configure the HTTP Server, specifying the server name and port number that you specified in Step 1.
Log into the IBM WebSphere Administrative Console.
Navigate to Servers, Server Types, Web Servers, and New.
Select the node and type:
Node = Select the default node, which has a format such as host-nameNode01.
Server Name = Enter the name that you entered for the HTTP Server Plug-in, such as webserver1.
Type = Select IBM HTTP Server.
Select IHS as the web server template.
Enter the following properties for the new web server:
Port = 8080
Web server installation location = /dir-name/IBM/HTTPServer
Plug-in installation location = /dir-name/IBM/HTTPServer/Plugins
Application mapping = All
Click Next, Finish, and Save.
Create a virtual host entry to enable access to the port number that you specified in Step 1.
If the port is not accessible, then error messages similar to the following ones are displayed:
SRVE0255E: A WebGroup/Virtual Host to handle /webcenter/ has not been defined.
SRVE0255E: A WebGroup/Virtual Host to handle host:8080 has not been defined.
In the IBM WebSphere Administrative Console, navigate to Environment, then Virtual Hosts, then default_host, and Host Aliases.
On the Host Aliases page, select New.
For Port, enter the port number that you specified in Step 1.
Leave Host Name as *.
Click Save.
Generate and propagate the Web Server plug-in that coordinates the wiring between the IBM WebSphere Application Server and the IBM HTTP Server front end.
Note:
You must repeat this step each time there is a change to applications that are deployed on the servers.
In the IBM WebSphere Administrative Console, navigate to Servers, Server Types, then Web Servers, and select the HTTP server that you created, such as webserver1.
Click Generate Plug-in.
Verify that the HTTP server that you created is selected, and click Propagate Plug-in.
Apply the analytics application to IBM WebSphere by following these steps:
In the IBM WebSphere Administration console, select Applications, Application Types, WebSphere Enterprise Applications, analytics_11.1.1, and ManageModules.
Select the two WAR files that are listed there for analytics.
Click Apply, then OK.
Click Review, select Synchronize Changes with Nodes, and click Save.
Update the httpd.conf file for the web server by following these steps:
Click the Web Server.
Next to Configuration file name, click Edit.
Scroll down and change the user and group from "nobody" and "nobody" to the user name and group name of the current user.
Change the User nobody and Group nobody settings to the names of the user and group who perform the configuration.
Click Apply, then OK.
Click OK to return to the Web Servers page.
Restart the Deployment Manager, the Node Agent, the OracleAdminServer, and other components, as described in Section 10.2.5, "Starting and Stopping Components on IBM WebSphere."
You must configure Oracle Access Manager and Oracle Internet Directory, as described in Oracle Fusion Middleware Administrator's Guide for Oracle Access Manager with Oracle Security Token Service and Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.
You must register the WebGate agent with Oracle Access Manager before you install WebGate. The WebGate agent intercepts HTTP requests from users for Web resources and forwards them to the Access Server for authentication and authorization. You can register the WebGate agent using the OAM Console or, if you have administrator rights, you can use the oamreg tool.
To register the WebGate instance with Oracle Access Manager using a graphic user interface on IBM WebSphere:
Log into the Administration Console for Oracle Access Manager.
On the Home page, click New OAM 10g Webgate.
Enter the details to create the instance, as described in the following list:
Name = IHS_host_name_biwas, for example myhost_biwas
Base URL: The URL for the IBM HTTP Server, for example http://myhost:8080
Access Client Password = The password for Oracle Access Manager
Host identifier = Same as Name
User defined params = Leave blank
Security= Open
Resource Lists = For Protected Resource List enter the following:
/…/*
/
For Public Resource List = Leave blank
Click OK.
To register the WebGate instance in inband mode with Oracle Access Manager using the oamreg command tool on IBM WebSphere:
Navigate to the following directory on the Oracle Access Manager server:
IDM_HOME/oam/server/rreg/client/
On the command line, untar RREG.tar.gz
gunzip RREG.tar.gz tar -xvf RREG.tar
The tool used to register the agent is located in the following location:
(UNIX) RREG_HOME/bin/oamreg.sh (Windows) RREG_HOME\bin\oamreg.bat
Note:
RREG_HOME is the directory where you extracted the contents of RREG.tar.gz/rreg.
Set the following environment variables in the oamreg.sh or oamreg.bat script:
OAM_REG_HOME - Set this variable to the absolute path to the directory where you extracted the contents of RREG.tar/rreg
JDK_HOME - Set this variable to the absolute path to the directory where Java/JDK is installed on your machine.
Change directories to RREG_HOME/input and create the bi.oam.conf file using the following example:
###########################################################################
# Copyright (c) 2009, 2013, Oracle and/or its affiliates. All rights reserved.
#
# This is a configuration file, to be used with the OAM Config Tool, for
# configuring policies in OAM in order to facilitate Single Sign On.
#
# Protected URIs:-
# A Protected URI (resource) implies that a user must be authenticated
# before accessing that resource. Upon accessing a protected uri, the
# user is redirected to the OAM login page for authentication.
# Subsequently, upon successful authentication, the user is redirected to the
# original requested resource.
#
# Public URIs:-
# A Public URI (resource), on the contrary, implies that a user be allowed
# access to that resource without authentication.
#
# This file essentially contains a list of protected and public URIs belonging
# to an Application.
#
# Refer to the documentation of OAM Config Tool for anything related to
# the OAM Config tool's usage and the documentation of OAM for anything
# related to OAM in general.
#
##########################
# File format description
##########################
# 1. Any line beginning with '#' is considered a comment and would be ignored
# 2. Likewise any empty line or any line beginning with ' ' (space) is ignored
# 3. All the Protected URIs must be listed followed by the keyword:
# "protected_uris".
# 4. All the Public URIs must be listed followed by the keyword: "public_uris"
#
# Note that Public URIs are optional. But you need to have at least one
# Protected URI listed
#
##########################
# Basic configuration
##########################
# 1. One Policy domain is created in OAM based on the parameter
# "app_domain", passed to the OAM Config Tool, during its execution.
#
# 2. This Policy domain is configured with an Authentication scheme
# that requires the user to authenticate.
#
# 3. All the URIs listed following the keyword, "protected_uris" are
# created as "resources" in OAM i.e. all these are protected by the
# default authentication scheme configured in OAM.
#
# 4. All the URIs listed following the keyword, "public_uris" are
# added to a default public policy in OAM. This policy is configured
# with an Anonymous Authentication Scheme, allowing access to everyone.
#
##########################
# Advanced configuration
##########################
# Note that under this configuration, the configuration listed as part of
# "Basic configuration" are also done in addition to the below.
#
# The OAM Config Tool can also be used to configure user defined Policies in
# OAM. The policies can be configured to be protected with a default
# authentication scheme (protected) or with an anonymous authentication scheme
# (public).
#
# Format for specifying Protected and Public Policies are the same, except that
# the Protected Policies must be listed under "protected_uris" whereas the
# Public Policies must be listed under "public_uris"
#
# 1. To specify the name of a Policy:
# - Line without leading "/" implies the name of the policy.
# - Only for public policy, if no name is specified then by default, the
# name used is "public_<app_domain>". Note that all protected policies
# must have a name.
#
# 2. To specify a URL Pattern for a policy:
# - List the URL Pattern next to the resource separated by one or more spaces
# - List the URL pattern for every resource in that policy
# For example:
# policy for allowing access to all images/scripts under /uri1 and /uri2
# /uri1 /.../{*.js,*.gif}
# /uri2 /.../{*.js,*.gif}
#
# 3. To specify a Query String for a policy:
# - List the resource followed by the querystring (separated by '?')
# - List the Query String for every resource in that policy
# For example:
# public policy with query string
# /uri3?{SoapImpl*,WSDL,privateWSDL}
# /uri4?{SoapImpl*,WSDL,privateWSDL}
#
##############################################################################
#
#
########################
#Product Name: BI (includes BI EE, RTD, EPM, BIP)
########################
#
###########################
protected_uris
###########################
/analytics/saw.dll
/aps
/bicontent
/bioffice
/calcmgr
/hr
/workspace
/ui
/xmlpserver
*
###########################
public_uris
###########################
Default Public Policy
/analytics
/analytics/saw.dll/wsdl
/bioffice/services/saw
/ui/do/logout
/xmlpserver/services
/xmlpserver/report_service
/xmlpserver/ReportTemplateService.xls
/xmlpserver/Guest
/biservices
/biofficeclient/OracleBIOffice.exe
/hr/modules/com/hyperion/reporting/web/repository/HRRepositoryXML.jsp
/analytics/saw.dll?{SoapImpl*,WSDL,wsdl,privateWSDL,privatewsdl}
Create a file called oam_request.xml using the following example to serve as the parameter file for the oamreg tool.
<?xml version="1.0" encoding="UTF-8"?>
<OAMRegRequest>
<serverAddress>http://$$oamhost$$:$$oamadminserverport$$</serverAddress>
<hostIdentifier>$$ihshost$$_biwas</hostIdentifier>
<agentName>$$ihshost$$_biwas</agentName>
<agentBaseUrl>http://$$ihshost$$:$$ihsport$$</agentBaseUrl>
<applicationDomain>$$ihshost$$_biwas</applicationDomain>
<autoCreatePolicy>true</autoCreatePolicy>
<primaryCookieDomain>.myserver.example.com</primaryCookieDomain>
<logOutUrls>
<url>/oamsso/logout.html</url>
</logOutUrls>
</OAMRegRequest>
Replace the variable contents within $$ihshost:ihsport$$ with the server name and port number for the IBM HTTP Server. Replace $$oam...$$ with the host name for Oracle Access Manager and the port number for the Administration Server.
Change to the RREG_Home directory.
Enter the following command:
RREG_HOME/bin/oamreg.sh inband input/oam_request.xml
Complete the following steps:
When prompted for the agent credentials, enter the administrator credentials for Oracle Access Manager.
Enter the password for Webgate.
Enter Yes when asked to import a URIs file and specify the full directory name of the RREG_HOME/input/bi.oam.conf file.
You see a message that indicates that the registration was successful. Notice that the ObAcessClient.xml file is generated in the output folder. Keep the file available for copying in a later step after you install WebGate.
You must update the application policy with resources for Oracle Business Intelligence.
To update the application policy with resources for Oracle Business Intelligence on IBM WebSphere:
Change to the RREG_HOME/input directory on the computer for Oracle Access Manager. The directory name is often IDM_HOME/oam/server/rreg
Create a policy update file called bi_policy_update.xml and include the following text:
<?xml version="1.0" encoding="UTF-8"?>
<PolicyRegRequest>
<serverAddress>http://$$oamhost$$:$$oamadminserverport$$</serverAddress>
<hostIdentifier>$$ihshost$$_biwas</hostIdentifier>
<applicationDomainName>$$ihshost$$_biwas</applicationDomainName>
</PolicyRegRequest>
Replace the variable contents with the appropriate server names and port numbers. For example, for serverAddress, specify the URL for the computer for Oracle Access Manager, such as http://myhost:17731.
For hostIdentifier and applicationDomainName, enter myhost_biwas
Edit the oamreg.sh file to ensure that the OAM_REG_HOME and JAVA_HOME variables are set correctly. The JAVA_HOME variable must be set to:
dir_name/MW_HOME/IM_HOME/jdk
Enter the following command:
RREG_HOME/bin/oamreg.sh policyUpdate input/bi_policy_update.xml
Complete the following steps:
When prompted for the agent credentials, enter the administrator credentials for Oracle Access Manager.
Enter the password for Webgate.
Enter Yes when asked to import an URIs file and specify the full directory name of the RREG_HOME/input/bi.oam.conf file.
The policy is updated with resources for Oracle Business Intelligence.
Restart the IBM HTTP Server.
Although Oracle Access Manager 11g can work with WebGate 10g and 11g, currently the IBM HTTP Server supports only WebGate 10g. You can locate the installation file for WebGate on the Oracle Access Manager page on Oracle Technology Network. Ensure that you have performed the previous steps in this process before installing WebGate.
To install and configure Webgate on IBM WebSphere:
Download WebGate 10g from Oracle Technology Network. The installable file is called Oracle Access Manager 10g - non OHS11g Webgates and 3rd Party Integrations.
For Windows, select Oracle_Access_Manager10_1_4_3_0_Win32_IHS22_WebGate installer
For Linux, select Oracle_Access_Manager10_1_4_3_0_linux_IHS22_WebGate installer
For Linux, ensure that the GCC libraries are available. If the IBM HTTP Server is 32-bit, then select 32-bit libraries. If the IBM HTTP Server is 64-bit, then select 64-bit libraries. The GCC libraries are provided in a .cpio file. Copy this file to any directory and enter one of the following commands:
cpio -i xxxx.cpio cat xxxx.cpio | cpio -idmv
When the command finishes, you see a .zip file in the directory. Unzip the file using a command such as unzip -q file-name.zip
When the command finishes, you see two libraries in the same directory. You use these libraries in this procedure.
Ensure that you edit the httpd.conf file, as described in Section 10.2.7.2.2, "Step 2: Configuring the IBM HTTP Server for IBM WebSphere."
On the computer on which the IBM HTTP Server is installed, run the WebGate Installer as the user who is running the IBM HTTP Server.
Specify a location for installing Webgate.
Note:
If you ran the installer once and it failed, then select a different directory for installation.
Specify the location of the GCC libraries.
When asked to specify the WebGate details, enter the following:
WebGate Id — Specify the agent name that you entered in "Step 5: Updating the Application Policy for Oracle Business Intelligence on IBM WebSphere" such as $$ihshost$$_biwas.
WebGate Password — Specify the password that you entered while running the oamreg.sh script.
Access Server Name — Specify a value such as oam_server1. Determine this value from the Oracle Access Manager Console.
Access Server HostName — Specify $$oamhost$$.
Access Server Port — Specify a value such as 5575. Determine this value from the Oracle Access Manager Console. Select System Configuration, then Server Instances, then oam_server1, then OAM Proxy, then Port.
Specify the automatic update of the httpd.conf file, and specify the proper location of the httpd.conf file for the IBM HTTP Server, which is usually IHS_HOME/conf.
Complete the wizard.
WebGate is now successfully installed.
Restart the IBM HTTP Server.
Follow the instructions in Section 11.9, "Configuring IBM WebSphere for OAM SSO and the IAP," which include the following steps:
Configuring a Standalone LDAP Registry for Oracle Access Manager in IBM WebSphere. This configuration happens automatically when you perform Step 5: Reassociating Oracle Business Intelligence with the Identity Store on IBM WebSphere. Ensure that the configuration points to the correct Oracle Internet Directory instance.
Adding and configuring a virtual host in IBM WebSphere. You can omit this step. You updated the default_host when you installed and associated the IBM HTTP Server. Do not create another host; use the one that you already have.
Configuring the reverse proxy for the IBM HTTP Server in the IBM WebSphere Console. You can omit this step and use webserver1 instead. Ensure that you remove any entries that refer to "/*". Leave other entries intact (such as "/analytics/*"); otherwise, the IBM HTTP Server does not forward URLs for Oracle Business Intelligence to the IBM WebSphere server
Creating the Interceptor Entry in the IBM WebSphere Console. When adding the OAMTrustAssociationInterceptor.jar file to the classpath for IBM WebSphere, you must add the file for OracleAdminServer and for bi_server1.
Configuring the TAI configuration file for Oracle Access Manager.
If you select the option of copying the oamtai.xml file in the fmwconfig directory, then ensure that the change is made in the profile directory for the Deployment Manager. This directory is the source of truth for other application server profiles.
The values that you specify in the oamtai.xml file are similar to what you provide during the installation of WebGate. The following shows a sample oamtai.xml file:
<OAM-configuration>
<AAAClientConnect>
<Parameters>
<param name = "hostPort" value ="adc2100132:8080"/>
<param name = "resource" value ="/Authen/SSOToken"/>
<param name = "operation" value ="GET"/>
<param name = "AccessGateName" value ="myserver_biwas"/>
<param name = "AccessGatePassword" value ="welcome1"/>
<param name = "AccessServerHost" value ="myserver.example.com"/>
<param name = "AccessServerPort" value ="5575"/>
<param name = "AccessServerName" value ="oam_server1"/>
<param name = "TransportSecurity" value ="open"/>
<param name = "debug" value ="false"/>
<param name = "minConn" value ="1"/>
<param name = "maxConn" value ="1"/>
<param name = "timeOutForConnPool" value ="30000"/>
<!--
Note:Following parameter is used for Anonymous User Authentication. Configure anonymous user value here
-->
<param name = "Anonymous" value =""/>
<param name = "assertionType" value ="HeaderBasedAssertion"/>
<param name = "customHeaderName" value ="OAM_REMOTE_USER"/>
</Parameters>
</AAAClientConnect>
</OAM-configuration>
For Oracle BI EE only, you configure the logout by creating a logout.html file.
To configure the logout for Oracle Business Intelligence on IBM WebSphere:
Follow the directions in Section 11.10.2.2, "Configuring SSO Logout for OPSS with ADF-coded applications and OAM 10g Webgate."
Create the logout.html file based on the following example:
<html> <head> <meta http-equiv="Content-Language" content="en-gb"> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> <title>New Page 1</title> </head> <body> <p>Logging out...</p> <script language="JavaScript"> window.location="/analytics"; </script> </body> </html>
Store the file in the IHS_HOME/htdocs directory.
Configure for the display of the file by following these steps:
Locate and log into the Oracle Access Manager Server.
Select Access System Configuration, then Access Gate Configuration.
Select the access gate that is associated with the instance of Oracle Business Intelligence.
Add /logout.html to the Web Server Client - LogOutURLs field.
Follow the steps in Section 11.10.2.2, "Configuring SSO Logout for OPSS with ADF-coded applications and OAM 10g Webgate."
Follow the steps in Section 11.10.2.3, "Configuring oamAuthenProvider.jar in the IBM WebSphere classpath" for the OracleAdminServer and for bi_server1.
Follow the steps in Section 11.10.2.4, "Verifying SSO Logout".
Note:
To work around an issue with Oracle Business Intelligence on IBM WebSphere, ensure that you close the browser after logging out. If you leave the browser open, then you risk retaining the session such that other users can access the browser and use Oracle Business Intelligence without logging in.
For Oracle BI EE only, you must use Fusion Middleware Control to enable SSO for Oracle Access Manager.
To update Oracle Business Intelligence for SSO on IBM WebSphere:
Log into Fusion Middleware Control.
Expand the Business Intelligence folder and select the coreapplication node.
Click Lock and Edit Configuration to enable changes to be made.
Display the Single Sign On tab of the Security page.
Select Enable SSO, then select Oracle Access Manager as the SSO provider.
In the SSO Provider Logoff URL box, enter the following value:
http://host-name:8080/logout.html
where host-name is the computer on which the IBM HTTP Server is running.
Click Apply, then Activate Changes.
Restart the processes for IBM WebSphere as described in Section 10.2.5, "Starting and Stopping Components on IBM WebSphere," ensuring that you restart the IBM HTTP Server and Oracle Business Intelligence.
Note:
Unless otherwise indicated, the information in this section applies to Oracle BI Enterprise Edition, Oracle BI Publisher, and Oracle Real-Time Decisions.
If you plan to use Secure Socket Layers (SSL) with Oracle Business Intelligence on IBM WebSphere, then you must configure it manually. (By default, SSL ports are turned on for IBM WebSphere if you followed the default installation flow for Oracle Business Intelligence.) The objectives of the manual configuration are to have a system in which all the Oracle Business Intelligence components communicate through SSL and to allow outside connections over HTTPS only. The following list outlines the differences between using SSL on IBM WebSphere and on Oracle WebLogic Server:
The format of the certificate authority public certificate for IBM WebSphere is different. Oracle Business Intelligence uses .DER (for binary files) and .PEM certificates. The default certificates for IBM WebSphere use .p12 format. Because Oracle Business Intelligence supports only .DER and .PEM formats, you must convert the default certificates for IBM WebSphere.
You do not configure SSL for Oracle Business Intelligence using the Security tab within Fusion Middleware Control. For IBM WebSphere, you use the JMX MBeans within the System MBean Browser.
To configure SSL for Oracle Business Intelligence on IBM WebSphere:
Verify that SSL is active on IBM WebSphere using the following steps:
In the IBM WebSphere Administration console, select the following from the left-hand tree: servers/server types/websphere application servers
Select bi_server1 and ports, and for WC_defaulthost, click "view associated transports".
Set the Enabled flag and the SSL Enabled flag for both HttpQueueIbBoundDefault and WCInboundDefault.
Repeat Step b for any other servers that are configured.
Convert the CA public certificate to either the .DER (for binary files) or .PEM format that Oracle Business Intelligence recognizes. The following steps provide an example of this conversion:
Change to the following directory that stores the CA public certificate:
MW_HOME/user_projects/domains/bifoundation_cell/bifoundation_cell_dmgr0/config/cells/bifoundation_cell/trust.p12
Enter the following command:
openssl pkcs12 -in trust.p12 -out WAStrust.pem -nodes
Enter the appropriate password to create a PEM version of the certificate that is named WASTrust.pem.
See IBM WebSphere documentation available on the WebSphere Application Server Information Center for information on passwords for certificates.
(Oracle BI EE Only) Follow the instructions in "Configuring SSL Communication Between Components" in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition with the following exceptions:
When selecting the generateSSLCertificates operation, use the CA public certificate that you created in the previous step, and select the appropriate format.
Restart the system components for Oracle Business Intelligence after completing the certification generation, as described in Section 10.2.5, "Starting and Stopping Components on IBM WebSphere."
(Oracle BI EE Only) Follow the instructions in "Enabling the SSL Configuration" in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition.
(Oracle BI EE Only) Test the SSL configuration by following the instructions in "Confirming SSL Status Using the MBean Browser" in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition
(Oracle RTD Only) Perform the following steps:
Configure IBM WebSphere to use the same store in its SSL configuration.
In the IBM WebSphere Administration console, select Security, SSL certificate and key management , SSL configurations, CellDefaultSSLSettings. Change the Trust Store name to the following:
BITrustStore ((cell):bifoundation_cell)
Expand the MW_HOME/Oracle_BI1/clients/rtd/rtd_client_11.1.1.zip file to a directory on the computer. That directory is referred to as RTD_HOME in this procedure.
Copy the MW_HOME/user_projects/domains/bifoundation_cell/bifoundation_cell_dmgr0/config/cells/bifoundation_cell/BITrustStore.jks file to the RTD_HOME/etc/ssl directory, creating the directory if it does not yet exist.
Configure Oracle RTD Studio to use the trusted store by changing the last line in the RTD_HOME/eclipse/eclipse.ini file to read as follows:
-Djavax.net.ssl.trustStore="..\etc\ssl\BITrustStore.jks
For CommandLineDeploy, execute the following command:
java -Djavax.net.ssl.trustStore="dir-nameBITrustStore.jks -jar deploytool.jar -deploy -sslConnection true ILS user-name password host-name port-num
For example:
Java -Djavax.net.ssl.trustStore=C:/RTD_HOME/etc/ssl/BITrustStore.jks -jar deploytool.jar -deploy -sslConnection true"C:/RTD_HOME/examples/CrossSell" weblogic psw dadvmh0044 9804
For Load Generator, in the RTD_HOME/scripts/sdexec.cmd script, uncomment the following line:
rem set TRUST_STORE_OPTS=-Djavax.net.ssl.trustStore="%SD_ROOT%\etc\ssl\sdtrust.store"
and replace it with the following one:
Djavax.net.ssl.trustStore=dir-nameBITrustStore.jks
For example:
-Djavax.net.ssl.trustStore=..\etc\ssl\BITrustStore.jks
For Batch Console, execute the following command:
java -Djavax.net.ssl.trustStore="dir-name/BITrustStore.jks" -jar batch-console.jar -url https://:
For example:
Java -Djavax.net.ssl.trustStore="c:/RTD_HOME/etc/ssl/BITrustStore.jks" -jar batch-console.jar -url https://localhost:ssl_port
Restart the Managed Server for Oracle Business Intelligence.
Turn off the non-HTTPS ports using the following steps:
In the IBM WebSphere Administration console, select the following from the left-hand tree: servers/server types/websphere application servers
Select bi_server1 and ports, and for WC_defaulthost, click "view associated transports".
Click HttpQueueIbBoundDefault, deselect the Enabled flag, and click Apply, then Save.
Repeat Steps b and c for WCInboundDefault.
Repeat Steps b and c for OracleAdminServer.
If you installed IBM WebSphere with Fix Pack 23 or later, then you can use TLS-based cipher suites, which do not function well with Oracle Business Intelligence. Perform the following steps to work around this issue:
In the IBM WebSphere Administration console, select Security, SSL certificate and key management , SSL configurations, NodeDefaultSSLSettings, and Quality of protection (QoP) settings.
In the Protocol box, select SSLv3 instead of the default of SSL_TLS, which does not work with Fix Pack 23.
Restart the system components for Oracle Business Intelligence, as described in Section 10.2.5, "Starting and Stopping Components on IBM WebSphere."
Verify that you cannot connect to Oracle Business Intelligence using the HTTP port, but that you can connect using the HTTPS port.
If you want to use map views in analyses in Oracle Business Intelligence, then you must manually configure Oracle Fusion Middleware MapViewer. The EAR file for MapViewer exists in exploded directory form in the ORACLE_HOME/bifoundation/jee directory. Perform this step before completing the steps in Section 10.2.7.1, "Configuring the LDAP-Based Identity Store on IBM WebSphere," otherwise authorization exceptions can occur.
To manually configure for map views on IBM WebSphere:
Delete the two JSF libraries that are packaged inside MapViewer using the following commands:
rm ORACLE_HOME/bifoundation/jee/mapviewer.ear/web.war/WEB-INF/lib/jsf-api.jar rm ORACLE_HOME/bifoundation/jee/mapviewer.ear/web.war/WEB-INF/lib/jsf-impl.jar
Because IBM WebSphere contains JSF libraries, any JSF libraries that are packaged within the ear files of applications create conflicts.
Deploy the ear file for MapViewer using these steps:
In the IBM WebSphere Administration console, select Applications, Application Types, and WebSphere enterprise applications.
Click Install.
Select Remote file system and enter the remote servers path to the ORACLE_HOME/bifoundation/jee/mapviewer.ear file.
Note that you cannot select the mapviewer.ear file, because the file has already been exploded. Instead, you must specify another .ear in the same location, then change the name of the file to mapviewer.ear.
Click Next through the remaining pages.
Save the configuration.
Update the security role mappings using these steps:
In the IBM WebSphere Administration console, select Applications, Application Types, WebSphere Enterprise Applications, and Oracle MapViewer.
Edit the Oracle MapViewer application and select Security role to user/group mapping.
Select the following two roles: map_admin_role and secure_maps_role.
Click Map Roles.
Click Search to search users in the identity store.
Select the user in the list; for example, "wasadmin".
Click OK twice and save your changes.
Restart the processes for IBM WebSphere and OPMN as described in Section 10.2.5, "Starting and Stopping Components on IBM WebSphere."
In Oracle BI EE, you can create actions that invoke Java methods in Enterprise Java Beans (EJBs). These Java methods return objects that implement the remote EJB interface that Oracle BI EE can use. For Oracle WebLogic Server, you use the information in Oracle Fusion Middleware Integrator's Guide for Oracle Business Intelligence Enterprise Edition to configure this action type. For IBM WebSphere, you create a web service around an EJB. For complete information on creating an EJB web service, see the IBM web site and other internet locations.
If you want to use Oracle Business Intelligence for Microsoft Office, then you must configure it manually.
To manually configure for Oracle BI for Microsoft Office on IBM WebSphere:
Deploy the ear file for the BI Office server using these steps:
In the IBM WebSphere Administration console, select Applications, Application Types, and WebSphere Enterprise Applications.
Click Install.
Select Remote file system and enter the remote servers path to the ORACLE_HOME/bifoundation/jee/bioffice.ear file.
Click Next through the remaining pages to accept the default selections, with one exception. On Step 2, "Map Modules to Servers," do not accept the default of OracleAdminServer. Instead, select the EAR file box, select bi_cluster from the list of servers, and click Apply. Verify that bi_cluster is displayed in the Server column, and click Next.
Save the configuration.
On the BI Office Server, change the SawBaseURL property in the bioffice.xml file to the following value:
http://host-name:port/analytics/saw.dll
Because of how Oracle BI for Microsoft Office is deployed on IBM WebSphere, you must change the property value in the file in each of these locations:
MW_HOME/user_projects/domains/bifoundation_cell/bifoundation_cell_node0/installedApps/BI_Cell/bioffice.ear/bioffice.war/WEB-INF/ MW_HOME/user_projects/domains/bifoundation_cell/bifoundation_cell_node0/config/cells/BI_Cell/applications/bioffice.ear/deployments/bioffice/bioffice.war/WEB-INF MW_HOME/user_projects/domains/bifoundation_cell_dmgr0/config/cells/BI_Cell/applications/bioffice.ear/deployments/bioffice/bioffice.war/WEB-INF
For more information, see "Setting Properties in the bioffice.xml Configuration File" in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition.
Deploy the war file for the BI Office client using these steps:
In the IBM WebSphere Administration console, select Applications, Application Types, and WebSphere Enterprise Applications.
Click Install.
Select Remote file system and enter the remote servers path to the ORACLE_HOME/bifoundation/jee/biofficeclient.war file.
Click Next through the remaining pages to accept the defaults, with two exceptions. First on Step 1, "Map Modules to Servers," change from the default of OracleAdminServer to bi_cluster, as described in Step 1 of this procedure.
Secondly, specify the following value for the web context root:
/biofficeclient
Save the configuration.
Restart the processes for IBM WebSphere as described in Section 10.2.5, "Starting and Stopping Components on IBM WebSphere."
On Oracle WebLogic Server, you scale the deployment of Oracle Business Intelligence using Fusion Middleware Control. On IBM WebSphere, you perform manual configuration steps in combination with Fusion Middleware Control for both JEE components and system components for Oracle Business Intelligence.
Scaling allows you to increase or decrease the capacity of a system by making effective use of resources. For example, user web requests can be directed to one of many Oracle BI Presentation Services components. In turn, each Presentation Services component can take advantage of the availability of multiple Oracle BI Servers.
You can scale both vertically and horizontally. Vertical scaling involves adding more Oracle Business Intelligence components to the same computer, to make increased use of the hardware resources on that computer. Horizontal scaling involves adding more computers to the environment. For example, Oracle Business Intelligence is horizontally scaled by distributing the processing of requests across multiple computers.
The following sections describe how to configure for scaling:
To configure for scaling out JEE components on IBM WebSphere:
Use the Administration Console for IBM WebSphere to verify that the following conditions are met:
Oracle Business Intelligence is installed with IBM WebSphere on the first host computer.
The installation of Oracle Business Intelligence on the first host computer includes two servers, which are named OracleAdminServer and bi_server1. The installation also includes a Node Agent and a single Deployment Manager.
The servers are managed as a cluster for IBM WebSphere that is called bi_cluster.
Install IBM WebSphere on the second host computer. Ensure that you select None as the installation type and click Finish on the Installation Results page.
Apply any patches as appropriate for IBM WebSphere on the second host computer, so that the second computer runs the same version as the first computer. Before applying patches, ensure that no processes for IBM WebSphere are running. For example, use the stopNode.sh script to stop the Node Agent.
Run the Profile Management Tool as follows:
Start the Profile Management Tool.
To launch the tool, run its script (often named pmt.sh), which is usually found in the following location:
WAS_HOME/bin/ProfileManagement/pmt.sh
For complete information on running and using the Profile Management Tool, see the documentation for IBM WebSphere.
Click Launch Profile Management Tool and Create.
On the Environment Selection page, select Custom profile, then click Next.
On the Profile Creation Options page, select Advanced profile creation, then click Next.
On the Profile Name and Location page, set the name to a value such as the following one
cell-name_node0 (for example, bifoundation_cell_node0)
Set the profile location to nearly the same value as on the first server. Specify the same directory structure on the second host computer as it is on the first host computer, as shown in the following example:
/scratch/shiphomes/MWHOME/user_projects/domains/bifoundation_cell/bifoundation_cell_node0
Click Next.
On the Node and Host Names page, click Next.
On the Federation page, specify the SOAP port number, user name, and password for the Deployment Manager on the first host computer. You can find the port number for SOAP in the AboutThisProfile.txt file, which is stored in the logs directory of the Deployment Manager on the first host computer. Look for the property that is named Management SOAP Connector Port.
Specify the administrator user name and password for connecting to IBM WebSphere on the first host computer.
The details that you specify on the Federation page connect the installation of IBM WebSphere to the cluster configuration on the first host computer.
Click Next multiple times to move through the Security Certificate and Port Values Assignment pages.
On the Profile Creation Summary page, click Create.
On the Profile Creation Complete page, clear the Launch the First Steps console box and click Finish.
Close the Profile Management Tool window.
Install Oracle Business Intelligence on the second host computer and select the following options:
For installation type, select Software-Only.
Install Oracle Business Intelligence in the same directory structure on the second host computer as it is installed on the first host computer, such as /mydir/myname/mw_home.
Create an IBM Managed Server (similar to bi_server1 on the first node) to handle the JEE applications for Oracle Business Intelligence on the new node. Ensure that you have the following details to include in the command that runs the creation script:
host-name — The name of the first host computer, where the Deployment Manager is installed and running.
port-num — The port number for SOAP for the Deployment Manager. The default number is 8879.
For information on port numbers, see Section 10.2.6, "Determining Ports for Oracle BI Components on IBM WebSphere."
admin-user — The user name for the Deployment Manager.
admin-password — The password for the Deployment Manager.
node-name — The local node name.
When you installed IBM WebSphere on the second host computer, a node was created there. To learn the name of this node, display the IBM WebSphere Administration Console, select System Administration and Nodes. Look for the name of the node on the second host computer.
server-name — The name of the server to create. Give the server a unique name, such as bi_serverx, where x is an integer. If a server named bi_server1 already exists on the computer, then name this server bi_server2.
Perform the following steps to create the server:
Ensure that the WAS_HOME environment variable is set to the directory for IBM WebSphere on the second host computer.
Start the node (which you stopped in a previous step) on the second host computer, using a command such as the following one:
MW_HOME/user_projects/domains/bifoundation_cell/bifoundation_cell_node0/bin/startNode.sh -username user_name -password password
Enter the following command to run the script to create the server:
ORACLE_HOME/common/bin/wsadmin.sh -connType SOAP -host host-name -port port-num -username admin-user -password admin-password -f ORACLE_HOME/bifoundation/was_install/WASScaleOutJEE.py -localNodeName node-name -serverName server-name
The new server is created and managed as a new member of the pre-existing cluster, which is called bi_cluster. The node is synchronized, and the new server is running.
Use the following settings to increase the performance in high-load environments. You must change these settings from their default values.
In the IBM WebSphere Administration console, update the Default and WebContainer thread pools for each server in the bi_cluster cluster. Increase the minimum and maximum pool sizes to improve performance. For example, select Application Servers, bi_serverx, Thread pools, and WebContainer and specify the following values, if the community numbers around 1800 users:
Minimum Size = 200
Maximum Size = 200
Restart the processes for IBM WebSphere and OPMN as described in Section 10.2.5, "Starting and Stopping Components on IBM WebSphere."
Verify the following:
That the list of applications that are running on the first host computer (such as bi_server1) are also running on the second host computer (such as bi_server2.) Use the IBM WebSphere Administration console to view the running applications.
That you can access Oracle Business Intelligence on the second host computer, which makes use of the system components (such as Presentation Services and the BI Server) on the first host computer.
For information on accessing Oracle Business Intelligence, see Section 10.2.6, "Determining Ports for Oracle BI Components on IBM WebSphere."
To configure for scaling out system components on IBM WebSphere:
Ensure that you have successfully followed the steps in Section 10.2.11.1, "Configuring for Scaling Out JEE Components on IBM WebSphere."
Prepare to create a new instance by entering the following commands on its host computer:
cd MW_HOME
chmod ug+x Oracle_BI1/opmn/bin/opmnctl
Run the opmnctl createinstance command to create an Oracle instance, using the following syntax:
./Oracle_BI1/opmn/bin/opmnctl createinstance -wascell cell-name -wasNode node-name -wasTrustStore store-name -adminHost host-name -adminPort port-num -instanceName instance-name-oracleInstance instance-name
The following provides a sample createinstance command:
./Oracle_BI1/opmn/bin/opmnctl createinstance -wasCell bifoundation_cell -wasNode myNode01 -wasTrustStore /scratch/shiphomes/MW_HOME/user_projects/domains/bifoundation_cell/bifoundation_cell_node0/config/cells/bifoundation_cell/BITrustStore.jks -adminHost myHose -adminPort 8880 -instanceName instance2 -oracleInstance instances/instance2
The following list describes the arguments in the syntax:
wasCell — The cell that includes the Administration Server, whose name is located in the following directory:
../user_projects/domains/cell-name/node-name/config/cells
wasNode — The node that includes the Administration Server, whose name is located in the following directory:
../user_projects/domains/cell-name/node-name/config/cells/cell-name/nodes
wasTrustStore — The cell-wide trust store for Oracle Business Intelligence that makes a secure connection with the OracleAdminServer. The store has a name such as the following:
MW_HOME/user_projects/domains/cell-name/node-name/config/cells/cell-name/BITrustStore.jks
adminHost — The host name for the Administration Server.
adminPort — The SOAP Connector port number for the Administration Server, which is stored in the following file:
../user_projects/domains/cell-name/node-name/config/cells/cell-name/nodes/node-name/serverindex.xml
Open the file and locate serverEntries with serverName OracleAdminServer. The port number is the SOAP_CONNECTOR_ADDRESS.
instanceName — The name for the new Oracle instance, such as instance2.
oracleInstance — The directory for the new Oracle instance, such as instances/instance2.
When prompted, enter the user name and password for the administrator and the password for the trust store.
To retrieve the password for the trust store manually, you must start a wsadmin console and enter the following commands:
wsadmin>Opss.listCred(map="oracle.bi.enterprise",key="bi.truststore.user") [Name : BITrustStore, Description : "BI TrustStore User", expiry Date : null ]
Start OPMN on the second host computer using a command such as the following one:
./instances/instance2/bin/opmnctl startall
Notify the Administration Server of the new component on the scaled-out host computer using the following steps:
On the host computer for the Administration Server, log into Fusion Middleware Control.
Expand the Business Intelligence folder and select the coreapplication node.
Click Lock and Edit Configuration to enable changes to be made
Display the Scalability tab of the Capacity Management page to see the new instance.
Change the number of BI Servers, Presentation Servers, or JavaHosts using the arrow keys.
To vertically scale the system components, increment the number of each component to be greater than 0 for a given host.
Click Apply, then Activate Changes.
Return to the Business Intelligence Overview page and click Restart.
An Oracle RTD cluster is the entire set of Oracle RTD instances that run any combination of the Oracle RTD services, namely Decision Server, Decision Center, Learning Services, and Batch Services.
The first stage in configuring an Oracle RTD cluster is to configure a JEE cluster, as described in Section 10.2.11.1, "Configuring for Scaling Out JEE Components on IBM WebSphere."
Subsequently, you must perform the following additional procedures on each server of the JEE cluster:
Note:
For load balancing in a cluster, you must tell the load balancer that the application is clustered. Therefore, for load balacing, you must deploy Oracle RTD (or ensure that it has already been deployed) on the cluster and on the HTTP Server. For more information on load balancing, see Section 10.2.12, "Configuring for Load Balancing with the IBM HTTP Server."
In the Administration Console for IBM WebSphere, you must specify which users are allowed to access Oracle RTD. The most straightforward way is, for the Oracle RTD application, to associate the Oracle RTD role "users" to all authenticated users and groups.
To register users and groups for Oracle RTD on IBM WebSphere:
In the IBM WebSphere Administration console, select Applications, Application Types, WebSphere enterprise applications, and OracleRTD.
Edit the OracleRTD application and select Security role to user/group mapping.
Select the Role users, click Map Special Subjects, and select All Authenticated in Application's Realm.
Click OK twice and save your changes.
Restart the processes for IBM WebSphere and OPMN as described in Section 10.2.5, "Starting and Stopping Components on IBM WebSphere."
The following two properties must be set up on each server of the JEE cluster to enable clustering for Oracle RTD:
SDGroupName is the name of the Oracle RTD cluster. Each Oracle RTD instance in the JEE cluster must have the same SDGroupName.
rtd.InstanceName specifies the unique name of the Oracle RTD instance within the cluster.
To set up the clustering properties for Oracle RTD:
In the IBM WebSphere Administration console, select Servers, Server Types, WebSphere application servers, then select the appropriate server.
In the Server infrastructure section, select Java and Process Management, Process definition, Java Virtual Machine, Custom properties, and New.
Enter Name and Value for both SDGroupName and rtd.InstanceName.
Ensure that the value for SDGroupName is the same on all servers of the cluster, and that the value for rtd.InstanceName is different on each server.
Click OK to save your changes.
Restart the processes for IBM WebSphere and OPMN as described in Section 10.2.5, "Starting and Stopping Components on IBM WebSphere."
Repeat these steps on each server of the cluster.
You can configure IBM HTTP Server as the load balancer for Oracle Business Intelligence on IBM WebSphere, as described in the following sections:
Step 1: Configuring the IBM HTTP Server for Oracle Business Intelligence on IBM WebSphere
Step 2: Configuring Oracle Business Intelligence to Recognize the Load Balancer on IBM WebSphere
Step 3: Verifying the Configuration of the Load Balancer on IBM WebSphere
The first step is to configure the IBM HTTP Server. Complete the procedure that is described in Section 10.2.7.2.2, "Step 2: Configuring the IBM HTTP Server for IBM WebSphere."
To configure Oracle Business Intelligence for the load balancer on IBM WebSphere:
Log into Fusion Middleware Control and display the System MBean Browser.
Locate the BIDomain MBean, which has details such as the following:
MBean Name = oracle.biee.admin:cell=bifoundation_cell,type=BIDomain,node=slc01ncjNode01,group=Service,process=OracleAdminServer
Description = MBean for managing a BI Domain
Lock the configuration to allow you to make changes.
In the FrontEndLoadBalancerBaseURL field, specify the value that you saw when installing the load balancer. In this example, you enter the value http://analytics.example.com.
Click the Apply button.
Commit your changes.
Use Fusion Middleware Control to restart Presentation Services and activate your changes.
To verify that the load balancer is configured properly for Oracle Business Intelligence on IBM WebSphere:
In a web browser, enter the URL to start Presentation Services. For information, see Section 10.2.6, "Determining Ports for Oracle BI Components on IBM WebSphere."
Create an analysis with two columns and attach an action link to one of the columns using the Interaction tab of the Column Properties dialog.
Save the analysis.
Create an agent to run the analysis and save that agent.
Run the agent.
When the agent has finished running, you see an alert on the Oracle Business Intelligence home page, which is the result of the agent running the analysis.
Click View for the agent.
Hover the mouse pointer over the links in the column that you added to the action link. You see that the links include the URL for the load balancer, rather than for the server name and port number for Oracle Business Intelligence.
You need not deinstall Oracle Business Intelligence unless you are updating to a new IBM WebSphere release. If you want to deinstall Oracle Business Intelligence, then use the following procedure.
To deinstall Oracle Business Intelligence on IBM WebSphere:
Ensure that IBM WebSphere and the Oracle Business Intelligence system are running.
Deinstall the components for Oracle Business Intelligence as described in "Deinstalling Oracle Business Intelligence" in Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.
Stop processes in IBM WebSphere and OPMN, as described in Section 10.2.5, "Starting and Stopping Components on IBM WebSphere."
Optionally, you can delete profiles to remove all of the user data such as the repository, catalog, and log files. Delete profiles by entering the following command:
WAS_HOME/bin/manageprofiles.sh -deleteAll
Delete the domain home and instances for example, MW_HOME/instance MW_HOME/user_projects and the binary files in the MW_HOME directory.
You can upgrade an existing Oracle Business Intelligence system to run on IBM WebSphere:
If you have a 10g Release of Oracle Business Intelligence that is running on Oracle WebLogic Server.
If you have a previous 11g Release of Oracle Business Intelligence that is running on Oracle WebLogic Server.
To upgrade Oracle Business Intelligence to run on IBM WebSphere:
Install Oracle Business Intelligence Release 11.1.1.7 on Oracle WebLogic Server, using the instructions in Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence. Ensure that you select the Enterprise Install and select Oracle WebLogic Server as the application server.
Upgrade from the earlier release of Oracle Business Intelligence to Release 11.1.1.7, using the instructions in Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence. Ensure that you upgrade the repository and Oracle BI Presentation Catalog.
Install Oracle Business Intelligence Release 11.1.1.7 on IBM WebSphere. Ensure that you select the Software-Only Install and follow the instructions in this chapter
Move the repository from the instance that is running with Oracle WebLogic Server to the instance that is running with IBM WebSphere using the following steps:
Copy the source repository file (.rpd) from the computer for Oracle WebLogic Server to an appropriate directory for Oracle Business Intelligence on the computer for IBM WebSphere.
Use Fusion Middleware Control on the computer for IBM WebSphere to upload the repository file. For information, see "Using Fusion Middleware Control to Upload a Repository and Set the Oracle BI Presentation Catalog Location" in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
Use the Oracle BI Administration Tool to update connection pool and database settings in the repository. The repository file might contain data source connection information from the Oracle WebLogic Server environment that must be changed to the connection settings for the IBM WebSphere environment.
Move the Oracle BI Presentation Catalog from the instance that is running with Oracle WebLogic Server to the instance that is running with IBM WebSphere using the following steps:
Copy the files for the source catalog from the computer for Oracle WebLogic Server to an appropriate directory for Oracle Business Intelligence on the computer for IBM WebSphere.
Use Fusion Middleware Control on the computer for IBM WebSphere to specify the location of the catalog. For information, see "Using Fusion Middleware Control to Upload a Repository and Set the Oracle BI Presentation Catalog Location" in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
Start Oracle Business Intelligence on IBM WebSphere and verify that you can open the catalog and see the upgraded analyses and other objects.
Use the information in this section to help troubleshoot issues with Oracle Business Intelligence with IBM WebSphere. This section contains the following topics:
Verifying the Configuration of Oracle Business Intelligence on IBM WebSphere
Viewing Log Files for Oracle Business Intelligence on IBM WebSphere
Before you perform any troubleshooting steps, verify that the configuration is running properly. The following list describes how to verify that processes are configured and running:
View the processes that are running in Oracle Process Manager and Notification Server by entering a command such as the following:
MW_HOME/instances/instance1/bin/opmnctl status
Verify that you can log into Oracle BI Presentation Services and other components by entering the appropriate URLs. See Section 10.2.6, "Determining Ports for Oracle BI Components on IBM WebSphere" for details on locating the port number to include when starting Presentation Services and other components on IBM WebSphere.
Verify that you can see two servers in the IBM WebSphere Administration console. One server is called OracleAdminServer, and the other is called bi_server1. You can see various components running on each of the servers.
If you have any issues with the configuration of Oracle Business Intelligence on IBM WebSphere, then check the log files that are described in the following list:
Administration Server Log Files:
user_projects/domains/cell_name/node_name/logs/OracleAdminServer/SystemOut.log
user_projects/domains/cell_name/node_name/logs/OracleAdminServer/SystemErr.log
Oracle BI Server Log Files:
user_projects/domains/cell_name/node_name/logs/bi_server1/SystemOut.log
user_projects/domains/cell_name/node_name/logs/bi_server1/SystemErr.log
If you attempt to access an instance of Oracle Business Intelligence that is not yet connected to an identity store, then you might see an error message that relates to the identity store.
You must install and configure an identity store for Oracle Business Intelligence. For more information, see Section 10.2.7.1, "Configuring the LDAP-Based Identity Store on IBM WebSphere."