Install Oracle SOA Suite 12c in Cluster

Introduction

This document is a reference guide for the installation and configuration of Oracle Fusion Middleware 11g products, including Oracle Weblogic 12.1.3, Oracle WebTier 12.1.3.

The process described on this document is based on Oracle’s SOA Enterprise Deployment Guide 12.2.1

Enviroment Requirements

To follow the procedures described in this document, it is necessary to consider the following requeriments for the servers:

  • Operating System: Red Hat Enterprise Linux 6.x
  • Database: An Oracle Enterprise Edition 11.2.0.4, 12c database instance should be available for use as metadata repository.
  • Software or Hardware based load balancer available
  • A shared disk presented to all servers that run the domain

 

Environment Information

Test environment information will be used in this document to describe all procedures.

  • Hosts:
    • soa12cnodo1
    • soa12cnodo2
  • Domain Name: soadomain
  • Domain Home:
    • /opt/oracle/Middleware/admin/domains/soadomain/aserver/soadomain/
    • /opt/oracle/Middleware/admin/domains/soadomain/mserver/soadomain/
  • Java Home: /opt/oracle/jdk1.8.0_65
  • Middleware Home: /opt/oracle/Middleware/mwhome
  • Weblogic Home: /opt/oracle/Middleware/mwhome/wlserver
  • SOA_HOME: /opt/oracle/Middleware/mwhome/soa

 

Oracle Documentation

  • Oracle® Fusion Middleware Enterprise Deployment Guide for Oracle SOA Suite 12c (12.2.1)

https://docs.oracle.com/middleware/1221/core/SOEDG/index.html

Environment Configuration

This section provides instructions on how to configure the network, file system and database resources necessaries to create a FMW HA environment.

All binaries and configuration files will be installed with the operating system “SOA” and group “DBA” on this document.

 

Configure /etc/sudoers

In all servers, edit file /etc/sudoers with root user, add the following lines:

Defaults:soa !requiretty

soa ALL=NOPASSWD:/sbin/ifconfig,/sbin/arping

 

 

Configure /etc/hosts

The hosts file should be edited on all servers with the complete list of URLs and VIPs used on the environment:

127.0.0.1               localhost

 180.120.10.214          soa12cnodo2 

180.120.10.213          soa12cnodo1 

180.120.10.164          admsoa12c 

180.120.10.210          soa12cdb-ha

Check network configuration

Before starting the installation is very important to check that the network is correctly configured.

  • Start by trying to ping all IPs defined in the previous step for the environment, no response should be received as IPs should not be up yet.
  • Test bringing up IPs on both nodes. Use the following commands with the user SOA:

 

sudo ifconfig eth0:1 180.120.10.164 netmask 255.255.255.0

sudo arping -q -U -c 3 -I eth0 180.120.10.164

 

  • Test connectivity to the IPs by trying to connect from a remote server.

 

Repository Database Requeriments

The parameters on this section are related to the Oracle database used as a metadata repository for the FMW products.

  • PROCESSES parameter equal or greater than 500
  • SESSIONS parameter equal or greater than 500
  • CHARACTER SET parameter should be AL32UTF8

 

Change Database Default Profile Password Life Time limit

By default, Oracle 11g Release 2 databases are configured with a 180-days limit for password life time, after that, the users are locked and password must be mandatory changed. As Oracle products rely on datasources passwords that are kept secret for database connections, and the availability of the application depends on these connections, is recommended to modify this limit to avoid unexpected down time due to locked users.

  1. Login to the repository instance as SYS user
  2. Execute the following commands:

 

 

SQL> select profile,limit from dba_profiles where resource_name = 'PASSWORD_LIFE_TIME';
 PROFILE                        LIMIT
 ------------------------------ ----------------------------------------
 DEFAULT                        180
 MONITORING_PROFILE             DEFAULT
 SQL>  alter profile DEFAULT limit PASSWORD_LIFE_TIME unlimited;Profile altered.SQL> select profile,limit from dba_profiles where resource_name = 'PASSWORD_LIFE_TIME';PROFILE                        LIMIT
 ------------------------------ ----------------------------------------
 DEFAULT                        UNLIMITED
 MONITORING_PROFILE             DEFAULT

Mount Shared Directory on SOA Servers

The cluster installation needs a shared directory mounted on both servers running SOA Suite. The filesystem used can be either NFS (version 4) or OCFS2 (I will user NFS). It is important that this disk or filesystem be presented from a storage solution with low latency connection to the servers.

  • For this installation the directory path chosen is:
/opt/oracle/Middleware/admin/domains/soadomain/aserver

 

  • Edit file /etc/exports and add the following lines on soa12cnodo1
/opt/oracle/Middleware/admin/domains/soadomain/aserver           180.120.10.214(rw,no_root_squash)
  • In case you don’t have nfs installed execute the following command
yum install nfs-utils nfs4-acl-tools portmap
  • Restart nfs services in all nodes
/etc/init.d/nfs restart
  • Mount the shared directory on soa12cnodo2
mount -t nfs4 180.120.10.213:/opt/oracle/Middleware/admin/domains/domain_test/aserver /opt/oracle/Middleware/admin/domains/domain_test/aserver

Binaries Installation and Environment Preparation

 

Oracle Fusion Middleware 12c Binaries Installation

Install Oracle software in the order established below (this must be made in both servers).

 

  1. Oracle Java JDK

Refer to Oracle Installation Guide on:

http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html

 

  1. Oracle Fusion Middleware Infrastructure
    Refer to Oracle Installation Guide on:
    https://docs.oracle.com/middleware/1221/core/SOEDG/index.html

    1. Create file infra.rsp: (THIS IS IN CASE WE WANT TO DO A SILENT INSTALL, BUT WE WILL NOT USE IT)
[ENGINE]
 #DO NOT CHANGE THIS.
 Response File Version=1.0.0.0.0
 [GENERIC]
 #The oracle home location. This can be an existing Oracle Home or a new Oracle Home
 ORACLE_HOME=/opt/oracle/Middleware/mwhome/
 #Set this variable value to the Installation Type selected. e.g. Fusion Middleware Infrastructure, Fusion Middleware Infrastructure With Examples.
 INSTALL_TYPE=Fusion Middleware Infrastructure
  1. Execute the installer in silent mode:
[oracle@soa12cnodo1 ~]$ /opt/oracle/jdk1.8.0_65/bin/java -jar fmw_12.2.1.0.0_infrastructure.jar -silent -responseFile /home/soa/Downloads/infra.rsp
  1. OR Execute the installer in normal:
[oracle@soa12cnodo1 ~]$ /opt/oracle/jdk1.8.0_65/bin/java -jar fmw_12.2.1.0.0_infrastructure.jar
  1. Oracle Weblogic Webtier 12.2.1
    Refer to Oracle Installation Guide on:
    https://docs.oracle.com/middleware/1221/core/WLSIG/toc.htm

    1. Create file ohs.rsp:

 

[ENGINE]
 #DO NOT CHANGE THIS.
 Response File Version=1.0.0.0.0
 [GENERIC]
 #The oracle home location. This can be an existing Oracle Home or a new Oracle Home
 ORACLE_HOME=/opt/oracle/Middleware/mwhome/
 #Set this variable value to the Installation Type selected. e.g. Fusion Middleware Infrastructure, Fusion Middleware Infrastructure With Examples.
 INSTALL_TYPE=Collocated HTTP Server (Managed through WebLogic server)
  1. Execute the installer in silent mode:
[oracle@soa12cnodo1 ~]$./fmw_12.2.1.0.0_ohs_linux64.bin -silent -responseFile /home/soa/Downloads/ohs.rsp
  1. OR Execute the installer in normal:
[oracle@soa12cnodo1 ~]$ ~]$./fmw_12.2.1.0.0_ohs_linux64.bin
  1. Oracle Oracle SOA Suite12.2.1
    Refer to Oracle Installation Guide on:
    http://docs.oracle.com/cd/E28280_01/install.1111/e13925/install_screens.htm#INSOA154
  2. Execute the installer in normal:
[oracle@soa12cnodo1 ~]$ /opt/oracle/jdk1.8.0_65/bin/java –jar fmw_12.2.1.0.0_soa.jar

Metadata Repository Schemas Creation

Before starting the creation of Weblogic Domains and configuration of the applications deployed there, it’s necessary to create the metadata repository using Oracle’s Repository Creation Utility:

  1. Login with ssh to the server soa12cnodo1
  2. Start RCU GUI by executing the file “/opt/oracle/Middleware/mwhome/oracle_common/bin/rcu”
  3. Press “Next” on the Welcome screen
  4. Select “System Load and Product Load”
  5. Type the database connection information:
    1. Database Type: selectOracle Database.
    2. Host Name: Type database hostname
    3. Port: Type database listener port.
    4. Service Name: Type database service name
    5. Username: SYS
    6. Password
    7. Role: SYSDBA
  6. Select components.
    1. Select “Create new prefix”. Use a descriptive prefix, in this case “PROD”
    2. Select the following components
      • SOA Suite. All dependencies will be automatically selected.
    3. Define Schemas Password. Select “Use same password for all schemas”, type password
    4. Specifying Custom Variables. Leave default options
    5. End of repository creation

 

 

Create and execute soaScript.sh

This script automates several tasks described in the SOA Enteprise Deployment Guide needed to prepare the environment for the SOA installation.

soaScript.sh

It performs the following actions:

  • Creates Linux aliases for ease of administration
  • Creates Weblogic domain administration scripts
  • Creates directory structure necessary for the Weblogic Domain.
  • Creates private & public ssl keys and certificates used by Weblogic Server for inter process communication.

 

  1. Login to first server (soa12cnodo1) as oracle user.
  2. Create osbScript.sh file and grant execute permissions to it.
  3. Execute script.
  4. Login to second server (soa12cnodo2) as oracle user
  5. Copy directory scripts_12c from soa12cnodo1 with scp

SOA Domain Configuration

   Create SOADOMAIN

 

  1. Connect to a GUI desktop on server cawlkl10.
  2. Execute de following script $ORACLE_HOME/oracle_common/bin/config.sh
/opt/oracle/Middleware/mwhome/oracle_common/common/bin/config.sh
  1. Select “Create a new WebLogic Domain”
Domain Location: /opt/oracle/Middleware/admin/domains/soadomain/aserver/soadomain

  1. Select products to configure:

Products:

  • Oracle SOA Suite
  • Oracle Enterprise Manager
  • Oracle WSM Policy Manager
  • Oracle JRF
  • Oracle HTTP Server (Collocated)

 

11

  1. Define application location:
  • Application location: /opt/oracle/Middleware/admin/domains/soadomain/aserver/soadoman/applications
  1. Define Weblogic user password.
  1. Select Domain mode. Choose “Production Mode”, select default JDK.
  1. Database Configuration Type. Select “RCU Data” option. Then complete the following fields:
  • Vendor: oracle
  • Driver: Oracle’s Driver (Thin) for Service connections, Version 9.0.1
  • DBMS/Service: Database Service name, i.e. TESTSOA
  • Host Name: Database host, i.e. 180.120.10.210
  • Port: Database listener port, i.e. 1521
  • Schema Owner: PROD_STB
  • Schema Password: Password chosen during RCU execution.

 

Click on “Get RCU Configuration” Click “Next”.

2

  1. Component Datasource. Leave the data as completed by the assistant. Click “Next”.
  2. JDBC Test. Make sure all tests end up correctly.
  3. Advanced Configuration. Select all boxes.

3

  1. Configure Administration Server
    • Server Name: AdminServer
    • Listen Address: 180.120.10.164
    • Listen Port: 7001
    • Server Groups: Unspecified

4

  1. Configure NodeManager. Select option “Per Domain Default Location”. Then complete credentials with user “weblogic”.

5

 

  1. 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.
  • soa_wls1/180.120.10.213/7003
  • soa_wls2/180.120.10.214/7003

For both managed servers, select the following“Server Groups”

  • JRF-MAN-SVR
  • SOA-MGD-SVRS
  • WSM-CACHE-SVR
  • WSMPM-MAN-SVR

6

 

  1. Create Clusters.
  • soa_cluster: Leave all fields blank
  1. Assign Servers to clusters:
    • soa_cluster
      1. soa_wls1
      2. soa_wls2

7

 

  1. Coherence Cluster. Leave all fields as default
  1. Configure Machines. Create 3 “Unix Machines”:
    • soa12cnodo1/180.120.10.213/5556
    • soa12cnodo2/180.120.10.214/5556
    • admsoa12c/180.120.10.164/5557

8

  1. Assign servers to Machines
    • Adminsoa12c
      1. AdminServer
    • soa12cnodo1
      1. soa_wls1
    • soa12cnodo2
      1. soa_wls2

9

  1. Configure OHS servers

10

11

  1. Configure Front end host. Deselect option.
  2. Assign System Components
  • soa12cnodo1: ohs1
  • soa12cnodo2: ohs2
  1. Deployment Targeting. Leave default configuration. Click “Next”.
  2. Services Targeting. Leave default configuration. Click “Next”.
  3. Configure JMS FileStore. Change the “Synchronous write policy” to “Direct –Write” for all Stores. Complete the Directory field according to the next :
  • /opt/oracle/Middleware/admin/domains/soadomain/aserver/WSM_CLUSTER/jms

 

12

Create boot.properties File

 

  1. Login to cawlkl10 as SOA user.
  2. Change directory to /opt/oracle/Middleware/admin/domains/soadomain/aserver/soadomain
  1. Create AdminServer’s security directory
[oracle@soa12cnodo1 ~]$ mkdir -p servers/AdminServer/security

 

  1. Create boot.properties files with username and password information used during the domain creation.
[oracle@soa12cnodo1 ~]$ vi servers/AdminServer/security/boot.properties

username=weblogic
password=xxxxxxx

 

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

 

Start AdminServer VIP

  1. Login to soa12cnodo1 as oracle user
  2. Change directory to /home/oracle/scripts12
  3. Execute script adminVipUP.sh

 

 

Start AdminServer

  1. Login to soa12cnodo1 as oracle user.
  2. Change directory to /opt/oracle/Middleware/admin/domains/soadomain/aserver/soadomain/
  1. Execute script startWeblogic.sh.

 

[oracle@soa12cnodo1 soadomain]$./startWeblogic &

 

The AdminServer process will be executing on the console session, do not close the console or press crtl+c until instructed to power down the AdminServer.

 

 

Stop AdminServer

Cancel the process running on the console by pressing crtl+c. Or login to Weblogic Administration Console and stop the server from “soadomain”, “Environment”, “Servers”, “Control”, “stop server”.

 

Execute Pack.sh

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

 

[oracle@soa12cnodo1~]$ /opt/oracle/Middleware/mwhome/oracle_common/common/bin/pack.sh -managed=true -domain=/opt/oracle/Middleware/admin/domains/soadomain/aserver/soadomain -template=soa12c.jar -template_name=soa12cDomainTemplate

 

 

Execute Unpack.sh on First Host

  1. Login to soa12cnodo1 as oracle user
  2. Execute pack.sh with the following command:
[oracle@soa12cnodo1 ~]$ /opt/oracle/Middleware/mwhome/oracle_common/common/bin/unpack.sh   -domain=/opt/oracle/Middleware/admin/domains/soadomain/mserver/soadomain -overwrite_domain=true -template=/opt/oracle/Middleware/admin/domains/soadomain/aserver/soadomain/soa12c.jar -log_priority=DEBUG -log=/tmp/unpack.log -app_dir=/opt/oracle/Middleware/admin/domains/soadomain/aserver/soadoman/applications


 

 

Execute Unpack.sh on Second Host

 

  1. Login to soa12cnodo2 as oracle user
  2. Execute pack.sh with the following command:
[soa@cawlkl10 ~]$ /opt/oracle/Middleware/mwhome/oracle_common/common/bin/unpack.sh   -domain=/opt/oracle/Middleware/admin/domains/soadomain/mserver/soadomain -overwrite_domain=true -template=/opt/oracle/Middleware/admin/domains/soadomain/aserver/soadomain/soa12c.jar -log_priority=DEBUG -log=/tmp/unpack.log -app_dir=/opt/oracle/Middleware/admin/domains/soadomain/aserver/soadoman/applications

 

 

Edit AdminServer NodeManager Configuration

 

  1. Login to soa12cnodo1 as oracle user
  2. Go to directory /opt/oracle/Middleware/admin/domains/soadomain/aserver/soadomain/nodemanager
  3. Edit file nodemanager.properties, making sure that the parameter ListenAddress is equal to “adminsoa12c” o “180.120.10.164”

 

Edit Server 1 NodeManager Configuration

 

  1. Login to soa12cnodo1 as oracle user
  2. Go to directory /opt/oracle/Middleware/admin/domains/soadomain/mserver/soadomain/nodemanager
  3. Edit file nodemanager.properties, making sure that the parameter ListenAddress is equal to “soa12cnodo1” or “180.120.10.213”, and all directory parameters point to the “mserver” domain.

 

 

Edit Server 2 NodeManager Configuration

 

  1. Login to soa12cnodo2 as oracle user
  2. Go to directory /opt/oracle/Middleware/admin/domains/soadomain/mserver/soadomain/nodemanager
  3. Edit file nodemanager.properties, making sure that the parameter ListenAddress is equal to “soa12cnodo2” or “180.120.10.214”, and all directory parameters point to the “mserver” domain.

 

 

Start NodeManagers

  1. Login to soa12cnodo1 as oracle user
  2. Change directory to /home/oracle/scripts_12c
  3. Execute script startNodeManagerAdmin.sh
  4. Execute script startNodeManager.sh
  5. Login to soa12cnodo2 as oracle user
  6. Change directory to /home/oracle/scripts_12c
  7. Execute script startNodeManager.sh

 

Start AdminServer

  1. Login to soa12cnodo1 as oracle user
  2. Change directory to /home/oracle/scripts_12c
  3. Execute script startWeblogic.sh

Create and Execute soaScript2.py

This script automates several domain configuration tasks described in the SOA Enteprise Deployment Guide (this is an example script)

soaScript.py

It performs the following actions:

  • Enables Weblogic Plugin option on the domain
  • Sets root , stage and upload directory for AdminServer and all managed servers
  • Sets SSL Identity and trust for AdminServer an all managed servers
  • Sets Transanction logs directory for all managed servers

 

  1. Login to first server (soa12cnodo1) as oracle user.
  2. Create osbScript.py file
  3. Go to directory “/opt/oracle/Middleware/mwhome/wlserver/server/bin/”
  4. Execute the command “. setWLSEnv.sh”. Make sure you place the dot and a space character before “setWLSEnv.sh”
[soa@cawlkl10 ~]$ wlogic
[soa@cawlkl10 wlserver_10.3]$ . setWLSEnv.sh
CLASSPATH=/SOA/12.1.3/middleware/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/SOA/12.1.3/middleware/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/SOA/12.1.3/jrockit/lib/tools.jar:/SOA/12.1.3/middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/SOA/12.1.3/middleware/wlserver_10.3/server/lib/weblogic.jar:/SOA/12.1.3/middleware/modules/features/weblogic.server.modules_10.3.6.0.jar:/SOA/12.1.3/middleware/wlserver_10.3/server/lib/webservices.jar:/SOA/12.1.3/middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/SOA/12.1.3/middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:
PATH=/SOA/12.1.3/middleware/wlserver_10.3/server/bin:/SOA/12.1.3/middleware/modules/org.apache.ant_1.7.1/bin:/SOA/12.1.3/jrockit/jre/bin:/SOA/12.1.3/jrockit/bin:/SOA/12.1.3/jrockit/bin:/SOA/12.1.3/middleware/wlserver_10.3/common/bin:/SOA/12.1.3/middleware/wlserver_10.3/server/bin:/SOA/12.1.3/middleware/wlserver_10.3/common/nodemanager:/sbin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin

Your environment has been set.
  1. Execute script using WLST: “java weblogic.WLST /home/oracle/soaScript.py”
[soa@cawlkl10 wlserver_10.3]$ java weblogic.WLST /home/oracle/osbScript.py

 

Start All Managed Servers

  1. Login to Weblogic Administration Console on

http://180.120.10.164:7001/console

 

  1. Go to “Environment”, “Servers”, then “Control” tab
  2. Select all managed servers and click “Start”
  3. After several minutes, refresh the page, the state of all servers should be “RUNNING”, otherwise, check the logs to find the errors.

Configure OHS1

  1. Login to soa12cnodo1 as oracle user.
  2. Edit file /opt/oracle/Middleware/admin/domains/soadomain/aserver/soadomain/config/fmwconfig/components/OHS/oh1/mod_wl_ohs.conf. (and the same file for mserver path)

Add the following lines:

NameVirtualHost *:7777
<VirtualHost *:7777>
    ServerName soacluster:80
    ServerAdmin you@your.address
    RewriteEngine On
    RewriteOptions inherit
    DynamicServerList OFF 

<Location /soa-infra>
    SetHandler weblogic-handler
    WebLogicCluster soa12cnodo1:7003,soa12cnodo2:7003
</Location>

# SOA inspection.wsil

<Location /inspection.wsil>
    SetHandler weblogic-handler
    WebLogicCluster soa12cnodo1:7003,soa12cnodo2:7003
</Location>
# Worklist
<Location /integration>
    SetHandler weblogic-handler
    WebLogicCluster soa12cnodo1:7003,soa12cnodo2:7003
</Location>
# B2B

<Location /b2bconsole>
    SetHandler weblogic-handler
    WebLogicCluster soa12cnodo1:7003,soa12cnodo2:7003
</Location>
<Location /b2b/services/ws/>
    SetHandler weblogic-handler
    WebLogicCluster soa12cnodo1:7003,soa12cnodo2:7003
</Location>
# UMS prefs
<Location /sdpmessaging/userprefs-ui>
    SetHandler weblogic-handler
    WebLogicCluster soa12cnodo1:7003,soa12cnodo2:7003
</Location>
# Default to-do taskflow
<Location /DefaultToDoTaskFlow>
    SetHandler weblogic-handler
    WebLogicCluster soa12cnodo1:7003,soa12cnodo2:7003
</Location>
# Workflow
<Location /workflow>
    SetHandler weblogic-handler
    WebLogicCluster soa12cnodo1:7003,soa12cnodo2:7003
</Location>
#Required if attachments are added for workflow tasks
 <Location /ADFAttachmentHelper>
    SetHandler weblogic-handler
    WebLogicCluster soa12cnodo1:7003,soa12cnodo2:7003
 </Location>
# SOA composer application
 <Location /soa/composer>
     SetHandler weblogic-handler
     WebLogicCluster soa12cnodo1:7003,soa12cnodo2:7003
</Location>
 <Location /frevvo>
     SetHandler weblogic-handler
     WebLogicCluster soa12cnodo1:7003,soa12cnodo2:7003
</Location>
# BPM
<Location /bpm/composer>
    SetHandler weblogic-handler
    WebLogicCluster soa12cnodo1:7003,soa12cnodo2:7003
</Location>
<Location /bpm/workspace>
    SetHandler weblogic-handler
    WebLogicCluster soa12cnodo1:7003,soa12cnodo2:7003
</Location>
</VirtualHost>

Configure OHS2

  1. Login to soa12cnodo2 as oracle user.
  2. Edit file /opt/oracle/Middleware/admin/domains/soadomain/mserver/soadomain/config/fmwconfig/components/OHS/instances/oh2/mod_wl_ohs.conf.

Add the following lines:

NameVirtualHost *:7777
<VirtualHost *:7777>
    ServerName soacluster:80
    ServerAdmin you@your.address
    RewriteEngine On
    RewriteOptions inherit
    DynamicServerList OFF 
<Location /soa-infra>
    SetHandler weblogic-handler
    WebLogicCluster soa12cnodo1:7003,soa12cnodo2:7003
</Location>
# SOA inspection.wsil
<Location /inspection.wsil>
    SetHandler weblogic-handler
    WebLogicCluster soa12cnodo1:7003,soa12cnodo2:7003
</Location>
# Worklist
<Location /integration>
    SetHandler weblogic-handler
    WebLogicCluster soa12cnodo1:7003,soa12cnodo2:7003
</Location>
# B2B
<Location /b2bconsole>
    SetHandler weblogic-handler
    WebLogicCluster soa12cnodo1:7003,soa12cnodo2:7003
</Location>
<Location /b2b/services/ws/>
    SetHandler weblogic-handler
    WebLogicCluster soa12cnodo1:7003,soa12cnodo2:7003
</Location>
# UMS prefs
<Location /sdpmessaging/userprefs-ui>
    SetHandler weblogic-handler
    WebLogicCluster soa12cnodo1:7003,soa12cnodo2:7003
</Location>
# Default to-do taskflow
<Location /DefaultToDoTaskFlow>
    SetHandler weblogic-handler
    WebLogicCluster soa12cnodo1:7003,soa12cnodo2:7003
</Location>
# Workflow
<Location /workflow>
    SetHandler weblogic-handler
    WebLogicCluster soa12cnodo1:7003,soa12cnodo2:7003
</Location>
#Required if attachments are added for workflow tasks
 <Location /ADFAttachmentHelper>
    SetHandler weblogic-handler
    WebLogicCluster soa12cnodo1:7003,soa12cnodo2:7003
 </Location>
# SOA composer application
 <Location /soa/composer>
     SetHandler weblogic-handler
     WebLogicCluster soa12cnodo1:7003,soa12cnodo2:7003
</Location>
 <Location /frevvo>
     SetHandler weblogic-handler
     WebLogicCluster soa12cnodo1:7003,soa12cnodo2:7003
</Location>
# BPM
<Location /bpm/composer>
    SetHandler weblogic-handler
    WebLogicCluster soa12cnodo1:7003,soa12cnodo2:7003
</Location>
<Location /bpm/workspace>
    SetHandler weblogic-handler
    WebLogicCluster soa12cnodo1:7003,soa12cnodo2:7003
</Location>
</VirtualHost>

Restart AdminServer

  1. Login to soa12cnodo1 as oracle user
  2. Change directory to /home/oracle/scripts_12c
  3. Execute script stopWeblogic.sh
  4. Execute script startWeblogic.sh

Start OHS Servers

  1. Login to soa12cnodo1 as oracle user
  2. Change directory to /home/oracle/scripts_12c
  3. Execute script startOhs1.sh
  4. Execute script startOhs2.sh

 

 

Configure FileAdapter for HA

 

  1. First will create the following directories on shared disk:
    1. mkdir /opt/oracle/Middleware/admin/domains/soadomain/aserver/WSM_CLUSTER/adapters
    2. mkdir /opt/oracle/Middleware/admin/domains/soadomain/aserver/dp

 

  1. Login to Weblogic Administration Console on

http://180.120.10.164:7001/console

 

  1. Go to “Deployments” on the “Domain Structure” frame.
  2. Select FileAdapter application
    32
  3. Go to “Configuration” tab, “Outbound Connection Pools” subtab, and expand “javax.resource.cci.ConnectionFactory”. Click on “eis/HAFileAdapter”.
    33
  4. Click “Lock&Edit” button, click on the “Property Value” cell of the property “controlDir”. Enter the directory /opt/oracle/Middleware/admin/domains/soadomain/aserver/WSM_CLUSTER/adapters. PRESS ENTER.
    34
  5. Save the changes. Define deployment plan on the shared directory, (both servers need to be able to read it) /opt/oracle/Middleware/admin/domains/soadomain/aserver/dp/FileAdapterPlan.xml
  6. Click ok, then activate changes.

Configure DBAdapter for HA

 

  • Login to Weblogic Administration Console on

http://180.120.10.164:7001/console

 

  • Go to “Deployments” on the “Domain Structure” frame.
  • Select DBAdapter application
  • Go to “Configuration” tab, “Outbound Connection Pools” subtab, and expand “javax.resource.cci.ConnectionFactory”. Click on “eis/DB/SOADemo”.35
  • Click “Lock&Edit” button, click on the “Property Value” cell of the property “sequencePreallocationSize” and change it to 60.36
  • Save the changes. Define deployment plan on the shared directory, (both servers need to be able to read it)
    /opt/oracle/Middleware/admin/domains/soadomain/aserver/dp/DBAdapterPlan.xml

 

Configure JMSAdapter for HA

  • Login to Weblogic Administration Console on

 http://180.120.10.164:7001/em

  • Go to “Deployments” on the “Domain Structure” frame.
  • Select JMSAdapter application
  • Go to “Configuration” tab, “Outbound Connection Pools” subtab, and expand “oracle.tip.adapter.jms.IJmsConnectionFactory”. Click on “eis/wls/Queue”.
  • Click “Lock&Edit” button, click on the “Property Value” cell of the property “Username” and enter “weblogic”.
  • Save the changes. Define deployment plan on the shared directory, (both servers need to be able to read it)
  • /opt/oracle/Middleware/admin/domains/soadomain/aserver/dp/JMSAdapterPlan.xml
  • Click ok, then activate changes.

 

Configure Security Providers Virtualization

  1. Login to Fusion Middleware Enterprise Manageron

 http://180.12.10.164:7001/em

  1. Expand “Weblogic Domain”, select “soadomain”.
  2. On the drop-down menu on the right pane select “Security”, “Security Provider Configuration”
    41
  3. Expand “Identity Store Provider”. Click “Configure”42
  4. Click “Add” button. Fill the blank fields:43

Click “OK” to save the changes.

44

Test Administration Scripts

  1. Login to soa12cnodo1 as oracle user.
  2. Execute script /home/oracle/scripts_12c/stop_soa.sh to stop the domain
  3. Execute script /home/oracle/scripts_12c/start_soa.sh to start the domain.

Testing URL

  1. Go to soa12cnodo1:7777/soa-infra.
  2. Provide login as weblogic user
  3. Go to soa12cnodo2:7777/soa-infra.
  4. Provide login as weblogic user

Installing and configuring Load Balancer

  1. Log in a new server in our case will be 180.120.10.210 as oracle user
  2. Download the installer for WebCache 11.1.1.9 from OTN

      ofm_webtier_linux_11.1.1.9.0_64_disk1_1of1.zip

  1. Install it by executing runInstaller from Disk1/runInstaller
  2. Select a new directory where install the WebCache
  3. Select the only WebCache
  4. Choose instance name and component name
  5. Set Administrator password
  6. Set port configuration as “automatic”
  7. Click install
  8. Access to administrative console by the url http://180.120.10.210:7786/webcacheadmin
    username: administrator
    passwd: the one choosen on install
  9. Go to “Origin Servers” and add both servers soa12cnodo1 and soa12cnodo2
  10. Go to site definition and add a new site definition
  11. add Site to server Mapping
  12. Configure new port for Load Balancer
  13. Modify $ORACLE_HOME/Oracle_WT1/ohs/bin permissions
    chown root .apachectl
    chmod 6750 .apachectl
  14. Restart Webcache
    cd /home/oracle/Middleware2/Oracle_WT1/instances/instance1/bin
    ./opmnctl stopall
    ./opmnctl startall

  

Checking Load Balancer

  1. Access to new url created from load balancer
    http://soacluster.com/
    http://soacluster/soa-infra

 

 

Print Friendly

Latest posts by Nicolas Garimaldi (see all)

Leave a Reply

Your email address will not be published. Required fields are marked *


CAPTCHA Image
Reload Image