Professional Documents
Culture Documents
SOA 11G Cluster Installation PDF
SOA 11G Cluster Installation PDF
SOA 11G Cluster Installation PDF
Introduction 1
SOA_cluster
Servers Configuration Before installation
xgsoapd5a server
Hostname xgsoapd5A.ea.com
Server Details
ORACLE_BASE /opt/fusion
xgsoapd5b server
Hostname xgsoapd5b.ea.com
Server Details
ORACLE_BASE /opt/fusion
Database details
Oracle DB 10.2.0.4
Version
In order to have JDK available for Weblogic installation, use JRockit Mission Control installer, available to
download on edelivery.oracle.com site (V20433-01.zip).
mkdir /opt/fusion/fmw
./jrmc-4.0.0-1.6.0-linux-x64.bin
/opt/fusion/fmw/jrmc-4.0.0-1.6.0
cd /opt/fusion/fmw
ln -s jrmc-4.0.0-1.6.0 java
Oracle SOA Suite components require schemas that must be installed in an Oracle database. You create and load
these schemas in your database by using RCU.
Run rcu.bat
Installation steps 3
SOA_cluster
Choose “Create”
Specify connection to one of the database nodes and connect as a system user with a
sysdba role
Installation steps 4
SOA_cluster
You can safely ignore the following warning if you get one:
Click OK to continue:
AS Common Schemas
Installation steps 5
SOA_cluster
- Metadata Services
- SOA Infrastructure
Click OK to continue:
Installation steps 6
SOA_cluster
Click on Manage Tablespaces button:
Click on each of the tablespaces with AIA prefix and edit data file as required:
Installation steps 7
SOA_cluster
Installation steps 8
SOA_cluster
Installation steps 9
SOA_cluster
Installation steps 10
SOA_cluster
Installation steps 11
SOA_cluster
Click OK button when finished with all tablespace
Installation steps 12
SOA_cluster
Click on “Create” button.
Installation steps 13
SOA_cluster
Login to the database as a user with admin privileges and add the following grants:
Perform installation of the Weblogic Server on both nodes of the cluster as per following steps:
Run the installer from the directory where you unzipped it:
Installation steps 14
SOA_cluster
Enter Middleware home directory and press Next
Enter “Yes” for the warning (you already have JRE in you Middleware Home)
Installation steps 15
SOA_cluster
Clear “Security Updates” checkbox:
Installation steps 16
SOA_cluster
Choose Custom install type
Installation steps 17
SOA_cluster
Review JDK selection
Installation steps 18
SOA_cluster
Review Installation Summary
Observe installation
Installation steps 19
SOA_cluster
Clear “Run Quickstart” checkbox and press “Done” button:
Installation steps 20
SOA_cluster
Install SOA Suite
Check if your /etc/oraInst.loc file points to the existing oraInventory directory. If not then rename your
/etc/oraInst.loc in order for the installer to create a new Oracle Inventory directory.
Perform installation of the Weblogic Server on both nodes of the cluster as per following steps:
Run the installer from the directory where you unzipped it:
Answer “y” on a question to continue after check for display colors failure
If you renamed /etc/oraInst.loc file earlier then you will get the following screen:
Enter a new location for the Inventory directory and press Ok.
Installation steps 21
SOA_cluster
You will receive the following screen at which point you should execute the requested script with root privileges and
click OK upon execution.
Installation steps 22
SOA_cluster
Observe prerequisite checking. Failure here might indicate a missing Linux package:
Installation steps 23
SOA_cluster
Specify Oracle Middleware Home as “/opt/fusion/fmw” and Oracle Home Directory
as “soa”
Installation steps 24
SOA_cluster
Observe the progress
Installation steps 25
SOA_cluster
Click Next when Progress reaches 100%
Installation steps 26
SOA_cluster
Click Finish
Installation steps 27
SOA_cluster
Create Weblogic Domain
According to the Oracle recommended approach, we configure soa_domain in a modular fashion. We run
configuration wizard 3 times:
Create domain directories from one of the nodes for admin and managed servers:
mkdir /11g/admin/soa_domain
mkdir /11g/admin/soa_domain/aserver
mkdir /11g/admin/soa_domain/node1
mkdir /11g/admin/soa_domain/node1/mserver
mkdir /11g/admin/soa_domain/node2
mkdir /11g/admin/soa_domain/node2/mserver
Installation steps 28
SOA_cluster
mkdir /11g/soadata/soa_domain/
mkdir /11g/soadata/soa_domain/apps
mkdir /11g/soadata/soa_domain/node1
mkdir /11g/soadata/soa_domain/node1/apps
mkdir /11g/soadata/soa_domain/node2
mkdir /11g/soadata/soa_domain/node2/apps
Make sure that you have VIP address for the Admin Server enabled (xgsoapd5v3.ea.com). Verify it’s presence with
/sbin/ifconfig command. It should report something similar to the following (assuming 10.50.131.44 is an IP-address
for xgsoapd5v3.ea.com):
If the address is not present, enable it on a free eth0:N interface. Here is an example:
Enable your network to register the new location of the virtual IP, for example:
Run the Configuration Wizard from the SOAhome directory to create a domain containing the Administration Server
and Oracle Web Services Manager. Later, you will extend the domain to contain SOA components.
cd /opt/fusion/fmw/soa/common/bin
./config.sh
In the Welcome screen, select Create a New WebLogic Domain, and click Next.
Installation steps 29
SOA_cluster
Select the following products:
- Oracle JRF
Installation steps 30
SOA_cluster
In the Specify Domain Name and Location screen, enter the domain name. Make sure
that the domain directory matches the directory and shared storage mount point. Enter
/11g/admin/soa_domain/aserver for the domain directory and /11g/soadata/soa_domain/apps for the application
directory:
In the Configure Administrator Username and Password screen, enter the username
and password to be used for the domain’s administrator:
Installation steps 31
SOA_cluster
Select “Production Mode” and available JDK in the Configure Server Start Mode and
JDK screen:
Installation steps 32
SOA_cluster
- Select the OWSM MDS schema
- Click Next
The Configure RAC Multi Data Sources Component Schema screen is displayed. In
this screen, do the following:
- Enter values for the Driver, Service Name, Username and Password,
specifying the connect information for the RAC database that was seeded with RCU
- Click Add
- Click Next
Installation steps 33
SOA_cluster
Observe automatic JDBC connection testing and click Next:
Installation steps 34
SOA_cluster
Enter “AdminServer” as a Name, VIP3 (xgsoapd5v3.ea.com) as a Listen Address and
7001 as a Listen Port
In the Configure Managed Servers screen, click Add to add the following managed
servers: WLS_WSM1 and WLS_WSM2 listening on port 7003 of physical hostnames:
Installation steps 35
SOA_cluster
In the Configure Clusters screen, Click Add to add WSM-PM_Cluster:
Installation steps 36
SOA_cluster
In the Assign Servers to Clusters screen, assign WLS_WSM1 and WLS_WSM2
servers to WSM-PM_Cluster
Installation steps 37
SOA_cluster
Add machines listening on physical hostnames:
Installation steps 38
SOA_cluster
In the Assign Servers to Machines screen, assign WLS_WSM1 and AdminServer to
host1 machine and WLS_WSM2 server to host2 machine:
Installation steps 39
SOA_cluster
In the Target Deployments to Clusters or Servers screen, make sure that the wsm-pm
application and the oracle.wsm.seedpolicies library is targeted to the WSM-PM_Cluster only. Make sure that all
other deployments are targeted to the AdminServer. Click Next.
Installation steps 40
SOA_cluster
In the Target Services to Clusters or Servers screen, select the following:
Note: All JDBC system resources should be targeted to both the Admin Server and WSM-PM_Cluster.
Note: JOC-Shutdown, JOC-Startup, and OWSM Startup Class should be targeted only to the WSM-PM_Cluster.
- Make sure that all the remaining services are targeted to the AdminServer
Installation steps 41
SOA_cluster
In the Configuration Summary screen, click Create
Installation steps 42
SOA_cluster
Observe the progress
Installation steps 43
SOA_cluster
In the Create Domain screen, click Done.
You have configured the domain. Now you have to create separate domain directories for Managed Servers if you do
cluster installation.
Use the pack and unpack commands to separate the domain directory used by the
Administration Server from the domain directory used by the managed server
cd /opt/fusion/fmw/oracle_common/common/bin
Start the Admin Server, specifying username and password when asked and stop it
with Ctrl-C after a successful start:
cd /11g/admin/soa_domain/aserver/soa_domain/bin
./startWebLogic.sh
Installation steps 44
SOA_cluster
Start the Admin Server in nohup mode and monitor it until it reaches RUNNING
state:
cd /11g/admin/soa_domain/aserver/soa_domain/bin
tail -f AdminServer.log
Disable Host Name Verification for AdminServer and WLS_WSM1 server by setting
Hostname Verification to None in SSL tab (Advanced section) for both servers in Weblogic Admin Console. In
Weblogic Admin Console, go to Environment/Machines. For every machine, go to Configuration/Node Manager and
change type to “Plain”. Restart Admin Server.
cd /opt/fusion/fmw/oracle_common/common/bin
./setNMProps.sh
cd /opt/fusion/fmw/wlserver_10.3/server/bin
./startNodeManager.sh
Click Ctrl-C
cd /opt/fusion/fmw/wlserver_10.3/common/nodemanager
StartScriptEnabled=true
StopScriptEnabled=true
SecureListener=false
cd /opt/fusion/fmw/wlserver_10.3/server/bin
Copy soadomaintemplate.jar file created earlier to the second node. Run unpack command on xgsoapd5b.ea.com to
unpack the propagated template
cd /opt/fusion/fmw/oracle_common/common/bin
Installation steps 45
SOA_cluster
Start Node Manager on the second node:
cd /opt/fusion/fmw/oracle_common/common/bin
./setNMProps.sh
cd /opt/fusion/fmw/wlserver_10.3/server/bin
./startNodeManager.sh
Click Ctrl-C
cd /opt/fusion/fmw/wlserver_10.3/common/nodemanager
StartScriptEnabled=true
StopScriptEnabled=true
SecureListener=false
cd /opt/fusion/fmw/wlserver_10.3/server/bin
/opt/fusion/fmw/soa/common/bin/wlst.sh
connect()
Enter Administrator username, password and URL for Admin Server when prompted
execfile('/opt/fusion/fmw/oracle_common/bin/configure-joc.py')
For the cluster installation you would have to answer ‘y’ when prompted if you want to specify a cluster name, then
enter WSM-PM_Cluster and 9991 discover port when prompted. Answer “true” for a Distributed Mode question on
cluster installation; do not exclude any servers.
Installation steps 46
SOA_cluster
On a first node:
On a second node:
cd /opt/fusion/fmw/soa/common/bin
./config.sh
Select the Weblogic domain directory for admin server, and click Next
Installation steps 47
SOA_cluster
Select Oracle SOA Suite 11.1.1.0. Click Next.
Installation steps 48
SOA_cluster
Select all 3 components schemas and the “Configure schemas as RAC multi data
source schemas” checkbox in the Configure JDBC Component Schema screen and click Next:
Installation steps 49
SOA_cluster
Select each component one by one (with an exception of already configured OWSM
MDS schema) and specify the database details, deselecting the current component schema after configuring it:
Installation steps 50
SOA_cluster
In the Test JDBC Data Sources screen, the connections should be tested
automatically. Click Next:
In the Select Optional Configuration screen, select Managed Servers, Cluster and
Machines, and then Deployment and services. Click Next:
Installation steps 51
SOA_cluster
In the Configure Managed Servers screen, add the required managed servers. A
server called soa_server1 is created automatically. Rename this to WLS_SOA1, specify listen address as
xgsopapd5v1.ea.com and port 7004.Similarly, add a new server called WLS_SOA2:
Installation steps 52
SOA_cluster
In the Assign Servers to Clusters screen, assign WLS_SOA1 and WLS_SOA2 servers
to SOA_Cluster:
Installation steps 53
SOA_cluster
Assign WLS_SOA1 server to xgsoapd5a.ea.com and WLS_SOA2 server to
xgsoapd5b.ea.com respectfully:
Installation steps 54
SOA_cluster
- The oracle.rules.*, oracle.sdp.*, and oracle.soa.* libraries should be
targeted only to SOA_Cluster
Installation steps 55
SOA_cluster
In the Target Services to Clusters or Servers screen, ensure that
- JOC Startup Class, JOC Shutdown Class, OWSM Startup Class are
targeted only to WSM-PM_Cluster
Installation steps 56
SOA_cluster
In the Configuration Summary screen click Extend
Installation steps 57
SOA_cluster
Click Done on the last screen.
Before you can start the WLS_SOA1 managed server on SOAHOST1, you must run
the soa-createUDD.py script. You run the script using WLST offline
. /11g/admin/soa_domain/aserver/soa_domain/bin/setDomainEnv.sh
Verify that the following JMS modules are listed in the admin console:
- SOAJMSModuleUDDs
- UMSJMSSystemResource
Installation steps 58
SOA_cluster
Click on each module, go to Subdeployments tab and then click SOAJMSSubDM or UMSJMSSubDMSOA
respectfully. Verify targeting to SOAJMSServer_auto_1 and SOAJMSServer_auto_2 in the first case. Then targeting
to UMSJMSServer_auto_1 and UMSJMSServer_auto_2 in the second case.
Disable Host Name Verification for WLS_SOA1 and WLS_SOA2 servers by setting
Hostname Verification to None in SSL tab (Advanced section) for the servers in Weblogic Admin Console
cd /opt/fusion/fmw/oracle_common/common/bin
http://xgsoapd5v1.ea.com:7004/soa-infra
http://xgsoapd5a.ea.com:7003/wsm-pm
http://xgsoapd5v1.ea.com:7004/b2bconsole
http://xgsoapd5v1.ea.com:7004/integration/worklistapp
cd /opt/fusion/fmw/oracle_common/common/bin
cd /opt/fusion/fmw/soa/soa/thirdparty/edifecs
Start WLS_SOA2 server from Weblogic Admin Console and validate the following
URLs:
http://xgsoapd5v2.ea.com:7004/soa-infra
http://xgsoapd5v2.ea.com:7004/b2bconsole
http://xgsoapd5v2.ea.com:7004/integration/worklistapp
mkdir /11g/admin/soa_domain/SOA_Cluster
mkdir /11g/admin/soa_domain/SOA_Cluster/jms
mkdir /11g/admin/soa_domain/SOA_Cluster/tlogs
Installation steps 59
SOA_cluster
- Using Weblogic Admin Console, expand Services, and then click on
Persistent Stores node. Enter the following location for each existing store:
/11g/admin/soa_domain/SOA_Cluster/jms
- Using Weblogic Admin Console, visit Services tab for WLS_SOA1 and
WLS_SOA2 servers and enter the following directory path:
/11g/admin/soa_domain/SOA_Cluster/tlogs
- Save
Perform installation of the Weblogic Server on both nodes of the cluster as per following steps:
Run the installer from the directory where you unzipped it:
Answer “y” on a question to continue after check for display colors failure
Installation steps 60
SOA_cluster
In the Select Installation Type screen, select Install and Configure, and click Next
Installation steps 61
SOA_cluster
In the Prerequisite Checks screen, ensure that all the prerequisites are met, then click
Next
Installation steps 62
SOA_cluster
Select only Oracle Http Server in the Configure Components screen:
Installation steps 63
SOA_cluster
On the first node enter /11g/admin/ohs_instance1 as Instance Home Location,
ohs_instance1 as Instance Name and ohs1 as OHS Component Name. On the second node you would enter
/11g/admin/ohs_instance2, ohs_instance2 and ohs2 respectively:
Installation steps 64
SOA_cluster
Uncheck security updates checkbox and answer Yes for the alert:
Installation steps 65
SOA_cluster
Click Install in the Installation Summary screen:
Observe progress
Installation steps 66
SOA_cluster
Click Next when Configuration Progress screen reaches 100%
NameVirtualHost *:7777
<VirtualHost *:7777>
ServerName http://xgsoapd5.ea.com:7777
ServerAdmin you@ea.com
RewriteEngine On
RewriteOptions inherit
# WSM-PM
<Location /wsm-pm>
SetHandler weblogic-handler
WebLogicCluster xgsoapd5a.ea.com:7003,xgsoapd5b.ea.com:7003
</Location>
Installation steps 67
SOA_cluster
<Location /console>
SetHandler weblogic-handler
WebLogicHost xgsoapd5v3.ea.com
WeblogicPort 7001
</Location>
<Location /consolehelp>
SetHandler weblogic-handler
WebLogicHost xgsoapd5v3.ea.com
WeblogicPort 7001
</Location>
<Location /em>
SetHandler weblogic-handler
WebLogicHost xgsoapd5v3.ea.com
WeblogicPort 7001
</Location>
<Location /soa-infra>
SetHandler weblogic-handler
WebLogicCluster xgsoapd5v1.ea.com:7004,xgsoapd5v2.ea.com:7004
</Location>
# Worklist
<Location /integration/>
SetHandler weblogic-handler
WebLogicCluster xgsoapd5v1.ea.com:7004,xgsoapd5v2.ea.com:7004
</Location>
# B2B
<Location /b2bconsole>
SetHandler weblogic-handler
WebLogicCluster xgsoapd5v1.ea.com:7004,xgsoapd5v2.ea.com:7004
</Location>
# UMS prefs
Installation steps 68
SOA_cluster
<Location /sdpmessaging/userprefs-ui >
SetHandler weblogic-handler
WebLogicCluster xgsoapd5v1.ea.com:7004,xgsoapd5v2.ea.com:7004
</Location>
<Location /DefaultToDoTaskFlow/>
SetHandler weblogic-handler
WebLogicCluster xgsoapd5v1.ea.com:7004,xgsoapd5v2.ea.com:7004
</Location>
# Workflow
<Location /workflow>
SetHandler weblogic-handler
WebLogicCluster xgsoapd5v1.ea.com:7004,xgsoapd5v2.ea.com:7004
</Location>
<Location /ADFAttachmentHelper>
SetHandler weblogic-handler
WebLogicCluster xgsoapd5v1.ea.com:7004,xgsoapd5v2.ea.com:7004
</Location>
<Location /soa/composer>
SetHandler weblogic-handler
WebLogicCluster xgsoapd5v1.ea.com:7004,xgsoapd5v2.ea.com:7004
</Location>
# AIA
<Location /AIA>
SetHandler weblogic-handler
WebLogicCluster xgsoapd5v1.ea.com:7004,xgsoapd5v2.ea.com:7004
</Location>
# BAM
<Location /OracleBAM>
SetHandler weblogic-handler
Installation steps 69
SOA_cluster
WebLogicCluster xgsoapd5v4.ea.com:7005,xgsoapd5b.ea.com:7005
</Location>
</VirtualHost>
NameVirtualHost *:7777
<VirtualHost *:7777>
ServerName http://xgosbpd5.ea.com:7777
ServerAdmin you@ea.com
RewriteEngine On
RewriteOptions inherit
<Location /console>
SetHandler weblogic-handler
WebLogicHost xgosbpd5v3.ea.com
WeblogicPort 8001
</Location>
<Location /consolehelp>
SetHandler weblogic-handler
WebLogicHost xgosbpd5v3.ea.com
WeblogicPort 8001
</Location>
<Location /em>
SetHandler weblogic-handler
WebLogicHost xgosbpd5v3.ea.com
WeblogicPort 8001
</Location>
<Location /sbconsole>
SetHandler weblogic-handler
WebLogicHost xgosbpd5v3.ea.com
WeblogicPort 8001
Installation steps 70
SOA_cluster
</Location>
</VirtualHost>
cd /11g/admin/ohs_instance1/bin
./opmnctl stopall
./opmnctl startall
http://xgsoapd5.ea.com:7777
http://xgsoapd5a.ea.com:7777/console
http://xgsoapd5b.ea.com:7777/console
http://xgsoapd5.ea.com:7777/console
http://xgsoapd5a.ea.com:7777/em
http://xgsoapd5b.ea.com:7777/em
http://xgsoapd5.ea.com:7777/em
http://xgsoapd5a.ea.com:7777/wsm-pm
http://xgsoapd5b.ea.com:7777/wsm-pm
http://xgsoapd5.ea.com:7777/wsm-pm
http://xgsoapd5a.ea.com:7777/soa-infra
http://xgsoapd5b.ea.com:7777/soa_infra
http://xgsoapd5.ea.com:7777/soa_infra
http://xgsoapd5a.ea.com:7777/integration/worklistapp
http://xgsoapd5b.ea.com:7777/integration/worklistapp
http://xgsoapd5.ea.com:7777/integration/worklistapp
http://xgsoapd5a.ea.com:7777/b2bconsole
http://xgsoapd5b.ea.com:7777/b2bconsole
http://xgsoapd5.ea.com:7777/b2bconsole
http://xgsoapd5a.ea.com:7777/sdpmessaging/userprefs-ui
http://xgsoapd5b.ea.com:7777/sdpmessaging/userprefs-ui
http://xgsoapd5.ea.com:7777/sdpmessaging/userprefs-ui
For the AdminServer, set Frontend Host and Ports (use LBR URL) in the
Services/HTTP tab in the Weblogic Admin Console
Set the Frontend Host and Ports for SOA_Cluster cluster in the HTTP tab.
Installation steps 71
SOA_cluster
Extend the Domain to Include BAM
cd /opt/fusion/fmw/soa/common/bin
./config.sh
Installation steps 72
SOA_cluster
Select oracle Business Activity Monitoring checkbox. Click Next.
Select BAM schema in the Configure JDBC Component Schema screen. Then select
Configure selected components schemas as RAC multi data source schemas and click Next:
Installation steps 73
SOA_cluster
Select BAM Schema in the Configure RAC Multi Data Sources Component Schema
screen. Specify database details as per following screenshot:
Observe Connection Testing. Click Next when all connections are successful.
Installation steps 74
SOA_cluster
Select checkboxes for Managed Servers, Clusters and Machines and for Deployments
and Services
Add the BAM_Cluster in the Configure Clusters screen and click Next:
Installation steps 75
SOA_cluster
Add WLS_BAM1 and WLS_BAM2 servers to the BAM_Cluster in the Assign
Servers to the Cluster screen and click Next:
Delete the Local Machine that appears by default in the Configure Machines screen.
Leave all other fields to their default values. Click Next.
Installation steps 76
SOA_cluster
In the Target Deployments to Clusters or Servers screen, ensure the following:
Installation steps 77
SOA_cluster
Installation steps 78
SOA_cluster
In the Target Services to Clusters or Servers screen, ensure that
- JOC Startup Class, JOC Shutdown Class, OWSM Startup Class are
targeted only to WSM-PM_Cluster
Installation steps 79
SOA_cluster
In the Configuration Summary screen click Extend
Installation steps 80
SOA_cluster
Click Done in the Creating Domain screen
cd /11g/admin/soa_domain/aserver/soa_domain/bin
Installation steps 81
SOA_cluster
You must run the soa-createUDD.py script using WLST before you can start the
WLS_BAM1 server:
. /11g/admin/soa_domain/aserver/soa_domain/bin/setDomainEnv.sh
Expand Services and then Messaging in the Domain Structure window in the Admin Console. Click JMS Modules.
Click UMSJMSSystemResource. Click the Subdeployments tab. Ensure that UMSJMSSubDMSOA is the only
subdeployment available. Go back to UMSJMSSystemResource and click Targets. Deselect BAM_Cluster as target.
Click Save and Activate.
Verify that the following modules are listed in the Oracle WebLogic Server Administration Console
- SOAJMSModuleUDDs
- UMSJMSSystemResource
- BAMJMSModuleUDDs
- UMSJMSModuleUDDsBAM
Click on each module, go to Subdeployments tab and then click SOAJMSSubDM or UMSJMSSubDMSOA,
BAMJMSSubDM, UMSJMSSubDMBAM respectfully.
/11g/admin/soa_domain/SOA_Cluster/jms
- Using Weblogic Admin Console, visit Services tab for WLS_BAM1 server
and enter the following directory path:
/11g/admin/soa_domain/SOA_Cluster/tlogs
- Save
Go to WLS_BAM2 server in the Admin Console. Click the Deployments tab. Select the oracle-bam application from
the Name column of the table. The Settings page for the oracle-bam application appears. Click the Targets tab. Click
Lock and Edit. Change the targets for the modules as described in the following table:
Installation steps 82
SOA_cluster
Component Type Target
cd /opt/fusion/fmw/oracle_common/common/bin
Copy soadomaintemplateBAM.jar to the same directory on the second node and run the following on the second
node:
cd /opt/fusion/fmw/oracle_common/common/bin
Start WLS_BAM1 server from the Admin Console and verify the status of the
following URL in IE browser:
http://xgsoapd5v4.ea.com:7005/OracleBAM
Start WLS_BAM2 server from Admin Console and verify access to the following
URL:
http://xgsoapd5b.ea.com:7005/OracleBAM
Configure the BAM Web Applications to Use the BAM Server in BAMHOST1
Expand BAM in the navigation tree. Right click OracleBamWeb(WLS_BAM1). Choose BAM Web Properties from
the context menu.
Enter http://xgsoapd5.ea.com:7777 for the Application URL and xgsoapd5v1.ea.com for the Server Name
Installation steps 83
SOA_cluster
Access Oracle Enterprise Manager Fusion Middleware Control through http://xgsoapd5.ea.com:7777/em
Expand BAM in the navigation tree. Right click OracleBamServer (WLS_BAM1). Choose System MBean Browser
from the context menu. Expand oracle.bam.server (located within Application Defined MBeans). Click the
BamServerConfig MBean.
Update the ADCServerName attribute by entering xgsoapd5v4.ea.com as a value. Update the ADCServerPort
attribute to the port 7005 of the BAM server. Click Apply
Now expand oracle.ba.web in the same tree. Set ServerPort attribute to port 7005 for BamWebConfig MBean for
both Server: WLS_BAM1 and Server: WLS_BAM2 subnodes. Click Apply on each page.
http://xgsoapd5v4.ea.com:7005/OracleBAM
http://xgsoapd5b.ea.com:7005/OracleBAM
http://xgsoapd5.ea.com:7777/OracleBAM
In this step we upgrade Weblogic Server to version 10.3.3 which is necessary for the SOA 11.1.1.3 upgrade required
for AIA 11g PS2. Perform the following on both nodes of the cluster:
Stop all servers on both nodes and do not start them before SOA upgrade is done.
Run the installer from the folder where you unzipped it to:
Installation steps 84
SOA_cluster
Click Next on Welcome screen
Installation steps 85
SOA_cluster
Review chosen Products and Components and click Next
Installation steps 86
SOA_cluster
Review Product Installation Directories and click Next
Installation steps 87
SOA_cluster
Uncheck “Run Quickstart” checkbox and click Done:
Installation steps 88
SOA_cluster
Upgrade SOA to version 11.1.1.3
In this step we run SOA 11.1.1.3 upgrade required for AIA 11g PS2. Download the installer from
edelivery.oracle.com (V20966-01.zip). Unzip it in to a separate directory and run the installer from there. Perform
the following steps on both nodes of the cluster (with an exception of running psa assistant for a database)
Run installer and answer “y” on a question to continue after display colors check
failure.
Set Oracle Middleware Home to /opt/fusion/fmw and Oracle Home Directory to soa
Installation steps 89
SOA_cluster
Review Installation Summary and click Install:
Installation steps 90
SOA_cluster
Observe the progress
Installation steps 91
SOA_cluster
Click Finish on the Installation Complete screen:
Installation steps 92
SOA_cluster
Run a Path Set Assistant on one of the cluster nodes:
cd /opt/fusion/fmw/soa/bin
After finishing upgrade on both nodes, start AdminServer using a script and start
managed servers from Weblogic Admin Console. Verify the environment by accessing the following URLs:
http://xgsoapd5.ea.com:7777/em
http://xgsoapd5.ea.com:7777/soa-infra
http://xgsoapd5.ea.com:7777/b2bconsole
http://xgsoapd5.ea.com:7777/integration/worklistapp
http://xgsoapd5.ea.com:7777/sdpmessaging/userprefs-ui
In this step we patch SOA with a patch 9822892. You have to download the following files from support.oracle.com:
- p6880880_111000_Linux-x86-64.zip
- p9822892_111130_Generic.zip
Install a newer version of Opatch utility in the soa Oracle Home. Backup existing
OPatch directory and unzip the patch
cd /opt/fusion/fmw/soa
mv OPatch OPatch_old
unzip p6880880_111000_Linux-x86-64.zip
/opt/fusion/fmw/soa/OPatch/opatch lsinventory
Find a Node manager process with ps -ef | grep NodeMan and kill it
StartScriptEnabled=true
StopScriptEnabled=true
Installation steps 93
SOA_cluster
Start the Node Manager
cd /opt/fusion/fmw/wlserver_10.3/server/bin
You have to run the patch twice on a first node specifying /11g/admin/soa_domain/aserver/soa_domain and
/11g/admin/soa_domain/node1/mserver/soa_domain as a Domain Home and once on the second node specifying
/11g/admin/soa_domain/node2/mserver/soa_domain
Disregard OUI-67851warnings
Start all managed servers using Admin Console after patching both nodes
http://xgsoapd5.ea.com:7777/soa-infra
http://xgsoapd5.ea.com:7777/b2bconsole
http://xgsoapd5.ea.com:7777/integration/worklistapp
http://xgsoapd5.ea.com:7777/sdpmessaging/userprefs-ui
There are installation prerequisites that you have to meet before installing AIA 11g PS2 Foundation Pack. Perform
the following steps:
Installation steps 94
SOA_cluster
Set the ANT_HOME, JAVA_HOME and PATH environment variables:
export ANT_HOME=/opt/fusion/fmw/modules/org.apache.ant_1.7.1
export JAVA_HOME=/opt/fusion/fmw/jrmc-4.0.0-1.6.0
export PATH=$ANT_HOME/bin:$JAVA_HOME/bin:$PATH
cd /opt/fusion/software/9717829/files/patch_9717829/files
AIA installer would use nmConnect WLST command during the installation.
However, by default, the nmConnect command cannot be used in a production environment. You must first perform
the following procedures to use nmConnect in a production environment:
- Update Node Manager credentials in the Weblogic Admin Console from the
Advanced options under domain_name > Security > General
- Run wlst.sh and connect to the Admin server using connect() command
First node:
nmEnroll(‘/11g/admin/soa_domain/aserver/soa_domain’,’/opt/fusion/fmw/wlserver_10.3/common/nodemanager’)
nmEnroll(‘/11g/admin/soa_domain/node1/mserver/soa_domain’,’/opt/fusion/fmw/wlserver_10.3/common/nodemana
ger’)
nmEnroll(‘/11g/admin/soa_domain/node2/mserver/soa_domain’,’/opt/fusion/fmw/wlserver_10.3/common/nodemana
ger’)
Enable Remote JDBC connections in Weblogic Servers. Make the following change
in setDomainEnv.sh file for all 3 of your domain directories:
WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=false" to
WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=true"
cd /opt/fusion/fmw/soa/bin
Edit ant-sca-compile.xml. Under the scac element at the end of the file, increase the following memory settings:
<jvmarg value="-Xms2048m"/>
<jvmarg value="-Xmx2048m"/>
Perform the following Cluster Installation Prerequisites. Assuming that you unzipped
AIA installation into /opt/fusion/software/AIA folder:
Installation steps 95
SOA_cluster
cd /11g/admin/soa_domain/aserver/soa_domain/bin
. ./setDomainEnv.sh
cd /opt/fusion/software/AIA
cp cd/Disk1/misc/lib/aia.jar /opt/fusion/fmw/soa/soa/modules/oracle.soa.ext_11.1.1
cd /opt/fusion/fmw/soa/communications/modules/oracle.sdp.client_11.1.1
cp parlayx.jar /opt/fusion/fmw/soa/soa/modules/oracle.soa.ext_11.1.1
cd /opt/fusion/fmw/soa/soa/modules/oracle.soa.ext_11.1.1
ant
mkdir /11g/admin/soa_domain/node1/mserver/soa_domain/AIAJMSFileStore_1
mkdir /11g/admin/soa_domain/node2/mserver/soa_domain/AIAJMSFileStore_2
mkdir /opt/fusion/fmw/AIA30
Run installer and answer “y” on a question to continue after display colors check
failure.
Installation steps 96
SOA_cluster
Click Next when Prerequisites Checks would be 1005 completed on the following
screen
Installation steps 97
SOA_cluster
Enter AIA30 as AIA Home, /opt/fusion/fmw/AIA30 as AIA Home Path and
/opt/fusion/fmw/jrmc-4.0.0-1.6.0 as JAVA Home. Make sure you select Complete Installation radio button and
Foundation Pack 11gR1 checkbox. Click Next:
Installation steps 98
SOA_cluster
Enter xgsoapd5v3.ea.com as an Admin Host Name, 7001 as an Admin Port,
soa_domain as a Domain Name, weblogic as an Admin User along with its password, choose SOA_Cluster from the
list of managed servers. Check Cluster Install checkbox. Enter /opt/fusion/fmw/soa as Local SOA Home,
xgsoapd5.ea.com as Cluster Proxy URL and 7777 as a Proxy Port. Click Next:
Installation steps 99
SOA_cluster
Press OK confirming nodemanager user password for both machines:
Installation steps100
SOA_cluster
Press Next on SOA Server Validation screen if you don’t see any red warnings:
Specify database details as per the following screen (any one of RAC node
connection details, AIA_TBS as a Default Tablespace). Click Next.
Installation steps101
SOA_cluster
Enter jdbc:oracle:thin:@soadrdb2-v.ea.com:1521/GSOAPD3 as MDS Repository
URL, AIA_MDS as MDS Username. Click Next
Installation steps102
SOA_cluster
Leave Oracle Enterprise Repository Details empty and click Next:
Installation steps103
SOA_cluster
Review Installation Summary and click Install:
Installation steps104
SOA_cluster
Observe Installation Progress
Installation steps105
SOA_cluster
Observe Configuration Progress
Installation steps106
SOA_cluster
Make sure it is 100% complete. It’s a long process. Then click Next:
Installation steps107
SOA_cluster
Click Finish:
Installation steps108
SOA_cluster
Go to myrealm Security Realm in Weblogic Admin Console, then to Users and
Groups tab, Users tab. Click on weblogic user, go to Groups tab and assign all groups started with AIA to weblogic
user. So, that we would be able to test AIA installation as a weblogic user later
Initial Capacity 20
Maximum Capacity 50
Capacity Increment 10
Login Delay 0
Similarly, set Login Delay attribute to 0 (it is in Advanced section of the Connection
Pool tab) for the following data sources:
AIACentralDS-rac0
AIACentralDS-rac1
AIADataSource-rac0
AIADataSource-rac1
Installation steps109
SOA_cluster
XrefDataSource-rac0
XrefDataSource-rac1
Configure AIA Error Logging for Cluster. Modify the following 3 files:
/11g/admin/soa_domain/aserver/soa_domain/config/fmwconfig/servers/WLS_SOA1/logging.xml
/11g/admin/soa_domain/node1/mserver/soa_domain/config/fmwconfig/servers/WLS_SOA1/logging.xml
/11g/admin/soa_domain/node2/mserver/soa_domain/config/fmwconfig/servers/WLS_SOA1/logging.xml
</log_handler>
</log_handler>
</log_handler>
Installation steps110
SOA_cluster
<logger name='oracle.aia.logging.error' level='NOTIFICATION:1' useParentHandlers='false'>
<handler name='aia-log-error-handler'/>
</logger>
<handler name='aia-log-trace-handler'/>
</logger>
<handler name='aia-log-debug-handler'/>
</logger>
Continue configure AIA Error Logging for Cluster. Modify the following 3 files:
/11g/admin/soa_domain/aserver/soa_domain/config/fmwconfig/servers/WLS_SOA2/logging.xml
/11g/admin/soa_domain/node1/mserver/soa_domain/config/fmwconfig/servers/WLS_SOA2/logging.xml
/11g/admin/soa_domain/node2/mserver/soa_domain/config/fmwconfig/servers/WLS_SOA2/logging.xml
</log_handler>
Installation steps111
SOA_cluster
</log_handler>
</log_handler>
<handler name='aia-log-error-handler'/>
</logger>
<handler name='aia-log-trace-handler'/>
</logger>
<handler name='aia-log-debug-handler'/>
</logger>
Continue configure AIA Error Logging for Cluster. Navigate to the Deployments in
the Admin Console. Click Install. Choose the path
/opt/fusion/fmw/AIA30/Infrastructure/Install/applications/AIALogApp.ear
Click Next. Choose Install this deployment as an application. Choose SOA_Cluster as a target. Name the deployment
as AIALogMetadata. Click Finish.
Installation steps112
SOA_cluster
AIA 11g FP PS2 application
Source aiaenv.sh
cd /opt/fusion/fmw/AIA30/aia_instances/AIA/bin
. ./aiaenv.sh
Apply the patch from the directory where you unzipped it earlier. For example:
cd /opt/fusion/software/9717829/
cd /opt/fusion/fmw/AIA30/Infrastructure/Install/AID
cd /opt/fusion/fmw/AIA30/aia_instances/AIA/config
cp AIAInstallProperties.xml AIAInstallProperties.xml.bak
Modify AIAInstallProperties.xml and make sure that you have rac configuration for all you data sources (use
/opt/fusion/fmw/AIA30/patch_9717829/files/ AIAInstallProperties_Template.xml file as an example):
<aia>
<jdbc-url>jdbc:oracle:thin:@soadrdb2-v.ea.com:1521/GSOAPD3</jdbc-url>
<username>AIA_AIA</username>
<password>[C@1c2925d3</password>
<createschema>true</createschema>
<sysusername>system</sysusername>
<syspassword>[C@1c294462</syspassword>
<role>SYSDBA</role>
<isRac>true</isRac>
<racCount>2</racCount>
<racInstances>rac0,rac1</racInstances>
<defaulttablespace>AIA_TBS</defaulttablespace>
Installation steps113
SOA_cluster
<temptablespace>TEMP</temptablespace>
<rac>
<serviceName>GSOAPD3</serviceName>
<rac0>
<instanceName>GSOAPD3A</instanceName>
<host>soadrdb1-v.ea.com</host>
<port>1521</port>
</rac0>
<rac1>
<instanceName>GSOAPD3B</instanceName>
<host>soadrdb2-v.ea.com</host>
<port>1521</port>
</rac1>
</rac>
</aia>
<sr>
<jdbc-url>jdbc:oracle:thin:@soadrdb2-v.ea.com:1521/GSOAPD3</jdbc-url>
<username>AIA_AIAEBOD</username>
<password>[C@1c32eb53</password>
<createschema>true</createschema>
<sysusername>system</sysusername>
<syspassword>[C@1c2f902a</syspassword>
<role>SYSDBA</role>
<isRac>true</isRac>
<racCount>2</racCount>
<racInstances>rac0,rac1</racInstances>
<defaulttablespace>AIA_TBS</defaulttablespace>
<temptablespace>TEMP</temptablespace>
Installation steps114
SOA_cluster
<rac>
<serviceName>GSOAPD3</serviceName>
<rac0>
<instanceName>GSOAPD3A</instanceName>
<host>soadrdb1-v.ea.com</host>
<port>1521</port>
</rac0>
<rac1>
<instanceName>GSOAPD3B</instanceName>
<host>soadrdb2-v.ea.com</host>
<port>1521</port>
</rac1>
</rac>
</sr>
<jms>
<jdbc-url>jdbc:oracle:thin:@soadrdb2-v.ea.com:1521/GSOAPD3</jdbc-url>
<username>AIA_JMSUSER</username>
<password>[C@1c2f26e2</password>
<createschema>true</createschema>
<sysusername>system</sysusername>
<syspassword>[C@1c2f5dff</syspassword>
<role>SYSDBA</role>
<isRac>true</isRac>
<racCount>2</racCount>
<racInstances>rac0,rac1</racInstances>
<defaulttablespace>AIA_TBS</defaulttablespace>
<temptablespace>TEMP</temptablespace>
<rac>
<serviceName>GSOAPD3</serviceName>
Installation steps115
SOA_cluster
<rac0>
<instanceName>GSOAPD3A</instanceName>
<host>soadrdb1-v.ea.com</host>
<port>1521</port>
</rac0>
<rac1>
<instanceName>GSOAPD3B</instanceName>
<host>soadrdb2-v.ea.com</host>
<port>1521</port>
</rac1>
</rac>
</jms>
<xref>
<jdbc-url>jdbc:oracle:thin:@soadrdb2-v.ea.com:1521/GSOAPD3</jdbc-url>
<username>AIA_XREF</username>
<password>[C@1c29f72d</password>
<createschema>true</createschema>
<sysusername>system</sysusername>
<syspassword>[C@1c2a4941</syspassword>
<role>SYSDBA</role>
<isRac>true</isRac>
<racCount>2</racCount>
<racInstances>rac0,rac1</racInstances>
<defaulttablespace>AIA_TBS</defaulttablespace>
<temptablespace>TEMP</temptablespace>
<rac>
<serviceName>GSOAPD3</serviceName>
<rac0>
<instanceName>GSOAPD3A</instanceName>
Installation steps116
SOA_cluster
<host>soadrdb1-v.ea.com</host>
<port>1521</port>
</rac0>
<rac1>
<instanceName>GSOAPD3B</instanceName>
<host>soadrdb2-v.ea.com</host>
<port>1521</port>
</rac1>
</rac>
</xref>
<aialifecycle>
<jdbc-url>jdbc:oracle:thin:@soadrdb2-v.ea.com:1521/GSOAPD3</jdbc-url>
<username>AIA_AIALIFECYCLE</username>
<password>[C@1c2bb8f4</password>
<createschema>true</createschema>
<sysusername>system</sysusername>
<syspassword>[C@1c2bd449</syspassword>
<role>SYSDBA</role>
<isRac>true</isRac>
<racCount>2</racCount>
<racInstances>rac0,rac1</racInstances>
<defaulttablespace>AIA_TBS</defaulttablespace>
<temptablespace>TEMP</temptablespace>
<rac>
<serviceName>GSOAPD3</serviceName>
<rac0>
<instanceName>GSOAPD3A</instanceName>
<host>soadrdb1-v.ea.com</host>
<port>1521</port>
Installation steps117
SOA_cluster
</rac0>
<rac1>
<instanceName>GSOAPD3B</instanceName>
<host>soadrdb2-v.ea.com</host>
<port>1521</port>
</rac1>
</rac>
</aialifecycle>
<db>
<aiademoparticipatingapp>
<jdbc-url>jdbc:oracle:thin:@soadrdb2-v.ea.com:1521/GSOAPD3</jdbc-url>
<username>FOD</username>
<password>[C@1c294462</password>
<createschema>true</createschema>
<sysusername>system</sysusername>
<syspassword>[C@1c294462</syspassword>
<role>SYSDBA</role>
<isRac>true</isRac>
<racCount>2</racCount>
<racInstances>rac0,rac1</racInstances>
<defaulttablespace>AIA_TBS</defaulttablespace>
<temptablespace>TEMP</temptablespace>
<rac>
<serviceName>GSOAPD3</serviceName>
<rac0>
<instanceName>GSOAPD3A</instanceName>
<host>soadrdb1-v.ea.com</host>
<port>1521</port>
</rac0>
Installation steps118
SOA_cluster
<rac1>
<instanceName>GSOAPD3B</instanceName>
<host>soadrdb2-v.ea.com</host>
<port>1521</port>
</rac1>
</rac>
</aiademoparticipatingapp>
</db>
cd $AIA_HOME/patch_9717829/files/
ant -f UpdateHarvester.xml
Copy AIA30 directory from Middleware Home on the first cluster node to the same
location on the second cluster node
AIAB2BErrorHandlerInterface
AIAB2BInterface
ReloadProcess
AIAAsyncErrorHandlingBPELProcess
AIAReadJMSNotificationProcess
SendNotificationProcess
AIAErrorTaskAdministrationProcess
Installation steps119
SOA_cluster
Configure Automatic Server Migration
You have to configure automatic server migration for WLS_SOA1, WLS_SOA2 and WLS_BAM1 servers.
Therefore, perform the following steps:
connect soa_leasing/welcome1@GSOAPD3
@leasing.ddl
connect bam_leasing/welcome1@GSOAPD3
@leasing.ddl
Installation steps120
SOA_cluster
- Click Multi Data Sources. The Summary of JDBC Multi Data Source page
appears.
- Click New. The Create a New JDBC Multi Data Source page appears.
- Click New.
- Click Next.
- Click Next.
- Click Next.
- Click Next.
- Click Next.
- Enter the service name, database name, host port, and password for your
leasing schema.
- Click Next.
- Click Multi Data Sources. The Summary of JDBC Multi Data Source page
appears.
Installation steps121
SOA_cluster
- Click New. The Create a New JDBC Multi Data Source page appears.
- Click New.
- Click Next.
- Click Next.
- Click Next.
- Click Next.
- Click Next.
- Enter the service name, database name, host port, and password for your
leasing schema.
- Click Next.
Interface=eth0
NetMask=255.255.255.128
UseMACBroadcast=true
Kill and restart Node Manager (this procedure is described earlier in the document)
Grant sudo privilege to the soaadmin user with no password restriction, and grant
execute privilege on the /sbin/ifconfig and /sbin/arping binaries. Make sure the script is executable by the soaadmin
Installation steps122
SOA_cluster
user. The following is an example of an entry inside /etc/sudoers granting sudo execution privilege for soaadmin and
also over ifconfig and arping:
- Click Save
- Click Save
- In the Available field, select xgsoapd5b.ea.com machine and click the right
arrow
- Select Automatic Server Migration Enabled. This enables the Node Manager
to start a failed server on the target node automatically.
- Click Save
- In the Available field, select xgsoapd5a.ea.com machine and click the right
arrow
- Click Save
Set the candidates machines for WLS_BAM1 server migration. You don’t need to do
it for WLS_BAM2 server.
Installation steps123
SOA_cluster
- In the Available field, select xgsoapd5b.ea.com machine and click the right
arrow
- Select Automatic Server Migration Enabled. This enables the Node Manager
to start a failed server on the target node automatically.
- Click Save
Login to the Admin Console. Go to the Summary of Servers and click on Customize
this table link. Add “Current Machine” column to the list of chosen columns to display and apply the changes. This
would enable you to see which machine a server runs on at the moment.
You can test automatic server migration using the following algorithm
- Find the process number for the managed server you are testing
- Wait for 30 seconds, find the new process number for the same server
(restarted by node manager) and kill it with -9 option again
Note that when you stop a managed server with Automatic Server Migration enabled
from the Admin Console, Node Manager brings the VIP interface the server is listening on down. It will also
automatically bring it up when you order to start the server.
Installation steps124
SOA_cluster