Loading cover... Drag cover to reposition
Matt Royalfield

Matt Royalfield

  Registered Users
Newbie
Timeline
About
Friends
Videos
Followers

Oracle SOA/BPM Suite 11.1.1.7 HA, EDG-based installation - Part II

Oracle Fusion Middleware DBA
Comments
Oracle SOA/BPM Suite 11.1.1.7 HA, EDG-based installation - Part II

This is the second and last part of the posts regarding the installation of a EDG-based SOA HA installation. The first part handled the configuration of the environment, this post will explain how to correctly configure the WebLogic domain, and the SOA applications for a highly available setup.

SOA Domain Configuration

1. Create Domain

  • Connect to a GUI desktop on server testserver1
  • Execute $SOA_HOME/common/bin/config.sh 
  • Select "Create a new WebLogic Domain"
  • Select products to configure:
    1. Oracle BPM Suite
    2. Oracle SOA Suite
    3. Oracle Enterprise Manager
    4. Oracle Business Activity Monitoring
    5. Oracle WSM Policy Manager
    6. Oracle JRF

select domain source

2. Define domain name, domain location and application location

    1. Domain name: soa_domain
    2. Domain Location: /opt/11.1.1.7/admin/domains/soa_domain/aserver/
    3. Application Location: /opt/11.1.1.7/admin/domains/soa_domain/aserver/applications

 define domain loc

  1. Define WebLogic user password 
  2. Select WebLogic Startup Mode. Choose "Production mode"
  3. Configure JDBC Component Schemas. You should carefuly fill this information with the name of the schemas created with RCU and the database connection information. After filling this page out, there will be connection testing of all datasources, every test should finish with a green mark and a "Succesful" message. For common fields as Vendor, Driver, Service, Host Name and Port, select all schemas at the same time and modify the fields on the top only once

datasource config

3. Select optional configuration steps:

    1. Administration Server
    2. Managed Servers, Clusters and Machines
    3. Deployment and services
    4. JMS File Store

4. Configure the Administration Server

    1. Name: AdminServer
    2. Listen Address: adminsoa-prod.mydom.com
    3. Listen Port: 7001

5. Configure Managed Servers.

On this step, is necessary to change the names of the managed servers already defined by the installer, and then create new ones for the second node of the cluster.

config mserver1

Change bam_server1 name to WLS_BAM1, and soa_server1 to WLS_SOA1.
Then, create 4 extra managed servers, the final list should look like this:

config mserver2

 Please note that servers BAM1/SOA1/SOA2 listen on specially created VIPs, while WSM1/WSM2/BAM2 listen on hosts addresses.  

6. Configure Clusters.

  • Create the following clusters (all should use unicast communication): 
    1. SOA_CLUSTER (add cluster address: soaprod-vip1.mydom.com,soaprod-vip2.mydom.com)
    2. BAM_CLUSTER
    3. WSM_CLUSTER  

7. Assign Servers to Clusters: 

    1. SOA_CLUSTER: WLS_SOA1/WLS_SOA2
    2. BAM_CLUSTER: WLS_BAM1/WLS_BAM2
    3. WSM_CLUSTER: WLS_WSM1/WLS_WSM2

8. Configure Machines.

Create 2 unix machines, listening on the default address and port

    1. testserver1.mydom.com/5556
    2. testserver2.mydom.com/5556

9. Assign Servers to Machines:

    1. testserver1.mydom.com: AdminServer/WLS_SOA1/WLS_WSM1/WLS_BAM1
    2. testserver2.mydom.com: WLS_SOA2/WLS_WSM2/WLS_BAM2

10. Target Deployments to Cluster or Servers:

    1. Select SOA_CLUSTER
      1. Unselect application WSM-PM
    2. Select BAM_CLUSTER
      1. Unselect application WSM-PM
    3. Select WSM_CLUSTER
      1. Select application WSM-PM
      2. Select DMS application
    4. Select AdminServer
      1. Unselect all oracle.soa.* libraries
      2. Unselect all oracle.sdp.* libraries

target deployments

11. Target Services to Clusters or Servers:

    1. Select SOA_CLUSTER
      1. Unselect JDBC resource mds-owsm
    2. Select BAM_CLUSTER
      1. Unselect JDBC resource mds-owsm
    3. Select WSM_CLUSTER
      1. Select JDBC resource mdw-owsm

target services

12. Configure JMS File Store.

Complete the Directory field according to the following table:

Name

Directory

PS6SOAJMSFileStore_Auto_1

/opt/11.1.1.7/admin/domains/soa_domain/aserver/SOA_CLUSTER/jms

PS6SOAJMSFileStore_Auto_1

/opt/11.1.1.7/admin/domains/soa_domain/aserver/SOA_CLUSTER/jms

UMSJMSFileStore_auto_1

/opt/11.1.1.7/admin/domains/soa_domain/aserver/SOA_CLUSTER/jms

UMSJMSFileStore_auto_2

/opt/11.1.1.7/admin/domains/soa_domain/aserver/SOA_CLUSTER/jms

UMSJMSFileStore_auto_3

/opt/11.1.1.7/admin/domains/soa_domain/aserver/BAM_CLUSTER/jms

UMSJMSFileStore_auto_4

/opt/11.1.1.7/admin/domains/soa_domain/aserver/BAM_CLUSTER/jms

BPMJMSFileStore_auto_1

/opt/11.1.1.7/admin/domains/soa_domain/aserver/SOA_CLUSTER/jms

BPMJMSFileStore_auto_2

/opt/11.1.1.7/admin/domains/soa_domain/aserver/SOA_CLUSTER/jms

SOAJMSFileStore_auto_1

/opt/11.1.1.7/admin/domains/soa_domain/aserver/SOA_CLUSTER/jms

SOAJMSFileStore_auto_2

/opt/11.1.1.7/admin/domains/soa_domain/aserver/SOA_CLUSTER/jms

AGJMSFileStore_auto_1

/opt/11.1.1.7/admin/domains/soa_domain/aserver/SOA_CLUSTER/jms

AGJMSFileStore_auto_2

/opt/11.1.1.7/admin/domains/soa_domain/aserver/SOA_CLUSTER/jms

13. Create domain summary

create dom

 

14.  Create boot.properties File

  1. Login to testserver1 as oracle
  2. Change directory to /opt/11.1.1.7/admin/domains/soa_domain/aserver/soa_domain
  3. Create AdminServer's security directory, then create boot.properties file with the username and password selected during domain creation

mkdir -p servers/AdminServer/security

vi servers/AdminServer/security/boot.properties

username=weblogic
password=xxxxxx


There should be no spaces after username or password and no new lines after or before those two.

15. Start AdminServer VIP

  1. Login to testserver1 as oracle
  2. Change directory to /home/oracle/scripts
  3. Execute script adminVipUp.sh

16. Start AdminServer

  1. Login to testserver1 as oracle
  2. Change directory to /opt/11.1.1.7/admin/domains/soa_domain/aserver/soa_domain
  3. Execute script startWeblogic.sh. The AdminServer will be executing in the console session, do not close the console or press crtl+c until instructed to power down the AdminServer 

17. Configure NodeManager Credentials

  1. Login to WebLogic Administration Console on http://adminsoa-prod.mydom.com:7001/console
  2. Go to "soa_domain" on "Domain Structure", then go to the tab "Security", subtab "General", then "Advanced"
  3. Click on "Change Center" , button "Lock and Edit".
  4. Define NodeManager user as "weblogic", use the same password defined during the domain creation.
  5. Save and then Activate changes.nodemCred

 

nodemCred2 

 

18. Apply JRF Template to WSM_CLUSTER

  1. Login to Fusion Middleware Enterprise manager on http://adminsoa-prod.mydom.com:7001/em
  2. Expand "Weblogic Domain", then expand "soa_domain" and click "WSM_CLUSTER"
  3. Click "Apply JRF Template" on the right panel

19. Stop AdminServer

Cancel the process running on the console using ctrl+c or stop the server from the AdminServer Console.

20. Edit setDomainEnv.sh

  1. Login to testserver1 as oracle
  2. Change directory to /opt/11.1.1.7/admin/domains/soa_domain/aserver/soa_domain/bin
  3. Edit the file setDomainEnv.sh with a text editor, find the following line 

EXTRA_JAVA_PROPERTIES="${EXTRA_JAVA_PROPERTIES} -Dsoa.archives.dir=${SOA_ORACLE_HOME}/soa -Dsoa.oracle.home=${SOA_ORACLE_HOME} -Dsoa.instance.home=${DOMAIN_HOME} -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=${WL_HOME}/server/lib/DemoTrust.jks"

Replace the highlighted text with:

EXTRA_JAVA_PROPERTIES="${EXTRA_JAVA_PROPERTIES} -Dsoa.archives.dir=${SOA_ORACLE_HOME}/soa -Dsoa.oracle.home=${SOA_ORACLE_HOME} -Dsoa.instance.home=${DOMAIN_HOME} -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=/opt/11.1.1.7/admin/domains/soa_domain/aserver/certs/appTrustKeyStore.jks"

 

21. Import Front End Certificate Authority SSL Certificate to the Java Trust Keystore

  1. Obtain the certificate from the CA that signed the SOA front end url certificate. 
  2. Login to testserver1 as oracle
  3. Execute "keytool" command to import the certificate to the trusted keystore: 


keytool -import -trustcacerts -keystore /opt/11.1.1.7/admin/domains/soa_domain/aserver/certs/appTrustKeyStore.jks -storepass ******* -file /home/oracle/verisign.cer -alias soa.mydom.com

Certificate was added to keystore

Note: If the signing CA is an intermediate authority, you will need to make one file containing both base64 certificates concatenated. 

22. Start NodeManager

  1. Login to testserver1 as oracle
  2. Change directory to /home/oracle/scripts
  3. Execute script startNodeManager.sh
  4. Login to testserver2 as oracle
  5. Change directory to /home/oracle/scripts
  6. Execute script startNodeManager.sh

23. Start AdminServer

  1. Login to testserver1 as oracle 
  2. Change directory to /home/oracle/scripts
  3. Execute script startWeblogic.sh

24. Create and Execute soaScript.py

This script automates several tasks described in the SOA Enteprise Deployment Guide needed to prepare the environment for the SOA installation. Before executing the script, you should read it carefully and update the required variables according to the environment.

 It performs the following actions:

  1. Enables Weblogic Plugin option on the domain

  2. Creates leasing datasource

  3. Sets root , stage and upload directory for AdminServer and all managed servers

  4. Sets SSL Identity and trust for AdminServer an all managed servers

  5. Sets replication groups for managed servers

  6. Enables auto migration for SOA and BAM servers

  7. Sets Transanction logs directory for all managed servers

  8. Sets Front end host for SOA

25. Next step:

  1. Login to first server as oracle.
  2. Create the script soaScript.py using file soaScriptPy.docx
  3. Execute the script using WLST:

 $SOA_HOME/common/bin/wlst.sh soaScript.py

26. Configure OHS Instance on Host testserver1

  1. Login to a GUI console on testserver1

  2. Execute $WTIER_HOME/bin/config.sh

  3. In the Welcome screen, click next
  4. Configure Components: select "HTTP Server" and "Associate Selected Components with WebLogic Domain"
  5. Specify Component Details: 
    1. Instance Home Location: /opt/11.1.1.7/admin/instances/instance1
    2. Instance Name: instance1
    3. OHS Component Name: ohs1
  6. Configure Ports: Leave "Auto Port Configuration". If there is no other process using it, the configuration utility will create the OHS Process listening on port 7777
  7. Specify Security Updates: unselect option "I wish to receive security updates via My Oracle Support"
  8. Create instance.
  9. Copy files soa_vh80.conf and soa_vh443.conf created with soaScript.sh to the OHS instance module configuration directory: "/opt/11.1.1.7/admin/instances/instance1/config/OHS/ohs1/moduleconf". Then, restart OHS server.

cp /home/oracle/soa_vh* /opt/11.1.1.7/admin/instances/instance1/config/OHS/ohs1/moduleconf
/opt/11.1.1.7/admin/instances/instance1 opmnctl restartproc process-type=OHS

27. Configure OHS Instance on Host testserver2

Repeat the steps of the previous section on the server testserver2. Change "Instance Home" and "Instance Name" for "instance2", and "OHS Component Name" to "ohs2.

28. Configure Load Balancer

At this point, the Load Balancer should be configured to balance requests between servers. All request should be received in the url http://soa.mydom.com, and should be balanced to http://testserver1.mydom.com:7777/ and http://testserver2.mydom.com:7777/, the OHS servers will take care of the doing the proxy work to the correct managed servers.

Create Managed Server Template 

  1. Login to testserver1 as oracle
  2. Execute pack.sh with the following command:

/opt/11.1.1.7/middleware/wlserver_10.3/common/bin/pack.sh -managed=true -domain=/opt/11.1.1.7/admin/domains/soa_domain/aserver/soa_domain -template=/opt/11.1.1.7/admin/domains/soa_domain/aserver/soaDomainTemplateI.jar  -template_name=DomainTemplate_Managed

29. Unpack Managed Server Template on Host testserver1

  1. Login to testserver1 as oracle
  2. Execute unpack.sh with the following command:  

/opt/11.1.1.7/middleware/wlserver_10.3/common/bin/unpack.sh -overwrite_domain=true -domain=/opt/11.1.1.7/admin/domains/soa_domain/mserver/soa_domain -template=/opt/11.1.1.7/admin/domains/soa_domain/aserver/soaDomainTemplateI.jar -app_dir=/opt/11.1.1.7/admin/domains/soa_domain/mserver/applications

30. Unpack Managed Server Template on Host testserver2

  1. Login to testserver2 as oracle
  2. Execute unpack.sh with the following command:  

/opt/11.1.1.7/middleware/wlserver_10.3/common/bin/unpack.sh -overwrite_domain=true -domain=/opt/11.1.1.7/admin/domains/soa_domain/mserver/soa_domain -template=/opt/11.1.1.7/admin/domains/soa_domain/aserver/soaDomainTemplateI.jar -app_dir=/opt/11.1.1.7/admin/domains/soa_domain/mserver/applications

31. Configure Java Object Cache for WSM_CLUSTER

  1. Login to testserver1 as oracle
  2. Change directory to /opt/11.1.1.7/middleware/oracle_common/common/bin
  3. Execute wlst.sh, then connect to the domain, and then execute configure-joc.py:

./wlst.sh

wls:/offline> connect('weblogic','xxxxxx','t3://adminsoa-prod.mydom.com:7001')
Connecting to t3://adminsoa-prod.mydom.com:7001 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'soa_domain'.

wls:/soa_domain/serverConfig>execfile('/opt/11.1.1.7/middleware /oracle_common/bin/configure-joc.py')

Enter Hostnames (eg host1,host2) : testserver1.com,testserver2.com
.
Do you want to specify a cluster name (y/n) y
.
Enter Cluster Name : WSM_CLUSTER
.
Enter Discover Port : 9991
.
Enter Distribute Mode (true|false) : true
.
Do you want to exclude any server(s) from JOC configuration (y/n) n

32. Change BAM Application Targets

  1. Login to WebLogic Administration Console on http://adminsoa-prod.mydom.com:7001/console
  2. Go to "Deployments" on the "Domain Structure" frame.
  3. Click on application "oracle-bam"
  4. Go to "Targets" tab. Click button "Lock & Edit"
  5. Select the following sub-deployments:
    • /oracle/bam
    • Oracle-bam-adc-ejb.jar
    • Oracle-bam-ems-ejb.jar
    • Oracle-bam-eventengine-ejb.jar
    • Oracle-bam-reportcache-ejb.jar
    • Oracle-bam-statuslistener-ejb.jar
    • sdpmessagingclient-ejb.jar
  6. Click button "Change Targets", select only WLS_BAM1 as target and save.
  7. Select the following subdeployments
    • OracleBAM
    • OracleBAMWS
  8. Click button "Change Targets", select BAM_CLUSTER as target and save. Activate changes.

 Bamtargets

 

33. Start All Managed Servers

  1. Login to WebLogic Administration Console on http://adminsoa-prod.mydom.com:7001/console
  2. Go to "Environment", "Servers", the "Control" tab.
  3. Select all managed servers and click "Start"
  4. After several minutes, refresh the page, the state of all servers should be "RUNNING", otherwise, check the logs to find the errors.

33. Copy system-jazn-data.xml File to aserver Directory

After starting all managed servers for the first time, the system-jazn-data.xml  file in the managed server domain home  is updated to include grants for all SOA Applications. This file should be copied to the AdminServer domain home before restarting any server again, because the Managed Servers obtain their copies of configuration files from the AdminServer, and the updated file could be lost.

  1. Login to testserver1 as oracle
  2. Copy the system-jazn-data.xml file on the mserver domain home to the aserver domain home:

cp /opt/11.1.1.7/admin/domains/soa_domain/mserver/soa_domain/config/fmwconfig/system-jazn-data.xml /opt/11.1.1.7/admin/domains/soa_domain/aserver/soa_domain/config/fmwconfig/system-jazn-data.xml

34. Change OPSS Store to Database

This procedure migrates the Oracle Platform Services Store from file (system-jazn-data.xml and cwallet.sso) to inside the Oracle metadata repository created for the installation. It is needed to make sure the problems described in the previous section do no reoccur. You can check the entire explanation here: http://fusionsecurity.blogspot.com.ar/2011/10/reassociation-business.html#more

  1. Create OPSS schema with RCU
  2. Create a datasource from WebLogic Administration Console, pointing to the OPSS schema created in the previous section. It should be targeted to all managed servers a Non-XA driver with support for global transactions
  3. Login to Enterprise Manager, go to WebLogic Domain > Security Provider > Configuration > Configure Security Stores
  4. Select "Oracle Database" as store type. Enter the JNDI name of the datasource on "Data Source Details"
  5. On "Root Node Details" enter "cn=SecurityStore" in "Root DN" and "soa_domain" in "Domain Name"
  6. Accept changes

35. Configure SOA Front End Server Name

  1. Login to Fusion Middleware Enterprise Manager on http://adminsoa-prod.mydom.com:7001/em
  2. Expand "Farm_soa_domain"
  3. Expand "SOA"
  4. Select "soa-infra(WLS_SOA1)
  5. On the right pane, select the drop-down menu "SOA Infrastructure", then click on "SOA Administration" and then "Common Properties"
  6. On the "Server URLs" section, complete the blank fields:
  7. Click "Apply"

 

soaServerUrl1

36. Configure BAM Server Front End Server Name

  1. Login to Fusion Middleware Enterprise Manager on http://adminsoa-prod.mydom.com:7001/em
  2. Expand "Farm_soa_domain"
  3. Expand "BAM"
  4. Select "OracleBAMServer(WLS_BAM1)
  5. On the right pane, select the drop-down menu "BAM Server", then click on "BAM Server Properties" . Complete the field "Application URL" with "soa.mydom.com", and click "Apply"

BamServer

 37. Configure BAM Web Front End Server Name

  1. Login to Fusion Middleware Enterprise Manager on http://adminsoa-prod.mydom.com:7001/em
  2. Expand "Farm_soa_domain"
  3. Expand "BAM"
  4. Select "OracleBAMWeb(WLS_BAM1)
  5. On the right pane, select the drop-down menu "BAM Web", then click on "BAM Web Properties"
  6. Complete the blank fields:
  7. Click "Apply". 
  8. Repeat steps 4 to 7 with "OracleBAMWeb(WLS_BAM2)
  9. On the BAM Web drop down menu, select “System MBean Browser”
  10. Expand the “Application Defined MBeans” branch, then “oracle.bam.web”, “Server: WLS_BAM1, “Application: oracle-bam”, “Config”, “BAMWebConfig”
  11. Change the value of the property "ServerPort" to 9001. Click Apply

 BamWeb

bamport 

38. Configure Resource Adapters for HA

In order to use the resource adapters in the SOA infrastructure, most of them have to be modified after installation using deployment plans, and then redeployed. This is usually done from the Administration Console. In an HA environment, the deployment plan must be accesible from all nodes during redeployment, so it's necessary to place them on the shared disk.

It's a good practice to modify the adapters for the first time in order to create the deployment plan in the shared directory before the developers start working on it, cause they might not be aware of the architecture and could face problems when placing it in a local directory. In the following example, the file adapter is modified to have the control directory in the shared disk (this is also mandatory):

  1. Login to WebLogic Administration Console in http://adminsoa-prod.mydom.com:7001/console
  2. Go to "Deployments" on the "Domain Structure" frame
  3. Click on application "FileAdapter" 
  4. Go to "Configuration" tab, "Outbound Connection Pools" subtab, and expand "javax.resource.cci.ConnectionFactory" click on "eis/HAFileAdapter"
  5. Click "Lock & Edit" button, click on the "Property Value" cell of the property "controlDir". Enter the directory "/opt/11.1.1.7/admin/domains/soa_domain/aserver/SOA_CLUSTER/fileadapter". Press "enter"
  6. Save the changes. Define the deployment plan on the shared directory: /opt/11.1.1.7/admin/domains/soa_domain/aserver/SOA_CLUSTER/dp/FileAdapterPlan.xml
  7. Click "Ok" and activate changes.

 

fadaptaer1

fadapter2

fadapter3

 

39. Configure Security Providers Virtualization

  1. Login to Fusion Middleware Enterprise Manager in http://adminsoa-prod.mydom.com:7001/em
  2. Expand "Farm_soa_domain". Expand "WebLogic Domain", select "soa_domain"
  3. On the drop-down menu on the right select "Security", then "Security Provider Configuration"
  4. Expand "Identity Store Provider". Click "Configure"
  5. Click "Add" button, fill the blank fields:
    • Property Name: virtualize
    • Value: true
  6. Click "Ok" to save the settings.

virtualize

40. Restart All Managed Servers

Using the Administration Console, restart all managed servers.

 

Disclaimer - Views expressed in this blog are author's own and do not necessarily represents the policies of aclnz.com

 

Tweet
Tags:
Oracle Fusion Middleware
Module Overloading in Oracle PL/SQL
Oracle Fusion Applications 11.1.9.2 Released

Related Posts