Installing Oracle Service Bus

Oracle Service Bus is installed on shared storage. To install Oracle Service Bus, follow these steps:

  1. On SOAHOST1, start the OSB installer:
    source envMidTier.sh
$JAVA_HOME/bin/java -d64 -jar $SOFTWARE_DIR/fmw_12.1.3.0.0_osb.jar
  2. In the Inventory Directory field, enter /u01/share/oracle/oraInventory and then click on OK.
  3. Click on Next.
  4. In the Oracle Home field, enter the value for [ORACLE_HOME] (for example, /u01/share/oracle/middleware/products/fmw1213) and then click on Next.
  5. Select Service Bus and click on Next.
  6. Click on Next.
  7. Click on Install.
  8. Click on Finish once the installation is done.

Extending the domain to include Oracle Service Bus

On Oracle Service Bus, in order to extend the domain, follow these steps:

  1. On SOAHOST1, stop the Admin Server:
    source envMidTier.sh
$ASERVER_HOME/bin/stopWebLogic.sh
  2. Start the WebLogic Server Configuration Wizard:
    cd $ORACLE_HOME/oracle_common/common/bin
./config.sh
  3. Click on Update an existing domain.
  4. In the Domain Location field, enter the value for [ASERVER_HOME] (for example, /u01/share/oracle/middleware/config/domains/soa_domain).
  5. Click on Next.
  6. Check Oracle Service Bus - 12.1.3.0 [osb] and then click on Next.
  7. Click on Get RCU Configuration.
  8. Click on Next.
  9. Click on Next.
  10. Click on Next.
  11. Check Managed Servers, Clusters and Coherence, and JMS File Store and then click on Next.
  12. Rename osb_server1 as wls_osb1.
  13. Change Listen Address to soahost1.packt.com.
  14. Change port 7003 to 8011.
  15. Under Server Groups, select only OSB-MGD-SVRS-ONLY.
  16. Click on Add and then enter wls_soa2, soahost2.packt.com, 8011, and then select only OSB-MGD-SVRS-ONLY.
  17. Click on Next.
  18. Click on Add.
  19. For Cluster Name, enter OSB_Cluster.
  20. For Frontend Host, enter osb.packt.com.
  21. For Frontend HTTP Port, enter 7777.
  22. For Frontend HTTPS Port, enter 4443.
  23. Click on Next.
  24. Assign wls_osb1 and wls_osb2 to OSB_Cluster and then click on Next.
  25. Click on Next.
  26. Click on Next.
  27. Assign wls_osb1 to the soahost1 machine.
  28. Assign wls_osb2 to the 4443 machine.
  29. Click on Next.
  30. Assign the [ASERVER_HOME]/OSB_Cluster/jms directory (for example, /u01/share/oracle/middleware/config/domains/soa_domain/OSB_Cluster/jms) for the WsseFileStore and FileStore.
  31. Click on Next all WsseFileStores and FileStores.
  32. Click on Update.
  33. Click on Next.
  34. Click on Finish.

Configuring the default persistence store for transaction recovery

Follow these steps to configure the default persistence store:

  1. On SOAHOST1, start the Admin Server:
    source envMidTier.sh
cd $ASERVER_HOME/servers/AdminServer/logs
nohup $ASERVER_HOME/bin/startWebLogic.sh > AdminServer.out &
  2. Navigate to http://admin.packt.com:7001/console.
  3. Log in as the weblogic user.
  4. Navigate to soa_domain | Environment | servers | wls_osb1 | Configuration | Services.
  5. In the Directory field, enter [ASERVER_HOME]/OSB_Cluster/tlogs (for example, /u01/share/oracle/middleware/config/domains/soa_domain/OSB_Cluster/tlogs).
  6. Click on Save.
  7. Repeat steps 4 to 6 for wls_osb2.
  8. Shut down the wls_wsm1 and wls_wsm2 managed servers.
  9. Shutdown the wls_soa1 and wls_soa2 managed servers.
  10. Activate the changes.
  11. Start up the wls_wsm1 and wls_wsm2 managed servers.
  12. Start up the wls_soa1 and wls_soa2 managed servers.

Propagating the domain to the domain directories and machines

Use these steps to propagate the domain to domain directories and machines:

  1. On SOAHOST1, pack and unpack the domain:
    source envMidTier.sh
cd $ORACLE_COMMON_HOME/common/bin

./pack.sh -managed=true -domain=${ASERVER_HOME} -template=soadomaintemplateExtOSB.jar -template_name=soadomaintemplateExtOSB

./unpack.sh -domain=${MSERVER_HOME} -overwrite_domain=true -template=soadomaintemplateExtOSB.jar -app_dir=${APPLICATION_HOME}
  2. On SOAHOST2, unpack the domain:
    source envMidTier.sh
cd $ORACLE_COMMON_HOME/common/bin

./unpack.sh -domain=[MSERVER_HOME] -overwrite_domain=true -template=soadomaintemplateExtOSB.jar -app_dir=${APPLICATION_HOME}
  3. On SOAHOST1, start the OSB managed server:
    source envMidTier.sh
cd $MSERVER_HOME/servers/wls_osb1/logs

nohup $MSERVER_HOME/bin/startManagedWebLogic.sh wls_osb1 http://admin.packt.com:7001 > wls_osb1.out &
  4. On SOAHOST2, start the OSB managed server:
    source envMidTier.sh
cd $MSERVER_HOME/servers/wls_osb2/logs

nohup $MSERVER_HOME/bin/startManagedWebLogic.sh wls_osb2 http://admin.packt.com:7001 -Dweblogic.management.username=weblogic > wls_osb2.out &
  5. Validate that the following URLs are accessible:

    http://osb.packt.com:7777/

    http://osb.packt.com:7777/sbinspection.wsil

Configuring the WebLogic proxy plug-in

Follow next steps to configure the WebLogic proxy plug-in:

  1. Navigate to http://admin.packt.com:7001/console.
  2. Log in as the weblogic user.
  3. Navigate to soa_domain | Environment | Clusters | OSB_Cluster | Configuration | General | Advanced.
  4. For WebLogic Plug-In Enabled, set the value to yes.
  5. Save and activate the changes.
  6. Restart the wls_osb1 and wls_osb2 managed servers.
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.133.124.145