My Oracle Support Banner

SOA 11g Enterprise Deployment: Creating a Base Domain (Doc ID 1543070.1)

Last updated on MARCH 08, 2023

Applies to:

Oracle SOA Suite - Version and later
Information in this document applies to any platform.


We will create the base domain 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 these steps will differ from the steps described in the EDG.

Our admin server is called SOAAdminServer and will be hosted on the SOA2 machine instead of SOA1 in the EDG. The failover machine for the SOAAdminServer is SOA1. SOAAdminServer will be hosted on SOA2 instead of SOA1, in order to have a more even load for SOA1 and SOA2 machines. In our environment, SOA1 will also host the WLS-BAM1 managed server which usually has a higher load as compared to WLS_BAM2, so we decided to use SOA2 as the machine for SOAAdminServer.

The VIP for our SOAAdminServer is VIPASSOA.

Our OWSM managed servers WLS_WSM1 and WLS_WSM2 are hosted on WSM1 and WSM2 machines as compared to the EDG, which has them on SOA1 and SOA2. This will require some additional steps in our environment for Node Manager setup on WSM1 and WSM2 and creation of the related domain directories for the managed servers on these machines.


Resources Used:


  • Database preparation is finished, all SOA schemas are created and accessible
  • Network and file system preparation is completed
  • All Fusion Middleware products are installed
  • Web tier is installed and configured


  • soaedg_domain is created (the domain name can differ, however, we will use the same one as in the EDG)
  • OWSM managed servers WLS_WSM1 and WLS_WSM2 and the WSMCluster are created
  • NodeManager for the SOAAdminServer (on SOA2) is started
  • SOAAdminServer is started on its VIP (VIPASSOA)
  • Domain directories are created on WSM1 and WSM2 for WLS_WSM1 and WLS_WSM2 managed servers.
  • Node Manager on WSM1 and WSM2 are started
  • WLS_WSM1 and WLS_WSM2 managed servers are up and running
  • Manual failover and recovery for SOAAdminServer has been tested successfully
  • OHS has been configured to support the VIP for the SOAAdminServer (VIPASSOA)


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
 Check Prerequisites
 Run the Configuration Wizard to Create the Domain
 Start NodeManager and SOAAdminServer on SOA2
 Create a file for the SOAAdminServer
 Start the Node Manager on SOA2
 Start the SOAAdminServer on SOA2
 Change NodeManager Credentials
 Restart the SOAAdminServer via the Node Manager
 Configure and Start WLS_WSM Managed Servers
 Create a Domain Template
 Create Separate Local Domain Directories for the Managed Servers
 Unpack the Domain Template to the Managed Server Directories
 Apply the JRF Template to the WSMCluster
 Disable Hostname Verification
 Change Upload and Stage Directory for all Servers
 Start Node Manager on WSM1 and WSM2
 Start WLS_WSM1 and WLS_WSM2 Managed Servers from the WLS Console
 Configure the Web Tier for the Domain
 Edit Virtual Hosts Definitions
 Restart OHS instances
 Activate the WebLogic Plugin for the soaedg_domain
 Register OHS with the Admin Server
 Add Frontend Host and Port
 Validate Access through OHS
 Test Manual Failover of SOAAdminServer
 Stop the admin server on SOA2
 Migrate the VIP VIPASSOA to SOA1
 Configure the VIP VIPASSOA on SOA1
 Verify that the VIP works
 Start the SOAAdminServer on SOA1
 Manually Migrate SOAAdminServer Back to SOA2
 Take a Backup of all Installations

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.