Setting the WLS Cluster address for Direct BindingRMI invocations to composites Configuring a Shared JMS Persistence Store
5.18 Setting the WLS Cluster address for Direct BindingRMI invocations to composites
When using direct binding composites, you must set the WLS Cluster address for the SOA_Cluster. To set the WLS Cluster address:1. In the WebLogic Server Administration Console, in the Change Center section,
click Lock Edit. 2. In the left pane, choose Environment from the Domain Structure window, and then choose Clusters. The Summary of Clusters page appears.3. Select the SOA_Cluster cluster.
4. In the Configuration, General tab, enter the following in the Cluster Address
field: SOAHOST1VHN1:8001,SOAHOST2VHN1:80015. Click Save.
6. To activate the changes, click Activate Changes in the Change Center section of
the Administration Console. 7. Restart the servers for the Frontend Host directive to take effect in the cluster.5.19 Configuring a Shared JMS Persistence Store
Configure the location for all of the persistence stores as a directory that is visible from both nodes. For more information see Section 2.3, Shared Storage and Recommended Directory Structure. You must then change all of the persistent stores to use this shared base directory as follows: 1. Log into the Oracle WebLogic Server Administration Console.2. In the Domain Structure window, expand the Services node and then click the
Persistence Stores node. The Summary of Persistence Stores page appears. 3. Select the persistence store represented as a hyperlink from the Name column of the table. The Settings page for the persistence store appear. Note: For asynch requestresponse interactions over direct binding, the SOA composites must provide their jndi provider URL for the invoked service to look up the beans for callback. If soa-infra config properties are not specified, but the WLS Cluster address is specified, the cluster address from the JNDI provider URL is used. This cluster address can be a single DNS name which maps to the clustered servers IP addresses or a comma separated list of server ip:port. Alternatively, the soa-infra config property JndiProviderURLSecureJndiProviderURL can be used for the same purpose if explicitly set by users. 5-20 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter 4. In the Configuration tab, enter the location on a persistent storage solution such as NAS or SAN that is available to other servers in the cluster in the Directory field. Specifying this location enables pending JMS messages to be sent. The location should follow the following directory structure: ORACLE_BASEadmindomain_namesoa_cluster_namejms5. Click Save and activate changes.
6. Restart the servers to make the change in the persistent stores effective.5.20 Configuring a Default Persistence Store for Transaction Recovery
Parts
» Oracle Fusion Middleware Online Documentation Library
» What is an Enterprise Deployment? Terminology
» Load Balancer Requirements Web Tier
» Oracle Identity Management Application Tier
» Data Tier What to Install Unicast Requirement
» Installation and Configuration Procedure Overview of Installation Strategies
» Database Host Requirements Supported Database Versions Initialization Parameters
» Loading the Oracle Fusion Metadata Repository in the Oracle RAC Database
» Configuring SOA Schemas for Transactional Recovery Privileges Backing Up the Database
» IPs and Virtual IPs Firewalls and Ports
» Hardware Requirements LDAP as Credential and Policy Store
» Installing Oracle HTTP Server on WEBHOST1 and WEBHOST2
» Validating Oracle HTTP Server Through the Load Balancer Backing Up Oracle HTTP Server
» Installing Oracle WebLogic Server Installing Oracle Fusion Middleware for WebCenter
» Enter HOMEoraInventory, where HOME is the home directory of the user Click Next.
» Applying the Java Required Files JRF Template to the WSM-PM_ Cluster
» Manually Failing Over the Administration Server to SOAHOST2
» Restarting the Administration Server Configuring Oracle Coherence for Deploying Composites
» Setting Connection Destination Identifiers for B2B Queues
» Validating Access Through Setting the Frontend HTTP Host and Port
» Installing Oracle Fusion Middleware Home Extending the Domain for WebCenter Components
» Generating Self-Signed Certificates Using the utils.CertGen Utility
» Configuring Node Manager to Use the Custom Keystores
» Configuring Search Services About Adding Oracle UCM to a Domain
» Extending the Domain to Include Oracle UCM
» Configuring the WC_UCM1 Managed Server
» Reassociating the Domain Policy Store
» Running the OAM Configuration Tool
» Configuring IP Validation for the Webgate Understanding Virtual Host configuration
» Configuring Virtual Hosts for OAM 10g
» The RREG Tool Register the WebGate Agent
» Configuring System Properties Setting Up Discussions Server to Use OAM as SSO Provider
» Monitoring the Topology Configuring UMS Drivers
» Managing Space in the SOA Infrastructure Database
» Performing Backups and Recoveries
Show more