In this post, lets walk through the steps of creating a Weblogic domain with SOA Server and BAM server. I have used SOA version 11.1.1.6 for illustration.
1. Prerequisites
The following installation needs to be ready to walk through this. This post only discusses the domation creation, but not product installations.- Weblogic Server 11.1.1.6
- SOA Suite 11.1.1.6
- JDeveloper 11.1.1.6
All the above are preferrably to be installed in a single MIDDLEWARE HOME, which in this case is D:\MWHomes\fmw-11116
Below is a picture of my installation (I have also installed OSB, but not required for this, you can ignore for this post).
In the session below lets walk through creating Weblogic domain.
2. Creating a Weblogic domain with Admin Server, SOA Server, BAM Server
Here are the steps in creating domain, and are elaborated further.
- Run RCU and create Schemas needed for the use of SOA Suite
- Run configuration Wizard for creating domain using the above schemas
- Verify the configured domain, and sample run AdminServer, managed servers
Note - In this blog we are configuring SOA server and BAM server in managed server mode exclusively and not merging with AdminServer. However, for development simplicity one may want to choose to merge them with AdminServer -especically when trying on a low hardware configuration machines.
2.1. Run RCU
run RCU to create repository / schemas for Weblogic domain for SOA server and BAM server only. Steps included are illustrated in the snap shots below:
Oracle XE 11g is used for this exercise, and that was running on localhost in this case.
Notice that 'Metadata Services(MDS)' gets selected automatically as part of dependency resolution.
Provide password with which these schemas are to be created
Schemas get created in the provided DB (Oracle 11g XE in this case) as follows:
2.2. Domain Configuration Wizard
After RCU creation, create Weblogic Domain by running configuration wizard as follows:
In the domain config wizard, choose the following:
- Oracle SOA Suite
- Oracle Enterprise Manager
- Oracle BAM
Name the domain.
Provide the domain Admin credentials - in this case weblogic / welcome1 were given.
Chosen the development mode and JDK
Provide the schema details that are created during the earlier step of 'running RCU'
Schema access gets validated
Select the optional configuration for "Managed Servers, Clusters and Machines" - this is for configuration of SOA and BAM managed servers.
Depending our configuration choices in the initial steps of domain creation, we will get two servers displayed in the next step soa_sever1 and bam_server1.
Provide appropriate port numbers for these servers to listen to. We have are doing a simple managed server configuration without clusters. Configuring soa_server1 on port 8001 and bam_server1 on port 9001 to listen to.
Skip the cluster configuration step.
For the machines configuration, select "All local machines"
Next, Move all servers under the local machine
Here is how the deployment summary looks like:
2.3. Verify the configured domain, and sample run servers
Start the Weblogic AdminServer
$MIDDLEWARE-HOME\user_projects\domains\fmw_domain1\bin\startWeblogic.cmd
Start the node manager
First set the node manager properties as follows:
$MIDDLEWARE-HOME\oracle_common\common\bin\setNMProps.cmd
and then run node manager as follows:
$MIDDLEWARE-HOME\wlserver_10.3\server\bin\startNodeManager.cmd
Start soa_server1
Now that node manager has been started, from the Weblogic server console, start soa_server1
Alternatively, soa_server1 can be started from command prompt without the help of node manager as follows:
$MIDDLEWARE-HOME\user_projects\domains\fmw_domain1\bin\startManagedWeblogic.cmd
Deploy sample composites and test them.
॥ स्वस्ति ॥
Comments
Post a Comment