C Additional Configuration Steps for the IBM WebSphere Server

C.1.1 ESB System Configurations

Ensure that the system information for the ESB services deployed are as follows:

• Virtual Host: The hostname of ESB design-time instance

• Port: The port number of ESB design-time instance

• Topic Location: ESB_JAVA_DEFERRED

The value of the 'Connection Factory Location' parameter does not matter for ESB on WebSphere 6.1.0.15, since ESB, by default, uses AQ messaging and uses the AQ JMS API to connect to the AQ Messaging topics.

C.1.2 Changing to File-based Slide Repository

By default, ESB on WebSphere 6.1.0.15 is configured to use database-based slide as the metadata repository. Perform the following steps configure ESB on WebSphere 6.1.0.15 to use file-based slide repository:

1. Rename Domain_file.xml to Domain.xml in the <SOA_HOME>/integration/esb/config directory.

2. Rerun IRCA for ORAESB schema from the<SOASuite 10.1.3.1 Installation pack>Disk1\install\soa_schema\irca\irca oraesb directory.

3. Execute the following script against ORAESB schema to upgrade it to 10.1.3.4: <SOASuite 10.1.3.4 Patchset Installation pack>\Disk1\install\soa_schema_upgrade\esb\sql\oracle\upgrade_10131_10134_oracle.sql

4. Edit the WAS_SOA10134_Installables/bin/ESB_data.aq.sql file and update the values for the following:

   • ESB_PARAMETER properties

   • DT_OC4J_HOST

   • DT_OC4J_PORT

5. Execute the following script against ORAESB schema to modify it for WebSphere Server:

   WAS_SOA10134_Installables/bin/ESB_data.aq.sql

C.1.3 Identify Service Configuration

The identity service in the default installation leverages the same model as the SOA Suite deployment on OC4J to obtain users from the Jazn.com realm. This can be changed by configuring the SOA_HOME/bpel/system/services/config/is_config.xml file. Refer to

http://download.oracle.com/docs/cd/B31017_01/integrate.1013/b28982/service_config.htm

for more details. Also, refer to the is_config.xml example files provided at SOA_HOME/bpel/system/services/config/ldap to connect to the external LDAP providers.