SOA Domain Installation Guide

Functional Specification Document
Oracle SOA Suite 11.1.1.4.0

Installation Guide
Quick reference
<<draft>>
Project Name:
Project Reference
Number:
Interface ID:
Interface Name:
Integration Tool:
Document Version:
Date:
Project Manager:
ORACLE SOA SUITE 11G & OSB 11G SETUP QUICK REFERENCE GGUIDE
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
Table of contents
1. INTRODUCTION...............................................................................................5
1.1.
1.2.
Document Purpose..............................................................................5
Scope.....................................................................................................5
2. REFERENCED DOCUMENTS.........................................................................5
3. ORACLE STANDALONE SOA SUITE 11G INSTALLATION STEPS............5
3.1.
3.2.
Only
3.3.
3.4.
3.4.1.
3.5.
3.5.1.
3.5.2.
3.6.
Install Database DBA Only...............................................................5

Create Schemas using Repository Creation Utility (RCU) DBA
5
Install 64 bit JRockit SDK for 64 bit OS (CM Team Only).................9
Install WebLogic Server 10.3.4 (CM Team Only)...............................9
Enabling Unicode Support (Unix Team Only).....................................................10
Install Oracle SOA Suite 11g - 11.1.1.4.0..........................................11

Starting the Installer.............................................................................................. 11
Installation Screens...............................................................................................11
Create Oracle soa suite 11g domain................................................12
3.6.1.
Configuring Oracle SOA Suite 11g and Creating a WebLogic SOA Suite Domain
(CM Team only).................................................................................................................... 12
3.7.
3.7.1.
3.7.2.
3.7.3.
Verify Server Configuration (CM Only)............................................16

Launching the Servers.......................................................................................... 16
Starting Node Manager......................................................................................... 18
Verifying the Installation........................................................................................ 19
4. INSTALL SOA SUITE IN CLUSTERD ENVIRONMENT................................20

5. UPDATE WEBLOGIC SCRIPTS....................................................................20
6. APPLY SOA PATCH.......................................................................................20
7. SECURITY.......................................................................................................20
7.1.
7.2.
7.3.
7.4.
7.4.1.
7.4.2.
7.5.
7.5.1.
7.5.2.
7.6.
7.6.1.
7.6.2.
Integration with Cisco AD Weblogic (CM only)............................20

Integration with Cisco AD OPSS (CM Only).................................21
Creating Application Role and Adding Users/Groups from AD....22
Configuring OWSM for securing Web-Services.............................24
Follow the steps below to create a user to authenticate for the Web-Services.....25
Below steps are required to create Security Credentials for OWSM.....................26
GM eBonding Http Basic Authentication (DEMO Env)...................27

GM eBonding Http Basic Authentication (Pre-Prod and Prod Env)

27
8. ADDING DATASOURCES..............................................................................29
9. ADDING CONNECTION FACTORIES FOR DB ADAPTER..........................32
2015 Cisco Systems, Inc. All rights reserved.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
10. JDEVELOPER (DEVELOPER ONLY)............................................................34

10.1.
SOA Extensions for JDeveloper (Developer only)......................34
11. USER MESSAGING DRIVER CONFIGURATIONS.......................................34

12. PINGWEB WAR..............................................................................................36
13. COM DATABASE SETUP...............................................................................36
14. GPL AGENT CREATION................................................................................36
15. DEPLOYMENT OF THE BPEL SERVICES..................................................36
15.1.
15.2.
Manula deployment of SOA Extension jar files...........................37

Patch deployment for Large File Size...........................................37
16. PRE-PROD DEPLOYMENT STEPS...............................................................38

17. GM EBONDING INSTALL SSL CERTIFICATE..............................................39
18. GM EBONDING PROXY CONFIGURATION IN LOAD BALANCER............39
19. GM EBONDING PROJECT JMS QUEUES...................................................40
20. ISERVICES APP MIGRATION (DESCOPED DONT DO THIS STEP).......42
20.1.
20.2.
20.3.
20.4.
20.5.
Classpath changes in weblogic-application.xml file..................42

Forbidden issue..............................................................................43
Change publishing folder..............................................................43
Weblogic User-Profile Changes....................................................43
Changing iservices.properties file................................................43
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
DOCUMENT REVISION HISTORY

Version
Date
0.1
0.2
03/10/2011
07/18/2011
0.3
07/29/2011
0.4
0.5
0.6
0.7
0.8
08/03/2011
08/04/2011
08/10/2011
09/07/2011
09/12/2011
0.9
1.0
10/20/2011
11/07/2011
Description
Author/Editor
Initial Draft
Added Section 5 for Cisco AD Integration and
Application Role configuration
Added Section 6,7 for Adding Data-sources and
Connection Factories
Included BPEL Deployment section
Added section 5.4 for OWSM configuration
Added iServices deployment steps
Update AD configuration after lookup issues
Updated Data-source configuration with database
details
Section 7.4.2: Added credential information for ATA
Section 16: Added PP and Prod deployment steps
Rajendra Naik
Ravi Singh
Ravi Singh
Venkata Meda
Ravi Singh
Venkata Meda
Ravi Singh
Ravi Singh
Ravi Singh
Venkat Meda
APPROVALS
Signatures on this page indicate agreement with document content. Changes requested after
sign-off will undergo a process for assessment, authorization, and communication.
Name
Role
Signoff Date
Remarks
REVIEWERS
Signatures on this page indicate agreement with document content after review.
Name
Shishir Jain
Role
Srinivas Rao
Delivery Head
Architecture Board
Signoff Date
Remarks
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
1. INTRODUCTION
1.1.
Document Purpose
The purpose of this document is to provide installation steps for Oracle SOA
Suite 11g (11.1.1.4.0) in clustered environment.
1.2.
Scope
This document covers the steps involved in the setting up the environment for
Oracle SOA Suite 11g, deploy SOA services, configure CISCO LDAP and
deploying the iServices applications in the new cluster.
2. REFERENCED DOCUMENTS
Item
Title
Uri
Oracle Guides
http://download.oracle.com/docs/cd/E17904
_01/doc.1111/e13925/overview.htm
3. ORACLE STANDALONE SOA SUITE 11G INSTALLATION STEPS

SOA Suite 11g
All
softwares
can
be
downloaded
from
http://www.oracle.com/technetwork/middleware/soasuite/downloads/index.html
the
You need to install the following softwares in the same order as below.
Note: While doing remote installation, your machine/laptop requires Cygwin X-windows
Client or similar client for linux environment.
3.1.
Install Database DBA Only
If you don't already have an Oracle database installed, install database with following
configuration or higher.
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit
CHARACTERSET =AL32UTF8
RAM - 8GB minimum, preferred 16 GB or more
CPU 4 cores or more
Red Hat Enterprise Linux Server release 5.3+ (Tikanga)

Modify Oracle processes limit to 300. Following is the SQL command for it.
ALTER SYSTEM SET processes=300 SCOPE=SPFILE;
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
3.2.
Create Schemas using Repository Creation Utility (RCU)
DBA Only
Oracle SOA Suite and Oracle BAM require that certain schemas exist in your Oracle
database prior to installation. You must run Repository Creation Utility (RCU) to create
the schemas in the database.
Download RCU 11.1.1.4.0
Follow the instructions below to start RCU and create the schemas:
1. Start RCU from the RCU_HOME/bin (on Linux operating systems) or
RCU_HOME\bin (on Windows operating systems) directory:
On Linux operating systems:
./rcu
On Windows operating systems:

rcu.bat
2. Welcome Screen
Click Next.
3. Create Repository Screen
Select Create.
Click Next.
4. Database Connection Details Screen
Select "Oracle Database" in the Database Type field, then provide the
following credentials to connect:
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. For example:
ora-node1-vip.mycompany.com
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
Port: Specify the database listener port number. The default port
number for Oracle databases is 1521.
If you do not know the listen port number for your database, you can
check the portlist.ini file, which is located in the
ORACLE_HOME/install (on UNIX operating systems) or
ORACLE_HOME\install (on Windows operating systems) directory on
the machine where the database is located.
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
o
o
Username: Specify the name of a user with DBA or SYSDBA

privileges. The default user name with SYSDBA privileges is SYS.
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.
Click Next. A "Checking Prerequisites" screen will appear. If there are errors,
some details about the error will be displayed on the Database Connection
Details Screen. Fix the error messages and click Next again.
After the checking is complete with no errors, click OK to dismiss the screen.
5. Select Components Screen
In the table that lists the available components, select SOA and BPM
Infrastructure. All of the product schemas within this component, including all
the dependent schemas, are automatically selected.
Table 1 Required Schemas for Oracle SOA Suite on Oracle Databases
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
Component
Schema Owner
SOA Infrastructure
prefix_SOAINFRA
Dependencies
prefix_MDS
(Metadata Services)
prefix_ORASDPM
Business Activity Monitoring prefix_ORABAM
prefix_MDS
(Metadata Services)
prefix_ORASDPM
User Messaging Service
prefix_ORASDPM
prefix_MDS
(User Messaging)
(User Messaging)
(Metadata Services)
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.
Click Next. A "Checking Prerequisites" screen will appear. If there are errors,
some details about the error will be displayed near the bottom of the screen.
Fix the error messages and click Next again.
After the checking is complete with no errors, click OK to dismiss the screen.
6. Schema Passwords Screen
Near the top of the screen, select Use same password for all schemas.
In the Password field, enter your password. Enter your password again in the
Confirm Password field.
Note:
You must remember or make a note of the schema passwords from this screen; you
will need them later when you are configuring your products.
Click Next.
7. Map Tablespaces Screen
Click Next. A "Creating Tablespaces" screen will appear. If there are errors,
some details about the error will be displayed on the Map Tablespaces Screen.
Fix the error messages and click Next again.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
After the tablespaces are created with no errors, click OK to dismiss the
screen.
8. Summary Screen
Click Create. A "CREATE" screen will appear. If there are errors, some details
about the error will be displayed on the Summary Screen. Fix the error
messages and click Next again.
After the schemas are created with no errors, click OK to dismiss the screen.
9. Completion Summary Screen
Click Close.
3.3.
Install 64 bit JRockit SDK for 64 bit OS (CM Team Only)
If you are using 64 bit OS, then you need to install 64 bit JRockit SDK. Download the
SDK from Oracle downloads page. Download the OS compatible version. E.g. RHEL 5.4
64 bit
3.4.
Install WebLogic Server 10.3.4 (CM Team Only)
Oracle SOA Suite requires an Oracle WebLogic Server on your system. If you do not
already have one, follow the instructions in this section to install Oracle WebLogic Server.
1. Ensure that access to directory /oracle/app/product/10.2/client is

available(CM team faced this issue during POC environment)
2. Download the 10.3.4 version of Oracle WebLogic Server from the following
URL:
http://www.oracle.com/technetwork/middleware/soasuite/downloads/index.ht
ml
3. Run the installer you just downloaded
4. Welcome Screen
Click Next.
5. Choose Middleware Home Directory Screen
Select Create a new Middleware Home.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
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.
Note:
You must remember or make a note this location; you will be asked for it later when
you are installing Oracle SOA Suite.
Click Next.
6. 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.
Click Next.
7. Choose Install Type Screen
Select Typical.
Click Next.
8. Choose Product Installation Directories Screen
Specify the desired location for your WebLogic Server home directory.
Click Next.
9. Choose Shortcut Location (Windows only)
If you are installing on a Windows system, you will be asked to specify a
location where you would like Windows to create a shortcut to Oracle
products.
Click Next.
10. Installation Summary Screen
Click Next.
11. Installation Progress Screen
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
No action is required on this screen; the installer will automatically advance to

the next screen when installation is complete.
12. Installation Complete Screen
De-select Run Quickstart.
Click Done.
3.4.1.
Enabling Unicode Support (Unix Team Only)
Your operating system configuration can influence the behavior of characters

supported by Oracle SOA Suite.
On a UNIX operating system, Oracle highly recommends that you enable
Unicode support by setting the LANG and LC_ALL environment variables to a
locale with the UTF-8 character set. This enables the operating system to
process any character in Unicode. SOA technologies are based on Unicode.
If the operating system is configured to use a non-UTF-8 encoding, SOA
components may function in an unexpected way. For example, a non-ASCII file
name can make the file inaccessible and cause an error. Oracle does not support
problems caused by operating system constraints.
3.5.
Install Oracle SOA Suite 11g - 11.1.1.4.0
Download SOA Suite 11.1.1.4.0.
3.5.1.
Starting the Installer
To start the installer on UNIX operating systems:

./runInstaller -jreLoc JRE_LOCATION
Note:
Starting the installer as root user is not supported.
To start the installer on Windows operating systems:

setup.exe -jreLoc JRE_LOCATION
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
The installer requires the full path to the location of a Java Runtime
Environment (JRE) on your 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 MW_HOME/jdk160_18 (on UNIX operating systems) or
MW_HOME\jdk160_18 (on Windows operating systems), where MW_HOME is the
Middleware home directory.
On 64-bit platforms, the JRE location is the JAVA_HOME you used to install
Oracle WebLogic Server.
3.5.2.
Installation Screens
To install Oracle SOA Suite:

1. Welcome Screen
Click Next.
2. Prerequisite Checks Screen
After the prerequisite checking is complete with no errors, click Next.
3. Specify Installation Location Screen
Oracle Middleware Home: Specify the location where WebLogic Server was
installed.
Oracle Home Directory: Specify the location where you want to install the
software:
o
o
If you specify a directory that already exists, it must be an empty

directory and it must be inside the Oracle Middleware home.
If you specify a new directory, it will be created inside the Oracle
Middleware home.
This will be your Oracle home directory. Runtime components cannot write
to this directory.
Note:
For the remainder of this document, this directory will be referred to as your SOA
Oracle home to avoid any confusion with the Oracle home directories of other
Oracle Fusion Middleware products.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
4. Installation Summary Screen

Click Install.
5. Installation Progress Screen
Click Next when the installation is complete.
6. Installation Complete Screen
Click Finish.
3.6.
Create Oracle soa suite 11g domain
3.6.1.
Configuring Oracle SOA Suite 11g and Creating a
WebLogic SOA Suite Domain (CM Team only)
After you have successfully installed your software, you can configure Oracle
SOA Suite components using the Oracle Fusion Middleware Configuration
Wizard. This Configuration Wizard is located in the
SOA_ORACLE_HOME/common/bin (on UNIX operating systems) or
SOA_ORACLE_HOME\common\bin (on Windows operating systems) directory.
1. Start the Configuration Wizard.
On UNIX operating systems:
./config.sh

config.cmd
If you are using a 32-bit operating system, Oracle JRockit SDK is installed
as part of the Oracle WebLogic installation. This is the JDK that the
Configuration Wizard will use by default. If you want to invoke the
Configuration Wizard with the Sun JDK, do the following prior to starting
the Configuration Wizard:
1. Set the JAVA_HOME environment variable to the location of the Sun
JDK. For example, you can set it to the Sun JDK that was installed
with Oracle WebLogic Server in the MW_HOME/jdk160_18 (on
UNIX operating systems) or MW_HOME\jdk160_18 (on Windows
operating systems) directory.
2. Set the JAVA_VENDOR environment variable to "Sun."
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
2. Welcome Screen
Select Create a New WebLogic Domain.
Click Next.
3. Select Domain Source Screen
Select Generate a domain configured automatically to support the
following products, then select the products that should be configured in
this domain. For Oracle SOA Suite installation, select:
o
o
Oracle SOA Suite - 11.1.1.0 [ORACLE_SOA1]

Oracle Enterprise Manager - 11.1.1.0 [ORACLE_SOA1]
Oracle WSM Policy Manager - 11.1.1.0 [oracle_common]
Oracle JRF WebServices Asynchronous services - 11.1.1.0

[oracle_common]
Oracle JRF - 11.1.1.0 [oracle_common]
WebLogic Advanced Web Services Extension - 10.3.4.0

[WebLogic_Home]
If you have previously installed Oracle Fusion Middleware products on

your system, you may see duplicate products on this screen; select only
those products associated with your SOA_ORACLE_HOME.
Click Next.
2.
Specify Domain Name and Location Screen

Specify the following domain information:
o
o
Domain name: The name of the domain you want to create. The
default name is base_domain.
Domain location: The absolute path to the directory where this
domain should be created. The default location is
MW_HOME/user_projects/domains (on UNIX operating systems)
or MW_HOME\user_projects\domains (on Windows operating
systems).
Application location: The absolute path to the directory where
applications created in this domain should reside. The default
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
location is MW_HOME/user_projects/applications (on UNIX

operating systems) or MW_HOME\user_projects\applications
(on Windows operating systems).
Click Next.
3.
Configure Administrator Username and Password Screen

Specify the following credentials for your administrator:
o
o
User name: The name of the administrator for this domain. The
default name is weblogic.
User password: The administrator's password.
Confirm user password: Re-enter the administrator's password.
Description: Enter a description for this user, or leave the default

description as is. This field is optional.
Click Next.
4.
Configure Server Start Mode and JDK Screen

In the "WebLogic Domain Startup Mode" portion of the screen, Select
Development Mode/Production Mode depending on your installation.
In the "JDK Selection" portion of the screen, select the JDK that is
recommended for your platform in Development Mode. This text can be
found immediately underneath Development Mode in the "WebLogic
Domain Startup Mode" section. For example, on a Linux system, you
would be asked to select "Sun SDK 1.6.0_18" from the list of available
JDKs.
Click Next.
5.
Configure JDBC Component Schema Screen

Configure the schema information for each data source listed on this
screen. When you make changes to any field on this screen, the changes
are applied to selected data sources only. For fields that are common with
all data sources (for example, all data sources reside on the same
database), you should select all of the data sources and make your
changes. The changes are saved automatically as you type.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
After all of the information that is common to all data sources has been
specified, then you will need to select individual or smaller groups of data
sources and enter information that is specific to them (for example, the
schema owner).
Table 1 Required Schemas for Oracle SOA Suite on Oracle Databases
Component
Schema Owner
SOA Infrastructure
prefix_SOAINFRA
Dependencies
prefix_MDS
(Metadata Services)
prefix_ORASDPM
Business Activity Monitoring prefix_ORABAM
prefix_MDS
(Metadata Services)
prefix_ORASDPM
User Messaging Service
prefix_ORASDPM
prefix_MDS
(User Messaging)
(User Messaging)
(Metadata Services)
Review the table on this screen and identify which fields you need to
modify:
o
o
o
Vendor: Select the vendor for your database from the drop-down
list.
Driver: Select the driver type from the drop-down list.
Schema Owner: Specify the schema owner for the schema; this is
the name of the schema for this component in the following
format:
prefix_schema-name
This information was specified on the Select Components Screen

when the schemas were created using RCU.
o
o
Password: Specify the password for the schema. You specified this
password on the Schema Passwords Screen when creating the
schemas using RCU.
DBMS/Service: Specify the service name for your database. This
is the database on which the schema resides.
Host Name: Specify the name of the machine where your database
is running.
Port: Specify the database listen port number.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
Click Next.
6.
Test Component Schema Screen

Verify that the connections to your data sources are successful.
Click Next.
7.
Select Optional Configuration Screen

Do not select anything on this screen.
Click Next.
8.
Configuration Summary
Verify the information on this screen. Use the navigation pane on the left
or the Previous button if you want to return to a previous screen to alter
some portion of the configuration.
If everything is correct, click Create.
9.
Creating Domain Screen

When the domain has been successfully created, the progress bar will be at
100% and the Done button will be active.
The last line in the summary information is the URL of the Administration
Server. You should make a note of this URL so that you can access the
Administration Server after it has been started.
Click Done to dismiss the Configuration Wizard.
3.7.
Verify Server Configuration (CM Only)
This section contains general information that will help you verify your installation and
configuration. Some components may require custom or manual configuration, and this
information is also included in this section:
3.7.1.
Launching the Servers
To get your deployments up and running, you must start the Administration
Server and various Managed Servers:
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
1. To start the Administration Server, run the startWebLogic.sh (on

UNIX operating systems) or startWebLogic.cmd (on Windows
operating systems) script in the directory where you created your new
domain.
On UNIX operating systems:
MW_HOME/user_projects/domains/domain_name/startWebLogic.
sh

MW_HOME\user_projects\domains\domain_name\startWebLogic.
cmd
You entered the domain name and location on the Specify Domain
Name and Location Screen in the configuration wizard.
2. To start the Managed Servers, run the startManagedWebLogic.sh
(on UNIX operating systems) or startManagedWebLogic.cmd (on
Windows operating systems) script in the bin directory inside the
directory where you created your domain.
This command also requires that you specify a server name. The
servers that need to be started are:
o
soa_server1
(Oracle SOA Server)
For example, to start Oracle SOA Server on UNIX operating systems:

./startManagedWebLogic.sh soa_server1
On Windows systems:
startManagedWebLogic.cmd soa_server1
Before WebLogic Server is started, you will be prompted for the WebLogic
Server username and password. These were provided on the Configure
Administrator Username and Password Screen in the configuration wizard.
Note:
If this is the first time that both Oracle SOA Server and Oracle BAM Server are being
started after installation and configuration, you must make sure that your startup of
Oracle SOA Server is complete before starting Oracle BAM Server.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
If you do not know the names of the managed servers that need to be started,
you can view the contents of the following file on UNIX operating systems:
MW_HOME/user_projects/domains/domain_name/startManagedWebLogic
_readme.txt
On Windows systems:
MW_HOME\user_projects\domains\domain_name\startManagedWebLogic
_readme.txt
Or, you can access the Administration Server console at the following URL:
http://host:admin_server_port/console
Supply the username and password that you specified on the Configure
Administrator Username and Password Screen of the Configuration Wizard.
Then, navigate to Environment > Servers to see the names of your managed
servers.
3.7.2.
Starting Node Manager
Starting Node Manager on a machine that hosts Managed Servers allows you
to start and stop the Managed Servers remotely using the Administration
Console or the command line. Node Manager can also automatically restart a
Managed Server after an unexpected failure.
To start Node Manager:
1. On UNIX operating systems, run the
MWHome/oracle_common/common/bin/setNMProps.sh
script.
On Windows operating systems, run the

MWHome\oracle_common\common\bin\setNMProps.cmd
script.
This script appends the required properties to the

nodemanager.properties file. These properties can also be
appended manually, or provided as command-line arguments.
Note:
The StartScriptEnabled=true property is required for Managed
Servers to receive proper classpath and command arguments.
The file containing the properties is nm.required.properties.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
2. On UNIX operating systems, start Node Manager by running the

MWHome/wlserver_10.3/server/bin/startNodeManager.sh script.
On Windows operating systems, start Node Manager by running the
MWHome\wlserver_10.3\server\bin\startNodeManager.cmd
script.
3.7.3.
Verifying the Installation
Start your browser and enter the following URLs:
To access the Administration Server:

http://host:admin_server_port
This information was visible on the Creating Domain Screen (the last
screen) of the Configuration Wizard.
To access the Administration Server console:

http://host:admin_server_port/console
You will be prompted for the username and password credentials that
you specified on the Configure Administrator Username and Password
Screen of the Configuration Wizard.
To access SOA Enterprise Manager :

http://host:admin_server_port/em
You will be prompted for the username and password credentials that
you specified on the Configure Administrator Username and Password
Screen of the Configuration Wizard.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
4. INSTALL SOA SUITE IN CLUSTERD ENVIRONMENT

Please refer the following document to install in clustered environment.
URL:
5. UPDATE WEBLOGIC SCRIPTS

This is the property we need to set it up in our servers
-Dservice.env=<values>
the possible values are :
sb
dev
qa
uat
int
bfix
pp
prod
6. APPLY SOA PATCH

Apply the SOA patch 11066656.
Verify the patch installation by executing the following command.
Opatch lsinventory
7. SECURITY
7.1.
Integration with Cisco AD Weblogic (CM only)
For Weblogic to authenticate and authorize against Cisco AD a new authenticator
needs to be added to the default realm using the following configuration:
1. Go to the directory $DOMAIN_HOME/config
2. Open the xml configuration file config.xml for editing.
3. Append the below xml element <sec:authentication-provider> as a child element
in the first place/order within the <realm> element.
<sec:authentication-provider xsi:type="wls:active-directory-authenticatorType">
<sec:name>ciscoADAuthenticator</sec:name>
<sec:control-flag>SUFFICIENT</sec:control-flag>
<wls:propagate-cause-for-login-exception>false</wls:propagate-cause-for-login-exception>
<wls:host>ds.cisco.com</wls:host>
<wls:user-name-attribute>sAMAccountName</wls:user-name-attribute>
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
<wls:principal>CN=iportalprod.gen,OU=Generics,OU=Cisco Users,DC=cisco,DC=com</wls:principal>
<wls:user-base-dn>OU=Cisco Users,DC=cisco,DC=com</wls:user-base-dn>
<wls:credential-encrypted>csgita2z4</wls:credential-encrypted>
<wls:user-from-name-filter>(&(sAMAccountName=%u)(objectclass=user)
(objectCategory=person))</wls:user-from-name-filter>
<wls:group-base-dn>OU=Standard,OU=Cisco Groups,DC=cisco,DC=com</wls:group-base-dn>
</sec:authentication-provider>
4. The values of user-base and group-base elements in the above xml, need to be
modified as per the environment.
5. All the Weblogic servers need to be restarted to reflect the changes.
7.2.
Integration with Cisco AD OPSS (CM Only)
For OPSS (Oracle Platform Security Services) to authenticate and authorize against the
Ciscos AD (Active Directory) the following configuration steps need to be followed:
1. Go to the directory $DOMAIN_HOME/config/fmwconfig
2. Open the xml configuration file jps-config.xml for editing.
3. Ensure that the below element for <ServiceProvider> is present under
<ServiceProviders>. If not, add it.
<serviceProvider
class="oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider"
name="idstore.ldap.provider" type="IDENTITY_STORE">
<description>LDAP-based IdentityStore Provider</description>
4. Locate the Service Instance for the provider "idstore.ldap.provider" under
<ServiceInstances>. If any LDAP is already configured OR if this element is not
present add a new instance using the below element. Ensure that the below
element is added.
<serviceInstance name="idstore.AD" provider="idstore.ldap.provider">
<property name="username.attr" value="sAMAccountName"/>
<property name="user.login.attr" value="sAMAccountName"/>
<property name="subscriber.name"
value="CN=iportalprod.gen,OU=Generics,OU=Cisco Users,DC=cisco,DC=com"/>
<property name="idstore.type" value="ACTIVE_DIRECTORY"/>
<property name="cleartext.ldap.credentials"
value="CN=iportalprod.gen,OU=Generics,OU=Cisco Users,DC=cisco,DC=com:csgita2z4"/>
<property name="ldap.url" value="ldap://ds.cisco.com:389"/>
<extendedProperty>
<name>user.object.classes</name>
<values>
<value>top</value>
<value>person</value>
<value>inetorgperson</value>
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
<value>organizationalperson</value>
<value>orcluser</value>
<value>orcluserv2</value>
<value>ctCalUser</value>
</values>
</extendedProperty>
<extendedProperty>
<name>user.search.bases</name>
<values>
<value>OU=Cisco Users,DC=cisco,DC=com</value>
</values>
</extendedProperty>
<extendedProperty>
<name>group.search.bases</name>
<values>
<value>OU=Standard,OU=Cisco Groups,DC=cisco,DC=com</value>
</values>
</extendedProperty>
</serviceInstance>
5. The values of <user.search.bases> and <group.search.bases> elements in the
above xml, need to be modified as per the environment.
6. Locate the <jpsContext> element with name default inside <jpsContexts>. Add
an element <serviceInstanceRef ref="idstore.AD"/> as a child. Ensure that it
looks like below:
<jpsContexts default="default">
<jpsContext name="default">
<serviceInstanceRef ref="credstore"/>
<serviceInstanceRef ref="keystore"/>
<serviceInstanceRef ref="policystore.xml"/>
<serviceInstanceRef ref="audit"/>
<serviceInstanceRef ref="idstore.AD"/>
<serviceInstanceRef ref="trust"/>
<serviceInstanceRef ref="pdp.service"/>
</jpsContext>
7. Delete the instance reference for idstore.ldap.
8. All the SOA servers need to be restarted to reflect the changes.
7.3.
Creating Application Role and Adding Users/Groups from AD
Create 2 Application Role with name SOMT and ITOPS using the steps below:
1. Open EM (Enterprise Manager) using admin login
2. Locate the Domain in left-hand pane under Weblogic Domains
3. Right Click on Domain and browse to Security -> Application Roles
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
4. Click on create to create a new application role.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
5. Set the Role details as below.
6. Add the Roles, Groups or Users from sections below on same page.
7. Add the user iportalprod.gen to Roles = {SOAAdmin, SOAOperator,
BPMWorkflowAdmin} roles on SOA-INFRA application.
7.4.
Configuring OWSM for securing Web-Services
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
7.4.1.
Follow the steps below to create a user to authenticate
for the Web-Services.
1. Open Weblogic console with Admin login
2. Go to Security Realms -> myrealm and choose Users and Groups tab.
3. Create
a
local
user
password=omsmanager10
with
username=omsmanager
with
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
7.4.2.
Below steps are required to create Security Credentials
for OWSM
1. Open EM (Enterprise Manager) using admin login
2. Locate the IServicesClusterDomain in left-hand pane under Weblogic
Domains
3. Right click on domain and go-to Security->Credentials
4. Ensure that there is a map with name oracle.wsm.security present. If
not, create it.
5. Add 5 Keys in the above map with names [oms.credentials,

saleslead.credentials, blis.credentials, order.credentials, ata.credentials
and iservices.credentials]. Username/Passwords for each key are
(omsmanager/omsmanager10,
salesconnector/salesconnector,
accountmanager/accountmanager,
ordermanager/ordermanager,
apollo.gen/csgita2z and is_user/user4isonly88$99).
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
7.5.
GM eBonding Http Basic Authentication (DEMO Env)
7.5.1.
Open Weblogic console with Admin login
Go to Security Realms -> myrealm and choose Users and Groups tab
Click on New
Create a New User Page comes up and
Enter the following:
Name: gmebond
Description:
GM eBonding project username
Password:
gmebond123
Confirm password:
gmebond123
7.5.2.
for OWSM
Open EM (Enterprise Manager) using admin login
Locate the Weblogic Domain->SOAClusterDomain in left-hand pane

under Weblogic Domains
Right click on SOAClusterDomain and go-to Security->Credentials
Ensure that there is a map with name oracle.wsm.security present. If

not, create it.
Then Click on Create Key
Add 1 Key in the above map with names
Key: [gmebond.credentials].
Username/Passwords: gmebond/gmebond123
7.6.
GM eBonding Http Basic Authentication (Pre-Prod and Prod
Env)
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
7.6.1.
Open Weblogic console with Admin login
Go to Security Realms -> myrealm and choose Users and Groups tab
Click on New
Create a New User Page comes up and
Enter the following:
Name: gmebond
Description:
GM eBonding project username
Password:
c!3C0W33#x
Confirm password:
c!3C0W33#x
7.6.2.
for OWSM
Open EM (Enterprise Manager) using admin login
Locate the Weblogic Domain->SOAClusterDomain in left-hand pane

under Weblogic Domains
Right click on SOAClusterDomain and go-to Security->Credentials
Ensure that there is a map with name oracle.wsm.security present. If

not, create it.
Then Click on Create Key
Add 1 Key in the above map with names
Key: [gmebond.credentials].
Username/Passwords: gmebond/ c!3C0W33#x
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
8. ADDING DATASOURCES
For deployed J2EE and SOA applications to interact with external databases, a datasource needs to be created using Weblogic Console.
Follow the below steps for adding a new data-source (e.g. for COSM database):
4.
5.
6.
7.
Open Weblogic Administration Console using admin login

Go to Services -> Data Sources
In Configuration tab click on New and choose Generic Data Source
Set the details for COSM as shown below and click Next.
8. Choose the correct Driver per database configuration (Check with DBA)
For Development/Sandbox choose Thin XA as shown below and click Next.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
9. Set the database details like (Database SID, IP Address, Port, Username and
Password) as shown below and click Next.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
10. Verify all the details at this Page, test the setup by clicking on Test Configuration and
Click Finish.
11. Repeat the steps 1-7 for BLiS datasource configuration. Ensure that the JNDI name
for cosm data-source is jdbc/eis/cosmDB and BLiS data-source is
jdbc/eis/DHDLDB
12. Add the below mentioned 3 data-sources. Please double check these details for each
environment. These are good for SOA SandBox only.
Data-Source Name = jdbc/eis/DHDLDB

JCA Connection Factory Name = eis/DB/DHDLConnection
Database Connection String = jdbc:oracle:thin:@10.224.167.212:1521:dbls3
Database User = blis
Data-Source Name = jdbc/BlisCOMDS

JCA Connection Factory Name = eis/DB/BlisCOMConnection
Database Connection String = jdbc:oracle:thin:@192.168.251.48:15021:DSVS
Database User = COMUSER
Data-Source Name = jdbc/ODSDS

JCA Connection Factory Name = eis/DB/ODSConnection
Database Connection String = jdbc:oracle:thin:@wonder.cisco.com:1521:ODSDEV
Database User = apollosoa
Contact Yuan Zhang for the passwords of the above databases.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
9. ADDING CONNECTION FACTORIES FOR DB ADAPTER

An Outbound Connection Factory is required by Database Adapter to talk to the datasources (configured above). Follow the below steps to create it for COSM.
1.
2.
3.
4.
Open Weblogic Administration Console using admin login

Go to Deployment, locate the module with name DbAdapter and click to open.
Go to tabs Configuration - > Outbound Connection Pools
Click on New
5. Choose javax.resource.cci.ConnectionFactory and click Next

6. Set JNDI Name as eis/DB/COSMConn and click Finish.
7.
Open the list of connection pools again (as in step 3) and click on the newly created
eis/DB/COSMConn as shown below
8. In the property page set the JNDI name of the data-source i.e. jdbc/eis/cosmDB as
configured in previous section. Click Save.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
9. Repeat the steps 1-8 for adding another connection factory for BLiS. Ensure that the
JNDI name is eis/DB/DHDLConnection and it points to the BLiS data-source with
JNDI name jdbc/eis/DHDLDB as created in previous section.
10. Create the following 3 connection factories. Refer to section 7-12 for more details:
eis/DB/DHDLConnection
eis/DB/BlisCOMConnection
eis/DB/ODSConnection
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
10. JDEVELOPER (DEVELOPER ONLY)

Download JDeveloper from the FMW download page.
Look for JDeveloper and Application Development Framework in the Required
Addition Software section.
Oracle Installer can be used to install Oracle JDeveloper Studio 11.1.1.x.x, the
ADF Runtime, and Oracle WebLogic Server 11g Release 1 (10.3.4) on your
system.
Oracle Installer is available in the following forms:
Generic installer (jdevstudio11114install.jar) that can be used to

install Oracle JDeveloper Studio on any platform. In order to use this
installer, you must have JDK 6.0 Update 18 or later installed on your
system.
Two platform-specific installers that include JDK 6.0 Update 18. You need
not have the JDK pre-installed on your system to use these platform
installers:
o
Windows Installer (jdevstudio11114install.exe)
Linux Installer (jdevstudio11114install.bin)
10.1.
SOA Extensions for JDeveloper (Developer only)
Install the SOA Extension using the JDeveloper Update Center. From the JDeveloper
menu choose Help > Check for Updates. In the Update Wizard, select Search Update
Centers and ensure Oracle Fusion Middleware Products is checked (screenshot).
Then ensure that Oracle SOA Composite Editor is checked ( screenshot, your version
may not match the screenshot exactly). The SOA Extension is approximately 200 MB.
11. USER MESSAGING DRIVER CONFIGURATIONS

Following are the steps to be executed as part of setting up User Messaging (Sending Emails).
These steps applicable to Oracle SOA (Enterprise Manager 11g)
1> Go to Enterprise Manager 11g
2> Under Farm_Domains --- Select User Messaging Service usermessagingdriver-email
(soa_server1)
3> Select from the drop down User Messaging Email Driver Email Driver properties
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
Edit/ Configure the Properties as below (Use applicable property values) and SAVE.
(Following are Mandatory properties setting up User Messaging successfully.
Common Configuration :
Sender Address AND Default Sender Address : Address of Sender
(EMAIL:sender@example.com, EMAIL:sender@example2.com)
MailAccessProtocol ------ IMAP
ReceiveFolder ----- INBOX
OutGoingMailServerPort ---- 25 (Default)
OutGoingDefaultFromAddr --- FromEmailAddress@cisco.com
OutGoingUserName --- (Your applicable user name)
OutGoingPassword ----- useClearTextPassword and enter password
IncomingMailServer ---- mail.cisco.com
Incoming Port ---- 143 (default port)
IncomingMailServerSSL false (default)
IncomingMailID AND IncomingUserID ------- username@cisco.com
Select User Messaging Service --- usermessagingserver (soa_server1) --- select

Message Status from drop down (or right click) --- Will list All the email messages sent
via user messaging. Email messages can be grouped by selecting appropriate View
Sender, Receiver, Operation, Status, TimeStamp etc
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
Select in EM
1> SOA --- Soa-Infra --- Soa Infrastructure --- SOA Administration --- WorkFlow
Notification Properties --- Here change FROM Address and Reply TO, Actionable
Email address as well. Also click More WorkflowNotification Configuration/ check
Properties. Configure the Sender, Receiver information here
2> SOA --- Soa-Infra --- Soa Infrastructure --- SOA Administration --- WorkFlow Task
Service Properties -- More WorkFlow Task Service Properties configuration.
Configure / Check the Sender / Receiver properties.
If Human Task is configured to send emails to all users in Role, then all users within that specified
role would receive emails from Human Task.
12. PINGWEB WAR

Use the attached war file for deployment on SOA server (Please take the latest file from CM team
balaji)
PingWeb.war.rar
13. COM DATABASE SETUP

This section explains the database configuration for COM DB
Raise the remedy ticket to run the DB scripts for COM DB. CVS Location for script is \soaservices\database-scripts\COMScripts\COM_SCHEMA_SCRIPTS.sql
14. GPL AGENT CREATION

This section explains the agent requirements in BLIS & BOSS.
GPL project requires gplautomation agent & user to be created in BLiS & BOSS.
Create this agent via BLiS UI App. Verify the agent in BLiS & BOSS.
15. DEPLOYMENT OF THE BPEL SERVICES

This section explains to configure and deploy the BPEL services when a new
environment is built.
Add the following entries in the soabuild.properteis file if not exist for the new
environment with environment specific values. <env> is like qa, uat, sandbox, prod, etc
a. <env>.serverURL=http://<host>:<port>
b. <env>.server=<host>
c. <env>.port=<port>
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
d.
e.
f.
g.
<env>.overwrite=true
<env>.user=weblogic
<env>.password=XXXXX
<env>.mdsurl=jdbc:oracle:thin:@<MDS DB host>:<DB
Port>:<service name>
h. <env>.mdsuser=SOA_MDS
i. <env>.mdspassword=XXXXXX
j. <env>.mdsinfra=soa-infra
k. <env>.forceDefault=true
l. <env>.TrailRunURL=http://sjhdde156.corp.webex.com:90
00 (Will provide by dev team)
m. <env>.CreateCVSDBUrl=sjdbbe310.corp.webex.com:143
13:bhdl (dev team will provide)
n. <env>.CreateCVSDBUser=cosm1
o. <env>.CreateCVSDBPassword=Webex_123
Then start the deploying services into the new environment.
a. First replace the following environment variable in the
soabuild.properteis file deployment.plan.environment
to environment like dev, sandbox, uat, qa
b. Then deploy the SOA applications by calling the following
targets in the same order mentioned bellow.
deployDVMEBO
build.CommonSOAApp
build.PartyMgmtSOAApp
build.AccountMgmtSOAApp
build.BOSSOAApp
build.CommonFaultHandlerSOAApp
build.OrderMgmtSOAApp
build.ProvisionMgmtSOAApp
build.PostOrderFulfillment
build.TrialRunSOAApp
build.OMSSOAApp
build.OrderProcessingMediatorSOAApp
build.CaseMgmtSOAApp
15.1.
Manula deployment of SOA Extension jar files
This sections explains the deploying the java code (Fault Policies jar) file to SOA
extension folder.
This is one time requirement only. After run first time, not required this step in future
deployments. Just copy the FaultPolicy.jar file after the build to the oracle.soa.ext_11.1.1
folder and restart the soa servers.
After execute the target build.CommonFaultHandlerSOAApp, FaultPolicy.jar will be

created under the folder CommonFaultHandlerSOAApp\JavaFaultPolicy\classes.
Copy the FaultPolicy.jar file to the

o
o
$MIDDLEWARE_HOME/ Oracle_SOA1/soa/modules/oracle.soa.ext_11.1.1. this

is sample value in DEV : /home/soa/Oracle/Middleware/
cd $MIDDLEWARE_HOME/Oracle_SOA1/soa/modules/oracle.soa.ext_11.1.1
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
Set the ANT_HOME & JAVA_HOME (ant wont be available in the soa folder.
We need to copy the ant to this VM)
Run the following command $ANT_HOME/bin/ant
Then restart the SOA servers.
15.2.
Patch deployment for Large File Size
o
This sections explains the patch deployment that is required for large file size
support. Without this, the BPEL processes like OrderMgmtSOAProject will not
get deployed.
Error - SCAC-50012
Patch Number - 11066656
Metalink note ID 1299247.1
Patch file is attached.
p11066656_111140_Generic.zip
16. PRE-PROD DEPLOYMENT STEPS

This section provides the detailed steps to deploy the SOA services in Pre-Prod & Prod
environments.
Run the build using Hudson. The binary (jar/zip) files are copied on the Hudson server in
a predefined folder (CM team should know the folder). After build copied the files to the
folder in the Hudson server please use the following steps.
Note: Steps 2, 3, 4 & 5 are one time job. Not required to do these steps for every
deployment, unless there are changes in the scripts.
1. Copy the binaries into the Pre-Prod & Prod servers
2. Create folder AntScripts in the Pre-Prod & Prod servers by logging
using soa user.
/home/soa/AntScripts
3. Copy the soa_build.xml, run.sh & prod.properteis files from CVS into
the Pre-Prod & Prod to the folder /home/soa/AntScripts
4. Change the prod.properteis to soabuild.properties
5. Change the file attributes using the chmod command
chmod 777 *
6. Run the following command to deploy the binaries to the server
./run.sh <env> <binary file full path>
Ex: ./run.sh pp <full path of jar/zip file>
7. The order of the files deployment as follows
./run.sh <env> CommonObjects_mds.zip
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
./run.sh <env> EnterpriseObjects_mds.zip
./run.sh <env> FaultPolicies_mds.zip
./run.sh <env> HighDeal_mds.zip
./run.sh <env> Schematron_mds.zip
./run.sh <env> sca_SalesLeadSOAProject_rev1.0.jar
./run.sh <env> sca_AtASOAProject_rev1.0.jar
./run.sh <env> sca_EmailSOAProject_rev1.0.jar
./run.sh <env> sca_EmailGatewaySOAProject_rev1.0.jar
./run.sh <env> sca_BusinessFaultPolicyProject_rev1.0.jar
./run.sh <env> sca_AccountMgmtSOAProject_rev1.0.jar
./run.sh <env> sca_PartyInqSOAProject_rev1.0.jar
./run.sh <env> sca_PartyMgmtSOAProject_rev1.0.jar
./run.sh <env> sca_ProvisionMgmtSOAProject_rev1.0.jar
./run.sh <env> sca_ProvisionConfigSOAProject_rev1.0.jar
./run.sh <env> sca_BOSSSOAProject_rev1.0.jar
./run.sh <env> sca_TrialRunSOAProject_rev1.0.jar
./run.sh <env> sca_SalesOrderMgmtSOAProject_rev1.0.jar
./run.sh <env> sca_OrderMgmtSOAProject_rev1.0.jar
./run.sh <env> sca_OMSSOAProject_rev1.0.jar
./run.sh <env> sca_CreateOrderValidatorSOAProject_rev1.jar
./run.sh <env> sca_OrderProcessingMediator_rev1.0.jar
./run.sh <env> sca_CaseMgmtSOAProject_rev1.0.jar
NOTE: As SOA is design/runtime time dependency, when first deployment to any

environment, this is required to build some apps first and deploy to environment and do
the build the remaining apps. Because the deployment time it looks for the end points, so
we need to build the applications first and deploy.
17. GM EBONDING INSTALL SSL CERTIFICATE

Install SSL certificate received from GM on to the following instances:
SOA_Managed1
SOA_Managed2
SOA_Managed3
SOA_Managed 4
on Pre-Prod and PRD Oracle Weblogic SOA Suite instances.
18. GM EBONDING PROXY CONFIGURATION IN LOAD

BALANCER
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
Please add the following to httpd.conf of the Apache web server which does the load
balancing:
For Pre-Prod:
Replace sjisbe381 host port with the actual Pre-prod secondary VIP.
ProxyPass /soa-infra/services/default/CaseMgmtSOAProject/ReceiveTicket_B2BHTTP
http://sjisbe381:21011/soa-infra/services/default/CaseMgmtSOAProject/ReceiveTicket_B2BHTTP
RequestHeader set SOAPAction "Send"
ProxyPassReverse /soa-infra/services/default/CaseMgmtSOAProject/ReceiveTicket_B2BHTTP
For Prd:
Replace sjisbe381 host port with the actual Prod secondary VIP.
ProxyPass /soa-infra/services/default/CaseMgmtSOAProject/ReceiveTicket_B2BHTTP
RequestHeader set SOAPAction "Send"
ProxyPassReverse /soa-infra/services/default/CaseMgmtSOAProject/ReceiveTicket_B2BHTTP
19. GM EBONDING PROJECT JMS QUEUES

Create the following JMS Queues under Oracle WebLogic Console administration under
SOAClusterDomain:
1. Create JMS Queue GMTicketOutBoundErrorQueue steps:
a. Navigate to the following:
Domain Structure->Services->Messaging->JMS Modules
b. Click on SOAJMSModule
c. Click on New
d. Select Radio Button Queue and Click Next
e. Enter the following
i. Name: GMTicketOutBoundErrorQueue
ii. JNDI Name: jms/GMTicketOutBoundErrorQueue
iii. Template: None
f. Click Next
g. Select one of the Subdeployments from the
(For eg: SOAJMSServer510588595)
h. Select the Target as SOAJMSServer_auto_1
i. Click Finish
2. Create JMS Queue GMTicketOutBoundQueue steps:
c. Click on New
drop
down
-----------------------------------------------------------------------------------------------------------------------------------------------------------------

i. Name: GMTicketOutBoundQueue
ii. JNDI Name: jms/GMTicketOutBoundQueue
iii. Template: None
f. Click Next
i. Click Finish
3. Create JMS Queue GMTicketErrorQueue steps:
c. Click on New
i. Name: GMTicketErrorQueue
ii. JNDI Name: jms/GMTicketErrorQueue
iii. Template: None
f. Click Next
i. Click Finish
4. Create JMS Queue GMTicketInBoundQueue steps:
c. Click on New
i. Name: GMTicketInBoundQueue
ii. JNDI Name: jms/GMTicketInBoundQueue
iii. Template: None
f. Click Next
i. Click Finish
5. Configure Redelivery for the GMTicketInBoundQueue
drop
down
drop
down
drop
down
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
c. Select GMTicketInBoundQueue
d. Under Settings for GMTicketInBoundQueue, click on the
DeliveryFailure.
e. Enter the following:
i. Redelivery Delay Override: 300000
ii. Redelivery Limit: 2
iii. Expiration Policy: Redirect
iv. Expiration Logging Format: <Do not enter anything in the
box>
v. Error Destination: GMTicketErrorQueue
f. Click on Save
6. Configure Redelivery for the GMTicketOutBoundQueue
c. Select GMTicketInBoundQueue
d. Under Settings for GMTicketInBoundQueue, click on the
DeliveryFailure.
e. Enter the following:
i. Redelivery Delay Override: 300000
ii. Redelivery Limit: 2
iii. Expiration Policy: Redirect
iv. Expiration Logging Format: <Do not enter anything in the
box>
v. Error Destination: GMTicketOutBoundErrorQueue
f. Click on Save
tab
text
tab
text
7. Create Connection Factory GMTicketInBoundCF

c. Click on New
d. Select Radio Button Connection Factory
e. Click Next
f. Enter the following:
i. Name: GMTicketInBoundCF
ii. JNDI Name: jms/GMTicketInBoundCF
g. Click on Next
h. Select the appropriate cluster where this queue. (For eg: All servers in
the cluster) and Click on Finish.
20. ISERVICES APP MIGRATION (DESCOPED DONT DO THIS

STEP)
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
This section explains the custom changes in the new Weblogic (10.4) server for deploying
the applications.
20.1.
Classpath changes in weblogic-application.xml file.
The following changes needs to be added in weblogic-applications.xml in META-INF
folder in the ear file for the following applications
o XML Fragment to add in weblogic-application.xml file


<wls:prefer-application-packages>
<wls:package-name>org.objectweb.asm.*</wls:package-name>
</wls:prefer-application-packages>
List of applications that required this change
o
AccountInqAppV2
AccountMgmtAppV2
PaymentMgmtAppV2
PaymentInqAppV2
OrderMgmtAppV2
CatalogMgmtAppv2
EventApp
SalesConnectorApp
SiteInquiryApp
SubscriptionMgmtApp
SystemCatalogApp
20.2.
Forbidden issue
In startWeblogic.sh add -Dservice.env=sb
In setDomainEnv.sh add this property for JAVA_OPTIONS
In setDomain.sh
o
o
-Dproperties.server.url=sjisde804v.corp.webex.com
APPLCN_PROPERTY_LOC="/home/iservices10/apps/a
pplications/dynamic-loading/
-Dapplication.resource.location=$
{APPLCN_PROPERTY_LOC}
-Dproperties.server.url=<LB URL>
Configuration of Role for AccountInq app.
20.3.
Change publishing folder
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
Change the publishing folder from /home/httpd/iservices10/public_html to
/home/httpd/soa/public_html
20.4.
Weblogic User-Profile Changes
Create users, groups & Roles in Weblogic Admin Console as per the following xls
document.
weblogicusers-org.xl
sx
20.5.
Changing iservices.properties file
Change BRM templates file paths
Change JNDI_PROVIDER PATH

SOA Domain Installation Guide

Uploaded by

Copyright:

Available Formats

SOA Domain Installation Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SOA Domain Installation Guide

Uploaded by

Copyright:

Available Formats

Functional Specification Document

Oracle SOA Suite 11.1.1.4.0

Install Database DBA Only...............................................................5

Install Oracle SOA Suite 11g - 11.1.1.4.0..........................................11

Create Oracle soa suite 11g domain................................................12

Verify Server Configuration (CM Only)............................................16

4. INSTALL SOA SUITE IN CLUSTERD ENVIRONMENT................................20

Integration with Cisco AD Weblogic (CM only)............................20

GM eBonding Http Basic Authentication (DEMO Env)...................27

GM eBonding Http Basic Authentication (Pre-Prod and Prod Env)

2015 Cisco Systems, Inc. All rights reserved.

10. JDEVELOPER (DEVELOPER ONLY)............................................................34

SOA Extensions for JDeveloper (Developer only)......................34

11. USER MESSAGING DRIVER CONFIGURATIONS.......................................34

Manula deployment of SOA Extension jar files...........................37

16. PRE-PROD DEPLOYMENT STEPS...............................................................38

Classpath changes in weblogic-application.xml file..................42

2015 Cisco Systems, Inc. All rights reserved.

DOCUMENT REVISION HISTORY

2015 Cisco Systems, Inc. All rights reserved.

3. ORACLE STANDALONE SOA SUITE 11G INSTALLATION STEPS

Red Hat Enterprise Linux Server release 5.3+ (Tikanga)

2015 Cisco Systems, Inc. All rights reserved.

On Windows operating systems:

2015 Cisco Systems, Inc. All rights reserved.

Username: Specify the name of a user with DBA or SYSDBA

2015 Cisco Systems, Inc. All rights reserved.

Business Activity Monitoring prefix_ORABAM

User Messaging Service

2015 Cisco Systems, Inc. All rights reserved.

1. Ensure that access to directory /oracle/app/product/10.2/client is

2015 Cisco Systems, Inc. All rights reserved.

2015 Cisco Systems, Inc. All rights reserved.

No action is required on this screen; the installer will automatically advance to

Enabling Unicode Support (Unix Team Only)

Your operating system configuration can influence the behavior of characters

Starting the Installer

To start the installer on UNIX operating systems:

To start the installer on Windows operating systems:

2015 Cisco Systems, Inc. All rights reserved.

To install Oracle SOA Suite:

If you specify a directory that already exists, it must be an empty

2015 Cisco Systems, Inc. All rights reserved.

4. Installation Summary Screen

On Windows operating systems:

2015 Cisco Systems, Inc. All rights reserved.

Oracle SOA Suite - 11.1.1.0 [ORACLE_SOA1]

Oracle WSM Policy Manager - 11.1.1.0 [oracle_common]

Oracle JRF WebServices Asynchronous services - 11.1.1.0

Oracle JRF - 11.1.1.0 [oracle_common]

WebLogic Advanced Web Services Extension - 10.3.4.0

If you have previously installed Oracle Fusion Middleware products on

Specify Domain Name and Location Screen

2015 Cisco Systems, Inc. All rights reserved.

location is MW_HOME/user_projects/applications (on UNIX

Configure Administrator Username and Password Screen

Confirm user password: Re-enter the administrator's password.

Description: Enter a description for this user, or leave the default

Configure Server Start Mode and JDK Screen