Installation of Oracle SOA 11g and related components on SOA_cluster

Contents
DOCUMENT CONTROL ................................................................................................... ERROR! BOOKMARK NOT DEFINED. INTRODUCTION ...................................................................................................................................................................... 1 SERVERS CONFIGURATION BEFORE INSTALLATION................................................................................................................ 2 xgsoapd5a server .................................................................................................................................................................. 2
Operating System Details .......................................................................................................................................................................... 2 Server Details............................................................................................................................................................................................ 2
xgsoapd5b server .................................................................................................................................................................. 2

Operating System Details .......................................................................................................................................................................... 2 Server Details............................................................................................................................................................................................ 2
Database details ................................................................................................................................................................... 2 INSTALLATION STEPS ............................................................................................................................................................. 3 Prepare JRE environment .................................................................................................................................................... 3 Run Repository Creation Utility (RCU)................................................................................................................................ 3 Install Weblogic Server ...................................................................................................................................................... 14 Install SOA Suite ................................................................................................................................................................ 21 Create Weblogic Domain ................................................................................................................................................... 28 Extend the Domain for SOA Components .......................................................................................................................... 46 Installing Oracle HTTP Server........................................................................................................................................... 60 Extend the Domain to Include BAM ................................................................................................................................... 72 Upgrade Weblogic Server to version 10.3.3 ....................................................................................................................... 84 Upgrade SOA to version 11.1.1.3 ....................................................................................................................................... 89 Patch SOA environment ..................................................................................................................................................... 93 Prepare for AIA 11g FP Installation .................................................................................................................................. 94 AIA 11g FP Installation ..................................................................................................................................................... 96 AIA 11g FP PS2 application ............................................................................................................................................ 113 Configure Automatic Server Migration ............................................................................................................................ 120
Introduction
This document contains steps performed for installation of Oracle SOA 11g to EA production environment.
Introduction 1 SOA_cluster
Servers Configuration Before installation

xgsoapd5a server
Operating System Details
Hostname Operating System Server Details
xgsoapd5A.ea.com RHEL 5.3 64-bit
ORACLE_BASE
/opt/fusion
xgsoapd5b server
Operating System Details
Hostname Operating System Server Details
xgsoapd5b.ea.com RHEL 5.3 64-bit
ORACLE_BASE
/opt/fusion
Database details
Oracle DB Version Hostnames Service Name
10.2.0.4
npddbsrv2.ea.com; npddbsrv3.ea.com GSOAPD3
Servers Configuration Before installation 2 SOA_cluster
Installation steps
Prepare JRE environment
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 Change permission for the executable file: chmod 764 jrmc-4.0.0-1.6.0-linux-x64.bin Run the following command: ./jrmc-4.0.0-1.6.0-linux-x64.bin Enter new Product Installation Directory when asked in a command prompt: /opt/fusion/fmw/jrmc-4.0.0-1.6.0 cd /opt/fusion/fmw ln -s jrmc-4.0.0-1.6.0 java Answer No on question to install Demos and Samples Answer No on question to install Source Code Create a symbolic link java in the /opt/fusion/fmw directory: Unzip the file Create a middleware home directory:
Run Repository Creation Utility (RCU)

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. The RCU 11.1.1.2.1 utility is available to download from www.oracle.com site (ofm_rcu_win32_11.1.1.2.1_disk1_1of1.zip). It creates a repository for SOA metadata and SOA composite instances. Run this utility on any Windows workstation connecting to the database. Unzip the file Run rcu.bat
Installation steps 3 SOA_cluster
Choose Create
sysdba role
Specify connection to one of the database nodes and connect as a system user with a
You can safely ignore the following warning if you get one:
Click OK to continue:
AS Common Schemas
Specify AIA prefix and choose the following schemas to create
SOA and BPM Infrastructure -
Metadata Services
SOA Infrastructure Business Activity Monitoring User Messaging Service
Click OK to continue:
Use the same password for all schemas:
Click on Manage Tablespaces button:
Click on each of the tablespaces with AIA prefix and edit data file as required:
Click OK button when finished with all tablespace Then click Close button:
Click on Create button. Observe repository creation:
Click Close when finished:
Login to the database as a user with admin privileges and add the following grants: grant select on sys.dba_pending_transactions to aia_soainfra; grant force any transaction to aia_soainfra;
Install Weblogic Server

Oracle SOA Suite runs on Oracle WebLogic Server. You must install Oracle WebLogic Server on every cluster node before you install Oracle SOA Suite. Download WLS 10.3.2 installer from edelivery.oracle.com (V18594-01.zip). Perform installation of the Weblogic Server on both nodes of the cluster as per following steps: Unzip downloaded file Run the installer from the directory where you unzipped it: /opt/fusion/fmw/java/bin/java -jar wls1032_generic.jar Click Next on Welcome screen
Enter Middleware home directory and press Next
Enter Yes for the warning (you already have JRE in you Middleware Home )
Clear Security Updates checkbox:
Choose Custom install type
Review the screen:
Review JDK selection
Review Product Installation Directories
Review Installation Summary
Observe installation
Clear Run Quickstart checkbox and press Done button:
Install SOA Suite

Use the installer to install Oracle SOA Suite. Download SOA 11.1.1.2 installer from edelivery.oracle.com (V18622-01.zip). 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: Unzip downloaded file Run the installer from the directory where you unzipped it: ./runInstaller -jreLoc /opt/fusion/fmw/java 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.
You will receive the following screen at which point you should execute the requested script with root privileges and click OK upon execution.
Click Next on Welcome screen
Observe prerequisite checking. Failure here might indicate a missing Linux package:
as soa
Specify Oracle Middleware Home as /opt/fusion/fmw and Oracle Home Directory
Review Installation Summary
Observe the progress
Click Next when Progress reaches 100%
Click Finish
Create Weblogic Domain

According to the Oracle recommended approach, we configure soa_domain in a modular fashion. We run configuration wizard 3 times: To install the Administration Server, Enterprise Manager and WSM-PM To install the SOA components To install the BAM components 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
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 its 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): eth0:1 Link encap:Ethernet HWaddr 00:0C:29:AD:53:B4 inet addr:10.50.131.44 Bcast:10.50.131.255 Mask:255.255.255.128 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 If the address is not present, enable it on a free eth0:N interface. Here is an example: sudo /sbin/ifconfig eth0:1 10.50.131.44 netmask 255.255.255.128 Enable your network to register the new location of the virtual IP, for example: sudo /sbin/arping -q -U -c 3 -I eth0 10.50.131.44
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 Follow the steps: In the Welcome screen, select Create a New WebLogic Domain, and click Next.
Select the following products: Oracle Enterprise Manager Oracle WSM Policy Manager Oracle JRF
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 domains administrator:
JDK screen:
Select Production Mode and available JDK in the Configure Server Start Mode and
In the Configure JDBC Components Schema screen, do the following:

Installation steps 32
SOA_cluster
schemas in the next panel -
Select the OWSM MDS schema Select Configure selected component schemas as RAC multi data source
Click Next
this screen, do the following: -
The Configure RAC Multi Data Sources Component Schema screen is displayed. In
Enter values for the Driver, Service Name, Username and Password, specifying the connect information for the RAC database that was seeded with RCU Enter the host name, instance name, and port Click Add Repeat this for each RAC instance Click Next
Observe automatic JDBC connection testing and click Next: Select Administration Server; Managed Servers, Clusters and Machines; Deployments and Services. Click Next:
7001 as a Listen Port
Enter AdminServer as a Name, VIP3 (xgsoapd5v3.ea.com) as a Listen Address and
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:
In the Configure Clusters screen, Click Add to add WSM-PM_Cluster:
servers to WSM-PM_Cluster
In the Assign Servers to Clusters screen, assign WLS_WSM1 and WLS_WSM2
Add machines listening on physical hostnames:
In the Assign Servers to Machines screen, assign WLS_WSM1 and AdminServer to host1 machine and WLS_WSM2 server to host2 machine:
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.
In the Target Services to Clusters or Servers screen, select the following: On the left, select WSM-PM_Cluster. On the right, select JDBC System Resource (this automatically selects all the wsm datasources (mds-owsm)) On the left, select AdminServer. On the right, select JDBC System Resource (this automatically selects all the wsm datasources (mds-owsm)). Note: All JDBC system resources should be targeted to both the Admin Server and WSM-PM_Cluster.
On the left, select WSM-PM_Cluster. On the right, select JOC-Shutdown, JOC-Startup, and OWSM Startup Class. On the left, select AdminServer. On the right, deselect JOC-Shutdown and JOC-Startup. Make sure these services are not targeted to the Admin Server. 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
In the Configuration Summary screen, click Create
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.
Make sure you have domain directories created in a file system 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 ./pack.sh -managed=true -domain=/11g/admin/soa_domain/aserver/soa_domain -template=soadomaintemplate.jar template_name=soa_domain_template ./unpack.sh -domain=/11g/admin/soa_domain/node1/mserver/soa_domain -template=soadomaintemplate.jar Start Admin Server and verify it.
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
Create boot.properties file with username and password pair in /11g/admin/soa_domain/aserver/soa_domain/servers/AdminServer/security directory. Create the directory if it doesnt exist.
state:
Start the Admin Server in nohup mode and monitor it until it reaches RUNNING
cd /11g/admin/soa_domain/aserver/soa_domain/bin nohup ./startWebLogic.sh > AdminServer.log & tail -f AdminServer.log In a browser, go to http://xgsoapd5v3.ea.com:7001/console, log in as Administrator. Verify that WLS_WSM1 and WLS_WSM2 servers are listed. Verify that WLS-PM_Cluster is listed. Check that you can access Oracle Enterprise Manager at http://xgsoapd5v3.ea.com:7001/em Apply JRF Template to WSM-PM_Cluster ( or server in non-clustered installation type ). Login to OEM Fusion Middleware Control, expand Farm_soa_domain, WebLogic domain, soa_domain, then select WSM-PM_Cluster. Click Apply JRF Template on the right. Wait for the confirmation message to appear. 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. Start Node Manager on the first 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 Edit nodemanager.properties to ensure that it contains the following properties: StartScriptEnabled=true StopScriptEnabled=true SecureListener=false cd /opt/fusion/fmw/wlserver_10.3/server/bin nohup ./startNodeManager.sh > NodeManager.log & Start WLS_WSM1 server from Weblogic Admin Console, validate it by accessing http://xgsoapd5a.ea.com:7003/wsm-pm and clicking Validate Policy Manager. Propagate the Domain Configuration to a directory for a second managed server: 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 ./unpack.sh -domain=/11g/admin/soa_domain/node2/mserver/soa_domain -template=soadomaintemplate.jar Disable Host Name Verification for WLS_WSM2 server by setting Hostname Verification to None in SSL tab (Advanced section) for the server in Weblogic Admin Console
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 Edit nodemanager.properties to ensure that it contains the following properties: StartScriptEnabled=true StopScriptEnabled=true SecureListener=false cd /opt/fusion/fmw/wlserver_10.3/server/bin nohup ./startNodeManager.sh > NodeManager.log &
Start WLS_WSM2 server from Weblogic Admin Console, validate it by accessing http://xgsoapd5b.ea.com:7003/wsm-pm and clicking Validate Policy Manager. Configure the Java Object Cache (JOC) for Oracle WSM: Connect to the Administration Server using WLST: /opt/fusion/fmw/soa/common/bin/wlst.sh connect() Enter Administrator username, password and URL for Admin Server when prompted
Run the following script: execfile('/opt/fusion/fmw/oracle_common/bin/configure-joc.py') Enter Hostnames: xgsoapd5a.ea.com,xgsoapd5b.ea.com 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. Exit with exit() command.
Extend the Domain for SOA Components

In this step we extend the domain created in a previous chapter. Stop all the servers Enable VIPs for SOA managed servers (xgsoapd5v1.ea.com and xgsoapd5v2.ea.com). For example,
On a first node: sudo /sbin/ifconfig eth0:3 10.50.131.41 netmask 255.255.255.128 sudo /sbin/arping -q -U -c 3 -I eth0 10.50.131.41 On a second node: sudo /sbin/ifconfig eth0:1 10.50.131.43 netmask 255.255.255.128 sudo /sbin/arping -q -U -c 3 -I eth0 10.50.131.43 Change directory to the location of the Configuration Wizard: cd /opt/fusion/fmw/soa/common/bin ./config.sh Select Extend an existing Weblogic domain, and click Next Start the configuration wizard
Select the Weblogic domain directory for admin server, and click Next
Select Oracle SOA Suite 11.1.1.0. Click Next.
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:
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:
automatically. Click Next:
In the Test JDBC Data Sources screen, the connections should be tested
In the Select Optional Configuration screen, select Managed Servers, Cluster and Machines, and then Deployment and services. Click Next:
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:
In the Configure Clusters screen, add SOA_Cluster:
to SOA_Cluster:
In the Assign Servers to Clusters screen, assign WLS_SOA1 and WLS_SOA2 servers
In the Configure Machines screen, add xgsoapd5a.ea.com and xgsoapd5b.ea.com machines as per following picture:
Assign WLS_SOA1 server to xgsoapd5a.ea.com and WLS_SOA2 server to xgsoapd5b.ea.com respectfully:
only to SOA_Cluster
In the Target Deployments to Clusters or Servers screen, ensure the following: usermessagingserver and usermessagingdriver-email should be targeted
targeted only to SOA_Cluster PM_Cluster
The oracle.rules.*, oracle.sdp.*, and oracle.soa.* libraries should be
The wsm-pm application should be targeted only to WSM-PM_Cluster The oracle.wsm.seedpolicies library should be targeted only to WSM-
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
mds-owsm* are targeted to both WSM-PM_Cluster and AdminServer
In the Configuration Summary screen click Extend
Click Done on the last screen. Start the AdminServer Set the following arguments for WLS_SOA1 server in the Configuration/Server Start tab for WLS_SOA1 server in the Weblogic Admin Console: -Xms2048m -Xmx2048m -Xgcprio:throughput -Duser.timezone=PST Dtangosol.coherence.wka1=xgsoapd5v1.ea.com -Dtangosol.coherence.wka2=xgsoapd5v2.ea.com Dtangosol.coherence.localhost=xgsoapd5v1.ea.com
Set the following arguments for WLS_SOA2 server in the Configuration/Server Start tab for WLS_SOA2 server in the Weblogic Admin Console: -Xms2048m -Xmx2048m -Xgcprio:throughput -Duser.timezone=PST Dtangosol.coherence.wka1=xgsoapd5v2.ea.com -Dtangosol.coherence.wka2=xgsoapd5v1.ea.com Dtangosol.coherence.localhost=xgsoapd5v2.ea.com
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 /opt/fusion/fmw/java/bin/java weblogic.WLST /opt/fusion/fmw/soa/bin/soa-createUDD.py --domain_home /11g/admin/soa_domain/aserver/soa_domain --soacluster SOA_Cluster Restart the Admin Server. Verify that the following JMS modules are listed in the admin console:
SOAJMSModuleUDDs UMSJMSSystemResource
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 Propagate the domain changes to Managed Server domain directory cd /opt/fusion/fmw/oracle_common/common/bin ./pack.sh -managed=true -domain=/11g/admin/soa_domain/aserver/soa_domain template=soadomaintemplateExtSOA.jar -template_name=soa_domain_templateExtSOA ./unpack.sh -domain=/11g/admin/soa_domain/node1/mserver/soa_domain -overwrite_domain=true template=soadomaintemplateExtSOA.jar -app_dir=/11g/soadata/soa_domain/apps Console Validate WLS_WSM1 and WLS_SOA1 servers by accessing the following URLs: 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 Copy soadomaintemplateExtSOA.jar created with pack utility to the same folder on a second node. Propagate the Domain Configuration on xgsoapd5b: cd /opt/fusion/fmw/oracle_common/common/bin ./unpack.sh -domain=/11g/admin/soa_domain/node2/mserver/soa_domain -overwrite_domain=true template=soadomaintemplateExtSOA.jar -app_dir=/11g/soadata/soa_domain/apps Extract the Xengine files on a second node of the cluster (xgsoapd5b) cd /opt/fusion/fmw/soa/soa/thirdparty/edifecs tar -xzvf XEngine.tar.gz URLs: http://xgsoapd5v2.ea.com:7004/soa-infra http://xgsoapd5v2.ea.com:7004/b2bconsole http://xgsoapd5v2.ea.com:7004/integration/worklistapp Configure a Shared JMS Persistent store Create directories on a shared volume: mkdir /11g/admin/soa_domain/SOA_Cluster mkdir /11g/admin/soa_domain/SOA_Cluster/jms mkdir /11g/admin/soa_domain/SOA_Cluster/tlogs
Start WLS_WSM1, WLS_WSM2, WLS_SOA1 servers from Weblogic Admin
Start WLS_SOA2 server from Weblogic Admin Console and validate the following
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
Save and Activate changes Configure a Default Persistence Store for Transaction Recovery 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 Restart all servers
Installing Oracle HTTP Server

Download Web utilities installer from edelivery.oracle.com (V18757-01.zip). Perform installation of the Weblogic Server on both nodes of the cluster as per following steps: Unzip downloaded file Run the installer from the directory where you unzipped it: ./runInstaller -jreLoc /opt/fusion/fmw/java Answer y on a question to continue after check for display colors failure Click Next on Welcome screen
In the Select Installation Type screen, select Install and Configure, and click Next
Next
In the Prerequisite Checks screen, ensure that all the prerequisites are met, then click
web
Set Oracle Middleware Home to /opt/fusion/fmw and Oracle Home Directory to
Select only Oracle Http Server in the Configure Components screen:
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:
Leave Auto Port Configuration checkbox checked in Configure Ports screen:
Uncheck security updates checkbox and answer Yes for the alert:
Click Install in the Installation Summary screen:
Observe progress
Click Next when Configuration Progress screen reaches 100% Click Finish on the Installation Complete screen Modify httpd.conf files on both servers. You can find it in the /11g/admin/ohs_instance1/config/OHS/ohs1 folder on the first node: 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> # Admin Server and EM
<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>
# SOA soa-infra app <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
<Location /sdpmessaging/userprefs-ui > SetHandler weblogic-handler WebLogicCluster xgsoapd5v1.ea.com:7004,xgsoapd5v2.ea.com:7004 </Location> # Default to-do taskflow <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> #Required if attachments are added for workflow tasks <Location /ADFAttachmentHelper> SetHandler weblogic-handler WebLogicCluster xgsoapd5v1.ea.com:7004,xgsoapd5v2.ea.com:7004 </Location> # SOA composer application <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
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
# Admin Server and EM <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
</Location> </VirtualHost> Restart HTTP Servers 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. Validate access through http servers:
Extend the Domain to Include BAM

In this step we extend the domain created in a previous chapter. Stop all the servers Enable VIP for WLS_BAM1 managed server (xgsoapd5v4.ea.com). For example: sudo /sbin/ifconfig eth0:4 10.50.131.45 netmask 255.255.255.128 sudo /sbin/arping -q -U -c 3 -I eth0 10.50.131.45 Change directory to the location of the Configuration Wizard: cd /opt/fusion/fmw/soa/common/bin ./config.sh Select Extend an existing Weblogic domain, and click Next Start the configuration wizard
Click Next
Select /11g/admin/soa_domain/aserver/soa_domain as WebLogic Domain Directory.
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:
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.
and Services
Select checkboxes for Managed Servers, Clusters and Machines and for Deployments
Add WLS_BAM1 server listening on xgsoapd5v4.ea.com on port 7005 and WLS_BAM2 server listening on xgsoapd5b.ea.com on port 7005 in the Configure managed Servers screen. Click Next. Add the BAM_Cluster in the Configure Clusters screen and click Next:
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. Assign WLS_BAM1 to xgsoapd5a.ea.com machine and WLS_BAM2 to xgsoapd5b.ea.com machine. Click Next.
SOA_cluster
In the Target Deployments to Clusters or Servers screen, ensure the following: usermessagingserver and usermessagingdriver-email should be targeted only to SOA_Cluster and BAM_Cluster WSM-PM should be targeted only to WSM-PM_Cluster The DMS Application should be targeted to BAM_Cluster, SOA_Cluster, WSM-PM_Cluster and Admin Server
The oracle.rules.*, oracle.sdp.* deployments should be targeted to SOA_Cluster and BAM_Cluster. The oracle.soa.* deployments should be targeted only to SOA_Cluster. The oracle.wsm.seedpolicies library should be targeted only to the WSMPM_Cluster
oracle.bam is targeted only to BAM_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
mds-owsm, mds-owsm-rac0, and mds-owsm-rac1 should be targeted to both WSM-PM_Cluster and AdminServer mds-soa, mds-soa-rac0, and mds-soa-rac1 should be targeted to both SOA_Cluster and AdminServer
OraSDPMDatasource, OraSDPMDatasource-rac0, and OraSDPMDatasource-rac1 should be targeted to both SOA_Cluster and BAM_Cluster
In the Configuration Summary screen click Extend
Click Done in the Creating Domain screen
Start the AdminServer cd /11g/admin/soa_domain/aserver/soa_domain/bin nohup ./startWebLogic.sh > AdminServer.log &
WLS_BAM1 server:
You must run the soa-createUDD.py script using WLST before you can start the
. /11g/admin/soa_domain/aserver/soa_domain/bin/setDomainEnv.sh /opt/fusion/fmw/java/bin/java weblogic.WLST /opt/fusion/fmw/soa/bin/soa-createUDD.py --domain_home /11g/admin/soa_domain/aserver/soa_domain --bamcluster BAM_Cluster extend=true Restart the Admin Server. 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. The first module subdeployment should be targeted to SOAJMSServer_auto_1 and SOAJMSServer_auto_2 The second module subdeployment should be targeted to UMSJMSServer_auto_1 and UMSJMSServer_auto_2 The third module subdeployment should be targeted to BAMJMSServer_auto_1 and BAMJMSServer_auto_2 The forth module subdeployment should be targeted to UMSJMSServer_auto_3 and UMSJMSServer_auto_4 Configure a JMS Persistence Store for BAM UMS: Using Weblogic Admin Console, expand Services, and then click on Persistent Stores node. Enter the following location for UMSJMSFileStore_auto_3 and UMSJMSFileStore_auto_4 existing store: /11g/admin/soa_domain/SOA_Cluster/jms and enter the following directory path: /11g/admin/soa_domain/SOA_Cluster/tlogs Save Untargeting the BAM Server System from WLS_BAM2 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:
Component Type Target
Save and Activate changes Configure a Default Persistence Store for Transaction Recovery Using Weblogic Admin Console, visit Services tab for WLS_BAM1 server
Component oracle-bam(11.1.1) /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 OracleBAM OracleBAMWS sdpmessagingclient-ejb.jar
Type Enterprise Application WEBAPP EJB EJB EJB EJB EJB WEBAPP WEBAPP EJB
Target BAM_Clu ster WLS_BA M1 WLS_BA M1 WLS_BA M1 WLS_BA M1 WLS_BA M1 WLS_BA M1 BAM_Clu ster BAM_Clu ster WLS_BA M1
Propagate the domain changes to Managed Server domain directory cd /opt/fusion/fmw/oracle_common/common/bin ./pack.sh -managed=true -domain=/11g/admin/soa_domain/aserver/soa_domain template=soadomaintemplateBAM.jar -template_name=soa_domain_templateBAM ./unpack.sh -domain=/11g/admin/soa_domain/node1/mserver/soa_domain -overwrite_domain=true template=soadomaintemplateBAM.jar -app_dir=/11g/soadata/soa_domain/node1/apps 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 ./unpack.sh -domain=/11g/admin/soa_domain/node2/mserver/soa_domain -overwrite_domain=true template=soadomaintemplateBAM.jar -app_dir=/11g/soadata/soa_domain/node2/apps
Disable Host Name Verification for WLS_BAM1 and WLS_BAM2 servers by setting Hostname Verification to None in SSL tab (Advanced section) for the servers in Weblogic Admin Console 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
URL:
Start WLS_BAM2 server from Admin Console and verify access to the following
http://xgsoapd5b.ea.com:7005/OracleBAM Configure the BAM Web Applications to Use the BAM Server in BAMHOST1 Access Oracle Enterprise Manager Fusion Middleware Control through http://xgsoapd5.ea.com:7777/em 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 Repeat the same for OracleBamWeb(WLS_BAM2). Configure ADC Server to Use the Appropriate BAMServer Address
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. Restart WLS_BAM1 and WLS_BAM2 servers from the Admin Console. in IE browser: http://xgsoapd5v4.ea.com:7005/OracleBAM http://xgsoapd5b.ea.com:7005/OracleBAM http://xgsoapd5.ea.com:7777/OracleBAM Validate access to OracleBAM by logging in as weblogic user to the following URLs
Upgrade Weblogic Server to version 10.3.3

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: (p9618487_1033_Generic.zip) Unzip the file Run the installer from the folder where you unzipped it to: /opt/fusion/fmw/java/bin/java -jar wls1033_upgrade_generic.jar Stop all servers on both nodes and do not start them before SOA upgrade is done. Download WLS 10.3.3 upgrade installer from support.oracle.com
Click Next on Welcome screen
Use an existing Middleware Home /opt/fusion/fmw. Click Next
Uncheck security updates emails checkbox and confirm Yes on notification.
Review chosen Products and Components and click Next
Review Product Installation Directories and click Next
Uncheck Run Quickstart checkbox and click Done:
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) failure. ./runInstaller jreLoc /opt/fusion/fmw/java Click Next on the Welcome screen Run installer and answer y on a question to continue after display colors check
Set Oracle Middleware Home to /opt/fusion/fmw and Oracle Home Directory to soa
Review Installation Summary and click Install:
Click on Next when progress reaches 100%
Click Finish on the Installation Complete screen:
cd /opt/fusion/fmw/soa/bin
Run a Path Set Assistant on one of the cluster nodes:
./psa -dbType Oracle -dbConnectString '//soadrdb2-v.ea.com:1521/GSOAPD3' -dbaUserName system schemaUserName AIA_SOAINFRA 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 http://xgsoapd5.ea.com:7777/OracleBAM (in IE browser)
Patch SOA environment

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 Perform the following steps on both nodes of the cluster: Stop all managed servers and leave the AdminServer running 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 Verify OUI inventory /opt/fusion/fmw/soa/OPatch/opatch lsinventory Find a Node manager process with ps -ef | grep NodeMan and kill it Modify Node Manager properties file /opt/fusion/fmw/wlserver_10.3/common/nodemanager/nodemanager.properies by ensuring the following parameters present: StartScriptEnabled=true StopScriptEnabled=true
Start the Node Manager cd /opt/fusion/fmw/wlserver_10.3/server/bin nohup ./startNodeManager.sh > NodeManager.log &
Unzip p9822892_111130_Generic.zip patch into a separate folder and run the following command from there: /opt/fusion/fmw/soa/OPatch/opatch apply auto The user would be interviewed for the following input:
AdminUser
: Please enter the WebLogic Admin Server username
AdminPassword : Please enter the WebLogic Admin Server password AdminServerURL : Please enter the WebLogic Admin Server URL DomainHome : Please enter the WebLogic domain directory location
ApplicationsDir : Please enter /opt/fusion/fmw/soa/soa/applications 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 Verify the Health of soa-infra deployment in Weblogic Admin Console Perform environment validation by accessing the following URLs: 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
Prepare for AIA 11g FP Installation

There are installation prerequisites that you have to meet before installing AIA 11g PS2 Foundation Pack. Perform the following steps: 01.zip) Unzip it to a separate folder. Download AIA 11G PS2 patch from support.oracle.com (p9717829_111120_Generic.zip) Unzip the patch to a separate folder Download AIA 11G PS1 Foundation Pack from edelivery.oracle.com (V20956-
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
Run the following script from the <Patch File location>/files/patch_9717829/files: ant -f UpdateInstaller.xml -DInstallerLocation=<Location where the Installer zip is unzipped> . For example: cd /opt/fusion/software/9717829/files/patch_9717829/files ant -f UpdateInstaller.xml -DInstallerLocation=/opt/fusion/software/AIA
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 Run nmEnroll([domainDir], [nmHome]). You would have to do that twice on node1 for two existing domain homes and once on node2. Like this: 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) Second node (dont forget to run wlst.sh from a second node): 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" For example, in the /11g/admin/soa_domain/aserver/soa_domain/bin/setDomainEnv.sh file for the AdminServer domain directory
cd /opt/fusion/fmw/soa/bin
Restart the AdminServer Increase Memory to Avoid Compilation Errors:
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:
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 Restart SOA servers Create the following directories: 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
AIA 11g FP Installation

Perform the following steps: failure. ./runInstaller -invPtrLoc /opt/fusion/fmw/soa/oraInst.loc -jreloc /opt/fusion/fmw/java Click Next on the Welcome screen Navigate to cd/Disk1 directory inside of your AIA installation directory location Run installer and answer y on a question to continue after display colors check
screen
Click Next when Prerequisites Checks would be 1005 completed on the following
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:
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:
Press OK confirming nodemanager user password for both machines:
Press Next on SOA Server Validation screen if you dont 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.
Enter jdbc:oracle:thin:@soadrdb2-v.ea.com:1521/GSOAPD3 as MDS Repository URL, AIA_MDS as MDS Username. Click Next
Leave Oracle Enterprise Repository Details empty and click Next:
Review Installation Summary and click Install:
Observe Installation Progress
Observe Configuration Progress
Make sure it is 100% complete. Its a long process. Then click Next:
Click Finish:
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 Modify LifeCycleDataSource-rac0 and LifeCycleDataSource-rac1 data sources in the admin console. Go to the Connection Pool tab and set the following settings: Initial Capacity Maximum Capacity Capacity Increment Statement Cache Size 200 900 20 50 10
Inactive Connection Timeout 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
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 Add the following log handlers: <log_handler name='aia-log-error-handler' class='oracle.core.ojdl.logging.ODLHandlerFactory' level='TRACE:32'> <property name='format' value='ODL-XML'/> <property name='path' value='/11g/admin/soa_domain/node1/mserver/soa_domain/servers/WLS_SOA1/logs/aiaerror.log'/> <property name='maxFileSize' value='10485760'/> <property name='maxLogSize' value='104857600'/> </log_handler>
<log_handler name='aia-log-trace-handler' class='oracle.core.ojdl.logging.ODLHandlerFactory' level='TRACE:32'> <property name='format' value='ODL-XML'/> <property name='path' value='/11g/admin/soa_domain/node1/mserver/soa_domain/servers/WLS_SOA1/logs/aiatrace.log'/> <property name='maxFileSize' value='10485760'/> <property name='maxLogSize' value='104857600'/> </log_handler>
<log_handler name='aia-log-debug-handler' class='oracle.core.ojdl.logging.ODLHandlerFactory' level='TRACE:32'> <property name='encoding' value='UTF-8'/> <property name='path' value='/11g/admin/soa_domain/node1/mserver/soa_domain/servers/WLS_SOA1/logs/aiadebug.log'/> <property name='maxFileSize' value='10485760'/> <property name='maxLogSize' value='104857600'/> </log_handler>
Add the following loggers:

<logger name='oracle.aia.logging.error' level='NOTIFICATION:1' useParentHandlers='false'> <handler name='aia-log-error-handler'/> </logger>
<logger name='oracle.aia.logging.trace' level='NOTIFICATION:1' useParentHandlers='false'> <handler name='aia-log-trace-handler'/> </logger>
<logger name='oracle.aia.logging.debug' level='NOTIFICATION:1' useParentHandlers='false'> <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 Add the following log handlers: <log_handler name='aia-log-error-handler' class='oracle.core.ojdl.logging.ODLHandlerFactory' level='TRACE:32'> <property name='format' value='ODL-XML'/> <property name='path' value='/11g/admin/soa_domain/node2/mserver/soa_domain/servers/WLS_SOA2/logs/aiaerror.log'/> <property name='maxFileSize' value='10485760'/> <property name='maxLogSize' value='104857600'/> </log_handler>
<log_handler name='aia-log-trace-handler' class='oracle.core.ojdl.logging.ODLHandlerFactory' level='TRACE:32'> <property name='format' value='ODL-XML'/> <property name='path' value='/11g/admin/soa_domain/node2/mserver/soa_domain/servers/WLS_SOA2/logs/aiatrace.log'/> <property name='maxFileSize' value='10485760'/> <property name='maxLogSize' value='104857600'/>
</log_handler>
<log_handler name='aia-log-debug-handler' class='oracle.core.ojdl.logging.ODLHandlerFactory' level='TRACE:32'> <property name='encoding' value='UTF-8'/> <property name='path' value='/11g/admin/soa_domain/node2/mserver/soa_domain/servers/WLS_SOA2/logs/aiadebug.log'/> <property name='maxFileSize' value='10485760'/> <property name='maxLogSize' value='104857600'/> </log_handler>
Add the following loggers:
<logger name='oracle.aia.logging.error' level='NOTIFICATION:1' useParentHandlers='false'> <handler name='aia-log-error-handler'/> </logger>
<logger name='oracle.aia.logging.trace' level='NOTIFICATION:1' useParentHandlers='false'> <handler name='aia-log-trace-handler'/> </logger>
<logger name='oracle.aia.logging.debug' level='NOTIFICATION:1' useParentHandlers='false'> <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.
Restart all servers including the AdminServer.
AIA 11g FP PS2 application

Perform the following steps on the first node: 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/ /opt/fusion/fmw/AIA30/OPatch/opatch apply -invPtrLoc $AIA_HOME/oraInst.loc -oh $AIA_HOME . -jre /opt/fusion/fmw/java Delete single node data sources cd /opt/fusion/fmw/AIA30/Infrastructure/Install/AID ant -f AIAInstallDriver.xml -DDeploymentPlan=$AIA_HOME/patch_9717829/files/DeleteDataSourceDP.xml DPropertiesFile=$AIA_INSTANCE/config/AIAInstallProperties.xml Backup and Modify the AIAInstallProperties.xml 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>
<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>
<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>
<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> </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>
<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> </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>
<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> </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>
<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>
</aiademoparticipatingapp> </db>
Execute the following command: ant -f AIAInstallDriver.xml -DDeploymentPlan=$AIA_HOME/patch_9717829/files/CreateMultiDatasourceDP.xml DPropertiesFile=$AIA_INSTANCE/config/AIAInstallProperties.xml Update the Harvester: 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 Restart all servers Validate AIA in the browser. Navigate to AIA Console at http://xgsoapd5.ea.com:7777/AIA . Login as weblogic user. Click on every tab and on About AIA link. Verify Foundation Pack Installation Login to em console at http://xgsoapd5.ea.com:7777/em as weblogic user. Expand Farm_soa_domain, SOA, soa-infra in the left panel. Navigate to Deployed Composites in the main panel and check whether you can view the following composites: AIAB2BErrorHandlerInterface AIAB2BInterface ReloadProcess AIAAsyncErrorHandlingBPELProcess AIAReadJMSNotificationProcess SendNotificationProcess AIAErrorTaskAdministrationProcess
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: Login to the database as a user with sysdba privileges Create leasing tablespaces for SOA and BAM: create tablespace soa_leasing logging datafile '/oradata_gsoapd3/GSOAPD3/data/soa_leasing.dbf' size 32m autoextend on next 32m maxsize 2048m extent management local; create tablespace bam_leasing logging datafile '/oradata_gsoapd3/GSOAPD3/data/osb_leasing.dbf' size 32m autoextend on next 32m maxsize 2048m extent management local; Create leasing users and assign to the leasing tablespace as follows: create user soa_leasing identified by welcome1; grant create table to soa_leasing; grant create session to soa_leasing; alter user soa_leasing default tablespace soa_leasing; alter user soa_leasing quota unlimited on soa_leasing; create user bam_leasing identified by welcome1; grant create table to bam_leasing; grant create session to bam_leasing; alter user bam_leasing default tablespace bam_leasing; alter user bam_leasing quota unlimited on bam_leasing; Create leasing tables using the leasing.ddl script as follows Copy the leasing.ddl file located in the /opt/fusion/fmw/wlserver_10.3/server/db/oracle/920 directory to the node with database access and sqlplus installed. Connect to sqlplus as a leasing user and run a script or copy/paste a create command from the script as an alternative connect soa_leasing/welcome1@GSOAPD3 @leasing.ddl connect bam_leasing/welcome1@GSOAPD3 @leasing.ddl Create SoaLeasing Multi-Data source From Domain Structure window in the Oracle WebLogic Server Administration Console, expand the Services node, then expand the JDBC node
appears. -
Click Multi Data Sources. The Summary of JDBC Multi Data Source page
Click Lock and Edit. Click New. The Create a New JDBC Multi Data Source page appears. Click New. Enter SoaLeasing as the Name Enter jdbc/SoaLeasing as the JNDI name. Select Failover as algorithm (default). Click Next. Select SOA_Cluster as the target. Click Next. Select non-XA driver (the default). Click Next. Click Create New Data Source. Enter SoaLeasing-rac0 as name. Enter jdbc/SoaLeasing-rac0 as JNDI name. Enter oracle as the database type. For the driver type, enter Oracle Driver (Thin) for RAC server-Instance connection Version 10,11. When creating the multi-datasources for the leasing table, enter names in the format of <MultiDS>rac0, <MultiDS>-rac1, and so on. Click Next. Deselect Supports Global Transactions. Click Next. Enter the service name, database name, host port, and password for your leasing schema.
Click Next. Click Test Configuration and verify the connection works. Target the data source to SOA_Cluster. Click Create a New Data Source, SoaLeasing-rac1, target it to SOA_Cluster, and repeat the steps for the second instance of your RAC database. Add created data sources to your multi-data source. Click Activate Changes. Create BamLeasing Multi-Data source From Domain Structure window in the Oracle WebLogic Server Administration Console, expand the Services node, then expand the JDBC node Click Multi Data Sources. The Summary of JDBC Multi Data Source page appears.
Click Lock and Edit.

SOA_cluster
Click New. The Create a New JDBC Multi Data Source page appears. Click New. Enter BamLeasing as the Name Enter jdbc/BamLeasing as the JNDI name. Select Failover as algorithm (default). Click Next. Select BAM_Cluster as the target. Click Next. Select non-XA driver (the default). Click Next. Click Create New Data Source. Enter BamLeasing-rac0 as name. Enter jdbc/BamLeasing-rac0 as JNDI name. Enter oracle as the database type. For the driver type, enter Oracle Driver (Thin) for RAC server-Instance connection Version 10,11. Click Next. Deselect Supports Global Transactions. Click Next. Enter the service name, database name, host port, and password for your leasing schema.
Click Next. Click Test Configuration and verify the connection works. Target the data source to BAM_Cluster. Click Create a New Data Source, BamLeasing-rac1, target it to BAM_Cluster, and repeat the steps for the second instance of your RAC database. Add created data sources to your multi-data source. Click Activate Changes. Add the following properties to /opt/fusion/fmw/wlserver_10.3/common/nodemanager/nodemanager.properties files on both nodes: 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
user. The following is an example of an entry inside /etc/sudoers granting sudo execution privilege for soaadmin and also over ifconfig and arping: soaadmin ALL=NOPASSWD: /sbin/ifconfig,/sbin/arping machines and click the right arrow machines and click the right arrow arrow Select Automatic Server Migration Enabled. This enables the Node Manager to start a failed server on the target node automatically. Click Save Select WLS_SOA2 server in the Admin Console Click the Migration tab In the Available field, select xgsoapd5a.ea.com machine and click the right arrow it for WLS_BAM2 server. Select WLS_BAM1 server in the Admin Console Click the Migration tab Click Save Set the candidates machines for WLS_BAM1 server migration. You dont need to do Select BamLeasing as a Data Source For Automatic Migration Click Save Set the candidates machines for SOA servers migration Select WLS_SOA1 server in the Admin Console Click the Migration tab In the Available field, select xgsoapd5b.ea.com machine and click the right Select SoaLeasing as a Data Source For Automatic Migration Click Save Enable Server Migration for BAM_Cluster Click the BAM_Cluster in Weblogic Admin Console Click the Migration tab In the Available field, select xgsoapd5a.ea.com and xgsoapd5b.ea.com Enable Server Migration for SOA_Cluster Click the SOA_Cluster in Weblogic Admin Console Click the Migration tab In the Available field, select xgsoapd5a.ea.com and xgsoapd5b.ea.com
arrow -
In the Available field, select xgsoapd5b.ea.com machine and click the right
Select Automatic Server Migration Enabled. This enables the Node Manager to start a failed server on the target node automatically. Click Save Activate changes and restart all servers 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 Issue kill -9 command Wait for 30 seconds, find the new process number for the same server (restarted by node manager) and kill it with -9 option again Observe a server being started on a different node 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 of Oracle SOA 11g and related components on SOA_cluster

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Installation of Oracle SOA 11g and related components on SOA_cluster

Transféré par

Droits d'auteur :

Formats disponibles

Contents

xgsoapd5b server .................................................................................................................................................................. 2

Servers Configuration Before installation

Hostname Operating System Server Details

xgsoapd5A.ea.com RHEL 5.3 64-bit

Hostname Operating System Server Details

xgsoapd5b.ea.com RHEL 5.3 64-bit

Oracle DB Version Hostnames Service Name

npddbsrv2.ea.com; npddbsrv3.ea.com GSOAPD3

Servers Configuration Before installation 2 SOA_cluster

Run Repository Creation Utility (RCU)

Installation steps 3 SOA_cluster

Installation steps 4 SOA_cluster

Specify AIA prefix and choose the following schemas to create

Installation steps 5 SOA_cluster

SOA and BPM Infrastructure -

SOA Infrastructure Business Activity Monitoring User Messaging Service

Use the same password for all schemas:

Installation steps 6 SOA_cluster

Click on Manage Tablespaces button:

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

Installation steps 12 SOA_cluster

Click on Create button. Observe repository creation:

Click Close when finished:

Installation steps 13 SOA_cluster

Install Weblogic Server

Installation steps 14 SOA_cluster

Enter Middleware home directory and press Next

Installation steps 15 SOA_cluster

Clear Security Updates checkbox:

Installation steps 16 SOA_cluster

Choose Custom install type

Review the screen:

Installation steps 17 SOA_cluster

Review JDK selection

Review Product Installation Directories

Installation steps 18 SOA_cluster

Review Installation Summary

Installation steps 19 SOA_cluster

Clear Run Quickstart checkbox and press Done button:

Installation steps 20 SOA_cluster

Install SOA Suite

Installation steps 21 SOA_cluster

Click Next on Welcome screen

Installation steps 22 SOA_cluster

Installation steps 23 SOA_cluster

Specify Oracle Middleware Home as /opt/fusion/fmw and Oracle Home Directory

Review Installation Summary

Installation steps 24 SOA_cluster

Observe the progress

Installation steps 25 SOA_cluster

Click Next when Progress reaches 100%

Installation steps 26 SOA_cluster

Installation steps 27 SOA_cluster

Create Weblogic Domain

Installation steps 29 SOA_cluster

Installation steps 30 SOA_cluster

Installation steps 31 SOA_cluster

In the Configure JDBC Components Schema screen, do the following:

The oracle.rules., oracle.sdp., and oracle.soa.* libraries should be