Extending a SOA Domain to Oracle Service Bus on cluster

Extending a SOA Domain to Oracle Service Bus

We had our SOA environment on a two node cluster and we had to extend this for OSB.Our SOA set up is based on the enterprise deployment guide as recommended from Oracle and below are the steps we did to extend the domain.We have installed WL_HOME and MW_HOME (binaries) on a shared storage and they are available from SOAHOST1 and SOAHOST2.

Back up the installation & Enable VIP for OSB servers

To back up the existing Fusion Middleware Home and domain run the following command on SOAHOST1

tar -cvpf fmwhomeback.tar ORACLE_BASE/product/fmw
tar -cvpf domainhomeback.tar ORACLE_BASE/admin/domain_name/aserver/domain_name

Enable the Virtual IPs VIP5 & VIP6 in the SOAHOST1 and SOAHOST2.

Extend a SOA Domain to Include Oracle Service Bus

Download & Install the OSB to create a new Oracle Service Bus home.

Extend a SOA Domain to Include Oracle Service Bus

Change directory to the location of the Configuration Wizard. This is within the Oracle Service Bus directory.
cd ORACLE_COMMON_HOME/common/bin
./config.sh


                          
Select Extend an existing WebLogic domain, and click Next




In the Select Extension Source screen, select Extend my domain automatically to support the following added products and select the following products (the components required by Oracle SOA and Oracle WSM Policy Manager should already be selected and grayed out):



Oracle Service Bus OWSM Extension - 11.1.1.7 [osb]
Oracle Service Bus - 11.1.1.0 [osb]
WebLogic Advance Web Services JAX-RPC Extension







Select the select the OSB JMS reporting Provider schema.










In the Test JDBC Component Schema screen, verify that the Oracle Service Bus JMS reporting datasources are correctly verified and click Next.






In the Select Optional Configuration screen, select the following:



Managed Servers, Clusters, and Machines
JMS Distributed Destinations
Deployments and Services
JMS File Store


Click Next.





In the Select JMS Distributed Destination Type screen leave the pre-existing JMS System Resources as they are and Select UDD from the drop down list for WseeJMSMOdule and JmsResources.
Click Next





In the Configure Managed Servers screen, add the required managed servers for Oracle Service Bus.

Select the automatically created server and click Rename to change the name to wls_osb1.

Click Add to add another new server and enter wls_osb2 as the server name.

Click Next.







In the Configure Clusters screen, add the Oracle Service Bus cluster







In the assign servers to clusters screen, assign servers to clusters as follows:

soa_cluster - if you are extending a soa domain.



wls_soa1
wls_soa2


wsm-pm_cluster:



wls_wsm1
wls_wsm2


osb_cluster:



wls_osb1
wls_osb2


click Next.







In the Assign Servers to Machines screen, assign servers to machines as follows:

ADMINHOST:

AdminServer

SOAHOST1

WLS_SOA1 (if extending a SOA domain)

WLS_WSM1

WLS_OSB1

SOAHOST2:

WLS_SOA2 (if extending a SOA domain)

WLS_WSM2

WLS_OSB2

Click Next.








In the Target Deployments to Clusters or Servers screen, ensure the following targets

Target usermessagingserver and usermessagingdriver-email only to SOA_Cluster. (The usermessaging-xmpp, usermessaging-smpp, and usermessaging-voicexml applications are optional.)
Target the oracle.sdp.*, and oracle.soa.* libraries only to SOA_Cluster.
Target the oracle.rules.* library only to AdminServer and SOA_Cluster.
Target the wsm-pm application only to WSM-PM_Cluster.
Target all Transport Provider Deployments to both the OSB_Cluster and the AdminServer.

Target this library to the SOA_Cluster also only if you are planning to deploy WebLogic WebServices to it.

Click Next.





In the Target Services to Clusters or Servers screen:
Target mds-owsm only to WSM-PM_Cluster and AdminServer.
Target mds-soa only to SOA_Cluster.

Click Next.






Enter the shared directory location specified for your JMS stores 





In the Configuration Summary screen click Extend.









Propagating the Domain Configuration to the Managed Server Directory in SOAHOST1 and to SOAHOST2

Run the pack command on SOAHOST1 to create a template pack:

cd ORACLE_COMMON_HOME/common/bin
./pack.sh -managed=true -domain=ORACLE_BASE/admin/
domain_name/aserver/domain_name -template=soadomaintemplateExtOSB.jar
 -template_name=soa_domain_templateExtOSB


Run the unpack command on SOAHOST1 to unpack the propagated template to the domain directory of the managed server:

./unpack.sh -domain=ORACLE_BASE/admin/domain_name/mserver/domain_name
-overwrite_domain=true -template=soadomaintemplateExtOSB.jar 
-app_dir=ORACLE_BASE/admin/domain_name/mserver/applications