11G Oralce Fusion Middleware SOA Suite Installation and Configuration Guide
By Lokesh TC (
[email protected])
SOA/OSB Installation and Configuration Guide by Lokesh T C
Table of Contents 10
Document Summary ............................................................................................................................................ 5
11
References ........................................................................................................................................................... 5
12
Introduction .......................................................................................................................................................... 6
13
Overview .............................................................................................................................................................. 6
14
Scope ................................................................................................................................................................... 8
15
Prerequisites ........................................................................................................................................................ 9 15.1 Installation Software Required ................................................................................................................... 9 15.2 Hardware ................................................................................................................................................. 10 15.3 Miscellaneous Software ........................................................................................................................... 10 15.4 Operating System Configuration.............................................................................................................. 11 15.4.1 Open File Limit .................................................................................................................................... 11 15.5 Oracle RAC Configuration ....................................................................................................................... 12 15.6 Oracle Account on the RAC Database .................................................................................................... 12 15.7 Unix Groups ............................................................................................................................................. 13 15.8 Unix Accounts .......................................................................................................................................... 13 15.9 User Account Configuration ..................................................................................................................... 13
16
15.9.1
Update .profile for oracle user for all servers as listed below ............................................................. 14
15.9.2
Update timeout configurations ............................................................................................................ 15
Software Installation for Oracle SOA Suite ........................................................................................................ 16 16.1 Pre Installation ......................................................................................................................................... 18 16.1.1 10G and 11G parallel install ............................................................................................................... 19 16.2 JDK 6 Installation (64 bit) ......................................................................................................................... 19 16.2.1
32-bit Installation Instructions ............................................................................................... 19
16.2.2 64-Bit Installation Instructions ............................................................................................... 20 16.3 SOA Repository Schema’s Installation using RCU Tool for core SOA domain ...................................... 21 16.3.1
Environment ................................................................................................................................ 21
16.3.2
Installation Steps ....................................................................................................................... 21
16.3.3
Create user, tablespace and DDL’s for the OSB Cluster ................................................... 28
16.3.4 Create user and tablespace for the JMS Server JDBC Store for SOACoreDomain ...... 29 16.4 SOA Repository Schema’s Installation using RCU Tool for SOA extension domain .............................. 29 16.4.1 Create user and tablespace for the JMS Server JDBC Store for SOAExtDomain ......... 29 16.5 Configuring SOA Schemas for Transactional Recovery Privileges ........................................................ 30 16.6 Drop SOA Repository Schemas using RCU Tool.................................................................................... 31 16.7 Oracle WebLogic Server Installation ....................................................................................................... 32 16.7.1
Installation Steps ....................................................................................................................... 32
16.7.2 Gold Backup of WebLogic Server Installation .................................................................................... 42 16.8 Install Oracle SOA Suite Components for Application Server Middle-Tier .............................................. 43 16.8.1
Installation Steps ................................................................................................................................ 43
16.8.2 Gold Backup of WebLogic Server Installation .................................................................................... 53 16.9 Install OSB Components for SOA Suite .................................................................................................. 53 16.9.1
Installation Steps ................................................................................................................................ 54
16.9.2 Gold Backup of WebLogic Server Installation .................................................................................... 64 16.10 Post Installation Tasks ............................................................................................................................. 65
SOA/OSB Installation and Configuration Guide by Lokesh T C
16.10.1
Extracting the XEngine Files ......................................................................................................... 65
17
Cloning Installation for Oracle SOA Suite .......................................................................................................... 66 17.1 What You Can Clone ............................................................................................................................... 66 17.2 Considerations and Limitations for Cloning ............................................................................................. 67 17.3 Cloning a Middleware Home and All of Its Oracle Homes ...................................................................... 67
18
Domain Configuration for Oracle SOA Suite ..................................................................................................... 69 18.1 Pre-requisites ........................................................................................................................................... 69 18.1.1
Enabling Access to ifconfig and arping Commands ........................................................................... 69
18.1.2 Enable Admin IP Address [Applicable for Cluster] ............................................................................. 70 18.2 Domain Installation and Configuration ..................................................................................................... 70 18.2.1
Cluster based domain creation using WLST Script for “SOACoreDomain” ....................................... 71
18.2.2
Cluster based domain Creation using WLST Script for “SOAExtDomain”. ........................................ 74
18.2.3
Standalone based domain Creation using WLST Script for “SOACoreDomain” ............................... 76
18.2.4 Creating a Separate Domain Directory for Managed Servers in the Same Node as the Administration Server for SOACoreDomain .............................................................................................................................. 78 18.2.5
Propagating the Domain Configuration to all the nodes Using the unpack for SOACoreDomain...... 78
18.2.6 Creating a Separate Domain Directory for Managed Servers in the Same Node as the Administration Server for SOAExtDomain ................................................................................................................................. 79
19
18.2.7
Propagating the Domain Configuration to all the nodes Using the unpack for SOAExtDomain ........ 80
18.2.8
Configure SetDomainEnv.sh [Applicable for standalone and cluster] ................................................ 81
18.2.9
Configure Node Manager [Applicable for standalone and cluster] ..................................................... 81
18.2.10
Enroll the Machine with Node Manager [Applicable standalone and cluster] ............................... 82
18.2.11
Start and test server URL’s ........................................................................................................... 82
Post Configuration Steps ................................................................................................................................... 83 19.1.1
Configure HTTP Front end host and port [Applicable for cluster] ...................................................... 83
19.1.2
Configure SOAP Url and Callback Url [Applicable for cluster] ........................................................... 84
19.1.3
Configure common libraries to the server classpath .......................................................................... 85
19.1.4
Purging SOA Suite 11g Composites Instances (Optional) ................................................................. 85
19.1.5
Improve SOA 11g Purge Performance (Optional) .............................................................................. 88
19.1.6
Create SOA Partitions ........................................................................................................................ 90
19.1.7
Create Application Users .................................................................................................................... 91
19.1.8
Create Application Resources ............................................................................................................ 91
19.1.9
Modify JDBC Datasource Parameters................................................................................................ 94
19.1.10
Migrate from JMS FileStore to JDBC Store ................................................................................... 95
19.1.11
Create TLOG Recovery Folder for migratable servers. ................................................................ 95
19.1.12
Configure Server LogHandler ........................................................................................................ 96
19.1.13
Configuring OSB Memory Threshold parameters ......................................................................... 97
19.1.14
Mapping from 10G to 11G parameters.......................................................................................... 97
19.1.15
Configuring Auto Recovery for Oracle BPEL Process Manager ................................................... 97
19.1.16
Configuring Automatic Recovery Attempts for Invoke and Callback Messages ........................... 98
19.1.17
Setting the global transaction timeout at Weblogic Domain Level ................................................ 98
19.1.18
Overriding the transaction timeout setting for BPEL EJB's ........................................................... 99
19.1.19
Setting Up Node Manager and servers to install Identity and Trust KeyStores ............................ 99
19.1.20
Import Trusted Certificate ............................................................................................................ 105
SOA/OSB Installation and Configuration Guide by Lokesh T C
20
19.1.21
Propogate Admin Server Script/Classpath changes to Managed Server Domain. ..................... 105
19.1.22
Validate Fail Over of Admin Servers [Applicable for Cluster] ...................................................... 105
19.1.23
Take a Middleware and Domain backup [Keep this as a last step]............................................. 107
Middleware environment backup plans............................................................................................................ 107
Appendix A: Design Considerations........................................................................................................................... 108 Appendix B: Servers Start Stop ................................................................................................................................. 109 Appendix C: ................................................................................................................................................................ 114 Appendix E: Component Installation Timing .............................................................................................................. 115
SOA/OSB Installation and Configuration Guide by Lokesh T C
10 Document Summary This document supplies a step by step guide for installing Oracle Fusion Middleware SOA Suite components with high availability specifically for the “Clustered Environment”. This document also provide steps to install and configure 11g for a standalone environment setup. Please note that all the steps that are relevant to standalone installation or configuration are expliclitly stated in the document and document assumes that one needs to selectively choose the steps while installing/configuring the software for standlone setup.
11 References Title
Version
Location
Oracle Fusion Middleware Download, Installation, and Configuration ReadMe
11G Release 1 (11.1.1.5)
http://download.oracle.com/docs/cd/E23104_01/dow nload_readme_ps4/download_readme_ps4.htm
Oracle Fusion Middleware Application Server Install Guide
11G Release 1 (11.1.1)
http://download.oracle.com/docs/cd/E21764_01/inde x.htm
Configuring High Availability for Oracle Fusion Middleware SOA Suite
11G Release 1 (11.1.1)
http://download.oracle.com/docs/cd/E21764_01/core .1111/e10106/ha_soa.htm
All Oracle Fusion Middleware Administration Guide
11G Release 1 (11.1.1)
http://download.oracle.com/docs/cd/E21764_01/nav/ portal_booklist.htm
Oracle Fusion Middleware Complete Requirements
11G
http://download.oracle.com/docs/html/E18558_01/fus ion_requirements.htm
WebLogic Server with Oracle RAC
11G
http://download.oracle.com/docs/cd/E12840_01/wls/ docs103/jdbc_admin/oracle_rac.html
Software Location including clone jar file
11G
/u01/shared/11g/software/11gbin
Domain configuration py files
11G
/u01/shared/11g/wlst
SOA/OSB Installation and Configuration Guide by Lokesh T C
12 Introduction This document supplies a step by step guide for installing Oracle Fusion Middleware SOA/OSB Suite components with high availability in an enterprise deployment. This Installation is intended for all the Clustered Environment(s). The Clustered Environment may span across a single node or multiple nodes of Solaris Platform.
13 Overview An enterprise deployment of Oracle SOA Suite is designed to support large-scale, mission-critical business software applications using SOA components. Here:
The system workload is managed and balanced effectively
Applications continue to operate when resources are added or removed
System maintenance and unexpected failures cause minimal downtime
Installing Oracle SOA Suite components in high availability topologies is a three-step process:
Run 11g (11.1.1.5) RCU to create schemas
Install an application server (Oracle WebLogic Server) using the main installation CD.
Install the Oracle Fusion Middleware 11g (11.1.1.5.0) products that you need from the component CDs.
Oracle WebLogic Application Server Oracle WebLogic Application Server 11g Release 1 (11.1.1.5.0) provides a complete Java 6, Enterprise Edition (J2EE) 5-compliant environment. Oracle SOA Suite It includes Service-Oriented Architecture components: Oracle Service Bus, Oracle BPEL Process Manager, Oracle Mediator, Meta Data Storage Repository, Oracle Business Activity Monitoring, Oracle Rules Service, and Oracle Web Services Manager.
SOA/OSB Installation and Configuration Guide by Lokesh T C
High Availability Topology This diagram details the high availability topology for Oracle SOA Suite components. Refer to Appendix A for design details of the deployment topology.
Oracle DB RAC Cluster MutltiDataSrc/ LB Enabled TNS
Oracle Database RAC Node - 1
SAN Storage Oracle Database RAC Node - 2 Application Server Domain Folders
SOA INFRA/MDS
Two Weblogic DOMAINs DM Zone Solaris Machine 1
Solaris Machine 2
PORT:8006
PORT:8006
OSB1
Solaris Machine 3 OSB CLUSTER
OSB2
PORT:8004
PORT:8004
SOA1
SOA2
PORT:8002
PORT:8002
PORT:9004
SOA Core Cluster
J2EE/WS Cluster
Node Manager
PORT:8004
SOA3
SOA4
PORT:8002
PORT:8002
MS3 SOAX Cluster
Node Manager
PORT:9004
PORT:9004
SOA6
SOA7
Active ADMIN1 Core Server WL Console EM Console
WL Console EM Console
Sun Fire T200, 1 CPU (32 virtual), 1200 MHZ,32GB RAM 2 x 72 (rootdisk) / 2 x 146 (ZFS pool)
Passive ADMIN2 Server WL Console EM Console
SOAExtDomain Coherence WKA Port 9081
Node Manager
PORT:9000
Passive ADMIN1 Server
SOACoreDomain Coherence WKA Port 8081
MS4
Node Manager
PORT:8000 Sun Fire T200, 1 CPU (32 virtual), 1200 MHZ,32GB RAM 2 x 72 (rootdisk) / 2 x 146 (ZFS pool)
OSB4
PORT:8004
SOA5
PORT:8000
PORT:8006
OSB3
MS2
MS1
Solaris Machine 4
PORT:8006
PORT:9000 Sun Fire T200, 1 CPU (32 virtual), 1200 MHZ,32GB RAM 2 x 72 (rootdisk) / 2 x 146 (ZFS pool)
Active ADMIN2 Add. Server WL Console EM Console
Sun Fire T200, 1 CPU (32 virtual), 1200 MHZ,32GB RAM 2 x 72 (rootdisk) / 2 x 146 (ZFS pool)
Fail Over Floating VIP’s OSB VIP’s (Node1,4/ Node2,3)
Admin1 Core Server VIP’s(Node1/Node2)
SOA Core VIP’s (Node1,2,3,4)
J2EE/WS VIP’s (Node2,3/ Node1/4)
SOA Extension(X) VIP’s (Node2/3/4)
Admin2 Additional Server VIP’s (Node3/ Node4)
CISCO Load Balancer (eai.ime.reuters.com) OSB LB
Round Robin to all nodes: 8006
ADMIN 1 Server Round Robin to node1/ node2:8000
SOA Core LB
J2EE/WS
SOA Extension (X)
ADMIN 2 Server
Round Robin to all nodes: 8004
Round Robin to all nodes:8002
Round Robin to node2,node3 & node4:9004
Round Robin to node3/node4:9000
SOA/OSB Installation and Configuration Guide by Lokesh T C
Load Balancer Rules Setting SOACoreDomain <>:80 - Core SOA - all URLs except /em/console/sbconsole <>:8006 - Core OSB <>:8002 - Core WS <>:80 - Core Admin - /em/console
SOAExtDomain <>:80 - Additional SOA - all URLs except /em/console <>:80 - Additional Admin - /em/console
14 Scope The following items are out of scope:-
•
Unix operating system installation and configuration • Shared NFS or CNFS mount point (50GB).
•
Physical network connectivity. This is considered implicit • VIP addresses for all the nodes as per DCHS document • LB related Requirements as per DCHS Architecture document. • Local or SAN storage for application (20GB)
•
Oracle RAC installation, including the SAN configuration
SOA/OSB Installation and Configuration Guide by Lokesh T C
15 Prerequisites The prerequisites are detailed below. For more details refer to documentation - Oracle Fusion Middleware 11G Relase1 (11.1.1.5) Installation Guide.
15.1
Installation Software Required
Download and copy the below list of packages on to your shared storage install-software folder. Table 1 List of Software Packages
Install Item
Description
Version
(1)
JDK-6 (32 bit)
1.6(B 24+)
JDK-6 (64 bit)
CD/ Install Package file
jdk-6u24-solaris-sparc.sh jdk-6u24-solaris-sparcv9.sh
(2)
SOA Oracle Repository Creation Utility
11.1.1.5
(3)
Oracle WebLogic Server
11.1.1.5
(4)
Oracle SOA Suite
11.1.1.5
ofm_rcu_win_11.1.1.5.0_disk1_1of1.zip (Windows) wls1035_generic.jar
ofm_soa_generic_11.1.1.5.0_disk1_1of2.zip ofm_soa_generic_11.1.1.5.0_disk1_2of2.zip
(5)
Oracle OSB
11.1.1.5
(6)
Domain Configuration Scripts
11G
ofm_osb_generic_11.1.1.5.0_disk1_1of1.zip
1) CreateAdditionalSOADomain.py 2) CreateCoreSOADomain.py 3) domain.properties 4) enrollnodemanager.py 5) startAdmin1Server.py 6) startAdmin2Server.py 7) and all scripts for post configuration steps
SOA/OSB Installation and Configuration Guide by Lokesh T C
15.2
Hardware
Table 2 Memory Requirements Unless otherwise noted, Table 1 lists the general minimum memory requirements for Oracle Fusion Middleware products. For the purposes of this document, "minimum available memory" is defined as the amount of physical memory (RAM) and swap memory combined. Operating System
Minimum Physical Memory Required
Minimum Available Memory Required
Solaris
2G
4GB
Table 3 System Availability Note - the Hardware requires being identical in specification for the application servers within the cluster. Refer to Appendix 1 for further details. Unix Solaris Solaris Solaris Solaris Solaris Solaris
System System System System System System
1 2 3 4 5 6
Description
Hardware Version
OS Version
Application Cluster Server 1 Application Cluster Server 2 Application Cluster Server 3 Application Cluster Server 4 Oracle RAC Database Server 1 Oracle RAC Database Server 2
SunFire T2000 Solaris V10 SunFire T2000 Solaris V10 SunFire T2000 Solaris V10 SunFire T2000 Solaris V10 Refer database installation guide Refer database installation guide
Checklist: • • • • • • •
Processor (>1.2GHz) Operating System (Unix/Solaris) Operating type (64 bit) Disk Space (15G) Physical Memory (Min 4G) Browser (IE 7.X) JDK 6 (b24+)
For the other detailed System requirements and specifications we can refer the link below http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-requirements-100147.html
15.3
Miscellaneous Software Table 4 – Software
Unix
Software
Installers PC
Exceed or Xwindows
Locati on
Notes Required for the Application Server install using an X-server
SOA/OSB Installation and Configuration Guide by Lokesh T C
15.4
Operating System Configuration
Table 5 Supported UNIX Operating Systems Reference: http://download.oracle.com/docs/pdf/E18558_01.pdf
Operating System Version
Platform
Supported Packages
Operating System Patches
SUNWarc, SUNWbtool, SUNWhea SUNWlibC, SUNWlibm, SUNWlibms Solaris SPARC64
Solaris 10 Update 4
127111-02
SUNWsprot, SUNWtoo, SUNWi1of
137111-04
SUNWi1cs, SUNWi15cs, SUNWxwfnt
Note before updating the system file consult you Solaris manual. Please read the installation documentation for this section. E.g. updating the /etc/system file must be done indirectly for Solaris 10 Table 6 System Setting Unix System Unix System[1-3] Unix System[1-3]
15.4.1
File /etc/system /etc/hosts
Required setting
crmlt2 crmdev3 RAC1 RAC2
Description Refer to Installation guide Make sure all Unix systems are mentioned in the /etc/hosts file.
Open File Limit
To increase the system resources for the product installed, the ‘maximum file descriptor’ should be set at 4096. Edit the /u01/export/home/oracle/.profile of the oracle user to include the following; ulimit -Hn 4096 ulimit -Sn 4096 This will take effect once the next time the oracle user logs on.
SOA/OSB Installation and Configuration Guide by Lokesh T C
15.5
Oracle RAC Configuration
Oracle RAC/No RAC database is a prerequisite for the installation. The connection information will be required for the installation
Table 7 Oracle RAC Cluster ORACLE_SID
RAC Member hostname
IP Address
Port
Description
RAC1
IP address only needed for adding the entry in the /etc/hosts file
1521
Member 1 of RAC
1521
Member 2 of RAC
RAC2
Other members of the RAC if used
15.6
Oracle Account on the RAC Database
Table 8 INSTANCE (RAC Oracle SERVICE_NAME)
A/C Name
ROLE
Default TableSpace
Description
APPSVR
Connect & DBA
USERS
RAC Login for the Installation schemas etc. Must have DBA privilege
SOA/OSB Installation and Configuration Guide by Lokesh T C
15.7
Unix Groups
Table 9 Env
A/C Name
Grp No
Description
1
dba
Oracle Fusion products group
15.8
Unix Accounts
Table 10 EAI User Account Env
A/C Name
A/C No
Shell
Group
Home Directory
Description
1
oracle
60003
ksh
dba
Home folder /u01/export/home/or acle/
Oracle Application Server 11g install
MWHOME file system /u01/oracle/product/ soa/11g/fmw/ Shared file system for WLSDOMAIN /u01/shared/11g//or acle/fmw/config/admi n/domains Shared file system for software /u01/shared/11g/soft ware Note: • • •
15.9
Shared file system WLSDOAMIN is used for DOMAIN Configuration files (/u01/shared/11g/oracle/fmw/config/admin/domains) 11G installable software is located at /u01/shared/11g/software 11G Application Source Code will be copied to “/u01/shared/11g/software/soa_deploy/code”
User Account Configuration
SOA/OSB Installation and Configuration Guide by Lokesh T C
15.9.1
Update .profile for oracle user for all servers as listed below
Table 11 Oracle 11g Installation and configuration environment variable settings Unix Syste m
File
Example Contents ############################################### # Title : .profile for the Oracle Weblogic Fusion Middleware Application # User # Version : 1 # By : Lokesh T.C # ############################################### #export DISPLAY=:0
SHARED_MOUNT=/u01/shared/11g;export SHARED_MOUNT MWHOME="/u01/oracle/product/soa/11g/fmw";export MWHOME WLSHOME="$MWHOME/wlserver_10.3";export WLSHOME SOAHOME="$MWHOME/Oracle_SOA";export SOAHOME ORACLE_HOME="$MWHOME/Oracle_SOA";export ORACLE_HOME WLSDOMAIN="/u01/shared/11g/oracle/fmw/config/admin/domains";ex
port WLSDOMAIN OSBHOME="$MWHOME/Oracle_OSB";export OSBHOME JAVA_HOME=$MWHOME/jdk1.6.0_24;export JAVA_HOME if [ ! -d "$MWHOME/cacheDir" ] then
mkdir -p $MWHOME/cacheDir fi
Solari s Sys1, 2,3,4
~oracle/.profile
CONFIG_JVM_ARGS=" -Dpython.cachedir=$MWHOME/cacheDir –Xms128m – Xmx512m -XX:PermSize=256m -XX:MaxPermSize=256m Djava.security.egd=file:/dev/./urandom";export CONFIG_JVM_ARGS LD_LIBRARY_PATH=$ORACLE_HOME/lib32:$ORACLE_HOME/opmn/lib:$WLSHOME/ser ver/adr;export LD_LIBRARY_PATH LD_LIBRARY_PATH_64=$LD_LIBRARY_PATH_64:$ORACLE_HOME/lib:$WLSHOME /server/native/solaris/sparc64:$WLSHOME/server/adr;export LD_LIBRARY_PATH_64 PATH=$JAVA_HOME/bin:$PATH:$ORACLE_HOME/bin:$ORACLE_HOME/opmn/bin: $ORACLE_HOME/OPatch:$WLSHOME/server/bin:$WLSHOME/common/bin:$MWH OME/modules/org.apache.ant_1.7.1/bin:$WLSHOME/server/adr;export PATH JAVA_OPTIONS="-DDomainRegistrationEnabled=true";export JAVA_OPTIONS ANT_OPTS="-Xms512m -Xmx1024m -XX:PermSize=512m XX:MaxPermSize=512m";export ANT_OPTS CLASSPATH=$CLASSPATH;export CLASSPATH TMP=/tmp;export TMP PS1="`hostname`:oracle>" unset TMOUT
# Stop the session timeout for the installer
# Added for code export EAI_ENV_TYPE=PROD export EAI_HOME=$SHARED_MOUNT/software/soa_deploy/code
SOA/OSB Installation and Configuration Guide by Lokesh T C
Ensure that the below Shared NFS Mount paths are mounted in all the nodes. If you choose different mount paths for the below variables then ensure that you modify the base path entries in oracle user .profile file. $SHARED_MOUNT=/u01/shared/11g $WLSDOMAIN=”/u01/shared/11g/oracle/fmw/config/admin/domains” Please ensure that you change the variable EAI_ENV_TYPE value as per the environment For ex: NFT, PROD, BLUE, BLUELITE, QA, BLRQA, B2CCQA, DEV, BLRDEV, B2CCDEV etc. 15.9.2
Update timeout configurations To ensure that the install does not timeout the TMOUT parameters in /etc/profile should be disabled. This is done by commenting them out. Edit the file /etc/profile # TMOUT=1800 # readonly TMOUT # export TMOUT This parameter should be changed back to its original setting once install is complete.
SOA/OSB Installation and Configuration Guide by Lokesh T C
16 Software Installation for Oracle SOA Suite The installation involves: •
Installation of JDK 6 (24+) (Please note that the JDK version depends on the SOA Suite Version, check certification guide of installing version of SOA Suite Software)
•
Installation of Client utility RCU in Windows/Linux for creating oracle schema’s for SOA suite (Local PC or at Jump Box)
•
Installation of Oracle WebLogic Server Middleware.
•
Installation of Oracle SOA Suite components for Oracle AS mid-tier.
•
Installation of Oracle OSB component for Oracle AS mid-tier
SOA/OSB Installation and Configuration Guide by Lokesh T C
Overview of an installation topology of SOA/OSB suite on Oracle WebLogic Server /reuters/oracle/ product/soa/11g/fmw
Shared file system NAS/NFS
JDK1.6.0_24
JAVA_HOME
MWHOME
wlserver_10.3
oracle_common
Oracle_SOA
Oracle_OSB
WLSHOME
MWHOME Oracle common
SOAHOME ORACLE_HOME
OSBHOME
modules
SOACoreDomain
/reuters/ shared/11g
/reuters/shared/ 11g/fmw/config/ admin/domains
SHARED_MOUNT
WLSDOMAIN
$SHARED_MOUNT /software/ soa_deploy/code
logs
adminlogs
utils
$WLSDOMAIN /deployplan
coherence_3.6
admin
SOAExtDomain
$WLSDOMAIN /certs
EAI_HOME
SOACoreDomain
aserver
soa_cluster/ tlogs
SOACoreDomain
applications
SOACoreDomain
SOAExtDomain
aserver
SOAExtDomain
soa_cluster/ tlogs
applications
mserver
mserver
SOACoreDomain
SOA/OSB Installation and Configuration Guide by Lokesh T C
SOAExtDomain
applications
SOAExtDomain
applications
The following components will be installed on the all the machines:
Table 13 Machine(s) ALL EAI Application Servers
WebLogic
SOA Suite
OSB
MWHOME/wlserver_10.3
MWHOME/Oracle_SOA
MWHOME/Oracle_OSB
The document will use the following environmental variables which will be used to point to particular directories during the installation process and also for setting up the x-server. Table 14 Environment Variables
Name
Value
HOME
/u01/export/home/oracle/ /u01/oracle/product/soa/11g/f mw $MWHOME/wlserver_10.3
MWHOME WLSHOME SOAHOME OSBHOME WLSDOMAIN JAVA_HOME DISPLAY
Description
Solaris EAI User Home directory Install directory of Oracle middleware binaries Install directory of Oracle Weblogic server $MWHOME/Oracle_SOA The directory of the SOA binaries $MWHOME/Oracle_OSB The directory of the OSB binaries /u01/shared/11g/oracle/fmw/co The directory of the domain nfig/admin/domains configuration – Shared file System $MWHOME/jdk1.6.0_24 The java6 home directory <>:<>
This is to perform remote installation
16.1 Pre Installation 1. Make sure the /etc/hosts is updated. Reference all prerequisites. 2. X-server needs to be run on the installers PC so the appropriate software will be required. 3. Ensure the TMOUT variable is unset. 4. The environment variable entries for the user account oracle must be added to the “.profile” file. 5. The Application Server requires to be running for the start of the Patch install
SOA/OSB Installation and Configuration Guide by Lokesh T C
16.1.1 10G and 11G parallel install In order to successfully install 11G on the system where 10G is also installed one needs to follow the below steps to keep both of them. As necessary one needs to switch back config files back and forth between 10G and 11G. 1. Rename/Back up OraInst.loc and oratab files, which is located in the following directory /var/opt/oracle Example: 1) mv /var/opt/oracle/oratab /var/opt/oracle/oratab10G_<> 2) mv /var/opt/oracle/oraInst.loc/var/opt/oracle/oraInst10G_<>
Note: If we want to upgrade the 10g after 11G installation, then please take a backup of oratab and oraInst.loc files of 11G and restore previously backed up files of 10G. The vice versa for 11G is also true.
16.2
JDK 6 Installation (64 bit) Installing the 64-bit JDK for the Solaris operating system on SPARC platforms is a two-step process. These steps can be performed in either order, but you must install the following bundles together: Install solaris-sparc (32-bit) with solaris-sparcv9 (64-bit) 1) Install the 32-bit JDK using the 32-bit JDK Installation Notes. 2) Install the supplemental files for 64-bit support using the following 64-bit installation instructions.
16.2.1 32-bit Installation Instructions
Note: (Refer Section 5.1 Table 1 and column Install Item (1) for the package information).
The below steps are for self-extracting binary file to install the JDK. 1. Download the self-extracting binary “jdk-6u24-solaris-sparc.sh” and check the file size to ensure that you have downloaded the full, uncorrupted software bundle. Copy the jdk-6u24-solaris-sparc.sh to $MWHOME that is /u01/oracle/product/soa/11g/fmw 2. Make sure that execute permissions are set on the self-extracting binary: On SPARC processors:
SOA/OSB Installation and Configuration Guide by Lokesh T C
chmod +x jdk-6u24-solaris-sparc.sh 3. Change directory to $MWHOME 4. Run the self-extracting binary. Execute the downloaded file with the path prepended to it. For example, if the file is in the current directory, prepend it with "./" (necessary if "." is not in the PATH environment variable): On SPARC processors: ./jdk-6u24-solaris-sparc.sh The binary code license is displayed, and you are prompted to agree to its terms (press ‘y’ or enter key to continue). The JDK files are installed in a directory called jdk1.6.0_24 i.e., /u01/oracle/product/soa/11g/fmw 5. Check for JDK Install, below is the example to check java version. java –d32 –version java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) Server VM (build 19.1-b02, mixed mode) 6. Delete 32-bit JDK from below file system rm /u01/oracle/product/soa/11g/fmw/jdk-6u24-solaris-sparc.sh
16.2.2 64-Bit Installation Instructions
Note: (Refer Section 5.1 Table 1 and column Install Item (1) for the package information). The below steps are for self-extracting binary file to install the JDK. 1. Download the self-extracting binary “jdk-6u24-solaris-sparcv9.sh” and check the file size to ensure that you have downloaded the full, uncorrupted software bundle. You can download to software directory and it does not have to be the directory where you want to install the JDK. Copy the jdk-6u24-solaris-sparcv9.sh to $MWHOME i.e., /u01/oracle/product/soa/11g/fmw 2. Make sure that execute permissions are set on the self-extracting binary: On SPARC processors: chmod +x jdk-6u24-solaris-sparcv9.sh 3. Change directory to the same directory from where you ran the self-extracting binary for the 32-bit install. This is the directory that contains the jdk1.6-24 directory of the 32-bit JDK.
SOA/OSB Installation and Configuration Guide by Lokesh T C
4. Run the self-extracting binary. Execute the downloaded file, prepending the path to it. For example, if the downloaded file is in the current directory, prepend it with "./" (necessary if "." is not in the PATH environment variable): On SPARC processors: ./jdk-6u24-solaris-sparcv9.sh The binary code license is displayed, and you are prompted to agree to its terms. The supplemental files for 64-bit support are installed in directories named for the machine architecture model, which are added at several locations within the same jdk1.6.0_ directory where the 32-bit JDK was installed. For example, on SPARC processors the 64-bit Java VM Library file (libjvm.so) is stored in the jre/lib/sparcv9/server. 5. Check for JDK Install, below is the example to check java version. java –d64 –version java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) Server VM (build 19.1-b02, mixed mode) 6. Delete 64-bit JDK from below file system rm /u01/oracle/product/soa/11g/fmw/jdk-6u24-solaris-sparc.sh
16.3
SOA Repository Schema’s Installation using RCU Tool for core SOA domain
This section sets up the SOA repository schemas for the following Oracle SOA Suite components on the Oracle 10g RAC databases: Oracle SOA Suite and Oracle OSB require that certain schemas to be exist in the database prior to installation. You must run Repository Creation Utility (RCU) to create the schemas in the database. 16.3.1 Environment This will need the following on the installation Environment:•
Java Version 1.6.
Note:
This utility could be run on Linux or Windows platforms and cannot be run on Solaris OS.
16.3.2 Installation Steps
1. Extract SOA Oracle Repository Creation Utility (Refer Section 5.1 Table 1 and column Install Item (2) for the package).
SOA/OSB Installation and Configuration Guide by Lokesh T C
2. Extract the contents to a directory of your choice, and run RCU from the RCU_HOME/bin (on UNIX operating systems) or RCU_HOME\bin (on Windows operating systems) directory with the commands shown in the next steps, where RCU_HOME is the folder where RCU was unzipped. 3. On UNIX operating systems: ./rcu 4. On Windows operating systems: rcu.bat Note: On Windows systems, make sure that you do not extract the RCU .zip file to a directory name containing spaces. 5. Welcome Screen Click Next. 6. Create Repository Screen Click Create. Click Next. 7. Database Connection Details Screen
SOA/OSB Installation and Configuration Guide by Lokesh T C
Provide the necessary credentials for RCU to be able to connect to your Oracle database: o
o o
Host Name: Specify the name of the machine on which your database resides in the format host.domain.com. For Oracle RAC databases, specify the Virtual IP name or one of the node names as the host name. Port: Specify the database listener port number. The default port number for Oracle databases is 1521. Database Name: Specify the service name for the database. Typically, the service name is the same as the global database name. If you are unsure what the service name for your database is, you can obtain it from the SERVICE_NAMES parameter in the database's initialization parameter file. If the initialization parameter file does not contain the SERVICE_NAMES parameter, then the service name is the same as the global database name, which is specified in the DB_NAME and DB_DOMAIN parameters. For Oracle RAC databases, specify the service name of one of the nodes in this field. For example: sales.mydomain.com.
o
Username: Specify the name of a user with DBA or SYSDBA privileges. The default user name with SYSDBA privileges is SYS.
SOA/OSB Installation and Configuration Guide by Lokesh T C
o o
Password: Specify the password for your database user. Role: Select the database user's role from the drop-down list. The SYS user requires the SYSDBA role. Note: Oracle SOA Infrastructure schemas are created with Unicode support (database tables created with NVARCHAR) only.
o o o o o
Server Name: Enter the host name, IP address, or complete server name in host\server format of the server where your database is running.. Port: Specify the database listener port number. Database Name: Specify the name of your database. Username: Specify the name of a user with DBA or SYSDBA privileges. Password: Specify the password for your database user.
Click Next. A "Checking Prerequisites" screen will appear. After the checking is complete with no errors, click OK to dismiss the screen. 8. Select Components Screen
SOA/OSB Installation and Configuration Guide by Lokesh T C
Near the top of the screen, select Create a New Prefix. The default prefix is DEV so change it to SOA.
Check the option SOA and BPM Infrastructure to select all the schemas in this category. If the schema has dependencies, the dependencies are automatically selected for you. Note: You must remember or make a note of these schema names and the prefix value from this screen; you will need them later when you are configuring your products. You will need to provide the schema name in the format prefix_schemaname. For example, if you have used the prefix SOA, you will supply the following schema name for the MDS schema: SOA_MDS
Table 2-1 Required Schemas for Oracle SOA Suite Products
Component
Schema Owner
SOA Infrastructure
SOAINFRA
prefix_MDS (Metadata Services) prefix_ORASDPM (User Messaging)
Business Activity Monitoring
ORABAM
prefix_MDS (Metadata Services) prefix_ORASDPM (User Messaging)
User Messaging Service ORASDPM
Selected Schemas
prefix_MDS (Metadata Services)
Click Next. A "Checking Prerequisites" screen will appear. After the checking is complete with no errors, click OK to dismiss the screen. 9. Schema Passwords Screen
SOA/OSB Installation and Configuration Guide by Lokesh T C
There are three ways to specify schema passwords on this screen: Use first option. o
o
o
Select Use same password for all schemas if you want to use a single password for all schemas and their auxiliary schemas. In the Password field, enter your password. Enter your password again in the Confirm Password field. Select Use main schema passwords for auxiliary schemas if you want to specify different passwords for the main schemas, but still have the same password used for their respective auxiliary schemas. If you select this option, only the main schemas will be visible in the table. For each schema, you must enter each schema's password in the Password column in the table, and enter the same password in the Confirm Password column. Select Specify different passwords for all schemas if you want to specify unique passwords for the main schemas and auxiliary schemas. If you select this option, all main schemas and auxiliary schemas will be visible in the table. For each schema and auxiliary schema, you must enter the password in the Password column in the table, and enter the same password in the Confirm Password column.
SOA/OSB Installation and Configuration Guide by Lokesh T C
Note: You must remember or make a note of the password(s) from this screen; you will need them later when you are configuring your products. In the above example the password is same for all the schemas.
Click Next. If will get to see the below tablespace not exist dialog in absence of the same. click OK to dismiss the screen, if you want to create a default tablespace.
10. Map Tablespaces Screen Click Next. A "Creating Tablespaces" screen will appear. After the tablespaces are created with no errors, click OK to dismiss the screen.
11. Summary Screen Click Create. A "CREATE" screen will appear. After the schemas are created with no errors, click OK to dismiss the screen.
SOA/OSB Installation and Configuration Guide by Lokesh T C
12. Completion Summary Screen Click Create. 16.3.3 Create user, tablespace and DDL’s for the OSB Cluster Note:change the DBHOME and ORCL value according to the environment: 1. Create a tablespace called soa_osb. For example, log on to SQL*Plus as the sysdba user and run the following command: SQL> create tablespace soa_osb_ts logging datafile 'DB_HOME/oradata/orcl/soa_osb_ts.dbf' size 32m autoextend on next 32m maxsize 2048m extent management local; Create a user named soa_osb and assign to it the soa_osb_ts tablespace. 2. Let the default password be present as is SQL> create user soa_osb identified by soa_osb; 3. SQL> grant create table to soa_osb; 4. SQL> grant create session to soa_osb; 5. SQL> grant CONNECT, RESOURCE to soa_osb;
SOA/OSB Installation and Configuration Guide by Lokesh T C
6. SQL> alter user soa_osb default tablespace soa_osb_ts; 7. SQL> alter user soa_osb quota unlimited on soa_osb_ts; 8. Run the Create DDL’s for OSB by connecting to the user “soa_osb” SQL> @$MWHOME/Oracle_OSB/dbscripts/oracle/reporting_runtime.sql 16.3.4 Create user and tablespace for the JMS Server JDBC Store for SOACoreDomain Note:change the DBHOME and ORCL value according to the environment: 1. Create a tablespace called soa_jms. For example, log on to SQL*Plus as the sysdba user and run the following command: SQL> create tablespace soa_jms_ts logging datafile 'DB_HOME/oradata/orcl/soa_jms_ts.dbf' size 32m autoextend on next 32m maxsize 2048m extent management local; Create a user named soa_jms and assign to it the soa_jms_ts tablespace. 2. Let the default password be present as is SQL> create user soa_jms identified by soa_jms; 3. SQL> grant create table to soa_jms; 4. SQL> grant create session to soa_jms; 5. SQL> grant CONNECT, RESOURCE to soa_jms; 6. SQL> alter user soa_jms default tablespace soa_jms_ts; 7. SQL> alter user soa_jms quota unlimited on soa_jms_ts;
16.4
SOA Repository Schema’s Installation using RCU Tool for SOA extension domain This section of the document is to create SOAX prefixed schema’s for a SOA extension domain. 1) Execute all the steps 1 to 7 under section 7.3 2) Follow all the information in the step 8 under section 7.3 except for the following text. Use SOAX prefix value instead of SOA. Near the top of the screen, select Create a New Prefix. The default prefix is DEV so change it to SOAX. 3) Follow all the steps from 9 onwards.
16.4.1 Create user and tablespace for the JMS Server JDBC Store for SOAExtDomain Note:change the DBHOME and ORCL value according to the environment:
SOA/OSB Installation and Configuration Guide by Lokesh T C
1. Create a tablespace called soax_jms. For example, log on to SQL*Plus as the sysdba user and run the following command: SQL> create tablespace soax_jms_ts logging datafile 'DB_HOME/oradata/orcl/soax_jms_ts.dbf' size 32m autoextend on next 32m maxsize 2048m extent management local; Create a user named soax_jms and assign to it the soax_jms_ts tablespace. 2. Let the default password be present as is SQL> create user soax_jms identified by soax_jms; 3. SQL> grant create table to soax_jms; 4. SQL> grant create session to soax_jms; 5. SQL> grant CONNECT, RESOURCE to soax_jms; 6. SQL> alter user soax_jms default tablespace soax_jms_ts; 7. SQL> alter user soax_jms quota unlimited on soax_jms_ts;
16.5
Configuring SOA Schemas for Transactional Recovery Privileges You need the appropriate database privileges to allow the Oracle WebLogic Server transaction manager to query for transaction state information and issue the appropriate commands, such as commit and rollback, during recovery of in-flight transactions after a WebLogic Server container crash. To configure the SOA schemas for transactional recovery privileges: Log on to sqlplus as a user with sysdba privileges. For example: sqlplus "/ as sysdba" Enter the following commands for all SOA_ & SOAX_ Schema Users: Grant select on sys.dba_pending_transactions to SOA_<>; Grant force any transaction to SOA_<>; Grant select on sys.dba_pending_transactions to SOAX_<>; Grant force any transaction to SOAX_<>; Below are the commands: Grant select on sys.dba_pending_transactions to SOA_SOAINFRA; Grant force any transaction to SOA_SOAINFRA; Grant select on sys.dba_pending_transactions to SOA_MDS; Grant force any transaction to SOA_MDS;
SOA/OSB Installation and Configuration Guide by Lokesh T C
Grant select on sys.dba_pending_transactions to SOA_ORABAM; Grant force any transaction to SOA_ORABAM; Grant select on sys.dba_pending_transactions to SOA_ORASDPM; Grant force any transaction to SOA_ORASDPM; Grant select on sys.dba_pending_transactions to SOA_EAIOWNER; Grant force any transaction to SOA_EAIOWNER; Grant select on sys.dba_pending_transactions to SOAX_MDS; Grant force any transaction to SOAX_MDS; Grant select on sys.dba_pending_transactions to SOAX_SOAINFRA; Grant force any transaction to SOAX_SOAINFRA; Grant select on sys.dba_pending_transactions to SOAX_EAIOWNER; Grant force any transaction to SOAX_EAIOWNER; Grant select on sys.dba_pending_transactions to SOAX_ORASDPM; Grant force any transaction to SOAX_ORASDPM; Grant select on sys.dba_pending_transactions to SOAX_ORABAM; Grant force any transaction to SOAX_ORABAM; Grant select on sys.dba_pending_transactions to SOA_JMS; Grant force any transaction to SOA_JMS; Grant select on sys.dba_pending_transactions to SOAX_JMS; Grant force any transaction to SOAX_JMS; Grant select on sys.dba_pending_transactions to SOA_OSB; Grant force any transaction to SOA_OSB; Grant select on sys.dba_pending_transactions to SOAX_OSB; Grant force any transaction to SOAX_OSB;
16.6
Drop SOA Repository Schemas using RCU Tool In order to drop it’s always good to drop SOA Repository Schemas using RCU tool and choose drop option which will also delete rows from SCHEMA_VERSION_REGISTRY table stored in sys users.
SOA/OSB Installation and Configuration Guide by Lokesh T C
16.7
Oracle WebLogic Server Installation
This section of the document illustrates the steps for Installing WebLogic 11g Generic jar on Solaris with SPARC machine. Download the WebLogic Installer wls1035_generic.jar (refer section 5.1) file and usually this can be run on any platform, irrespective of operating environments. It is also supports both 64 bit and 32 bit Operating System type. Please note that there is the need for pre-installed JDK 1.6 update (24+). You must download a stable version of JDK otherwise it will throw the exceptions as unsecured JDK. 16.7.1 Installation Steps Note: The 32-bit executable files are bundled with the appropriate JDK version. If you use the 64-bit installer, you will need to invoke the installer with a supported JDK for your platform. This JDK must be installed on your system before you install Oracle WebLogic Server. Refer to the Oracle Fusion Middleware certification document for a list of supported JDKs for your platform Installation of Oracle WebLogic Fusion Middleware Application Server. To start the installation program in graphical mode for installation files with names ending in .jar, perform the following steps. 1. Ensure that the system, patch, kernel and other requirements are met as specified in the Oracle Application Server Installation Guide. 2. Ensure that all the environment variables are set in the installing machine. 3. Copy the installation compressed file of the Application Server into the oracle account under a directory called /u01/oracle/product/soa/11g/fmw 4. Start the X-Server running on the your Local PC 5. Go to the directory where you downloaded the installation program. 6. Launch the installation program by entering the following command. java
-d64 -jar wls1035_generic.jar
The installation program begins to install the software with the welcome screen. 7. Click Next.
SOA/OSB Installation and Configuration Guide by Lokesh T C
8. Choose Middleware Home Directory Screen
Select Create a new Middleware Home to create a new Middleware Home directory. Specify the desired location of your new Middleware Home directory. If this directory already exists on your system, it must be an empty directory. If this directory does not already exist, then it will be created for you. Click Next.
SOA/OSB Installation and Configuration Guide by Lokesh T C
Middleware Home Directory to be used - /u01/oracle/product/soa/11g/fmw 9. Register for Security Updates Screen
Select whether or not you want to receive the latest product and security updates. If you choose not to receive anything, you will be asked to verify your selection before continuing. Uncheck the checkbox. Click on to continue.
SOA/OSB Installation and Configuration Guide by Lokesh T C
10. Choose Install Type Screen
Select Typical and click Next to continue.
SOA/OSB Installation and Configuration Guide by Lokesh T C
a.
JDK Selection Screen Select the JDKs you want to install. Oracle recommends that you use the Sun SDK if you are installing in a development environment. Typically, this environment provides a more relaxed security configuration and enables you to auto-deploy applications. In a development environment, boot.properties is used for user names and passwords and polling is used for application deployment. If you are installing in a production environment, Oracle recommends that you use the Oracle JRockit SDK. Production environments are for applications running in their final form. Full security is enabled and applications may be clustered or use other advanced features. In this mode, user names and passwords are required and polling is not used for application deployment. Click Next.
SOA/OSB Installation and Configuration Guide by Lokesh T C
Choose Product Installation Directories Screen Specify the location for the WebLogic Server Home directory as per the environment variables.
SOA/OSB Installation and Configuration Guide by Lokesh T C
Weblogic Server location: /u01/oracle/product/soa/11g/fmw/wlserver_10.3 Oracle Coherence location: /u01/oracle/product/soa/11g/fmw/coherence_3.6 Note: Coherence cluster configuration is part of WLST script before creating the SOACore or SOAExt Domain domains For more information about the WebLogic Home directory, refer to "Middleware Home and WebLogic Home Directories" in Oracle Fusion Middleware Installation Planning Guide. Click Next Installation Summary Screen
SOA/OSB Installation and Configuration Guide by Lokesh T C
Click Next
SOA/OSB Installation and Configuration Guide by Lokesh T C
Installation Progress Screen
SOA/OSB Installation and Configuration Guide by Lokesh T C
Installation Complete Screen
De-select Run Quickstart Click Done For more information about installing Oracle WebLogic Server, refer to Oracle WebLogic Server Installation Guide.
SOA/OSB Installation and Configuration Guide by Lokesh T C
16.7.2
Gold Backup of WebLogic Server Installation
To perform a full online/offline backup: 1. To avoid an inconsistent backup, do not make any configuration changes until the backup is completed. To ensure that no changes are made in the Oracle WebLogic Server domain, lock the WebLogic Server configuration.
2. Back up the Middleware home ($MWHOME) on Node1. For example: tar -cvf mw_home_backup_<>.tar $MWHOME/*
3. If the domain is not located within the Middleware home, back up the Administration Server domain separately. This backs up Java components such as Oracle SOA Suite and Oracle OSB Servers. This step can be performed For example: tar -cvf domain_home_backup_<>.tar $WLSDOMAIN/user_projects/domains/*
In most cases, you do not need to backup the Managed Server directories separately, because the Administration Server domain contains information about the Managed Servers in its domain. The recommended recovery procedures for Managed Servers call for restoring the Middleware home and using the pack and unpack utilities.
4. Backup the OraInventory directory. For example: tar -cvf oraInv_bkp_<>.tar /u01/export/home/oracle/oraInventory/*
5. Back up OraInst.loc and oratab files, which is located in the following directory: Ignore if we have chosen the local inventory at the time of installation. /var/opt/oracle/
6. Backup the database repositories using the Oracle Recovery Manager (RMAN) if necessary otherwise ignore. For detailed steps, see the Oracle Database Backup and Recovery User's Guide, which is available at: http://www.oracle.com/technology/documentation/database.html
SOA/OSB Installation and Configuration Guide by Lokesh T C
16.8 Install Oracle SOA Suite Components for Application Server Middle-Tier This section of the document contains installation steps for SOA suite components. This will be installed on top Oracle WebLogic Server. Note: The installer requires the location of a Java Runtime Environment (JRE) on the installing system. When you installed Oracle WebLogic Server, a JRE was installed on your system. You can use this location (the location of the jre directory) to start the installer. The default location for the JRE is MWHOME/jdk16u24+ (on UNIX operating systems), where MWHOME is the Middleware Home directory. On 64-bit platforms, the JRE location is the JAVA_HOME you used to install Oracle WebLogic Server. Refer to Section, "Install Oracle WebLogic Server". 16.8.1
Installation Steps
Installation of Oracle WebLogic Fusion Middleware Application Server To start the installation program in graphical mode for installation, perform the following steps. 1. Ensure that the system, patch, kernel and other requirements are met as specified in the Oracle Application Server Installation Guide. 2. Ensure that all the environment variables are set in the installing machine. 3. Copy the installation compressed file of the Application Server into the oracle account under a directory called /u01/oracle/product/soa/11g/fmw/soasuite 4. Start the X-Server running on the your Local PC 5. Go to the directory where you downloaded the installation program. 6. Run the following commands to extract the package to soasuite directory. unzip ofm_soa_generic_11.1.1.5.0_disk1_1of2.zip unzip ofm_soa_generic_11.1.1.5.0_disk1_2of2.zip
7. To Disable 10G Oracle Home if already installed, then follow the below steps below otherwise ignore this step. If you already have 10G installed on this machine and planning to install 11G without wiping out the 10G binaries. Then, follow the below steps Go to /var/opt/oracle and execute the following commands to take inventory location backup. mv oraInst.loc oraInst<> mv oratab oratab<>
SOA/OSB Installation and Configuration Guide by Lokesh T C
Note: In order to enable 10G, we need to revert back the renamed files back to its original names i.e oraInst.loc and oratab. 8. Launch the installation program located at soasuite/Disk1 folder by entering the following command. ./runInstaller -jreLoc $JAVA_HOME/jre The installation program begins to install the software with Welcome Screen. Click Next to Continue.
By default the inventory folder will point to user $HOME folder. Click Next.
Select the Check box as “Continue Installation with local inventory” and OK to continue
SOA/OSB Installation and Configuration Guide by Lokesh T C
root@gvap-oracles01 #cd /u01/export/home/oracle/oraInventory root@gvap-oracles01 # ./createCentralInventory.sh Setting the inventory to /u01/export/home/oracle/oraInventory Setting the group name to dba Creating the Oracle inventory pointer file (/var/opt/oracle/oraInst.loc) Changing permissions of /u01/export/home/oracle/oraInventory to 770. Changing groupname of /u01/export/home/oracle/oraInventory to dba. The execution of the script is complete root@gvap-oracles01 #
SOA/OSB Installation and Configuration Guide by Lokesh T C
SOA/OSB Installation and Configuration Guide by Lokesh T C
9. My Oracle Support Update If you have the PROXY server details for connecting to the Internet from the installing box and also the oracle 11G support account details then furnish the details and the test connection otherwise Select Skip software updates radio check box and continue with next step.
SOA/OSB Installation and Configuration Guide by Lokesh T C
10. Pre-Requisite Checks,
A "Checking Prerequisites" screen will appear. After the checking is complete with no errors, click Next.
SOA/OSB Installation and Configuration Guide by Lokesh T C
11. Select SOA Suite Installation Location and Click Next.
SOA/OSB Installation and Configuration Guide by Lokesh T C
12. Selection WebLogic as Application Server and click Next
SOA/OSB Installation and Configuration Guide by Lokesh T C
13. Click Install on the Installation Summary Screen.
SOA/OSB Installation and Configuration Guide by Lokesh T C
14. Click Next on Installation Progress Screen.
SOA/OSB Installation and Configuration Guide by Lokesh T C
15. Click Finish to complete the installation
16.8.2
Gold Backup of WebLogic Server Installation
[Refer to the steps under section 7.5.2]
16.9 Install OSB Components for SOA Suite This section of the document contains installation of OSB Component of SOA suite. This will be installed on top of SOA Suite binary. Please Note: The installer requires the location of a Java Runtime Environment (JRE) on the installing system. When you installed Oracle WebLogic Server, a JRE was installed on your system. You can use this location (the location of the jre directory) to start the installer. The default location for the JRE
SOA/OSB Installation and Configuration Guide by Lokesh T C
is MWHOME/jdk16u24+ (on UNIX operating systems), where MWHOME is the Middleware Home directory. On 64-bit platforms, the JRE location is the JAVA_HOME you used to install Oracle WebLogic Server. Refer to Section, "Install Oracle WebLogic Server". 16.9.1
Installation Steps
Installation of Oracle WebLogic Fusion Middleware Application Server. To start the installation program in graphical mode for installation, perform the following steps. 1. Ensure that the system, patch, kernel and other requirements are met as specified in the Oracle Application Server Installation Guide. 2. Ensure that all the environment variables are set in the installing machine. 3. Copy the installation compressed file of the Application Server into the oracle account under a directory called /u01/oracle/product/soa/11g/fmw/osb 4. Start the X-Server running on the your Local PC 5. Go to the directory where you downloaded the installation program. 6. Run the following commands to extract the package to “osb” directory. unzip ofm_osb_generic_11.1.1.5.0_disk1_1of1.zip
7. Launch the installation program located at osb/Disk1 folder by entering the following command. ./runInstaller -jreLoc $JAVA_HOME/jre The installation program begins to install the software with Welcome Screen. Click Next to Continue.
SOA/OSB Installation and Configuration Guide by Lokesh T C
SOA/OSB Installation and Configuration Guide by Lokesh T C
8.
My Oracle Support Update If you have the PROXY server details for connecting to the Internet from the installing box and also the oracle 11G support account details then furnish the details and the test connection otherwise Select Skip software updates radio check box and continue with next step.
SOA/OSB Installation and Configuration Guide by Lokesh T C
9. Select OSB Installation Location and Click Next.
SOA/OSB Installation and Configuration Guide by Lokesh T C
10. Leave the default value for Select Install Location and click Next.
SOA/OSB Installation and Configuration Guide by Lokesh T C
11. Prerequisite Checks and click Next. A "Checking Prerequisites" screen will appear. After the checking is complete with no errors, click Next.
SOA/OSB Installation and Configuration Guide by Lokesh T C
12. Leave the default values for Product Home Installation Location, OEPE Location should be blank and Click Next.
Ignore below warning as we are not installation OSB Eclipse Plug-ins, click ok to continue
SOA/OSB Installation and Configuration Guide by Lokesh T C
13. Click Next on the Installation Progress Screen.
SOA/OSB Installation and Configuration Guide by Lokesh T C
14. Installation Progress Screen.
SOA/OSB Installation and Configuration Guide by Lokesh T C
15. Click Finish to complete the installation
SOA/OSB Installation and Configuration Guide by Lokesh T C
16.9.2
Gold Backup of WebLogic Server Installation
Back up the Middleware home ($MWHOME) For example: tar -cvf mw_home_WL_backup_.tar $MWHOME/*
SOA/OSB Installation and Configuration Guide by Lokesh T C
16.10 Post Installation Tasks 16.10.1 Extracting the XEngine Files To enable B2B's XEngine we need to extract the content of the XEngine tar manually: Go to the installing node and run the following commands cd $ORACLE_HOME/soa/thirdparty/edifecs gunzip XEngine.tar.gz tar -xvf XEngine.tar
SOA/OSB Installation and Configuration Guide by Lokesh T C
17 Cloning Installation for Oracle SOA Suite Cloning is the process of copying an existing entity to a different location while preserving its state. Some situations in which cloning Oracle Fusion Middleware is useful are: •
•
Creating a Middleware home or Oracle home that is a copy of a production, test, or development environment. Cloning enables you to create a new Middleware home or an Oracle home with all patches applied to it in a single step. This is in contrast to separately installing, configuring and applying any patches to separate Oracle homes. Preparing a "gold" image of a patched home and deploying it to many hosts.
The cloned entity behaves the same as the source entity. For example, a cloned Oracle home can be de-install or patched using the installer. It can also be used as the source for another cloning operation.
17.1 What You Can Clone You can clone the following, on the same host or a different host: •
Middleware home: You can apply the clone of the Middleware home to the same host or a different host. The clone must be on the same operating system as the source
•
Oracle home: You can apply the clone of an Oracle home to the same Middleware home or to a different Middleware home, which can be on the same host or a different host. The clone must be on the same operating system as the source.
•
If you are applying the clone of an Oracle SOA Suite or Oracle WebCenter Oracle home, ensure that the same type of Oracle home is not present in that Middleware home. That is, you can have only one Oracle SOA Suite Oracle home in a Middleware home and you can have only one Oracle WebCenter Oracle home in a Middleware home.
•
Oracle Internet Directory: You can clone Oracle Internet Directory to a different Oracle instance, in the same Middleware home or a different Middleware home, on the same host or a different host. You cannot clone it to the same Oracle instance.
•
Oracle Virtual Directory: You can clone Oracle Virtual Directory to a different Oracle instance, in the same Middleware home or a different Middleware home, on the same host or a different host. You cannot clone it to the same Oracle instance.
SOA/OSB Installation and Configuration Guide by Lokesh T C
17.2 Considerations and Limitations for Cloning Note the following important additional considerations about cloning: •
Cloning does not carry over all the dependencies of the source Oracle home, such as loadable modules or application-specific libraries to the cloned home, because cloning proceeds by copying the entire source Oracle home to the destination Oracle home. Any files outside the source Oracle home are not automatically copied. Hence, any applications that refer to files outside the source Oracle home may not work properly in the cloned home.
•
If you created symbolic links to files or applications outside the source Oracle home, you must re-create the link manually in the cloned home for your applications to work properly.
•
When you clone a Middleware home, only the read-only portions of the Middleware home are cloned. Any user configuration files, such as the user_projects directory, are excluded from the cloned image. The WebLogic Server domain is not cloned.
•
If a cloning operation fails, but it results in the Oracle home being registered with Oracle Inventory, you cannot use the same Oracle home in subsequent cloning operations. Either use another directory and name for the Oracle home in subsequent cloning operations or un-install the Oracle home before attempting another cloning operation.
•
If you are applying the clone of a Middleware home or an Oracle home on a host that does not yet have Oracle Fusion Middleware installed, the host must have JDK 1.6 or higher installed. In addition, the PATH, CLASSPATH, and JAVA_HOME environment variables must point to the JDK.
17.3 Cloning a Middleware Home and All of Its Oracle Homes Note: This section of the document requires that section from 1 to 6 have been completed prior to performing the cloning. Also assumes that backup/renaming of 10G oraInst.loc and oratab is done. 1. Copy the JDK from node1 to shared drive cp –R $JAVA_HOME $SHARED_MOUNT
2. Ensure that backup/renaming of 10G oraInst.loc and oratab is done. Copy the Oracle Inventory file to node2, node3 & node4. copy /var/opt/oracle/oraInst.loc from node1 to node2, node3 & node4 3. At the source node1 Middleware home, execute the createClone command, using the following syntax: $MWHOME/oracle_common/bin/copyBinary.sh -javaHome $SHARED_MOUNT/jdk1.6.0_24 d64 -archiveLoc $SHARED_MOUNT/clone/mw_clone.jar -sourceMWHomeLoc $MWHOME invPtrLoc /var/opt/oracle/oraInst.loc 4. Copy the pre-requisites for cloning on node2, node3 and node4. Login into Node1 and execute the following commands
SOA/OSB Installation and Configuration Guide by Lokesh T C
cp $MWHOME/oracle_common/bin/pasteBinary.sh $SHARED_MOUNT cp $MWHOME/oracle_common/jlib/cloningclient.jar $SHARED_MOUNT 5. Login into Node2, Node3 and Node4 and execute the following command to clone the Middleware Home: 1) Ensure you have absolute path and folders available on all nodes /u01/oracle/product/soa/11g 2) Ensure the following directory is deleted. rm –R fmw 3) Navigate to the directory where pre-requisites artifacts exists. cd /u01/shared/11g/ 4) Apply the cloning command. ./pasteBinary.sh -javaHome $SHARED_MOUNT/jdk1.6.0_24 -d64 -archiveLoc $SHARED_MOUNT/clone/mw_clone.jar -targetMWHomeLoc $MWHOME -invPtrLoc /var/opt/oracle/oraInst.loc 6. The Middleware home is restored at $MWHOME and all of the Oracle homes are restored under it with the same name as that of source Oracle home name. 7. Delete the archive files (mw_clone.jar, cloningclient.jar and JDK) located at $SHARED_MOUNT folder. Note: for more information, check this. http://www.art2dec.com/documentation/docs/fmw11g1114documentation/core.1111/e10105/cl one.htm#CACBAJBA
SOA/OSB Installation and Configuration Guide by Lokesh T C
18 Domain Configuration for Oracle SOA Suite This section of the document describes how to install and configure a clustered environment for the SOA suite. The clustered environment is based on: •
Four Servers: • 32 GB internal memory • At least 32 CPU/Cores • SunOS 5.10 operating system
•
Each machine may contain minimum of three server instances; • 11 managed servers [SOA1-SOA8,OSB1-4,WLSMS1-4] • 4 cluster definitions • 2 admin server running in active-passive (applicable for multiple nodes) configuration mode. A local physical storage • Weblogic Server binaries • SOA Suite • OSB binaries A Shared storage • Domain Configuration files • Installable binaries • Release code base. A database • Oracle Database, 10G or higher
•
•
•
The particular document can also be used for standalone environment and can ignore installations or configurations steps related to multiple nodes related sections.
18.1 Pre-requisites An Oracle database is up and running and loaded with the SOA repository based on the Oracle Repository Creation Utility. This document assumes that the all the steps in Section 7 is completed. 18.1.1 Enabling Access to ifconfig and arping Commands To start and stop the network adapter for the admin server we need root privileges. We can provide these just for the ifconfig and arping commands by using sudo which allows running certain commands with root privileges. To set this up on each machine run the visudo command as root to edit the /usr/local/etc/sudoers permission file and add the following:
## SOA Suite Settings oracle ALL=NOPASSWD: /sbin/ifconfig, /sbin/arping This grants the oracle user access to the ifconfig and arping commands without having to provide a password by using sudo. Obviously this needs to be done on all middleware servers.
SOA/OSB Installation and Configuration Guide by Lokesh T C
18.1.2 Enable Admin IP Address [Applicable for Cluster] The Admin server needs to be able to be started on any of the SOA servers so we have assigned it an IP address that can float between machines. Before we configure our cluster we need to assign the Admin server IP address to a machine in the cluster. For my environment I issued the following commands as the root user: Use the VIP Addresses which was registered at DNS level to fluctuate between two nodes. Active Admin Server of SOACoreDomain will run on node1 so the fluctuation should be between node1 and node2/node3. This require one set of VIP address registered for node1, node2 and node3 Active Admin Server of SOAExtDomain will run on node4 so the fluctuation should be between node4 and node2/node3. This requires one set of VIP address registered for node4, node2 and node3.
ifconfig bge0:1 plumb + broadcast + up /usr/sbin/arp -q -U -c 3 -I bge0 Example: sudo /sbin/ifconfig bge0:1 plumb 10.0.3.100 netmask 255.255.255.0 + broadcast + up sudo /usr/sbin/arp -q -U -c 3 -I bge0 10.0.3.100 OR Where IP_Address is the virtual IP address and the netmask is the associated netmask. In the following example, the IP address is being enabled on the interface eth0.
ifconfig eth0:1 130.35.46.17 netmask 255.255.225.0 + broadcast + up /usr/bin/arp -q -U -c 3 -I eth0 130.35.46.17 The ifconfig command associates a sub-interface (eth1:9 in my case) with a particular IP address and associated netmask. We used eth1:9 to avoid any possible future clashes with node manager which will be responsible for assigning floating IP addresses for managed servers that can migrate between machines. The arping command sends an unsolicited update (-U) 3 time (-c 3) on interface eth1 (-I eth1) alerting nodes on the sub-net of the association between this IP address and the adapter, this is important if the IP address was previously assigned to another adapter, such as occurs during migration of the admin server from one machine to another. It is a good idea to create this as a shell script on shared storage, perhaps in the AServer folder, because you will need it to start the admin server on different machines.
Note: Provide the admin IP addresses to System administrator to carry out this section. Notes are added for understand.
18.2 Domain Installation and Configuration To install and configure the SOA/OSB/WLS following steps are performed.
SOA/OSB Installation and Configuration Guide by Lokesh T C
•
Configure Weblogic SOA cluster using Interactive mode/WLST Script Mode • Select Applications • Define servers • Define Node managers • Define cluster or standalone configuration • Define datasources • Define SOA Partitions • Define Users • Define JDBC/MQ/File Resource Adapters • Define Oracle Coherence settings
•
Start and test SOA cluster
18.2.1 Cluster based domain creation using WLST Script for “SOACoreDomain” [Applicable only for Cluster] This section of the document provides a step by step process for running the automated WLST script to create a HA Cluster of Oracle WebLogic Domain Configuration containing SOA/OSB/Webservice components on a shared mount path. [Please refer to the appendix section C for IP and HostName details] 1. Login into Node1 using oracle user account. 2. Go to software folder on the node1 where the below files are located. 1) CreateCoreSOADomain.py 2) domain.properties 3. Open file “domain.properties” and change the information as per the environment capacity and in Production Replica type of environments leave the default values as is. Step 1) Change the value to dev if the configuration of the environment is Development otherwise prod SERVER_MODE=prod
Step 2) Specify the node1, node2, node3 & node4, the Floating/Physcial IP Addresses & hostnames respectively. On single node use the same IP and Name for all the entries. #Managed Servers IP domain1.soac-vip1=<
IP IP IP IP
IP IP IP IP IP IP IP IP
Address Address Address Address
Address Address Address Address Address Address Address Address
or or or or
or or or or
or or or or
HostName HostName HostName HostName
HostName HostName HostName HostName
HostName HostName HostName HostName
of of of of
of of of of of of of of
node1>> node2>> node3>> node4>> node1>> node2>> node3>> node4>>
node1>> node2>> node3>> node4>>
domain1.cadm-vip1=<>
SOA/OSB Installation and Configuration Guide by Lokesh T C
#Node manager domain1.Machine1IP=<> domain1.Machine2IP=<> domain1.Machine3IP=<> domain1.Machine4IP=<> domain1.Machine1Name=<> domain1.Machine2Name=<><> domain1.Machine3Name=<><> domain1.Machine4Name=<><>
Step 2) Keep the default as is for Production Replica type of environments otherwise consult Technical Team for Scaling down the memory size depending on the installing environment. domain1.Admin_Java_Arguments=<> domain1.WLSCore_Java_Arguments=<> domain1.SOACore_Java_Arguments=<> domain1.OSBCore_Java_Arguments=<>
Modify the JVM Arguments if required [On cluster leave the defaults]: domain1.Admin_Java_Arguments=–Xss512k -XX:PermSize=640m -XX:MaxPermSize=640m –Xms4g – Xmx4g –XX:NewRatio=2 -XX:+AggressiveOpts -XX:+UseParallelGC -XX:+UseParallelOldGC XX:ParallelGCThreads=2 -XX:InitialSurvivorRatio=10 -XX:SurvivorRatio=10 XX:+HeapDumpOnOutOfMemoryError XX:HeapDumpPath=/u01/export/home/oracle/crash/admin1_java.hprof -verbose:gc Xloggc:/u01/export/home/oracle/crash/admin1_gc.log -verbose:gc -XX:+PrintGCDetails XX:+PrintGCTimeStamps -XX:+PrintHeapAtGC -XX:+PrintTenuringDistribution
domain1.WLSCore_Java_Arguments=–Xss512k -XX:PermSize=256m -XX:MaxPermSize=256m –Xms2g –Xmx2g –XX:NewRatio=2 -XX:+AggressiveOpts -XX:+UseParallelGC -XX:+UseParallelOldGC XX:ParallelGCThreads=2 -XX:InitialSurvivorRatio=10 -XX:SurvivorRatio=10 XX:+HeapDumpOnOutOfMemoryError XX:HeapDumpPath=/u01/export/home/oracle/crash/wlscore_java.hprof -verbose:gc Xloggc:/u01/export/home/oracle/crash/wlscore_gc.log -verbose:gc -XX:+PrintGCDetails XX:+PrintGCTimeStamps -XX:+PrintHeapAtGC -XX:+PrintTenuringDistribution
domain1.SOACore_Java_Arguments=–Xss512k -XX:PermSize=512m -XX:MaxPermSize=512m –Xms4g –Xmx4g –XX:NewRatio=2 -XX:+AggressiveOpts -XX:+UseParallelGC -XX:+UseParallelOldGC XX:ParallelGCThreads=3 -XX:InitialSurvivorRatio=10 -XX:SurvivorRatio=10 XX:+HeapDumpOnOutOfMemoryError XX:HeapDumpPath=/u01/export/home/oracle/crash/soarcore_java.hprof -verbose:gc Xloggc:/u01/export/home/oracle/crash/soacore_gc.log -verbose:gc -XX:+PrintGCDetails XX:+PrintGCTimeStamps -XX:+PrintHeapAtGC -XX:+PrintTenuringDistribution
domain1.OSBCore_Java_Arguments=–Xss512k -XX:PermSize=256m -XX:MaxPermSize=256m –Xms2g –Xmx2g –XX:NewRatio=2 -XX:+AggressiveOpts -XX:+UseParallelGC -XX:+UseParallelOldGC XX:ParallelGCThreads=2 -XX:InitialSurvivorRatio=10 -XX:SurvivorRatio=10 XX:+HeapDumpOnOutOfMemoryError XX:HeapDumpPath=/u01/export/home/oracle/crash/osb_java.hprof -verbose:gc -
SOA/OSB Installation and Configuration Guide by Lokesh T C
Xloggc:/u01/export/home/oracle/crash/osb_gc.log -verbose:gc -XX:+PrintGCDetails XX:+PrintGCTimeStamps -XX:+PrintHeapAtGC -XX:+PrintTenuringDistribution
PRODUCTION/UAT(BLUE): Ensure that the following parameters are removed from the below key-value pairs in domain.properties i.e 1. domain1.OSBCore_Java_Arguments 2. domain1.SOACore_Java_Arguments 3. domain1.WLSCore_Java_Arguments 4. domain1.Admin_Java_Arguments verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintHeapAtGC XX:+PrintTenuringDistribution
Step3) Specify the VIP Address created at DNS for Admin Servers # Administration server configuration domain1.AdminIP=<> domain1.AdminPasswd=<> Note: AdminPasswd should be of minimum 8 characters consisting of alphanumeric characters Step 4) Update the Database Connection URL Parameters and If RAC DB used: domain1.DBURL=jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=on )(ADDRESS=(PROTOCOL=tcp)(HOST=<>)(PORT=<>))(ADDRESS=(PROTOCOL=tcp)(HOST=<>)(PORT=<>)))(CONNECT_DATA=(SERVICE_NAME=<>))) OR If no RAC DB: domain1.DBURL=jdbc:oracle:thin:@<>:<>/<> domain1.DBPASSWORD=<>
4. Execute the below command for creating domain. Change directory to – cd /u01/shared/11g/wlst wlst.sh CreateCoreSOADomain.py SOACoreDomain
5. Execute the below command to apply JRF to WLSCoreCluster and remove all the adapters from Admin Servers. $ORACLE_HOME/common/bin/wlst.sh ApplyConfigurations.py
6. Modify the JVM Memory parameters in setDomainEnv.sh SOACoreDomain: [Applicable for cluster]
SOA/OSB Installation and Configuration Guide by Lokesh T C
•
Open file $WLSDOMAIN/SOACoreDomain/aserver/SOACoreDomain/bin/setDomainEnv.sh
•
Search for the below text # IF USER_MEM_ARGS the environment variable is set, use it to override ALL
MEM_ARGS values
•
Add the
below entry as a next line at the mentioned step (2).
USER_MEM_ARGS=<> export USER_MEM_ARGS
•
save the file
18.2.2 Cluster based domain Creation using WLST Script for “SOAExtDomain”. [Applicable only for Cluster] This section of the document provides a step by step process for running the automated WLST script for creating a HA Cluster of Oracle WebLogic Domain Configuration on shared mount path from any node. This section assumes that the previous sections (1-8) are completed. 1. Login into Node1 using oracle user account. 2. Go to software folder on the node1 where the below files are located. 1) CreateAdditionalSOADomain.py 2) domain.properties 3. Open file “domain.properties” and change the information as per the environment capacity and in Production Replica type of environments leave the default values as is. Step 1) Specify the node1, node2, node3 & node4, the VIP Addresses & hostnames respectively. On single node use the same IP and Name for all the entries. #Managed Servers IP domain2.soax-vip5=<> domain2.soax-vip6=<> domain2.soax-vip7=<> domain2.aadm-vip1=<> #Node manager IP domain2.Machine1IP==<> domain2.Machine2IP=<> domain2.Machine3IP=<> domain2.Machine4IP=<< hostname of the node4>> domain2.Machine1Name=<< hostname of the node1>> domain2.Machine2Name=<< hostname of the node2>><> domain2.Machine3Name=<< hostname of the node3>><> domain2.Machine4Name=<< hostname of the node4>><>
SOA/OSB Installation and Configuration Guide by Lokesh T C
Step 2) Keep the default as is for Production Replica type of environments otherwise request to consult Technical Team for Scaling down the memory size depending on the capacity of environment. domain2.Admin_Java_Arguments=<> domain2.SOA_Java_Arguments=<>
Modify the JVM Arguments if required [On cluster leave the defaults: domain2.Admin_Java_Arguments=–Xss512k -XX:PermSize=512m -XX:MaxPermSize=512m – Xms4g –Xmx4g –XX:NewRatio=2 -XX:+AggressiveOpts -XX:+UseParallelGC XX:+UseParallelOldGC -XX:ParallelGCThreads=3 -XX:InitialSurvivorRatio=10 XX:SurvivorRatio=10 -XX:+HeapDumpOnOutOfMemoryError XX:HeapDumpPath=/u01/export/home/oracle/crash/admin2_java.hprof -verbose:gc Xloggc:/u01/export/home/oracle/crash/admin2_gc.log -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintHeapAtGC -XX:+PrintTenuringDistribution
domain2.SOA_Java_Arguments=–Xss512k -XX:PermSize=512m -XX:MaxPermSize=512m –Xms4g –Xmx4g –XX:NewRatio=2 -XX:+AggressiveOpts -XX:+UseParallelGC -XX:+UseParallelOldGC XX:ParallelGCThreads=3 -XX:InitialSurvivorRatio=10 -XX:SurvivorRatio=10 XX:+HeapDumpOnOutOfMemoryError XX:HeapDumpPath=/u01/export/home/oracle/crash/soaext_java.hprof -verbose:gc Xloggc:/u01/export/home/oracle/crash/soaext_gc.log -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintHeapAtGC -XX:+PrintTenuringDistribution
PRODUCTION/UAT(BLUE): Ensure that the following parameters are removed from the below key-value pairs in domain.properties i.e 1. domain2.Admin_Java_Arguments 2. domain2.SOA_Java_Arguments verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintHeapAtGC XX:+PrintTenuringDistribution
Step3) Specify the VIP Address created at DNS for Admin Servers # Administration server configuration domain2.AdminIP=<> domain2.AdminPasswd=<> Step 4) Update the Database Connection URL Parameters and If RAC DB used: domain2.DBURL=jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=on )(ADDRESS=(PROTOCOL=tcp)(HOST=<>)(PORT=<>))(ADDRESS=(PROTOCOL=tcp)(HOST=<>)(PORT=<>)))(CONNECT_DATA=(SERVICE_NAME=<>))) OR If no RAC DB: domain2.DBURL=jdbc:oracle:thin:@<>:<>/<> domain2.DBPASSWORD=<>
SOA/OSB Installation and Configuration Guide by Lokesh T C
4. Execute the below command for creating domain. Change directory to – cd /u01/shared/11g/wlst wlst.sh CreateAdditionalSOADomain.py SOAExtDomain SOAExtDomain: [Applicable only for cluster] 1) Open file $WLSDOMAIN/SOAExtDomain/aserver/SOAExtDomain/bin/setDomainEnv.sh 2) Search for the below text # IF USER_MEM_ARGS the environment variable is set, use it to override ALL MEM_ARGS values
3) Add the
below entry as a next line at the mentioned step (2).
USER_MEM_ARGS=<> export USER_MEM_ARGS
4) save the file
18.2.3 Standalone based domain Creation using WLST Script for “SOACoreDomain” [Applicable only for Standalone] This section of the document provides a step by step process for running the automated WLST script to create a standalone domain of Oracle WebLogic Domain Configuration. [Please refer to the appendix section C for IP and HostName details] Note: APPLICABLE Only for STANDALONE box and not intended for PRODUCTION setup. 1. Login into Node1 using oracle user account. 2. Go to software folder on the node1 where the below files are located. 1) CreateStandaloneCoreSOADomain.py 2) domain.properties 3. Open file “domain.properties” and change the information as per the environment capacity and in Production Replica type of environments leave the default values as is. Step 1) Change the value to “dev” if the configuration of the environment is Development otherwise “prod” SERVER_MODE=prod
Step 2) Specify the hostname or Physcial IP Address. domain1.cadm-vip1=<>
SOA/OSB Installation and Configuration Guide by Lokesh T C
Step 2) Configure the JVM memory. domain1.Admin_Java_Arguments=<>
Modify the JVM Arguments as below: domain1.Admin_Java_Arguments=–Xss512k -XX:PermSize=768m -XX:MaxPermSize=768m –Xms4g – Xmx4g –XX:NewRatio=2 -XX:+AggressiveOpts -XX:+UseParallelGC -XX:+UseParallelOldGC XX:ParallelGCThreads=2 -XX:InitialSurvivorRatio=10 -XX:SurvivorRatio=5 XX:+HeapDumpOnOutOfMemoryError XX:HeapDumpPath=/u01/export/home/oracle/crash/admin1_java.hprof -verbose:gc Xloggc:/u01/export/home/oracle/crash/admin1_gc.log -verbose:gc -XX:+PrintGCDetails XX:+PrintGCTimeStamps -XX:+PrintHeapAtGC -XX:+PrintTenuringDistribution
Step3) Specify the VIP Address created at DNS for Admin Servers # Administration server configuration domain1.AdminIP=<> [same as step 2] domain1.AdminPasswd=<> Note: AdminPasswd should be of minimum 8 characters consisting of alphanumeric characters Step 4) Update the Database Connection URL Parameters and If RAC DB used: domain1.DBURL=jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=on )(ADDRESS=(PROTOCOL=tcp)(HOST=<>)(PORT=<>))(ADDRESS=(PROTOCOL=tcp)(HOST=<>)(PORT=<>)))(CONNECT_DATA=(SERVICE_NAME=<>))) OR If no RAC DB: domain1.DBURL=jdbc:oracle:thin:@<>:<>/<> domain1.DBPASSWORD=<>
4. Execute the below command for creating domain. Change directory to – cd /u01/shared/11g/wlst wlst.sh CreateStandaloneCoreSOADomain.py SOACoreDomain
5. Modify the JVM Memory parameters in setDomainEnv.sh SOACoreDomain: [Applicable for Standalone]
SOA/OSB Installation and Configuration Guide by Lokesh T C
•
Open file $WLSDOMAIN/SOACoreDomain/aserver/SOACoreDomain/bin/setDomainEnv.sh
•
Search for the below text # IF USER_MEM_ARGS the environment variable is set, use it to override ALL
MEM_ARGS values
•
Add the
below entry as a next line at the mentioned step (2).
USER_MEM_ARGS=<> export USER_MEM_ARGS
•
save the file
18.2.4 Creating a Separate Domain Directory for Managed Servers in the Same Node as the Administration Server for SOACoreDomain [Applicable only for Cluster]
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 in node1. Take a backup of existing jar if already exists: mv $WLSHOME/common/bin/soaosbwlsdomaintemplate.jar $WLSHOME/common/bin/soaosbwlsdomaintemplate<>.jar
1. Run the pack command on Node1 to create a template pack as follows: cd $WLSHOME/common/bin ./pack.sh -managed=true -domain=$WLSDOMAIN/SOACoreDomain/aserver/SOACoreDomain template=soaosbwlsdomaintemplate.jar -template_name=soa_osb_wls_domain_template
18.2.5 Propagating the Domain Configuration to all the nodes Using the unpack for SOACoreDomain [Applicable only for Cluster]
To propagate the domain configuration, complete these steps: 1. Run the following command on Node1 to copy the template file created in the previous step to node2,node3 and node4. 2. node1> cd $WLSHOME/common/bin 3. node1> scp soaosbwlsdomaintemplate.jar oracle@<>:$WLSHOME/common/bin 4. node1> scp soaosbwlsdomaintemplate.jar oracle@<>:$WLSHOME/common/bin 5. node1> scp soaosbwlsdomaintemplate.jar oracle@<>:$WLSHOME/common/bin
6. Run the unpack command on Node1, Node2,Node3 & Node4 to unpack the propagated template. Note: "It is required to remove the existing domain directory in node2/node3/node4 or the operation will fail.
SOA/OSB Installation and Configuration Guide by Lokesh T C
The unpack command will create a new domain directory for you. This means that if you have made any configuration changes specific to the managed servers (such as MS1/OSB1/SOA1 etc) running on the nodes (node1/2/3/4) where you are running the unpack command, you will have to redo these configuration changes. Node1> cd $WLSHOME/common/bin
Take a backup of existing MServer folder if already exists: mv $MWHOME/admin/SOACoreDomain $MWHOME/admin/SOACoreDomain<> Node1> cd $WLSHOME/common/bin Node1> ./unpack.sh -domain=$MWHOME/admin/SOACoreDomain/mserver/SOACoreDomain/ template=soaosbwlsdomaintemplate.jar app_dir=$MWHOME/admin/SOACoreDomain/mserver/applications -overwrite_domain=true Node2> cd $WLSHOME/common/bin
Take a backup of existing MServer folder if already exists: mv $MWHOME/admin/SOACoreDomain $MWHOME/admin/SOACoreDomain<> Node2> ./unpack.sh -domain=$MWHOME/admin/SOACoreDomain/mserver/SOACoreDomain/ template=soaosbwlsdomaintemplate.jar app_dir=$MWHOME/admin/SOACoreDomain/mserver/applications -overwrite_domain=true Node3> cd $WLSHOME/common/bin
Take a backup of existing MServer folder if already exists: mv $MWHOME/admin/SOACoreDomain $MWHOME/admin/SOACoreDomain<> Node3> ./unpack.sh -domain=$MWHOME/admin/SOACoreDomain/mserver/SOACoreDomain/ template=soaosbwlsdomaintemplate.jar app_dir=$MWHOME/admin/SOACoreDomain/mserver/applications -overwrite_domain=true Node4> cd $WLSHOME/common/bin
Take a backup of existing MServer folder if already exists: mv $MWHOME/admin/SOACoreDomain $MWHOME/admin/SOACoreDomain<> Node4> ./unpack.sh -domain=$MWHOME/admin/SOACoreDomain/mserver/SOACoreDomain/ template=soaosbwlsdomaintemplate.jar app_dir=$MWHOME/admin/SOACoreDomain/mserver/applications -overwrite_domain=true
18.2.6 Creating a Separate Domain Directory for Managed Servers in the Same Node as the Administration Server for SOAExtDomain [Applicable only for Cluster]
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 in node1. Take a backup of existing jar if already exists: mv $WLSHOME/common/bin/soaextdomaintemplate.jar $WLSHOME/common/bin/soaextdomaintemplate<>.jar
SOA/OSB Installation and Configuration Guide by Lokesh T C
1. Run the pack command on Node1 to create a template pack as follows: cd $WLSHOME/common/bin ./pack.sh -managed=true -domain=$WLSDOMAIN/SOAExtDomain/aserver/SOAExtDomain template=soaextdomaintemplate.jar -template_name=soaextdomaintemplate_template
18.2.7 Propagating the Domain Configuration to all the nodes Using the unpack for SOAExtDomain [Applicable only for Cluster]
To propagate the domain configuration, complete these steps: 1. Run the following command on Node1 to copy the template file created in the previous step to node2,node3 and node4. 2. node1> cd $WLSHOME/common/bin 3. node1> scp soaextdomaintemplate.jar oracle@<>:$WLSHOME/common/bin 3. node1> scp soaextdomaintemplate.jar oracle@<>:$WLSHOME/common/bin 3. node1> scp soaextdomaintemplate.jar oracle@<>:$WLSHOME/common/bin
5. Run the unpack command on Node2,Node3 & Node4 to unpack the propagated template. Note: "It is required to remove the existing domain directory in node2/node3/node4 or the operation will fail. The unpack command will create a new domain directory for you. This means that if you have made any configuration changes specific to the managed servers (such as SOA5 etc) running on the nodes (node1/2/3/4) where you are running the unpack command, you will have to redo these configuration changes. Node1> cd $WLSHOME/common/bin
Take a backup of existing MServer folder if already exists: mv $MWHOME/admin/SOAExtDomain $MWHOME/admin/SOAExtDomain<> Node1> ./unpack.sh -domain=$MWHOME/admin/SOAExtDomain/mserver/SOAExtDomain/ template=soaextdomaintemplate.jar app_dir=$MWHOME/admin/SOAExtDomain/mserver/applications -overwrite_domain=true Node2> cd $WLSHOME/common/bin
Take a backup of existing MServer folder if already exists: mv $MWHOME/admin/SOAExtDomain $MWHOME/admin/SOAExtDomain<> Node2> ./unpack.sh -domain=$MWHOME/admin/SOAExtDomain/mserver/SOAExtDomain/ template=soaextdomaintemplate.jar app_dir=$MWHOME/admin/SOAExtDomain/mserver/applications -overwrite_domain=true Node3> cd $WLSHOME/common/bin
Take a backup of existing MServer folder if already exists: mv $MWHOME/admin/SOAExtDomain $MWHOME/admin/SOAExtDomain<>
SOA/OSB Installation and Configuration Guide by Lokesh T C
Node3> ./unpack.sh -domain=$MWHOME/admin/SOAExtDomain/mserver/SOAExtDomain/ template=soaextdomaintemplate.jar app_dir=$MWHOME/admin/SOAExtDomain/mserver/applications -overwrite_domain=true Node4> cd $WLSHOME/common/bin
Take a backup of existing MServer folder if already exists: mv $MWHOME/admin/SOAExtDomain $MWHOME/admin/SOAExtDomain<> Node4> ./unpack.sh -domain=$MWHOME/admin/SOAExtDomain/mserver/SOAExtDomain/ template=soaextdomaintemplate.jar app_dir=$MWHOME/admin/SOAExtDomain/mserver/applications -overwrite_domain=true
18.2.8 Configure SetDomainEnv.sh [Applicable for standalone and cluster] Node1> cd $SHARED_MOUNT/wlst and run the below command ./find_and_replace_in_files.sh Node2> cd $SHARED_MOUNT/wlst and run the below command ./find_and_replace_in_files.sh Node3> cd $SHARED_MOUNT/wlst and run the below command ./find_and_replace_in_files.sh Node4> cd $SHARED_MOUNT/wlst and run the below command ./find_and_replace_in_files.sh
18.2.9 Configure Node Manager [Applicable for standalone and cluster] 1. Start Node Manager
On each server, start the Node managers, to create the initial property file. Stop the node manager after is has been started. , see appendix. Change directory to – cd /u01/shared/11g/wlst ./StartNodeManager.sh
2. Enable Start and Stop through Node Manager
Edit the node manager configuration to enable the stop and start using shell scripts. cd $WLSHOME/common/nodemanager vi nodemanager.properties and set/add the following properties StartScriptEnabled=true
SOA/OSB Installation and Configuration Guide by Lokesh T C
StopScriptEnabled=true NativeVersionEnabled=false SecureListener=false DomainRegistrationEnabled=true
This will enable the nodemanager to start and stop using shell scripts. Repeat this step on all the nodes Start the node managers on each server, see appendix B.
18.2.10 Enroll the Machine with Node Manager [Applicable standalone and cluster]
Note: Ensure that the admin servers are running on node1 and node4 before you proceed with the below steps. Refer Appendix B for starting Admin Server (SOACoreDomain and SOAExtDomain). To enroll the machine with Node Manager using below command:
1) Copy the file to any location on all nodes, where the domain.properties was modified lastime. If domain.properties file not avaiable then please copy it from node1 to all the nodes. enrollnodemanager.py 2) Execute the following command on all the nodes (Node1/Node2/Node3/Node4). cd $SHARED_MOUNT/wlst wlst.sh enrollnodemanager.py SOACoreDomain wlst.sh enrollnodemanager.py SOAExtDomain
18.2.11 Start and test server URL’s
Start all the Managed Servers as per the architecture diagram on all nodes. See appendix on how to start Managed servers. Verify for each node if the following URL's are working. Here node1 and node4 must use LB IP Address/Alias Name or VIP of DNS configured for node1 and node4 only. http://<
Host Host Host Host
for for for for
SOACoreDomain>>/soa-infra SOACoreDomain>>/b2bconsole SOACoreDomain>>/console SOACoreDomain>>/integration/worklistapp
http://<
Host Host Host Host
for for for for
SOAExtDomain>>//soa-infra SOAExtDomain>>/b2bconsole SOAExtDomain>>/console SOAExtDomain>>/integration/worklistapp
Check in enterprise manager that the whole SOA Infra is up and running. http://<>:8000/em
SOA/OSB Installation and Configuration Guide by Lokesh T C
http://<>:9000/em
Check OSB Console running. http://<>:8000/sbconsole Please refer to Appendix B for starting all the manager servers
19 Post Configuration Steps
19.1.1 Configure HTTP Front end host and port [Applicable for cluster]
Apply the settings for SOACoreDomain: Navigate to the following URL: 1. 2. 3. 4. 5. 6. 7.
http://<>:8000/console Expand Environment tree Click to Clusters Click on OSBCluster Click on HTTP Tab Click on Lock & Edit button on the top left corner. Enter the Appropriate Front end Host and HTTP port for OSB Cluster, which is a Load Balancer IP and port. 8. Click on Save Navigate to the following URL: 1. 2. 3. 4. 5. 6. 7.
http://<>:8000/console Expand Environment tree Click to Clusters Click on SOACluster Click on HTTP Tab Click on Lock & Edit button on the top left corner. Enter the Appropriate Front end Host and HTTP port for SOA Core Cluster, which is a Load Balancer IP and port. 8. Click on Save
Navigate to the following URL: http://<>:8000/console Expand Environment tree Click to Clusters Click on WLSCoreCluster Click on HTTP Tab Click on Lock & Edit button on the top left corner. Enter the Appropriate Front end Host and HTTP port for WLS Core Cluster, which is a Load Balancer IP and port. 8. Click on Save
1. 2. 3. 4. 5. 6. 7.
SOA/OSB Installation and Configuration Guide by Lokesh T C
Apply the settings for SOAExtDomain: Navigate to the following URL: http://<>:9000/console Expand Environment tree Click to Clusters Click on SOAExtCluster Click on HTTP Tab Click on Lock & Edit button on the top left corner. Enter the Appropriate Front end Host and HTTP port for SOAExtCluster, which is a Load Balancer IP and port. 8. Click on Save 1. 2. 3. 4. 5. 6. 7.
19.1.2 Configure SOAP Url and Callback Url [Applicable for cluster]
Apply the settings for SOACoreDomain: Navigate 1. 2. 3. 4.
to the following URL: http://<>:8000/em Go to Farm_soadomain tree Expand the SOA tree item Right-click-mouse on ‘soa-infra’ and go to 1) SOA Administration •
Common Properties
Change the two URLs: Callback Server: http://<> Server: http://<> Click on Apply Verify the changes are cascaded on all SOA servers [ex:SOA1,SOA2,SOA3,SOA4]
Apply the settings for SOAExtDomain: Navigate 1) 2) 3) 4)
to the following URL: http://>:9000/em Go to Farm_soadomain tree Expand the SOA tree item Right-click-mouse on ‘soa-infra’ and go to 1. SOA Administration 1. Common Properties Change the two URLs: Callback Server: http://<> Server: http://<>
SOA/OSB Installation and Configuration Guide by Lokesh T C
Click on Apply Verify the changes are cascaded on all SOA servers [ex:SOA5, SOA6, SOA7]
19.1.3 Configure common libraries to the server classpath
MQ Library 1. Get the file from SAMI common/lib/com.ibm.mq.jar 2. Copy the “com.ibm.mq.jar” to domain lib folder. 3. Go to location where the file “com.ibm.mq.jar” is present and use the below command to copy it to domain folder. [Applicable for Cluster and Standalone] SOACoreDomain: cp com.ibm.mq.jar $WLSDOMAIN/SOACoreDomain/lib [Applicable for Cluster] SOAExtDomain: cp com.ibm.mq.jar $WLSDOMAIN/SOAExtDomain/lib
XPath Library [Applicable for Cluster and Standalone] 1) Get the file from SAMI common/lib/CustomXPathFunctions.jar 2) Copy the “CustomXPathFunctions.jar” to domain lib folder. 3) Go to location where the file “CustomXPathFunctions.jar” is present and use the below command to copy it to domain folder. SOACoreDomain: cp CustomXPathFunctions.jar $WLSDOMAIN/SOACoreDomain/lib [Applicable for Cluster] SOAExtDomain: cp CustomXPathFunctions.jar $WLSDOMAIN/SOAExtDomain/lib
19.1.4 Purging SOA Suite 11g Composites Instances (Optional) The PL/SQL purge scripts contain procedures that you will execute with various options depending upon your purging goals. The PL/SQL procedures are installed or loaded by the one time execution of the PL/SQL script in your dehydration store. After the PL/SQL script has been run, you can then execute the various PL/SQL procedures to purge instances as needed. 1.
Log in to the schema
SOA/OSB Installation and Configuration Guide by Lokesh T C
If you're using 11g Oracle BPEL Process Manager installed as part of an 11g Oracle SOA Suite or 11g Oracle BPM Suite, you'll start by granting the privileges to the SOA_SOAINFRA user, then logging in to the SOA_SOAINFRA schema. Use Case 11.1.1.5 SOAINFRA Schema in an Oracle Database 10.2.0.4.0 sqlplus /nolog >sqlplus / as sysdba SQL> GRANT EXECUTE ON DBMS_LOCK TO SOA_SOAINFRA; Grant succeeded. SQL> GRANT CREATE ANY JOB TO SOA_SOAINFRA; Grant succeeded. SQL>exit >sqlplus SOA_SOAINFRA/
2.
Install the Procedures (First time Users Only )
Run the script to install the procedures. This is a one time installation step. Use Case 11.1.1.5 SOAINFRA Schema in an Oracle Database 10.2.0.4 SQL> @/rcu/integration/soainfra/sql/soa_purge/soa_purge_scripts.sql Procedure created. Function created. Type created. Type body created. PL/SQL procedure successfully completed. Package created. Package body created. SQL>
To check if the procedure exists in the schema, use a simple select statement such as this: SQL> select owner, object_name, object_type, created, last_ddl_time, timestamp from dba_objects where object_type='PACKAGE BODY' and object_name='SOA';
3.
Identify and/or Customize the Purge Procedure
You will need to identify the syntax and possibly customize the procedure according to your purging goal. Depending upon the version, there may be several possible procedures available for use. Review the text of the installation script or the product documentation for more details on the procedures. 4.
Call the Procedure
Once the procedure is loaded and you've identified the method you'll use to purge instances, you'll run the procedure. You may want to perform a simple select statement to count the existing instances prior to purging.
Use Case 11.1.1.5 SOAINFRA Schema in an Oracle Database 10.2.0.4 SQL> select count(cikey) from composite_instance;
•
To clear out instances from a specific date/time (ie...January 1, 2011 to January 31, 2011) with a retention for all instances updated by January 31 2011, batch of 20000 instances with a runtime of 60 minutes call delete_instances ( to_timestamp('2010-01-01','YYYY-MM-DD'), to_timestamp('2010-01-31','YYYY-MM-DD'),20000,60,to_timestamp('2010-01-31','YYYY-MMDD'),false);
•
To clear out instances using the explicit single threaded script as shown in the readme (ie.. January 1, 2011 to January 31, 2011):
SOA/OSB Installation and Configuration Guide by Lokesh T C
DECLARE MAX_CREATION_DATE timestamp; MIN_CREATION_DATE timestamp; batch_size integer; max_runtime integer; retention_period timestamp; BEGIN MIN_CREATION_DATE := to_timestamp('2010-01-01','YYYY-MM-DD'); MAX_CREATION_DATE := to_timestamp('2010-01-31','YYYY-MM-DD'); max_runtime := 60; retention_period := to_timestamp('2010-01-31','YYYY-MM-DD'); batch_size := 10000; soa.delete_instances( min_creation_date => MIN_CREATION_DATE, max_creation_date => MAX_CREATION_DATE, batch_size => batch_size, max_runtime => max_runtime, retention_period => retention_period, purge_partitioned_component => false); END; /
•
To clear out instances using the explicit parallel script as shown in the readme (ie.. January 1, 2011 to January 31, 2011): (Ensure to grant following privileges to soainfra user: 'Create Job' and 'execute on dbms_lock') DECLARE max_creation_date timestamp; min_creation_date timestamp; retention_period timestamp; BEGIN min_creation_date := to_timestamp('2010-01-01','YYYY-MM-DD'); max_creation_date := to_timestamp('2010-01-31','YYYY-MM-DD'); retention_period := to_timestamp('2010-01-31','YYYY-MM-DD'); soa.delete_instances_in_parallel( min_creation_date => min_creation_date, max_creation_date => max_creation_date, batch_size => 10000, max_runtime => 60, retention_period => retention_period, DOP => 3, max_count => 1000000, purge_partitioned_component => false); END; /
Parallel procedure has been designed to spawn multiple database jobs which will purge the SOA dehydration store data in parallel. This procedure is designed to purge large SOA dehydration stores housed on high-end database nodes with multiple CPUs and good IO sub-system. It is recommended that this procedure is executed during a maintenance window, as it acquires a lot of resources and may contend with normal online operations. To determine the optimal number of jobs to spawn will require on-site testing and tuning. As a rule of thumb, the number of jobs should not exceed the number of CPUs on the node by more than one. For example, on a quad core / 4 thread CPU rdbms box you may set and run the script to from 1-4 to match the number of CPUs.
SOA/OSB Installation and Configuration Guide by Lokesh T C
Note The retention_period is applied only on BPEL where users would want to retain the composite instances based on the modify_date on the BPEL instances (cube_instance). In this case, the modify_date of the BPEL instances table, which can be different than the composite created_date, is used as a second level of filtering. for example: min_creation_date = 1st June 2011 max_creation_date = 30 June 2011 retention_period = 1st July 2011 The above will delete all "composite instances" where created_time of composite between 1st June 2011 and 30 June 2011 and modify_date of cube_instance < 1st July 2011. 5. Recover Space as needed - optional Space recovery is not included in the Purge Script as this is a specific Database Maintenance task that needs to be performed by a DBA. The following sample instructions can help in space recovery: 1. Run an index rebuild
Rebuilding an Existing Index 2. Running PL/SQL for space release: alter table deallocate unused; alter table enable row movement; alter table shrink space compact; alter table shrink space; alter table disable row movement;
Table Reference: audit_trail, audit_details, cube_instance, cube_scope, dlv_message, dlv_message_ref, dlv _subscription, document_ci_ref, document_dlv_message_ref, invoke_message, header_properties, work_item, wi_fault, xml_document
For example; alter table audit_trail alter table audit_trail alter table audit_trail alter table audit_trail alter table audit_trail
deallocate unused; enable row movement; shrink space compact; shrink space; disable row movement;
... through to; alter alter alter alter alter
table table table table table
xml_document xml_document xml_document xml_document xml_document
deallocate unused; enable row movement; shrink space compact; shrink space; disable row movement;
19.1.5 Improve SOA 11g Purge Performance (Optional) Customize the Purge Procedure There are a couple of optimizations that are available for purging. The following indexes can help in purge performance but the decision to use these indexes should be left to your DBA.
SOA/OSB Installation and Configuration Guide by Lokesh T C
NOTE: In general you are free to create or remove indexes as per requirement. Advise that these indexes could help in purge but decision to use these indexes should be left to DBA, who need to do analysis of database/environment and ensure that these indexes are really needed and help on overall performance. SQL> create index temp_cube_instance_idx on temp_cube_instance(cikey); SQL> create index dlv_message_cikey_idx1 on dlv_message(cikey); The below two indexes should be analyzed by a senior DBA prior implementation: SQL> create index on DOCUMENT_DLV_MSG_REF.DOCUMENT_ID; SQL> create index on REFERENCE_INSTANCE.COMPOSITE_INSTANCE_ID;
We have seen that in some cases, due to the large amount of data being deleted from SOAINFRA schema, there is some performance degradation on SOA runtime processing. It is always good practice to update Table Statistics and perform an Index Rebuild in order to recover performance. 1.
Rebuilding an Existing Index
Before rebuilding an existing index, compare the costs and benefits associated with rebuilding to those associated with coalescing indexes The following statement rebuilds the existing index emp_name: ALTER INDEX REBUILD; The REBUILD clause must immediately follow the index name, and precede any other options. It cannot be used in conjunction with the DEALLOCATE UNUSED clause. You have the option of rebuilding the index online. Rebuilding online enables you to update base tables at the same time that you are rebuilding. The following statement rebuilds the emp_name index online: ALTER INDEX REBUILD ONLINE;
Note: Online index rebuilding has stricter limitations on the maximum key length that can be handled, compared to other methods of rebuilding an index. If an ORA-1450 (maximum key length exceeded) error occurs when rebuilding online, try rebuilding offline, coalescing, or dropping and recreating the index. 2.
Making an Index Invisible
To make a visible index invisible, issue this statement: ALTER INDEX index INVISIBLE; To make an invisible index visible, issue this statement: ALTER INDEX index VISIBLE; To find out whether an index is visible or invisible, query the dictionary views USER_INDEXES, ALL_INDEXES, or DBA_INDEXES. For example, to determine if the index IND1 is invisible, issue the following query: SELECT INDEX_NAME, VISIBILITY FROM USER_INDEXES WHERE INDEX_NAME = 'IND1';
SOA/OSB Installation and Configuration Guide by Lokesh T C
INDEX_NAME ---------IND1 3.
VISIBILITY ---------VISIBLE
Renaming an Index
To rename an index, issue this statement: ALTER INDEX index_name RENAME TO new_name; 4.
Monitoring Index Usage
Oracle Database provides a means of monitoring indexes to determine whether they are being used. If an index is not being used, then it can be dropped, eliminating unnecessary statement overhead. To start monitoring the usage of an index, issue this statement: ALTER INDEX index MONITORING USAGE; Later, issue the following statement to stop the monitoring: ALTER INDEX index NOMONITORING USAGE; The view V$OBJECT_USAGE can be queried for the index being monitored to see if the index has been used. The view contains a USED column whose value is YES or NO, depending upon if the index has been used within the time period being monitored. The view also contains the start and stop times of the monitoring period, and a MONITORING column (YES/NO) to indicate if usage monitoring is currently active. Each time that you specify MONITORING USAGE, the V$OBJECT_USAGE view is reset for the specified index. The previous usage information is cleared or reset, and a new start time is recorded. When you specify NOMONITORING USAGE, no further monitoring is performed, and the end time is recorded for the monitoring period. Until the next ALTER INDEX...MONITORING USAGE statement is issued, the view information is left unchanged. 19.1.6 Create SOA Partitions
[Applicable for Cluster and Standalone] Apply the settings for SOACoreDomain: $ORACLE_HOME/common/bin/wlst.sh soaManagePartition.py t3://<>:<<8004>> For standalone use 8000 port
[Applicable for Cluster] Apply the settings for SOAExtDomain: $ORACLE_HOME/common/bin/wlst.sh soaManagePartition.py t3://<>:<<9004>> For standalone use 9000 port
SOA/OSB Installation and Configuration Guide by Lokesh T C
19.1.7 Create Application Users
[Applicable for Cluster and Standalone] Apply the settings for SOACoreDomain: 1. Open file "UserManagement_SOACoreDomain.properties" 2. Modify the password as per your SOX statndards ( Ensure that password must have atleast 8 characters in length and atleast one numeric charters) a. Modify the Admin URL, UserName and Password for SOACore Domain. b. Run the command $ORACLE_HOME/common/bin/wlst.sh UserManagement.py c. Enter the Domain Name as SOACoreDomain
[Applicable for Cluster only] Apply the settings for SOAExtDomain: 1. Open file "UserManagement_SOAExtDomain.properties" 2. Modify the password as per your SOX statndards ( Ensure that password must have atleast 8 characters in length and atleast one numeric charters) a. Modify the Admin URL, UserName and Password for SOAExtDomain. b. Run the command $ORACLE_HOME/common/bin/wlst.sh UserManagement.py c. Enter the Domain Name as SOAExtDomain
19.1.8 Create Application Resources [Applicable for Cluster only]
Apply the settings for SOACoreDomain: Open file "ResourceAdapter_SOACoreDomain.properties" and edit the following key-value pairs 1. domain1.xref.connectionpool.password.1=<> 2. domain1.om.connectionpool.password.2=<> 3. domain1.soa.connectionpool.password.3=<> 4. domain1.jms.connectionpool.password.4=<> 5. domain1.resource.ftpHost=<< node FTP HOST>> 6. domain1.resource.ftpUserName=<< node FTP HOST>> 7. domain1.resource.ftpPassword=<> 8. domain1.resource.mqQueueManager=<> 9. domain1.resource.mqHost=<>
SOA/OSB Installation and Configuration Guide by Lokesh T C
10. domain1.total.mq.nodes=1 11. Based on the step (10) set node1,node2,node3 and node4 values for the following keys domain1.mqsiebel.resource.mqport.node.1=<> domain1.mqsiebel.resource.mqChannel.node.1=<> domain1.mqsiebel.resource.mqport.node.2=<> domain1.mqsiebel.resource.mqChannel.node.2=<>
domain1.mqsiebel.resource.mqport.node.3=<> domain1.mqsiebel.resource.mqChannel.node.3=<>
domain1.mqsiebel.resource.mqport.node.4=<> domain1.mqsiebel.resource.mqChannel.node.4=<>
12. global.resource.deployment.plan.path=<> mkdir -p $WLSDOMAIN/deployplan 13. Run the command to create JDBC Resources for SOACoreDomain $ORACLE_HOME/common/bin/wlst.sh JDBCResourceCreation.py SOACoreDomain Note: If you get any error, login into /console and click on undo all changes before resuming it again after the fix. 14. Run the command to create Adapter Resources for SOACoreDomain $ORACLE_HOME/common/bin/wlst.sh ResourceAdapterCreation.py SOACoreDomain [Applicable for Standalone only] Open file "ResourceAdapter_SOACoreDomain.properties" and edit the following key-value pairs 1. domain1.xref.connectionpool.password.1=<> 2. domain1.om.connectionpool.password.2=<> 3. domain1.soa.connectionpool.password.3=<> 4. domain1.jms.connectionpool.password.4=<> 5. domain1.resource.ftpHost=<< node FTP HOST>> 6. domain1.resource.ftpUserName=<< node FTP HOST>>
SOA/OSB Installation and Configuration Guide by Lokesh T C
7. domain1.resource.ftpPassword=<> 8. domain1.resource.mqQueueManager=<> 9. domain1.resource.mqHost=<> 10. domain1.total.mq.nodes=<> 11. Based on the step (10) set node1, values for the following keys domain1.mqsiebel.resource.mqport.node.1=<> domain1.mqsiebel.resource.mqChannel.node.1=<>
12. global.resource.deployment.plan.path=<> mkdir –p $WLSDOMAIN/deployplan 13. Open file “ResourceAdapter_SOACoreDomain.properties” and set the following key value pairs domain1.xref.datasource.target.1=Servers/AdminServer domain1.om.datasource.target.2=Servers/AdminServer domain1.soa.datasource.target.3=Servers/AdminServer domain1.jms.datasource.target.4=Servers/AdminServer
14. Run the command to create JDBC Resources for SOACoreDomain $ORACLE_HOME/common/bin/wlst.sh JDBCResourceCreation.py SOACoreDomain Note: If you get any error, login into /console and click on undo all changes before resuming it again after the fix. 15. Run the command to create Adapter Resources for SOACoreDomain $ORACLE_HOME/common/bin/wlst.sh ResourceAdapterCreation.py SOACoreDomain [Applicable for Cluster only]
Apply the settings for SOAExtDomain: Open file "ResourceAdapter_SOAExtDomain.properties" and edit the following key-value pairs 1. domain1.xref.connectionpool.password.1 =<> 2. domain1.om.connectionpool.password.2=<> 3. domain1.soa.connectionpool.password.3=<> 4. domain1.resource.ftpHost=<< node FTP HOST>>
SOA/OSB Installation and Configuration Guide by Lokesh T C
5. domain1.resource.ftpUserName=<< node FTP HOST>> 6. domain1.resource.ftpPassword=<> 7. domain1.resource.mqQueueManager=<> 8. domain1.resource.mqHost=10.15.35.35 <> 9. domain1.total.mq.nodes=1 1. Based on the step (10) set node1,node2,node3 and node4 values for the following keys domain1.mqsiebel.resource.mqport.node.1=<> domain1.mqsiebel.resource.mqChannel.node.1=<> domain1.mqsiebel.resource.mqport.node.2=<> domain1.mqsiebel.resource.mqChannel.node.2=<>
domain1.mqsiebel.resource.mqport.node.3=<> domain1.mqsiebel.resource.mqChannel.node.3=<>
10. global.resource.deployment.plan.path=<> mkdir –p $WLSDOMAIN/deployplan 11. Run the command to create JDBC Resources for SOAExtDomain $ORACLE_HOME/common/bin/wlst.sh JDBCResourceCreation.py SOAExtDomain Note: If you get any error, login into /console and click on undo all changes before resuming it again after the fix. 12. Run the command to create Adapter Resources for SOACoreDomain $ORACLE_HOME/common/bin/wlst.sh ResourceAdapterCreation.py SOAExtDomain
19.1.9 Modify JDBC Datasource Parameters Run the following command to update datasource properties for OSB and MDS
Apply the settings for SOACoreDomain: 1. Go to $SHARED_MOUNT/wlst folder 2. Run te below command [Applicable for Cluster only] $ORACLE_HOME/common/bin/wlst.sh ModifyDataSourceParams.py Cluster
SOA/OSB Installation and Configuration Guide by Lokesh T C
[Applicable for Standalone only] $ORACLE_HOME/common/bin/wlst.sh ModifyDataSourceParams.py StandAlone
Apply the settings for SOAExtDomain: None 19.1.10 Migrate from JMS FileStore to JDBC Store
Apply the settings for SOACoreDomain: 1. Go to $SHARED_MOUNT/wlst folder 2. Run te below command [Applicable for Cluster only] $ORACLE_HOME/common/bin/wlst.sh MigrateJMSFiletoJDBCStoreSOACoreDomain.py Cluster [Applicable for Standalone only] $ORACLE_HOME/common/bin/wlst.sh MigrateJMSFiletoJDBCStoreSOACoreDomain.py StandAlone
Apply the settings for SOAExtDomain: 1. Go to $SHARED_MOUNT/wlst folder 2. Run te below command [Applicable for Cluster only] $ORACLE_HOME/common/bin/wlst.sh MigrateJMSFiletoJDBCStoreSOAExtDomain.py Cluster
19.1.11 Create TLOG Recovery Folder for migratable servers. [Applicable for Cluster only]
Apply the settings for SOACoreDomain: 1. Run the following command mkdir -p $WLSDOMAIN/SOACoreDomain/soa_cluster/tlogs 2. Go to $SHARED_MOUNT/wlst folder 3. Run te below command $ORACLE_HOME/common/bin/wlst.sh CreateTlogPath_SOACoreDomain.py
Apply the settings for SOAExtDomain: 1. Run the following command mkdir -p $WLSDOMAIN/SOAExtDomain/soa_cluster/tlogs 2. Go to $SHARED_MOUNT/wlst folder 3. Run te below command $ORACLE_HOME/common/bin/wlst.sh CreateTlogPath_SOAExtDomain.py
SOA/OSB Installation and Configuration Guide by Lokesh T C
19.1.12 Configure Server LogHandler Note: # List of Log Levels # trace, debug, info, notice, warning, error, critical, alert, emergency [Applicable for Cluster only]
1. Open “domain_log.properties” file and edit following values For Production and UAT/NFT (BLUE), set the following values stdoutSeverity = error logBRSeverity = error logFileSeverity = Info memBufferSeverity = error Other than Production and UAT/NFT (BLUE), set the following values stdoutSeverity = Info logBRSeverity = Info logFileSeverity = Info memBufferSeverity = Info 2. Change the SOACoreDomain and SOAExtDomain Server URL’s and credentials domain.1.admin.url=t3://<>:8000 domain.1.admin.password=<> domain.2.admin.url=t3:// <>:9000 domain.2.admin.password=<> 3. Run the following command $SOAHOME/common/bin/wlst.sh -i DomainLogConfigurtionChange.py > log.txt 4. Send the log.txt file to EAI Technical Validation team for further verification [Applicable for Standalone only]
2. Open “domain_log.properties” file and edit following values stdoutSeverity = Info logBRSeverity = Info logFileSeverity = Info memBufferSeverity = Info 3. Change the SOACoreDomain Server URL’s and credentials domain.1.admin.url=t3://<>:8000 domain.1.admin.password=<> 4. Change the below key-value pairt as suggested total.domain.count=1 total.domain.1.server.count=1
SOA/OSB Installation and Configuration Guide by Lokesh T C
5. Run the following command $SOAHOME/common/bin/wlst.sh -i DomainLogConfigurtionChange.py > log.txt 6. Send the log.txt file to EAI Technical Validation team for further verification. 19.1.13 Configuring OSB Memory Threshold parameters Login to SOACoreDomain Console 1. http://<>:8000/console 2. Expand Environment tree 3. Click to Servers 4. Click on OSB1 5. Click on Overload Tab 6. Click on Lock & Edit button on the top left corner. 7. Change the “Free Memory Percent High Threshold value to 10” 8. Change the “Free Memory Percent Low Threshold value to 20” 9. Click on Save 10. Click on activate the changes and release Note: Above steps has to be ompleted for rest OSB2,OSB3 and OSB4 Server 19.1.14 Mapping from 10G to 11G parameters
To configure automatically recovery attempts for invoke and callback messages: 1. In the navigator, right-click soa-infra and select SOA Administration > BPEL Properties. 2. Click More BPEL Configuration Properties. 3. Set the following properties to values and click Apply DispatcherEngineThreads =60 DispatcherInvokeThreads=40 DispatcherSystemThreads=3 DispatcherMaxRequestDepth =800 syncMaxWaitTime=240
4. Click Apply.
19.1.15 Configuring Auto Recovery for Oracle BPEL Process Manager
To disable auto recovery SOA/OSB Installation and Configuration Guide by Lokesh T C
1. 2. 3. 4. 5. 6. 7.
Log in to Oracle Enterprise Manager Fusion Middleware Control. Right-click soa-infra. Select SOA Administration > BPEL Properties. Click More BPEL Configuration Properties. In the Name column, click RecoveryConfig. Expand RecurringScheduleConfig. Set the following properties to values and click Apply. maxMessageRaiseSize =0
8. Expand StartupScheduleConfig, respectively. 9. Set the following properties to values and click Apply. maxMessageRaiseSize=0 19.1.16 Configuring Automatic Recovery Attempts for Invoke and Callback Messages
To configure automatically recovery attempts for invoke and callback messages: 5. In the navigator, right-click soa-infra and select SOA Administration > BPEL Properties. 6. Click More BPEL Configuration Properties. 7. Go to MaxRecoverAttempt and set the below value field. MaxRecoverAttempt=0
8. Click Apply. 19.1.17 Setting the global transaction timeout at Weblogic Domain Level
This property controls the transaction timeout seconds for active transactions. If the transaction is still in the "active" state after this time, it is automatically rolled back. * Log into Oracle WebLogic Administration Console. * Click Services -> JTA. * Change the value of Timeout Seconds to 7200 (the default is 30). * Click Save. * Restart Oracle WebLogic Server.
SOA/OSB Installation and Configuration Guide by Lokesh T C
19.1.18 Overriding the transaction timeout setting for BPEL EJB's
The timeout properties for the EJB's control the particular timeout setting for the SOA application, overriding the global setting specified by the JTA timeout * Log into Oracle WebLogic Administration Console. * Click Deployments. * Expand soa-infra -> EJBs. * Click on the configuration tab for the timeout setting for each of EJB’s listed below and the change the time out values as suggested. * Following EJBs need to be updated: [TBD] BPELActivityManagerBean [Change it to 300] BPELDeliveryBean [Change it to 300] BPELDispatcherBean [Change it to 300] BPELEngineBean [Change it to 300] BPELFinderBean [change it to 300] BPELInstanceManagerBean [change it to 300] BPELProcessManagerBean [change it to 300] BPELSensorValuesBean [change it to 300] BPELServerManagerBean [change it to 300] * Click Save. * Restart Oracle WebLogic Server.
19.1.19 Setting Up Node Manager and servers to install Identity and Trust KeyStores
This section describes how to configure Node Manager to enable host name verification for the communications between Node Manager, the Administration Server and Managed Servers. This requires
SOA/OSB Installation and Configuration Guide by Lokesh T C
the use of certificates for the different addresses communicating with the Administration Server. In this chapter, the steps for configuring VIP Host Name certificates for host name verification are provided.
1.1
About the Node Manager
The Node Manager enables you to start and stop the Administration Server and the managed servers.
1.2
Enabling Host Name Verification Certificates for Node Manager inall the nodes
Perform these steps to set up host name verification certificates for communication between the Node Manager and the Administration Server. Step 1: Generating Self-Signed Certificates Using the utils.CertGen Utility Step 2: Creating an Identity Keystore Using the utils.ImportPrivateKey Utility Step 3: Creating a Trust Keystore Using the keytool Utility Step 4: Configuring Node Manager to Use the Custom Keystores
1.3
Generating Self-Signed Certificates Using the utils.CertGen Utility
Follow these steps to create self-signed certificates on Physical Nodes and <> These certificates should be created using the network name/alias. 1. Set up your environment by running the (on any node) $WLSHOME/server/bin/setWLSEnv.sh
script: In the Bourne shell, run the following command: NODE1> . setWLSEnv.sh
Verify that the CLASSPATH environment variable is set: NODE1> echo $CLASSPATH
2. Create a user-defined directory for the certificates. For example, create a directory called certs under the $WLSDOMAIN directory. Note that certificates can be shared across WLS domains. 3. NODE1> cd $WLSDOMAIN 4. NODE1> mkdir certs
5. Change directory to the user-defined directory. 6. NODE1> cd certs 7. Run the utils.CertGen
tool from the user-defined directory to create the certificates for all EAI hosts
and VIP hosts. Syntax: java utils.CertGen [export | domestic] [hostname]
Examples: Login into Node1
SOA/OSB Installation and Configuration Guide by Lokesh T C
For Physical Nodes: NODE1> java utils.CertGen welcome1 <>_cert <>_key domestic <> java utils.CertGen welcome1 <>_cert <>_key domestic <> java utils.CertGen welcome1 <>_cert <>_key domestic <> java utils.CertGen welcome1 <>_cert <>_key domestic <>
Repeat the following step for all the VIP Host names which are present in the appendix [NA for Standalone as VIP Host names may not be used] [WE CAN SKIP THE BELOW SECTIONS IF HOSTNAME VERIFICATION IS NOT PLANNED TO USE] NODE1> java utils.CertGen welcome1 <>
HOST NAME1>>_cert <>_key
java utils.CertGen welcome1 <>_cert <>_key domestic <>
SOA/OSB Installation and Configuration Guide by Lokesh T C
1.4
Creating an Identity Keystore Using the utils.ImportPrivateKey Utility
Follow these steps to create an Identity Keystore for all Physical Nodes and <>. 1. Create a new identity keystore called appIdentity KeyStore using the utils.ImportPrivateKey utility. Create this keystore under the same directory as the certificates (i.e $WLSDOMAIN/certs). Note: The Identity Store is created (if none exists) when you import a certificate and the corresponding key into the Identity Store using the utils.ImportPrivateKey utility. Import the certificate and private key for both Physical Host1..4 and VIPHOST1..N into the Identity Store. Make sure that you use a different alias for each of the certificate/key pair imported. Syntax: java utils.ImportPrivateKey []
Examples: Login into Node1 For Physical Nodes: NODE1> java utils.ImportPrivateKey appIdentityKeyStore.jks welcome1 <> welcome1 $WLSDOMAIN/certs/<>_cert.pem $WLSDOMAIN/certs/<>_key.pem NODE1> java utils.ImportPrivateKey appIdentityKeyStore.jks welcome1 <> welcome1 $WLSDOMAIN/certs/<>_cert.pem $WLSDOMAIN/certs/<>_key.pem NODE1> java utils.ImportPrivateKey appIdentityKeyStore.jks welcome1 <> welcome1 $WLSDOMAIN/certs/<>_cert.pem $WLSDOMAIN/certs/<>_key.pem NODE1> java utils.ImportPrivateKey appIdentityKeyStore.jks welcome1 <> welcome1 $WLSDOMAIN/certs/<>_cert.pem $WLSDOMAIN/certs/<>_key.pem For all the VIP HostNames: [WE CAN SKIP THE BELOW SECTIONS IF HOSTNAME VERIFICATION IS NOT PLANNED TO USE] NODE1> java utils.ImportPrivateKey appIdentityKeyStore.jks welcome1 <> welcome1 $WLSDOMAIN/certs/<>_cert.pem $WLSDOMAIN/certs/<>_key.pem NODE1> java utils.ImportPrivateKey appIdentityKeyStore.jks welcome1 <> welcome1 $WLSDOMAIN/certs/<>_cert.pem $WLSDOMAIN/certs/<>_key.pem
SOA/OSB Installation and Configuration Guide by Lokesh T C
1.5
Creating a Trust Keystore Using the keytool Utility
Follow these steps to create the Trust Keystore for all Physical Nodes and <. 1. Copy the standard java keystore to create the new trust keystore since it already contains most of the root CA certificates needed. Oracle does not recommend modifying the standard Java trust key store directly. Copy the standard Java keystore CA certificates located under the $WLSHOME/server/lib directory to the same directory as the certificates. For example: cp $WLSHOME/server/lib/cacerts $WLSDOMAIN/certs/appTrustKeyStore.jks
2. The default password for the standard Java keystore is changeit. Oracle recommends always changing the default password. Use the keytool utility to do this. The syntax is: keytool -storepasswd -new -keystore -storepass
For example: cd $WLSDOMAIN/certs keytool -storepasswd -new welcome1 -keystore appTrustKeyStore.jks -storepass changeit
3. The CA certificate CertGenCA.der is used to sign all certificates generated by the utils CertGen tool and is located at $WLSHOME/server/lib directory. This CA certificate must be imported into the appTrustKeyStore.jks using the keytool utility. The syntax is: keytool -import -v -noprompt -trustcacerts -alias -file -keystore
