SOA 11g Enterprise Deployment: Extending a Domain for SOA and BPM Components
(Doc ID 1544123.1)
Last updated on DECEMBER 25, 2019
Applies to:Oracle SOA Suite - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
We will extend the soaedg_domain created in previous steps for SOA and BPM components for our enterprise environment following the Enterprise Deployment Guide (EDG) for SOA 11g.
As our environment differs from the topology used in the EDG, some of the steps will differ from the steps described in the EDG.
We have created the WSM managed servers on machines separate from the machines that will be used for the SOA managed servers. We will use SOA1 and SOA2 machines for WLS_SOA1 and WLS_SOA2 managed servers. Because of that, we did not define our virtual IP addresses for the SOA managed servers yet, so we will do this now. We will also create the domain directories for the managed servers on SOA1 and SOA2 in this chapter, while in the EDG they have been already created while creating the base domain for the same reason.In our environment, the managed servers for SOA and WSM will all listen on ports 8001.
We will also include information for an environment which uses both SOA and BPM. The task is mainly the same, with some additions for BPM.
- Extending the Domain for SOA Components
- Extending the Domain to Include Oracle BPM
- IP and hostname definitions for our advisor sample environment
- Managing the Topology for an Enterprise Deployment
- Base domain installation is completed and verified.
- The soaedg_domain previously created is extended for SOA and optionally BPM components. All managed servers for SOA Suite are configured and verified.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Enable Virtual IP Addresses for the SOA Servers|
|Run the Configuration Wizard to Extend the Domain for SOA|
|Restart the Admin Server SOAAdminServer|
|Disable Hostname Verification for the SOA Managed Servers|
|Start the Node Manager on SOA1|
|Propagate Domain Changes to Managed Server Directories|
|Create the Managed Server's Domain Directory for WLS_SOA2|
|Create a new Domain Template for the soaedg_domain on SOA2|
|Extract the Domain Template to the Domain Directory for WLS_SOA2|
|Create the Domain Directory for WLS_SOA1|
|Extract the Domain Template to the Domain Directory for WLS_SOA1|
|Start the SOA Managed Servers|
|Validate GridLink DataSources|
|Configure the Web Tier|
|Configure OHS for the SOA Servers|
|Add VIPMSSOA1 and VIPMSSOA2 to the /etc/hosts file on WEB1 and WEB2|
|Define Frontend Host and Port for the SOACluster|
|Configure Persistence Store on Shared Disk|
|Configure B2B for High Availability|
|Updating the B2B Instance Identifier for Transports|
|Configure Adapters for High Availability|
|Enable High Availability for the File Adapter|
|Enable High Availability for the FTP Adapter|
|Enable High Availability for the JMS Adapter|
|Enable High Availability for the DBAdapter|