This chapter describes issues you might encounter when you install and configure supported Oracle Fusion Middleware products on IBM WebSphere. It includes the following topics:
Note:
This chapter contains issues you might encounter while installing, configuring, or managing any of the Oracle Fusion Middleware products on IBM WebSphere.Be sure to review the product-specific release note chapters elsewhere in this document for any additional issues specific to the products you are using.
This section describes general issue and workarounds. It includes the following topics:
Section 9.1.1, "Log File Error Message when Starting the SOA Server"
Section 9.1.2, "Save Settings Button Under Accessibility User Preferences Has Incorrect Label"
Section 9.1.4, "Cannot Create an XA Connection Factory in the IBM WebSphere Administration Console"
Section 9.1.6, "Adding Shared Libraries to Deploy a Task Form from Oracle JDeveloper"
Section 9.1.7, "Setting Cookie Paths for Oracle SOA Suite Applications"
Section 9.1.8, "Deploying a SOA Composite Application to a SOA Cluster"
Section 9.1.10, "One-and-Only-One Event Subscriptions Are Not Supported"
Section 9.1.11, "Deployed Task Form Startup Failure in IBM WebSphere Administration Console"
Section 9.1.12, "Oracle BPM Worklist Displays as Undefined in Administration Console"
Section 9.1.13, "Dashboard Tab May Display Completed SOA Composite Instance States as Running"
Section 9.1.14, "Two-Way SSL Configuration with Oracle SOA Suite Is Not Supported"
Section 9.1.15, "Multiple Fault Recovery Failure with the Recover With Options Dialog"
Section 9.1.16, "IBM WebSphere Application Server - ND Installation Requires a Server Restart"
Section 9.1.17, "Test Emulations of Asynchronous BPEL Processes Fail"
Section 9.1.18, "SETMANAGEDCONNECTION() Fails with ILLEGALSTATEEXCEPTION for the AQ Adapter"
Section 9.1.21, "For the JMS Adapter, Instances Become Recoverable Even Without Failover"
Section 9.1.22, "Kerberos and SPNEGO are not supported with Oracle WSM"
Section 9.1.23, "REST Security Policies and Templates Not Certified"
When you start the SOA server (for this example, named soa_server1) in an IBM WebSphere Application Server environment, you can receive the following error message in the WAS_HOME/profiles/CustomXX/logs/soa_server1/soa_server1-diagnostic.log file.
This message can be safely ignored.
[2013-02-21T10:46:10.786-08:00] [soa_server1] [ERROR] [] [oracle.soa.mediator.dfw] [tid: Non-deferrable Alarm : 0] [ecid: disabled,0] [APP: soa-infra] failed to deregister mbean[[ javax.management.InstanceNotFoundException: oracle.mediator:type=MediatorDiagnostic,name=MediatorDiagnostic at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean (DefaultMBeanServerInterceptor.java:1106) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor. exclusiveUnregisterMBean (DefaultMBeanServerInterceptor.java:427) at . . . . . .
In Business Process Workspace, the Save Settings button under Preferences > Accessibility contains an incorrect label. The label for this button should be OK instead of LABEL_OK.
When Oracle Business Process Management (Oracle BPM) is installed on IBM WebSphere Application Server, a java.lang.OutOfMemoryError occurs when running automation tests. This is because the default memory configuration for WebSphere Application Server is set too low for this. This does not occur when Oracle BPM is installed on IBM WebSphere Network Deployment.
As a workaround, make the following changes to the JVM properties:
Initial heap size increased to 1024MB
Maximum heap size increased to 2148MB
MaxPermSize increased to 512 MB
Verbose garbage collection is selected
You cannot create an XA connection factory as a messaging provider in the IBM WebSphere Administration Console. The connection factories created by default are non-XA types. For example:
Go to IBM WebSphere Administration Console:
http://host:port/ibm/console
Go to Resources > Queue connection Factories.
Attempt to create an XA-based connection factory.
There is no provision to select an XA mode. You can only create non-XA connection factories.
On an IBM WebSphere Application Server instance, the accessibility options will not be set even if you have selected the option on the User Messaging Preferences login screen.
As a workaround, set the accessibility option on the User Messaging Preferences Settings page as follows:
Go to Oracle UMS User Messaging Preferences UI:
http://host:port/sdpmessaging/userprefs-ui
Enter a valid user name and password.
In the User Messaging Preference Login page, select Standard from the Accessibility Mode drop-down list and click Login.
After logging in, click the Settings link at the top right corner of the User Messaging Preferences page.
In the Settings page, you can set your Accessibility options in the following manner:
Select Screen Reader from the Accessibility Mode options, if desired.
Select the High Contrast checkbox if you want the text to be displayed in high contrast.
Select the Large Fonts check box if you want the text to be displayed in large fonts.
Click the Home link to go to the User Messaging Preferences page. The Accessibility options, that you chose to set in the Settings page, will be enabled.
Note:
The Settings options in UMS User Messaging Preferences is session based. If you log out or close the browser, you will lose the accessibility options settings. You will need to reset the settings after each login.When you deploy a SOA composite application with a task flow from Oracle JDeveloper to the SOA server on IBM WebSphere, the application cannot be started correctly due to a ClassNotFound error. The shared library of the application is empty.
As a workaround, perform the following steps:
Go to IBM WebSphere Administration Console.
Select Applications > Application Types > WebSphere Enterprise Applications > task_form_name > Shared library references.
Manually add adf.oracle.domain_1.0_11.1.1.2.0 and oracle.jsp.next_11.1.1_11.1.1.
Restart the application.
By default, applications deployed on IBM WebSphere have their cookie path set to "/". This default setting means that all applications on the same IBM WebSphere cell share the same session identifier. Therefore, as you move between applications, the session identifier value for the previous application is overwritten.
For example, if you access Oracle SOA Composer (/soa/composer), then access Oracle Enterprise Manager (/em), and then return to Oracle SOA Composer (/soa/composer), you are prompted to log in again because the previous session identifier value is overwritten at the point at which you log in to Oracle Enterprise Manager.
Section "Setting Cookie Paths for WebCenter Portal Application Modules Post Deployment" of the Third-Party Application Server Guide describes how to specify unique cookie paths for each application. This action enables you to avoid session invalidation as you move between applications.
In Step 4 of that section, where you click Manage Modules in IBM WebSphere Administration Console to select the modules to manage, and Step 5, where you specify the cookie path, note the following Oracle SOA Suite details to specify.
| Target Server | Application Name | Modules | Cookie Path |
|---|---|---|---|
| soa_server1 | composer
(Oracle SOA Composer) |
soa-composer-was.war | /soa/composer |
| worklistapp
(Oracle BPM Worklist) |
worklist-was.war | /integration/worklistapp |
|
| bam_server1 | oracle-bam
(Oracle BAM) |
bam-web.war | /OracleBAM |
| soa_server1/bam_server1 | usermessagingserver
(Oracle User Messaging Server) |
sdpmessaginguserprefs-ui-web.war | /sdpmessaging/userprefs-ui |
| OracleAdminServer | em
(Oracle Enterprise Manager) |
em.war | /em |
After performing these tasks, you must restart the target servers (soa_server1, bam_server1, and OracleAdminServer).
When you deploy a SOA composite application from Oracle JDeveloper, you cannot select the application server to which to deploy. Instead, the application is deployed to the Deployment Manager by default.
As a workaround, log in to the IBM WebSphere Administration Console, uninstall the application from the Deployment Manager, and reinstall the application to the SOA cluster by using the generated .ear file.
You cannot deploy a SOA bundle file from Oracle Enterprise Manager Fusion Middleware Control. As a workaround, use the wsadmin command line shell.
For example, assume vacationapproval.zip is a SOA bundle file that includes three SOA composite applications.
wsadmin> soa.sca_deployComposite("http://myhost.us.example.com:7001",
"/tmp/vacationapproval.zip")
For more information about wsadmin commands, see Section "Oracle SOA Suite wsadmin and WLST Command Differences" of the Oracle Fusion Middleware Third-Party Application Server Guide.
Business events are published to the Event Delivery Network (EDN). EDN provides support for delivering events to one-and-only-one subscribers, in which the event is sent to the subscriber in its own global (that is, JTA) transaction. However, one-and-only-one subscriptions are not supported when using EDN with IBM WebSphere Server.
As a workaround, change the one and only one consistency level of the event subscription to guaranteed in the Create Mediator dialog.
Note:
This change downgrades the consistency level. Therefore, a system failure may cause an event to be delivered more than once because there is no global transaction. If the subscriber fails to process the event, the event is not resent.When you attempt to start a deployed task form application in the IBM WebSphere Administration Console, it fails. You receive an error message similar to the following:
Was2Form failed to start. Check the logs for server dmgr on node DefaultCellManager01 for details. ErrorAn error occurred while starting Was2Form. Check the logs for server dmgr on node DefaultCellManager01 for more information.
As a workaround, perform the following steps:
Deploy the task flow in Oracle JDeveloper at the application level, instead of the project level. This generates the EAR file.
Undeploy the task flow from the IBM WebSphere Administration Console. Save directly to the master configuration to synchronize changes to all nodes.
Deploy the EAR file generated in step 1 through the IBM WebSphere Administration Console.
Go to Websphere Enterprise Applications > Install > Pick EAR from Locale file system.
Click Next (use the default options).
On step 2 of the deploy page "Map modules to servers," select all modules, highlight only the SOA server (for example, soa_server1), and click Apply.
On step 3, "Map virtual hosts for Web modules," select the WAR file.
At the end, save directly to the master configuration again.
Select the EAR file to start it.
If you configure an Oracle SOA Suite cluster or single server environment on IBM WebSphere, you may receive an error when accessing Oracle BPM Worklist indicating that it is undefined. If you log in to IBM WebSphere Administration Console, and select Applications > WebSphere enterprise applications > worklistapp > Shared library references, and see that only one row (worklistapp) is displayed when two rows should display (worklistapp and worklist-was.war), you must perform the following steps.
Uninistall Oracle BPM Worklist (known as worklistapp in the IBM WebSphere Administration Console).
Re-install Oracle BPM Worklist.
To uninistall Oracle BPM Worklist:
Log in to the IBM WebSphere Administration Console.
From the panel on the left hand side, select Applications > Application Type > WebSphere enterprise applications.
Select the check box for worklistapp from the Enterprise Applications list.
Click the Stop button to stop worklistapp.
Select worklistapp again.
Click the Uninstall button, and click OK.
Select Review from the Save and Review options.
Select Synchronize changes with nodes, and click Save.
Wait until configuration synchronization is complete, then click OK.
Confirm that worklistapp is now removed (uninstalled) from Enterprise Applications.
To re-install Oracle BPM Worklist:
If not already there, navigate to Applications > Application Type > WebSphere enterprise applications.
Click Install.
Select the Remote file system option:
Click Browse > DefaultCellDepMgrNode.
Click the root directory (/), and go to your ORACLE_HOME.
Navigate to soa/applications.
Select worklist-was.ear, and click OK.
Select the default Fast Path, and click Next.
Select the installation options:
Change the name Oracle BPM Worklist to worklistapp, and click Next.
Map the modules to the servers:
Select the check boxes for the two modules (jar and war).
From the Clusters and servers list, select server=soa_server1 or the server or cluster on which Oracle SOA Suite is installed.
Click Apply.
Confirm that the two modules now have the correct server value (for example, soa_server1) in the server column.
Click Next.
Map the virtual hosts for the web modules:
Select the one web module.
Click Next.
On the Summary screen, review the information, and click Finish.
Output displays on the screen, and you are prompted to save or review your local changes.
Select Review.
Save your workspace changes:
Click Synchronize changes with Nodes.
Verify that Total changed documents is 29 (if not, there may be an error).
Click Save.
Wait until configuration synchronization is complete, then click OK.
The worklistapp is now installed and ready to be started.
Verify that the worklistapp is present in the Enterprise Applications list.
Select worklistapp, and click Start.
Confirm that the Application Status is up.
Test that Oracle BPM Worklist in accessible by visiting the following URL:
http://host:port/integration/worklistapp
The Dashboard tab of a SOA composite application in Oracle Enterprise Manager Fusion Middleware Control may show the state of an instance as running even though the instance has actually completed. In this scenario, verify the actual instance state on the Flow Trace page.
Two-way SSL configuration on IBM WebSphere is not supported. Therefore, there is no support for Oracle Web Service Manager (OWSM) two-way security policies that are SSL-configured. Note that one-way SSL is supported (for example, in which you create an SSL-configured SOA service that invokes another SOA service).
If you click Recover With Options on the Fault and Rejected Messages tab of a SOA composite application, and attempt to recover all faults by selecting Recover All in the Recover With Options dialog, the faults are not recovered and display as pending. The problem only occurs with the Recover With Options dialog. Individual instance recovery and selecting multiple instances for recovery works correctly.
If you install IBM WebSphere Application Server - Network Deployment (ND) for use with Oracle SOA Suite, you must restart the server for JCA adapter binding components to be active. Otherwise, JNDIs are not active, and you receive the following error message:
Non Recoverable System Fault : BINDING.JCA-12563 Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Write' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. File_MEDComposite:WriteMed [ Write_ptt::Write(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. . . . . . .
You cannot create test emulations involving asynchronous BPEL processes in a SOA composite application on IBM WebSphere. During test execution, this results in an CannotInstantiateObjectException exception error.
When running Oracle AQ Technology Adapter cases on the WebSphere Platform, you might encounter the following error:
javax.resource.spi.ResourceAllocationException: setManagedConnection: illegal state exception. State = STATE_ACTIVE_FREE MCW = 28392839
To follow-up on this exception, IBM PMR # 69026,756 has been created
When you deploy an application using Oracle Fusion Middleware on IBM WebSphere, you might receive the following runtime error:
oracle.fabric.common.PolicyEnforcementException: PolicySet Invalid: WSM-06102 PolicyReference The policy reference URI oracle/wss_username_token_service_policy is not valid
To workaround this issue, perform the following steps:
Open the policy-accessor-config.xml file, which can found at the following location:
WAS_HOME/profiles/Dmgr01/config/cells/DefaultCell/fmwconfig/
Locate the policy-accessor properties and uncomment the following properties and set the value of each property as shown:
<property name="active.protocol">
remote
</property>
<property name="java.naming.provider.url">
corbaloc:iiop:hostname:rmi.port
</property>
In this example, replace hostname and rmi.port to identify the host and RMI port where the policy manager is running.
No restart is required. By default, the new version of the policy-accessor-config.xml is loaded every 10 mins. However, if you want to pick up the changes immediately, then you can restart the server.
When running Oracle Enterprise Manager Fusion Middleware Control on IBM WebSphere, you might experience errors if you attempt to stop or start the internal Oracle applications that are displayed under the Internal Applications folder in the target navigation pane.
The applications listed here are internal Oracle applications. You should not start or stop these applications from Fusion Middleware Control. If you must stop or start these applications, then start or stop the managed servers that host the internal applications.
When the SOA JMS adapter is installed on WebSphere and is communicating with the IBM WebSphere Default JMS Messaging provider, you must set the property Persistent message reliability to Assured persistent rather than Reliable persistent; otherwise, an incorrect setting can result in loss of messages.
Also, occasionally when the failover scenario does not occur, you can see situations that include an error (transaction timing out, or the closing of JMS session) from the IBM WebSphere JMS, making instances become recoverable. If this happens, you need to manually recover the instances from the Oracle Enterprise Manager.
Kerberos and Simple and Protected GSSAPI Negotiation Mechanism (SPNEGO) are not supported with Oracle Web Services Manager.
Note the following limitations:
The Kerberos policies and assertion templates included with Oracle WSM are not supported.
SPNEGO functionality is not supported.
The current release of REST security policies and templates are not certified on IBM WebSphere.
This section describes configuration issues and their workarounds. It includes the following topics:
Section 9.2.1, "Error Configuring a Cell When IBM WebSphere Installed on Windows 2003 and 2008"
Section 9.2.2, "Configuring Coherence for a SOA Cluster on IBM WebSphere"
Section 9.2.8, "Additional Configurations For SSO Logout on WebSphere"
When IBM WebSphere is installed on Windows 2003 or Windows 2008, the following error sometimes displays when you attempt to create a cell:
WebSphere Profile Update Failed! No Changes Were Saved To The WebSphere Profile Profile Location: x:\mydir\APPSER~1\profiles\Dmgr02 Reason Exception saving changes to WebSphere configuration
The issue is due to the Jython libraries shipped with IBM WebSphere. As a workaround:
Locate and edit the file:
WAS_HOME\optionalLibraries\jython\Lib\javaos.py
Locate the function: _getOsType
Edit the _osTypeMap variable to return "nt" as the default.
_osTypeMap = (
( "nt", r"(nt)|(Windows NT)|(Windows NT 4.0)|(WindowsNT)|"
r"(Windows 2000)|(Windows XP)|(Windows CE)" ),
( "dos", r"(dos)|(Windows 95)|(Windows 98)|(Windows ME)" ),
( "mac", r"(mac)|(MacOS.*)|(Darwin)" ),
( "None", r"(None)" ),
( "nt", r"(.*)" ), # default - posix seems to vary mast widely
)
Save the changes.
When you configure a SOA cluster on IBM WebSphere, you must configure Oracle Coherence with the host names and other required cluster properties.
For Oracle WebLogic Server environments, refer to the Oracle Coherence configuration information "Configuring Oracle Coherence for Deploying Composites" in the High Availability Guide.
When configuring a SOA Cluster on IBM WebSphere, you perform a similar set of tasks, using the following instructions that are specific to IBM WebSphere:
Login to the IBM WebSphere Administrative Console.
Navigate to the Java Virtual Machine Custom Properties page:
Servers > soa_server_name > Java and Process Management > Process Definition > Java Virtual Machine > Custom Properties
Add the following properties:
For a multicast cluster:
tangosol.coherence.clusteraddress tangosol.coherence.clusterport
For a unicast cluster:
tangosol.coherence.wka1 (= host1) tangosol.coherence.wka2 (= host2) tangosol.coherence.localhost = (host?) tangosol.coherence.wka1.port tangosol.coherence.wka2.port tangosol.coherence.localport
When you install and configure Oracle BAM on IBM WebSphere, you cannot configure the Oracle BAM servers in the high availability, two-node configuration as described "Configuring High Availability for Oracle BAM" in the High Availability Guide.
Instead, when configuring Oracle BAM on IBM WebSphere, you must use a cold failover configuration. For more information, see "Active-Passive Topologies for Oracle Fusion Middleware High Availability" in the High Availability Guide.
When using Fusion Middleware products on IBM WebSphere ND with an IBM @ HTTPServer (IHS) front end, requests coming in to the Content Server may instead be routed to the Fusion Middleware Welcome page that is running on the cell's Administration Server (OracleAdminServer).
For requests to be properly routed to the Content Server, perform the following steps after fully configuring the cell.
Refer to IBM's Network Deployment documentation for detailed information about editing, propagating, and regenerating the plugin-cfg.xml file:
Disable automatic propagation of the plugin-cfg.xml file.
For example:
IBM/HTTPServer/plug-in/config/webserver1/plugin-cfg.xml
Manually regenerate plugin-cfg.xml.
Manually edit plugin-cfg.xml to remove any entries that may cause requests to be routed to OracleAdminServer.
Manually propagate plugin-cfg.xml to the IHS Web server plugin.
If you update the cell after performing these steps, you might see this issue again. If so, then repeat these configuration steps.
Users are not able to register WSRP/JPDK Producers in Oracle WebCenter Portal's Pagelet Producer Console in an IBM WebSphere Application Server instance. To resolve this issue, follow the steps below to add the necessary role (AppConnectionManager) to the Pagelet Producer application.
Open WebSphere Admin Console.
Under WebSphere Applications Deployment, right-click pagelet-producer and select Security and Application Roles.
Click Application stripe and select pagelet-producer.
In the Starts with field, enter AppConnectionManager and click Search. Select the AppConnectionManager role and click Edit.
Under Members, click Add to open a dialog that allows you to search for principals and assign the necessary users or groups to the role. Select the required user(s) and click OK to close the dialog.
Click OK to save the application settings.
Restart the WC_Portlet managed server (the updated security settings do not take effect until the server is restarted).
While trying to set passwords (such as the Proxy Password), through WebCenter Portal's Pagelet Producer Console in an IBM WebSphere Application Server instance, the following error displays:
ADF_FACES-60097: For more information, please see the server's error log foran entry beginning with: ADF_FACES-60096:Server Exception during PPR, #9
To workaround this issue you must grant some additional permissions to the pagelet producer application:
Using wsadmin, connect to the Dmgr server for the cell configured with the pagelet producer application:
WC_HOME/common/bin/wsadmin.sh -conntype SOAP -user admin username -password password -host Dmgr_host -port admin_SOAP_port
See also "Running WebCenter Portal wsadmin Commands " in Third-Party Application Server Guide.
Run the following Opss.grantPermission command to grant permissions to the pagelet producer application to update proxy passwords:
wsadmin> Opss.grantPermission(appStripe=None,principalClass=None,principalName=None, codeBaseURL='file:${user.install.root}/installedApps/DefaultCell/pageletproduc er.ear/', permClass='oracle.security.jps.service.credstore.CredentialAccessPermission', permTarget='context=SYSTEM,mapName=ensemble,keyName=*',permActions='read,write ,update,delete')
Restart the WC_Portlet managed server (the updated security settings do not take effect until the server is restarted).
To configure Oracle SOA Suite for high availability on WebSphere, follow the instructions in "Federating a Remote Machine to an Existing Cell" in Configuration Guide for IBM WebSphere Application Server.
However, when following these instructions, you must be sure to stop and restart the Deployment Manager before configuration of the second node. For more information, see "Configuring the Deployment Manager to Detect the Remote Node Agent" in the Third-Party Application Server Guide.
You must configure the Sync Filter to get SSO logout on WebSphere to work well. In the deployment descriptor (for example, web.xml) of the application, the filter can be configured for certain URL patterns as in the following example.
<filter> <display-name>SSOSessionSynchronizationFilter</display-name> <filter-name>SSOSessionSynchronizationFilter</filter-name> <filter-class>oracle.security.was.filter.SSOSessionSynchronizationFilter</filter-class> </filter> <filter-mapping> <filter-name>SSOSessionSynchronizationFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping>
You also need to add the following JAR to the WebSphere classpath:
$MiddleWareHome/oracle_common/modules/oracle.ssofilter_11.1.1/ssofilter.jar
You can receive an ArrayIndexOutOfBoundsException error in the log file after accessing the Log Configuration page in Oracle Enterprise Manager Fusion Middleware Control.
The Log Configuration page is displayed correctly. The error has no impact on product functionality and can be ignored.
This section describes documentation errata. It includes the following topic:
Steps that describe how to patch a WebCenter Portal 11.1.1.6.0 installation to 11.1.1.7.0 are documented in "Patching WebCenter Portal on IBM WebSphere from 11.1.1.6 to 11.1.1.7"in Third-Party Application Server Guide.
Changes to the information provided are listed below:
Before you start - Determine your existing Oracle Web Services Manager (OWSM) security policy URIs
Oracle recommends that you record your existing OWSM policy URI settings before you patch to WebCenter Portal 11.1.1.7.0. This step is missing from the documentation.
To determine your existing settings prior to patching WebCenter Portal 11.1.1.6.0, follow the steps described in "Determining OWSM Policy URIs for Spaces, Discussions, and Portlet Web Service End Points" in Patching Guide.
Step 10 - Use the Patch Set Assistant to update all the required schemas
This step must be done before Step 5 "Start the upgraded IBM WebSphere node agent and deployment manager".
Section 10.2.11.1 of Third-Party Application Server Guide describes the steps for configuring for scaling out JEE components for Oracle Business Intelligence on IBM WebSphere. These steps must be updated because they differ slightly depending on whether you install with the Installer for 32-bit or 64-bit systems.
The steps when using the 32-bit Installer are as follows:
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.
The Profile Management tool is displayed at the end of the IBM WebSphere installation. Provide the settings for the Profile Management tool as described in the existing Step 4 in Section 10.2.11.1.
Stop the NodeAgent using the stopNode.sh script.
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.
Start the NodeAgent using the startNode.sh script.
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
Follow the existing Step 6 in Section 10.2.11.1 to 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.
The steps when using the 64-bit Installer are as follows:
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.
Unlike for the 32-bit Installer, the NodeAgent does not exist until the profile is created for the 64-bit Installer.
Run the Profile Management tool as described in the existing Step 4 in Section 10.2.11.1.
Stop the NodeAgent using the stopNode.sh script.
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
Start the NodeAgent using the startNode.sh script.
Follow the existing Step 6 in Section 10.2.11.1 to 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.
Section 10.4 describes how to upgrade Oracle Business Intelligence to run on IBM WebSphere. The section begins with a bulleted list that needs to be reworded as follows:
If you have a 10g Release of Oracle Business Intelligence that is running on IBM WebSphere.
If you have a previous 11g Release of Oracle Business Intelligence that is running on Oracle WebLogic Server.