In this post, lets walk through the steps of extending an existing SOA Suite 11g domain (that doesn't have OSB server), with an OSB server.
SOA 11g Version 11.1.1.6 on Windows 7 has been used for this illustration.
Prerequisites
The following installation needs to be ready to walk through this. Covering the details of installation are outside the scope of this blog.- Weblogic Server 11.1.1.6
- SOA Suite 11.1.1.6
- JDeveloper 11.1.1.6
- OEPE 11.1.1.8 (for compatibility with OSB 11.1.1.6)
- OSB 11.1.1.6
All the above are preferably to be installed in a single MIDDLEWARE HOME, which in this case is D:\MWHomes\fmw-11116 going forward will be referred as $MIDDLWARE-HOME
Below is a picture of my installation (I have installation OEPE elsewhere for a different reason, however, it is preferable to install it inside the same middleware home.)
Besides installation, we need to have a domain with SOA Server configured, so that, we can extend that domain with OSB server. I have fmw_domain1 created for this, with SOA server and BAM server in it, and both these servers are configured as managed servers and not merged with AdminServer.
For detailed steps of creating a SOA 11g Weblogic domain, pl refer to the blog "Creating Weblogic domain with SOA server and BAM"
Extending existing Weblogic domain with OSB
Run the domain configuration Utility (located at $MIDDLWARE-HOME\oracle_common\common\bin\config.cmd , OR alterntively at, $MIDDLEWARE-HOME\wlserver_10.3\common\bin\config.cmd)
In the first screen, choose "Extend an existing Weblogic Domain"
And, then on the next screen choose the particular domain to be extended by navigating through folder structure, in this case fmw_domain1
In the next screen, choose the products OSB and OSB OWSM extension. (Note - if OSB for developers is choosen, then OSB functionality will be merged with AdminServer and it will not be avaialble as an exclusive managed server). Dependency products gets selected automatically.
In the next screen provide schema info.
Note - the prefix of schema has been changed to DEV (in my case I have given DEV3 for the existing domain) -irrespective of what was given earlier while running the RCU. Pl update this first before progressing further.
Except two component schemas, -OWSM MDS Schema and OSB JMS Reporting provider, all are configuration of existing domain. Even for these two components also, they are using existing schemas DEV3_MDS and DEV3_SOAINFRA. (No new schemas need to be created, and hence no need to run RCU for this extension of domain.)
Note - modify OSB JMS Reporting Provider configuration, by changing the DB and driver info. Its default would be 'derby', and I am changing this here to 'Oracle' and so is the driver change.
In the next screen while choosing optional configuration, select 'Managed Servers, Clusters and Machines'
In the next screen, configure OSB server by providing appropriate port for it, and other details. In this case, I have provided 10001 as the port # for OSB.
Skip the clusters configuration in the next page, and move to machine configuration. Keep the machine configuration as-is (We are still running on the same local machine, and running in a single node environment)
In the next page, assign OSB server to the local machine where all other servers are already assigned in the existing server configuration.
In the next screen, verify the deployment summary, and 'Extend' the domain.
Verify the domain configuration
After configuring the domain, verify the domain configuration. Deploy sample service(s) and test them.
॥ स्वस्ति ॥
Comments
Post a Comment