Oracle OTM-EBS Integration Technical Guide v1

Oracle Transportation Management
E-Business Suite Integration with OTM – Technical Guide
ORACLE WHITE PAPER | APRIL 2017

Table of Contents
Abstract ......................................................................................................................................................... 3
Requirements................................................................................................................................................ 3
Prerequisites ................................................................................................................................................. 3
Creating SOA Schemas Using the Repository Creation Utility (RCU) ............................................................ 4
Installing WebLogic Server 10.3.6 ................................................................................................................. 9
Installing Oracle SOA Suite 11.1.1.9.0......................................................................................................... 14
Create and Configure the WebLogic Server Domain for SOA ..................................................................... 20
Installing Patch 13882058 ....................................................................................................................... 26
Starting WebLogic Administration Server and Configuring Node Manager Port ................................... 26
Create or Verify the Oracle E-Business Suite Users for Authorized Access ................................................ 31
Collecting the SOA Artifacts and Utilities on the Oracle E-Business Suite Installation for Deployment .... 35
Set the Required Environment Variables in the WebLogic Environment ................................................... 36
Configuring EbsBpelGlobal11g.properties file ............................................................................................ 36
Creating Datasource and Connection Factories ......................................................................................... 37
Executing the ant Scripts to Deploy the BPEL Process Files for EBS Shipping – OTM and EBS PO – OTM
Integration Flows ........................................................................................................................................ 54
Deploying the OTM Voucher to EBS Account Payables SOA Composites .................................................. 78
Deploying the OtmVoucherUserExit Composite..................................................................................... 78
Deploying the OtmVoucherToOracleApInvoice Composite ................................................................... 86
2 | E-Business Suite Integration with OTM – Technical Guide

Abstract
This document provides the technical background and steps required to integrate Oracle BPEL Process
Manager available in Oracle SOA Suite 11G with Oracle E-Business Suite Release 12.2.x. Additional steps
are provided on how to integrate Oracle BPEL Process Manager with Oracle Transportation
Management 6.4.x. The note covers the necessary configuration for integrating EBS and OTM with SOA
Suite 11g. This is a necessary configuration required for EBS to integrate with Oracle Transportation
Management (OTM) if using the standard SOA composites that are delivered for EBS and OTM. This
technical guide is tailored for specific integration of EBS with OTM products.
This guide also covers the required steps for installing and configuring SOA on the same physical server
hosting EBS. The guide is intended to provide all of the necessary information and tools to install and
configure the middleware used for EBS-OTM integration.
Requirements
 Application Server – Oracle WebLogic Server version 10.3.6
 Fusion Middleware Component – Oracle SOA Suite 11.1.1.9.0
 EBS Application version 12.2.x
 OTM Application version 6.4.x
Prerequisites
The following prerequisites exists for the middleware architecture:
 Oracle SOA Suite 11g Release 1 (11.1.1) and required Fusion Middleware components must be
installed on a standalone server accessing an Oracle E-Business Suite Release 12 database, or in
a separate fusion middleware ORACLE_HOME on an existing Oracle E-Business Suite application
tier server node. This guide will cover the latter configuration where they are installed in a
separate fusion middleware ORACLE_HOME on the same server hosting EBS.
 The Oracle SOA Suite 11g Fusion Middleware libraries are installed on the same server where
EBS is hosted but in a different Fusion Middleware ORACLE_HOME directory. Refer to
https://docs.oracle.com/middleware/11119/core/INSOA/toc.htm for the steps needed to
install SOA.
 WebLogic 10.3.6 libraries is installed in the separate fusion middleware ORACLE_HOME. Refer
to https://docs.oracle.com/middleware/11119/wls/WLSIG/toc.htm for the steps needed to
install WebLogic. A compatible Java version should also be installed to use for the installation.
 The Repository Creation Utility (RCU) has been downloaded. The Repository Creation Utility
can be downloaded from My Oracle Support as Patch 20996068 .
 The SOA suite schemas will be hosted on the same database where the EBS schemas are
hosted. They can also be hosted in a separate database if needed.
 EBS 12.2.x is installed.
 OTM 6.4.x is installed on a separate server than where EBS and SOA are installed.

Creating SOA Schemas Using the Repository Creation Utility (RCU)
The Oracle Fusion Middleware RCU is used to install the database schemas that are required by specific
Oracle Fusion Middleware products. The RCU can be downloaded from My Oracle Support as Patch
20996068. The same database hosting the EBS schema will be used to host the SOA schemas. You must
know the SYS or SYSTEM user password for the EBS database in order to create the repositories. Do
NOT continue until you know the SYS or SYSTEM user password.
After downloading the .zip file from Patch 20996068, extract the contents to a directory of your choice.
This directory will be referred to as the RCU_HOME directory.
Start RCU from the bin directory inside the RCU_HOME directory:
cd RCU_HOME/bin
./rcu
You should see the following screens:
Select Create to create a new repository

After entering the SYS user password, the utility will check the database connection. Once complete,
the following screen will be displayed. Select the following components which are needed for SOA and
specify the prefix for the schema names:

Specify the schema passwords. For ease of remembrance, select to use the same passwords for all
schemas. It is VERY important that you take note of the passwords and schema owner names in this
screen as they will be needed when installing SOA. Do not lose this information.

Click Next to proceed with creating the necessary tablespaces.

Click Create to create the tablespaces. Once completed, you will receive a confirmation that the
components have been created successfully.

Installing WebLogic Server 10.3.6
Since the installation of SOA will be done on the same server as EBS, a separate installation of WebLogic
must be done as the application server for SOA. This must be located in a different Fusion Middleware
ORACLE_HOME directory than the one used for EBS. The general documentation for WebLogic Server
10.3.6 is located here:
https://docs.oracle.com/middleware/11119/wls/WLSIG/toc.htm
Note that if you are using the general installer, Java must be installed on the server. The following
screenshots are an overview of what you will go through after starting the installer in graphical mode
per the link above.

You MUST ensure to select to “Create a new Middleware Home” and define a new directory for the new
WebLogic installation. Take note of the path for the Middleware Home as it will be needed for the SOA
installation:

Uncheck checkbox for “I wish to receive security updates via My Oracle Support” and click Next. Choose
the Typical installation type:

Specify the location of the JDK where Java is installed:

Proceed without changing the installation directories. The following screen will be displayed if the
installation is successful:

Installing Oracle SOA Suite 11.1.1.9.0
After WebLogic has been installed, you are now ready to install the SOA suite libraries. The general SOA
documentation is located here:
https://docs.oracle.com/middleware/11119/core/INSOA/toc.htm
From the link above, follow Section 2.2.1 to obtain the software. Follow Section 2.2.2 for steps to start
the installer. Once started you should see the following screen:

Click Next to Skip Software Updates

After passing the required system prerequisites, you will be prompted to select the Oracle Middleware
Home. This directory should be the same directory as the Oracle Middleware Home specified for the
WebLogic installation in the previous section.

The install will look for the application server and will detect the WebLogic server previously installed:

Click through the installation summary. The following 2 screens indicate a successful installation of SOA:

Click Finish to complete the installation.

Create and Configure the WebLogic Server Domain for SOA
After the WebLogic and SOA libraries have been installed, the next step is to create the server domain
and configure the SOA suite components. This will be done through the Fusion Middleware
Configuration Wizard utility.
To start the configuration wizard:
cd SOA_ORACLE_HOME/common/bin
./config.sh
Once the wizard is started, select to create a new WebLogic domain:

Make the following selections for domain sources:

You can keep the default domain name and click Next. For ease of access, do not change the domain
location or application location:

Specify the credentials for the WebLogic administrator. It is important that you take note of the
credentials inputted here as they will be needed for any administrative tasks for WebLogic such as
starting and stopping services.

Specify the location of the JDK where Java is installed:

In the following screens, you will configure the JDBC for the previously created component schemas that
were created via the RCU. Input the DB service name, host name of the database, database port, and
schema passwords that were set in the “Creating SOA Schemas Using the Repository Creation Utility
(RCU)” section and validate the connection settings. Once the connections have been established for
each component schema, you can proceed with the optional configuration of WebLogic.
IMPORTANT NOTE: Since the application server for SOA is installed on the same server as EBS, it is
important that you do not click next on the following screen, without first checking the box for
Administration Server – Modify Settings. This is because without doing so, the Admin server will be
installed with default settings. Since there is already another WebLogic instance for EBS, there will be
an issue with conflicting ports for the admin server. Ensure to check the checkbox next to
Administration Server – Modify Settings and change the WebLogic Admin port to something other than
7001 (example: 7010) as 7001 is being used for the EBS WebLogic instance. You do NOT need to change
settings for the SOA managed server as the default port of 8001 is not in use. Failure to do this step will
result in failing to startup the WebLogic server.
After changing the port, you will get a confirmation that the domain was created successfully.

Installing Patch 13882058
One-off patch 13882058 is required to be installed for SOA. Download the patch from Patch 13882058 .
The fndext.jar file must be added to the WebLogic CLASSPATH on the Oracle SOA Suite 11g installation.
Unzip the patch, and copy the fndext.jar to the $DOMAIN_HOME/lib directory of the current
WebLogic domain where SOA is installed.
Starting WebLogic Administration Server and Configuring Node Manager Port

Prior to starting the WebLogic Server and the node manager, you will need to ensure that the node
manager properties are correctly set.
Navigate to $ORACLE_HOME /wlserver_10.3/common/nodemanager and edit the

nodemanager.properties file.
Set the property Start Script Enabled to true. Failure to set this property will result in errors when
starting the SOA managed server.
StartScriptEnabled=true
Save the nodemanager.properties file with the change.
To start the WebLogic Admin Server, the following environment variables should be set. Do not blindly
copy and paste the values below as they are shown for example purposes only. Use the correct values
and paths based on your specific WebLogic install:
export MW_HOME=/global/oracle/omsoa01/app/Middleware
export ORACLE_INSTANCE=${MW_HOME}/instances/instance1
export DOMAIN_NAME=soa_domain
export DOMAIN_HOME=${MW_HOME}/user_projects/domains/${DOMAIN_NAME}
export WLS_USER=weblogic
export WLS_PW=password
export ADMIN_URL_HTTP=`cat ${DOMAIN_HOME}/bin/startManagedWebLogic.sh | awk '/ADMIN_URL=\"http/

{gsub(/\"/, "", $1); sub(/.*=/, "", $1); print $1}'`
export ADMIN_URL_T3=`cat ${DOMAIN_HOME}/bin/stopManagedWebLogic.sh | awk '/ADMIN_URL=\"t3/

{gsub(/\"/, "", $1); sub(/.*=/, "", $1); print $1}'`

Once the environment variables have been set, navigate to $DOMAIN_HOME. Execute the following
command to start the weblogic admin server:
nohup ./startWebLogic.sh -Dweblogic.management.username=${WLS_USER} -

Dweblogic.management.password=${WLS_PW} >weblogic.out&
Access the WebLogic Admin console through a browser:
http://<server_host_name>:<weblogic_port>/console
Enter the WebLogic Administrator user credentials specified when creating the WebLogic Server Domain
earlier in this section.

From the domain menu, select Environment -> Machines and then Select LocalMachine

Click on the Node Manager tab and change the listen port to an available port (ex: 5557). 5556 is used
by the node manager of the EBS Weblogic instance and thus cannot be used for the node manager that
controls the SOA managed server.

Click Save to activate the changes. You should now be able to start Node Manager successfully by
performing the following from the server:
Navigate to $ORACLE_HOME /wlserver_10.3/server/bin. Run the following command to start the node
manager:
nohup ./startNodeManager.sh >nodemanager.out&
The node manager must be running in order to start the SOA managed server in WebLogic. Once node
manager has started, you can start the SOA managed server from the WebLogic Admin Console. From
the console, navigate to Environment -> Servers and click the ‘Control’ tab. Check the checkbox next to
SOA server and click Start. The SOA managed server should start successfully and should eventually
show a State of RUNNING.

Create or Verify the Oracle E-Business Suite Users for Authorized Access
The EBS-OTM integration requires a limited number of E-Business Suite user(s) that will be authorized to
connect to the Oracle E-Business Suite database. The authorization to connect to the Oracle E-Business
Suite database is determined by the role UMX|APPS_SCHEMA_CONNECT. A user that has this role will
be authorized to connect to the Oracle E-Business Suite database. Within the Oracle E-Business Suite,
the system administrator creates these users and assigns the UMX|APPS_SCHEMA_CONNECT role to
them.
Application users must be initially created using the Users window in the System Administrator
responsibility within the Oracle E-Business Suite (Security > Users > Define menu path), shown in the
following screenshot. The user meant to have the UMX|APPS_SCHEMA_CONNECT role does not need
any assigned responsibilities. For better security, in fact, this user should not have any roles or
responsibilities other than UMX|APPS_SCHEMA_CONNECT.
Note: For EBS, this user has usually already been created which is ASADMIN. If this user exists, verify
their roles and responsibilities as below. If this user does not exist, you can create the user with the
respective role and responsibility. You must know the password for ASADMIN. If you do not know
the password for ASADMIN then login to EBS as sysadmin/sysadmin and update the password for
ASADMIN. Alternatively, you can create a new user with the respective role and responsibility. The
password for this user will be needed when deploying the SOA composites.

The following screenshot shows the Roles and Role Inheritance page in the User Management
responsibility, specifically showing the Apps Schema Connect role. Note that the displayed name of the
role is translated, but the UMX|APPS_SCHEMA_CONNECT code stays the same across languages.

The following screenshot shows the Users page in the User Management responsibility. In this example,
a search for users with the Apps Schema Connect role displays several users with this role.

Click the Update icon for a particular user to navigate to the Update User page. The Update User page is
shown below. Click the Assign Roles button to add the respective role for this user if it does not exist as
the screenshot shows below:

Collecting the SOA Artifacts and Utilities on the Oracle E-Business Suite
Installation for Deployment
This section describes the steps to create the payload.zip file. This file contains the SOA artifacts and the
utilities required to deploy the SOA processes from the Oracle E-Business Suite products to the Oracle
SOA Suite 11g installation.
The ant command used in this section generates the payload file. The payload file contains a DBC file,
which is used to connect to the Oracle E-Business Suite from the Oracle SOA Suite 11g installation.
To create the payload file, perform the following steps on the Oracle E-Business Suite instance:
Step 1: Source Oracle E-Business Suite environment file from RUN File System:
source $APPL_TOP/APPS.env
Step 2: Run the following ant script
ant -f $JAVA_TOP/oracle/apps/fnd/bpel/util/txk_integration_packager.xml -
DIntegration=bpel11g
-DFMWNodeName=<Oracle SOA Suite 11g Node name>
-DFMWIpAddress=<The Oracle SOA Suite IP Address>
-DgenDBC=<yes or no>
The following is an example of the command with sample values:
ant -f $JAVA_TOP/oracle/apps/fnd/bpel/util/txk_integration_packager.xml -
DIntegration=bpel11g -DFMWNodeName=ebsotm.us.oracle.com -
DFMWIpAddress=10.141.154.117 -DgenDBC=yes
Note: A DBC file will be generated in the above example as the flag -DgenDBC is set to yes (-DgenDBC
=yes).
The ant script performs the following:
 Collects technology integration specific files for SOA integration. The collected files include the
following:
o All BPEL, Mediator, Human Task Forms related files from different product directories in
the Oracle E-Business Suite installation.
o Central SOA process deployment files (for example, the EbsBpelMasterBuild11g.xml and
corresponding properties files)
 Packages all the collected contents (from a staging directory) into a payload.zip file in the
following location:
$APPLRGF/TXK/EBS_BPEL_payload.zip

Step 3: Copy the payload file to the Oracle SOA Suite 11g Server $ORACLE_HOME (the separate
ORACLE_HOME for the SOA server which is different than the EBS ORACLE_HOME). The payload files are
located in the $APPLRGF/TXK directory of the source Oracle E-Business Suite machine:
 EBS-BPEL payload file: $APPLRGF/TXK/EBS_BPEL_payload.zip
Copy the payload file to the Oracle SOA Suite 11g Server and unzip the file. This will create
$ORACLE_HOME/appsutil/<Oracle E-Business Suite instance name>/bpel directory.
Set the Required Environment Variables in the WebLogic Environment

Before you begin the SOA configuration, ensure that the following environment variables are set:
Note: The environment variables set in the above example are for illustration only. Do NOT blindly
copy these values to your environment. The values of the environment variables shown are examples
only. Set the appropriate environment variables based on your specific installation.
export BEA_HOME /u01/Integration/SOAMW_Home

export WL_HOME=$BEA_HOME/wlserver_10.3
export MW_HOME=$BEA_HOME
export ORACLE_HOME=$BEA_HOME/Oracle_SOA1
export CLASSPATH=$CLASSPATH:$MW_HOME/wlserver_10.3/server/lib/weblogic.jar
export DOMAIN_HOME=$MW_HOME/user_projects/domains/soa_domain
export ANT_CONTRIB=$MW_HOME/modules/net.sf.antcontrib_1.1.0.0_1-0b2
export PATH=$PATH:$MW_HOME/modules/org.apache.ant_1.7.1/bin
export JDK_HOME= /usr/java/jdk1.7.0_79
export JAVA_HOME= /usr/java/jdk1.7.0_79
Configuring EbsBpelGlobal11g.properties file

The $MW_HOME/appsutil/<Oracle E-Business Suite instance name>/bpel/EbsBpelGlobal11g.properties
file is used to specify the values to be used by the deployment script to deploy the SOA processes and
create Connection Objects to Oracle E-Business Suite in the Oracle SOA Suite 11g environment. The
following is a list of the only needed properties to be modified in the EbsBpelGlobal11g.properties file
for EBS-OTM integration.
Note: The value listed for each property are for example purposes only. Do NOT blindly copy these
values. The values should be specified based on your OTM and EBS installations. The values for
EbsAppsAdapter, EbsDBAdapter, and EbsAqAdapter should be the only ones kept the same. All other
property values not specified below can be left blank in the EbsBpelGlobal11g.properties file.

EbsAppsAdapter=eis/Apps/otm_EbsAppsAdapter
EbsDbAdapter=eis/DB/otm_EbsDbAdapter
EbsAqAdapter=eis/AQ/otm_EbsAqAdapter
oracle.home=/u01/Integration/SOAMW_Home/Oracle_SOA1
wl.home=/u01/Integration/SOAMW_Home/wlserver_10.3
wl.user=weblogic
wl.soaServerURL=http://ebsotm.us.oracle.com:8001
wl.target.server=soa_server1
wl.soaAdminServerURL=t3://ebsotm.us.oracle.com:7010
otm.server.url=http://otmebs.us.oracle.com:7778
Creating Datasource and Connection Factories

JDBC datasources must be created using the DBC file generated in Section Collecting the SOA Artifacts
and Utilities on the Oracle E-Business Suite Installation for Deployment and the Oracle E-Business Suite
credentials (for the user created and/or verified in Section Create or Verify the Oracle E-Business Suite
Users for Authorized Access) to establish a connection to the Oracle E-Business Suite from the Oracle
SOA Suite 11g installation. An associated Connection Factory is also needed for the particular Adapter
that is required for the Oracle E-Business Suite product being deployed to SOA Suite 11g.
This section provides detailed information regarding the creation of these Connection Objects by using
the supplied ANT scripts.
The provided command-line ant script, as part of this installation will create the Connection Factories as
per the property values specified for the particular connection Adapter (EbsDbAdapter,
EbsAppsAdapter, or EbsAqAdapter) in the EbsBpelGlobal11g.properties file.
Note: The ant commands are for illustration only. Ensure that both the WebLogic Admin and
Managed Servers are up and running before executing the ant command per section Starting
WebLogic Administration Server and Configuring Node Manager Port.
Before running the ant script following environment files are need to be sourced:
source $MW_HOME/user_projects/domains/<soa_domain>/bin/setDomainEnv.sh
source $MW_HOME/Oracle_SOA1/common/bin/setWlstEnv.sh

Navigate to $MW_HOME/appsutil/<Oracle E-Business Suite instance name>/bpel directory and run the
following ant command. Below is a detail of the command inputs.
ant -f EbsBpelMasterBuild11g.xml createConnections \
-DdataSourceName=<DataSource Name> \
-DdataSourceJNDIName=<JNDI Name for DataSource> \
-DasadminUser=<Name of the ASADMIN user > \
-DasadminPassword=<Password of the ASADMIN user > \
-DdbcFile=<Fully qualified name of the DBC file > \
-DdataSourceType=<DataSource typeL XA or NONXA> \
-Dadapters=<specify multiple if multiple EBS Products are deployed in the same SOA Suite 11g>\
-DproductName=<Oracle E-Business Suite Product being deployed> \
-DignoreDataSourceExists=<yes or no value to indicate to continue even if the DataSource exists>
The following is an example of the ant command to be used for OTM:
ant -f EbsBpelMasterBuild11g.xml createConnections \

-DdataSourceName=CustomerDbConnectionDS \
-DdataSourceJNDIName=jdbc/CustomerDBConnectionDS \
-DasadminUser=ASADMIN \
-DasadminPassword=password \
-DdbcFile=$MW_HOME/appsutil/EBSOTM_ebsotm/bpel/EBSOTM_EBSOTM.US.ORACLE.COM.dbc \
-DdataSourceType=NONXA \
-Dadapters=multiple \
-DproductName=otm \
-DignoreDataSourceExists=yes
The above command will create otm_EbsAQAdapter, otm_EbsAppsAdapter, and otm_EbsDbAdapter

with the datasource name CustomerDbConnectionDS. This is the most common form of the connection
object creation scenario where the standard Connection Objects are created automatically using the
script provided in the deployment package. After creating the Connection Objects for each of the Oracle
E-Business Suite – OTM integration flows, you can proceed to the next step of deploying the SOA
composites.
If the command executed successfully, a similar output should be seen as follows:
Buildfile: EbsBpelMasterBuild11g.xml
[echo] BEA_HOME: /u01/Integration/SOAMW_Home
getCredentials:
[input] Please enter password for username: weblogic :
init:
[echo] Adapter Configuration : -Dadapters= multiple
[echo] Setting this flag to "multiple" allows multiple adapter deployments

[echo] Example: msc_AppsAdapter, ahl_AppsAdapter, etc.
[echo] Connections with the naming convention product_name_EbsDB/APPS/AQAdapter needs
[echo] to be created.
[echo] Default (no flag) is to use Adapter values from EbsGlobal.properties file
findOS:
getWLSAdminPasswordWindows:
getWLSAdminPasswordUnix:
echoON:
[input] skipping input as property wl.password has already been set.
echoOFF:
getASADMINPasswordWindows:
getASADMINPasswordUnix:
echoON:
[input] skipping input as property asadminPassword has already been set.
echoOFF:
checkDBCExists:
getappsDBDetails:

executeTXKFMWGenericConfigUtility:
createDataSource:
[echo] ********************************************************************
[echo] CREATING DATA SOURCE
[echo] ********************************************************************
[wlst] Connecting to server using username:weblogic url:t3://ebsotm.us.oracle.com:7010
[wlst]
[wlst] Connecting to t3://ebsotm.us.oracle.com:7010 with userid weblogic ...
[wlst] Successfully connected to Admin Server 'AdminServer' that belongs to domain

'base_domain'.
[wlst]
[wlst] Warning: An insecure protocol was used to connect to the
[wlst] server. To ensure on-the-wire security, the SSL port or
[wlst] Admin port should be used instead.
[wlst]
[wlst] Check if Datasource CustomerDbConnectionDS already exits
[wlst] Check if JNDI Name jdbc/CustomerDBConnectionDS already exits
[wlst] Changing to Edit Mode
[wlst] Location changed to edit tree. This is a writable tree with
[wlst] DomainMBean as the root. To make changes you will need to start
[wlst] an edit session via startEdit().
[wlst]
[wlst] For more help, use help(edit)
[wlst] You already have an edit session in progress and hence WLST will
[wlst] continue with your edit session.
[wlst]
[wlst] Starting an edit session ...
[wlst] Started edit session, please be sure to save and activate your
[wlst] changes once you are done.
[wlst]

[wlst] Creating Datasource : CustomerDbConnectionDS
[wlst]
[wlst] Setting JDBCDataSourceParams for the Datasource CustomerDbConnectionDS
[wlst]
[wlst] Setting JNDI name for the Datasource CustomerDbConnectionDS
[wlst]
[wlst] Setting JDBCDriverParams for the Datasource CustomerDbConnectionDS
[wlst]
[wlst] Setting User and dbcFile properties for the Datasource CustomerDbConnectionDS
[wlst]
[wlst] Setting JDBCConnectionPoolParams for the Datasource CustomerDbConnectionDS
[wlst]
[wlst] Setting GlobalTransactionsProtocol for the Datasource CustomerDbConnectionDS
[wlst]
[wlst] Setting target for the Datasource CustomerDbConnectionDS
[wlst]
[wlst] Saving all your changes ...
[wlst] Saved all your changes successfully.
[wlst] Activating all your changes, this may take a while ...
[wlst] The edit lock associated with this edit session is released
[wlst] once the activation is completed.
[wlst] Activation completed
[wlst] Successfully created Datasource CustomerDbConnectionDS
[wlst] Disconnected from weblogic server: AdminServer
createOutboundConnections:
[echo] ********************************************************************
[echo] CREATING CONNECTION FACTORIES INSTANCES
[echo] ********************************************************************
[wlst] Connecting to server using username:weblogic url:t3://ebsotm.us.oracle.com:7010
[wlst]
[wlst] Connecting to t3://ebsotm.us.oracle.com:7010 with userid weblogic ...

[wlst] Successfully connected to Admin Server 'AdminServer' that belongs to domain
'base_domain'.
[wlst]
[wlst] Warning: An insecure protocol was used to connect to the
[wlst] server. To ensure on-the-wire security, the SSL port or
[wlst] Admin port should be used instead.
[wlst]
[wlst] Creating connection factory instance eis/AQ/otm_EbsAqAdapter for AqAdapter
[wlst]
[wlst]
[wlst] Loading application from

/u01/Integration/SOAMW_Home/Oracle_SOA1/soa/connectors/AqAdapter.rar ...
[wlst] Plan for your application will be written to

/u01/Integration/SOAMW_Home/Oracle_SOA1/soa/connectors/AQplan.xml
[wlst] <Nov 16, 2016 12:11:27 PM EST> <Info> <J2EE Deployment SPI> <BEA-260072> <Saved
configuration for application, AqAdapter.rar>
[wlst] Loaded application from

/u01/Integration/SOAMW_Home/Oracle_SOA1/soa/connectors/AqAdapter.rar and the deployment plan from
/u01/Integration/SOAMW_Home/Oracle_SOA1/s
oa/connectors/AQplan.xml
[wlst] The WLSTPlan object is assigned to variable wlstPlan_AqAdapter_rar.
[wlst]
[wlst] Check if connection factory instance eis/AQ/otm_EbsAqAdapter already exits
[wlst]
[wlst]
[wlst] Creating the plan variables
[wlst]
[wlst]
[wlst] Creating variable assignments
[wlst]
[wlst] Creating VariableAssignment for ModuleOverride AqAdapter.rar and ModuleDescriptor

with URI META-INF/weblogic-ra.xml.
[wlst] Created VariableAssignment with name var_eis/AQ/otm_EbsAqAdapter successfully.
[wlst] Creating VariableAssignment for ModuleOverride AqAdapter.rar and ModuleDescriptor

[wlst] Created VariableAssignment with name datasourcevar_eis/AQ/otm_EbsAqAdapter

successfully.

[wlst]
[wlst] Setting Xpath for connection factory instance
[wlst]
[wlst]
[wlst] Setting connection properties for the connection factory instance
[wlst]
[wlst]
[wlst] Saving the plan of AqAdapter
[wlst]
configuration for application, AqAdapter.rar>
[wlst] Location changed to edit tree. This is a writable tree with
[wlst] DomainMBean as the root. To make changes you will need to start
[wlst] an edit session via startEdit().
[wlst]
[wlst] For more help, use help(edit)
[wlst] You already have an edit session in progress and hence WLST will
[wlst] continue with your edit session.
[wlst]
[wlst] Redeploying application AqAdapter ...
[wlst] <Nov 16, 2016 12:11:32 PM EST> <Warning> <WebLogicDescriptorWL> <BEA-2156000>

<"config-root" /tmp/oracle/./config/deployments/AqAdapter.rar/plan was not found>
[wlst] <Nov 16, 2016 12:11:32 PM EST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating
redeploy operation for application, AqAdapter [archive: null], to soa_server1
.>
[wlst] You have an edit session in progress, hence WLST will not
[wlst] block for your redeployment to complete.
[wlst] Started the Redeployment of Application. Please refer to the returned WLSTProgress
object or variable LAST to track the status.
[wlst] Successfully deployed AqAdapter.rar

[wlst]
[wlst] Creating connection factory instance eis/DB/otm_EbsDbAdapter for DbAdapter
[wlst]
[wlst]

/u01/Integration/SOAMW_Home/Oracle_SOA1/soa/connectors/DbAdapter.rar ...

/u01/Integration/SOAMW_Home/Oracle_SOA1/soa/connectors/DBplan.xml
configuration for application, DbAdapter.rar>

/u01/Integration/SOAMW_Home/Oracle_SOA1/soa/connectors/DbAdapter.rar and the deployment plan from
/u01/Integration/SOAMW_Home/Oracle_SOA1/s
oa/connectors/DBplan.xml
[wlst] The WLSTPlan object is assigned to variable wlstPlan_DbAdapter_rar.
[wlst]
[wlst] Check if connection factory instance eis/DB/otm_EbsDbAdapter already exits
[wlst]
[wlst]
[wlst]
[wlst]
[wlst]
[wlst] Creating VariableAssignment for ModuleOverride DbAdapter.rar and ModuleDescriptor

[wlst] Created VariableAssignment with name var_eis/DB/otm_EbsDbAdapter successfully.
[wlst] Creating VariableAssignment for ModuleOverride DbAdapter.rar and ModuleDescriptor


[wlst] Created VariableAssignment with name datasourcevar_eis/DB/otm_EbsDbAdapter
successfully.
[wlst]
[wlst]
[wlst]
[wlst]
[wlst]
[wlst] Saving the plan of DbAdapter
[wlst]
configuration for application, DbAdapter.rar>
[wlst] Already in Edit Tree
[wlst]
[wlst] Redeploying application DbAdapter ...

<"config-root" /tmp/oracle/./config/deployments/DbAdapter.rar/plan was not found>
redeploy operation for application, DbAdapter [archive: null], to soa_server1
.>
[wlst] Successfully deployed DbAdapter.rar
[wlst]

[wlst] Creating connection factory instance eis/Apps/otm_EbsAppsAdapter for

OracleAppsAdapter
[wlst]
[wlst]

/u01/Integration/SOAMW_Home/Oracle_SOA1/soa/connectors/AppsAdapter.rar ...

/u01/Integration/SOAMW_Home/Oracle_SOA1/soa/connectors/Appsplan.xml
configuration for application, AppsAdapter.rar>

/u01/Integration/SOAMW_Home/Oracle_SOA1/soa/connectors/AppsAdapter.rar and the deployment plan
from /u01/Integration/SOAMW_Home/Oracle_SOA1
/soa/connectors/Appsplan.xml
[wlst] The WLSTPlan object is assigned to variable wlstPlan_AppsAdapter_rar.
[wlst]
[wlst] Check if connection factory instance eis/Apps/otm_EbsAppsAdapter already exits
[wlst]
[wlst]
[wlst]
[wlst]
[wlst]
[wlst] Creating VariableAssignment for ModuleOverride AppsAdapter.rar and ModuleDescriptor

[wlst] Created VariableAssignment with name var_eis/Apps/otm_EbsAppsAdapter successfully.
[wlst] Creating VariableAssignment for ModuleOverride AppsAdapter.rar and ModuleDescriptor

[wlst] Created VariableAssignment with name datasourcevar_eis/Apps/otm_EbsAppsAdapter

successfully.
[wlst]
[wlst]
[wlst]

[wlst]
[wlst]
[wlst] Saving the plan of OracleAppsAdapter
[wlst]
configuration for application, AppsAdapter.rar>
[wlst] Already in Edit Tree
[wlst]
[wlst] Redeploying application OracleAppsAdapter ...

<"config-root" /tmp/oracle/./config/deployments/AppsAdapter.rar/plan was not found>
redeploy operation for application, OracleAppsAdapter [archive: null], to soa_
server1 .>
[wlst] Successfully deployed AppsAdapter.rar
[wlst]
[wlst] Disconnected from weblogic server: AdminServer
[wlst] <Nov 16, 2016 12:11:46 PM EST> <Warning> <JNDI> <BEA-050001> <WLContext.close() was
called in a different thread than the one in which it was created.>

createConnections:
[echo] Sucessfully Created Connections
BUILD SUCCESSFUL
Total time: 40 seconds
You can also verify the connection factory through the WebLogic admin console. Access the admin
console through http://<server_host_name>:<weblogic_port>/console
Enter the WebLogic Administrator credentials:

You can verify the data source creation, by selecting Services -> Data Sources from the left hand menu.
If you used the same naming convention for the data source as what was provided as an example when
running the ant command, then you should see a CustomerDvConnectionDS data source configured.

Click on the CustomerDbConnectionDS data source and select the Monitoring tab, and then select the
Testing tab.

Select the SOA server and click Test Data Source. You should receive a confirmation that the test of the
data source was successful as shown in the screenshot below.

To verify the connection adapters, click on Deployments and select one of the adapters (i.e. AqAdapter).

Select the Configuration tab and then the Outbound Connection Pools tab. Expand the Connection
Factory which should show the otm_ebsAqAdapter. You can verify each adapter in the same method.

Executing the ant Scripts to Deploy the BPEL Process Files for EBS
Shipping – OTM and EBS PO – OTM Integration Flows
At this point of the process, the connectivity has been established between SOA and Oracle E-Business
Suite environment. You can proceed with the deployment of the SOA composites to the Oracle SOA
Suite 11g. This section will cover the deployment of SOA composites for the EBS Shipping – OTM
integration flow, as well as, the EBS Purchase Order (PO) – OTM integration flow.
The ant scripts for deployment and the property files are located in the $MW_HOME/appsutil/<EBS
Environment name>/bpel directory. Navigate to the specified directory.
The following 3 commands will be executed separately for OTM. You will need the weblogic admin
password as an input for each command:
ant -f EbsBpelMasterBuild11g.xml -Dadapters=multiple wsh_otm
ant -f EbsBpelMasterBuild11g.xml -Dadapters=multiple wms_otm
ant -f EbsBpelMasterBuild11g.xml -Dadapters=multiple po_otm
If executed successfully, a similar command line output as below should be seen for all three commands:
[oracle@ebsotm bpel]$ ant -f EbsBpelMasterBuild11g.xml -Dadapters=multiple wsh_otm
getCredentials:
init:

usage:
[echo] November-16-2016 01:19 PM
[echo] Master Build All targets: ant -k -Dstage.dir={/build root directory} -f

EbsBpelMasterBuild11g.xml all
[echo] Master Build one specific product team deployment : ant -Dstage.dir={/build root
directory} -f EbsBpelMasterBuild11g.xml {all or product_name}
wsh_otm:
[echo] MASTER stage.dir = /u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel
init:
[echo] IN Central Build teamsars is :

sca_wsh_SendOtmDocument.jar,sca_wsh_SendLocRefDataToOtm.jar,sca_wsh_SendRefDataStlToOtm.jar,sca_w
sh_SendDlvyToOtmService.jar,sca_wsh
_SendItemRefDataToOtm.jar,sca_wsh_SendTripToOtmService.jar,sca_wsh_SendTxnToOtmService.jar,sca_ws
h_ReceivePShipmentFromOtm.jar
[echo] IN Central Build filelist is : ${filelist}
[echo] Deploying files directly from directory (without any order)
projectwithlist:
processProjects:
[echo] javafiles : sca_wsh_SendOtmDocument.jar
extractFile:
[mkdir] Created dir: /u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/newtemp
[unzip] Expanding:
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendOtmDocument.jar into
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh
/newtemp
[echo] javafiles :: sca_wsh_SendOtmDocument.jar
[echo] composite.name :: WshSendOtmDocument

[echo] composite.revision :: 1.0
[echo] sarName : ${newSarName}
processConfigplan:
[copy] Copying 1 file to /u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh
[echo] src.dir : /u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh
[echo] configplans :
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/WshSendOtmDocument_cfgplan.xml
[echo] Adapter use flag is set to multiple
[echo] *******Adapter flag set to multiple
[echo] +++File being changed :

/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/WshSendOtmDocument_cfgplan.xml
[echo] teamdbadapter name : eis/DB/otm_EbsDbAdapter
[echo] teamaqadapter name : eis/AQ/otm_EbsAqAdapter
[echo] teamappsadapter name : eis/Apps/otm_EbsAppsAdapter
deployComposite:
[echo] sarName :
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendOtmDocument.jar
[echo] Before Deployment - checking the values
[echo]
configplans:/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/WshSendOtmDocument_cfgpla
n.xml
[echo]
sarName:/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendOtmDocument.jar
[echo] oracle.home = /u01/Integration/SOAMW_Home/Oracle_SOA1
deploy:
[input] skipping input as property serverURL has already been set.
[input] skipping input as property sarLocation has already been set.
[input] skipping input as property password has already been set.
[deployComposite] setting user/password..., user=weblogic

[deployComposite] Processing
sar=/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendOtmDocument.jar
[deployComposite] Adding sar file -

/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendOtmDocument.jar
[deployComposite] INFO: Creating HTTP connection to host:ebsotm.us.oracle.com, port:8001
[deployComposite] INFO: Received HTTP response from the server, response code=200
[deployComposite] ---->Deploying composite success.
[delete] Deleting directory

/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/newtemp
processProjects:
[echo] javafiles : sca_wsh_SendLocRefDataToOtm.jar
extractFile:
[unzip] Expanding:
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendLocRefDataToOtm.jar into
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel
/wsh/newtemp
[echo] javafiles :: sca_wsh_SendLocRefDataToOtm.jar
[echo] composite.name :: WshSendLocRefDataToOtm
processConfigplan:
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/WshSendLocRefDataToOtm_cfgplan.xml


/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/WshSendLocRefDataToOtm_cfgplan.xml
deployComposite:
[echo] sarName :
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendLocRefDataToOtm.jar
[echo]
configplans:/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/WshSendLocRefDataToOtm_cf
gplan.xml
[echo]
sarName:/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendLocRefDataToOtm.j
ar
deploy:
sar=/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendLocRefDataToOtm.jar

/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendLocRefDataToOtm.jar


processProjects:
[echo] javafiles : sca_wsh_SendRefDataStlToOtm.jar
extractFile:
[unzip] Expanding:
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendRefDataStlToOtm.jar into
/wsh/newtemp
[echo] javafiles :: sca_wsh_SendRefDataStlToOtm.jar
[echo] composite.name :: WshSendRefDataStlToOtm
processConfigplan:
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/WshSendRefDataStlToOtm_cfgplan.xml

/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/WshSendRefDataStlToOtm_cfgplan.xml
deployComposite:
[echo] sarName :
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendRefDataStlToOtm.jar

[echo]
configplans:/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/WshSendRefDataStlToOtm_cf
gplan.xml
[echo]
sarName:/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendRefDataStlToOtm.j
ar
deploy:
sar=/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendRefDataStlToOtm.jar

/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendRefDataStlToOtm.jar

processProjects:
[echo] javafiles : sca_wsh_SendDlvyToOtmService.jar
extractFile:
[unzip] Expanding:
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendDlvyToOtmService.jar into
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpe
l/wsh/newtemp
[echo] javafiles :: sca_wsh_SendDlvyToOtmService.jar

[echo] composite.name :: WshSendDlvyToOtmService
processConfigplan:
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/WshSendDlvyToOtmService_cfgplan.xml

/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/WshSendDlvyToOtmService_cfgplan.xml
deployComposite:
[echo] sarName :
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendDlvyToOtmService.jar
[echo]
configplans:/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/WshSendDlvyToOtmService_c
fgplan.xml
[echo]
sarName:/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendDlvyToOtmService.
jar
deploy:

sar=/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendDlvyToOtmService.jar

/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendDlvyToOtmService.jar

processProjects:
[echo] javafiles : sca_wsh_SendItemRefDataToOtm.jar
extractFile:
[unzip] Expanding:
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendItemRefDataToOtm.jar into
l/wsh/newtemp
[echo] javafiles :: sca_wsh_SendItemRefDataToOtm.jar
[echo] composite.name :: WshSendItemRefDataToOtm
processConfigplan:

/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/WshSendItemRefDataToOtm_cfgplan.xml

/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/WshSendItemRefDataToOtm_cfgplan.xml
deployComposite:
[echo] sarName :
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendItemRefDataToOtm.jar
[echo]
configplans:/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/WshSendItemRefDataToOtm_c
fgplan.xml
[echo]
sarName:/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendItemRefDataToOtm.
jar
deploy:
sar=/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendItemRefDataToOtm.jar

/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendItemRefDataToOtm.jar


processProjects:
[echo] javafiles : sca_wsh_SendTripToOtmService.jar
extractFile:
[unzip] Expanding:
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendTripToOtmService.jar into
l/wsh/newtemp
[echo] javafiles :: sca_wsh_SendTripToOtmService.jar
[echo] composite.name :: WshSendTripToOtmService
processConfigplan:
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/WshSendTripToOtmService_cfgplan.xml

/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/WshSendTripToOtmService_cfgplan.xml
deployComposite:

[echo] sarName :
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendTripToOtmService.jar
[echo]
configplans:/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/WshSendTripToOtmService_c
fgplan.xml
[echo]
sarName:/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendTripToOtmService.
jar
deploy:
sar=/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendTripToOtmService.jar

/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendTripToOtmService.jar

processProjects:
[echo] javafiles : sca_wsh_SendTxnToOtmService.jar
extractFile:

[unzip] Expanding:
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendTxnToOtmService.jar into
/wsh/newtemp
[echo] javafiles :: sca_wsh_SendTxnToOtmService.jar
[echo] composite.name :: WshSendTxnToOtmService
processConfigplan:
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/WshSendTxnToOtmService_cfgplan.xml

/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/WshSendTxnToOtmService_cfgplan.xml
deployComposite:
[echo] sarName :
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendTxnToOtmService.jar
[echo]
configplans:/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/WshSendTxnToOtmService_cf
gplan.xml
[echo]
sarName:/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendTxnToOtmService.j
ar

deploy:
sar=/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendTxnToOtmService.jar

/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_SendTxnToOtmService.jar

processProjects:
[echo] javafiles : sca_wsh_ReceivePShipmentFromOtm.jar
extractFile:
[unzip] Expanding:
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_ReceivePShipmentFromOtm.jar
into /u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/
bpel/wsh/newtemp
[echo] javafiles :: sca_wsh_ReceivePShipmentFromOtm.jar
[echo] composite.name :: WshReceivePShipmentFromOtm
processConfigplan:

/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/WshReceivePShipmentFromOtm_cfgplan.xm
l

/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/WshReceivePShipmentFromOtm_cfgplan.xm
l
deployComposite:
[echo] sarName :
[echo]
configplans:/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/WshReceivePShipmentFromOt
m_cfgplan.xml
[echo]
sarName:/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_ReceivePShipmentFromO
tm.jar
deploy:
sar=/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wsh/sca_wsh_ReceivePShipmentFromOtm.j
ar



BUILD SUCCESSFUL
[oracle@ebsotm bpel]$ ant -f EbsBpelMasterBuild11g.xml -Dadapters=multiple wms_otm
getCredentials:
init:
usage:

wms_otm:
init:

[echo] IN Central Build teamsars is : ${wms.sarfiles}
[echo] Using file order list for this deployment from EbsBpelLocal.properties
projwithnolist:
[echo] library.Project:${library.project}
[echo] JAVAFILES IS : sca_wms_SendDockDoorToOtm.jar
processProjects:
[echo] javafiles : sca_wms_SendDockDoorToOtm.jar
extractFile:
[mkdir] Created dir: /u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wms/newtemp
[unzip] Expanding:
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wms/sca_wms_SendDockDoorToOtm.jar into
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/w
ms/newtemp
[echo] javafiles :: sca_wms_SendDockDoorToOtm.jar
[echo] composite.name :: WmsSendDockDoorToOtm
processConfigplan:
[copy] Copying 1 file to /u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wms
[echo] src.dir : /u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wms
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wms/WmsSendDockDoorToOtm_cfgplan.xml


/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wms/WmsSendDockDoorToOtm_cfgplan.xml
deployComposite:
[echo] sarName :
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wms/sca_wms_SendDockDoorToOtm.jar
[echo]
configplans:/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wms/WmsSendDockDoorToOtm_cfgp
lan.xml
[echo]
sarName:/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wms/sca_wms_SendDockDoorToOtm.jar
deploy:
sar=/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wms/sca_wms_SendDockDoorToOtm.jar

/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wms/sca_wms_SendDockDoorToOtm.jar

/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/wms/newtemp
BUILD SUCCESSFUL

[oracle@ebsotm bpel]$ ant -f EbsBpelMasterBuild11g.xml -Dadapters=multiple po_otm
getCredentials:
init:
usage:

po_otm:
init:
[echo] IN Central Build teamsars is : ${po.sarfiles}
[echo] Using file order list for this deployment from EbsBpelLocal.properties
projwithnolist:
[echo] library.Project:${library.project}

[echo] JAVAFILES IS : sca_po_SendPoToOtm.jar
processProjects:
[echo] javafiles : sca_po_SendPoToOtm.jar
extractFile:
[mkdir] Created dir: /u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/po/newtemp
[unzip] Expanding:
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/po/sca_po_SendPoToOtm.jar into
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/po/newtem
p
[echo] javafiles :: sca_po_SendPoToOtm.jar
[echo] composite.name :: PoSendPoToOtm
processConfigplan:
[copy] Copying 1 file to /u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/po
[echo] src.dir : /u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/po
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/po/PoSendPoToOtm_cfgplan.xml

/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/po/PoSendPoToOtm_cfgplan.xml

deployComposite:
[echo] sarName :
/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/po/sca_po_SendPoToOtm.jar
[echo]
configplans:/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/po/PoSendPoToOtm_cfgplan.xml
[echo]
sarName:/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/po/sca_po_SendPoToOtm.jar
deploy:
sar=/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/po/sca_po_SendPoToOtm.jar

/u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/po/sca_po_SendPoToOtm.jar
[delete] Deleting directory /u01/Integration/SOAMW_Home/appsutil/EBSOTM_ebsotm/bpel/po/newtemp
BUILD SUCCESSFUL
[oracle@ebsotm bpel]$

Once the SOA processes are deployed, they can be viewed and verified on the Enterprise Manager
Console of the Oracle SOA Suite 11g installation within the particular domain. Access Enterprise
Manager from a browser through http://<server_host_name>:<weblogic_port>/em.
Enter the WebLogic Administrator credentials to login.

Once logged in, click on SOA -> soa-infra from the left hand menu.

Click on the ‘Deployed Composites’ tab and a list of active composites should be displayed which were
created through the ant commands.

Deploying the OTM Voucher to EBS Account Payables SOA Composites
The previous section covered the deployment of SOA composites for EBS Shipping – OTM integration
flow and EBS PO – OTM integration flow. The EBS Account Payables (AP) – OTM integration flow is
deployed as a separate process. The OtmVoucherToOracleApInvoice SOA Composite is used to interface
the outbound Oracle Transportation Management (OTM) product Voucher XML interface to the Oracle
E-Business Suite (EBS) Accounts Payable product Invoice XML interface. This composite will require
configuration setup and changes to the .jar file prior to deploying.
The OtmVoucherToOracleApInvoice SOA Composite is dependent on another composite

OtmVoucherUserExit. The OtmVoucherUserExit composite must be deployed prior to deploying
OtmVoucherToOracleApInvoice. You can acquire both composites from the server where OTM is
installed in the following directory:
$OTM_HOME/utils/integration/bpel/flows folder
Files:
OtmVoucherToOracleApInvoice_11g.zip
OtmVoucherUserExit_11g.zip
FTP the above mentioned zip files to either your local desktop or the SOA server (wherever you will be
making the modifications to these composites).
Deploying the OtmVoucherUserExit Composite

Unzip OtmVoucherUserExit_11g.zip to a local directory. Within this unzipped archive, there is a deploy
folder which contains the following 2 files:
sca_OtmVoucherUserExit_rev1.0.jar
shared_archive.jar
Create a zip file which will contain both sca_OtmVoucherUserExit_rev1.0.jar and shared_archive.jar.
These must be deployed together, otherwise you will receive errors when deploying the
OtmVoucherToOracleApInvoice composite. The shared_archive.jar file contains the WSDL that will be
reference by the OtmVoucherToOracleApInvoice composite. The zip file to be created can be named
anything (ex. Soa.zip) as long as it contains both sca_OtmVoucherUserExit_rev1.0.jar and
shared_archive.jar.

Access the Enterprise Manager console through a browser using the WebLogic Admin user credentials.
http://<server_host_name>:<weblogic_port>/em

From the left hand menu, select SOA -> soa-infra.

Select the SOA Infrastructure menu -> SOA Deployment -> Deploy…

If the zip file you created containing both sca_OtmVoucherUserExit_rev1.0.jar and shared_archive.jar is
on your local desktop, select ‘Archive is on the machine where this web browser is running’. Otherwise,
if the zip file is located on the SOA server, select ‘Archive on the server where Enterprise Manager is
running’.
Browse for the zip file and select the archive location. Under Configuration Plan select ‘No external
configuration plan is required’.
Click Next.

Select default for the SOA Partition and click Next.

Select Deploy as default revision and click ‘Deploy’.

If successfully deployed, you will receive a similar confirmation as below for the OtmVoucherUserExit
composite:
‘Composite “OtmVoucherUserExit [1.0]” has been successfully deployed’

Deploying the OtmVoucherToOracleApInvoice Composite
Unzip OtmVoucherToOracleApInvoice_11g.zip to a local directory. Within this unzipped archive, there

is a deploy folder which contains the following 2 files:
sca_OtmVoucherToOracleApInvoice_rev1.0.jar
deployPlan.xml
You will need to download a tool that has the capability of opening and modifying contents of .jar files.
You can use JDeveloper 11g, Winzip or any other tool to open
sca_OtmVoucherToOracleApInvoice_rev1.0.jar.
Once the .jar file has been opened, you will need to make modifications to the following files contained
in sca_OtmVoucherToOracleApInvoice_rev1.0.jar:
 ApInvoice_db.jca
 composite.xml
 QueryOrgId_db.jca
 xsl/Voucher_To_ApInvoice_Transform.xsl

The ApInvoice_db.jca will be configured to use the previously created Data Source and DbAdapter
Outbound Connection pool for the SOA server, created in the Creating Datasource and Connection
Factories Section. Edit ApInvoice_db.jca by editing the following highlighted line as follows:
<connection-factory location="eis/DB/otm_EbsDbAdapter" UIConnectionName="otm_EbsDbAdapter"

adapterRef="">
Note: The above is used as an example based on the parameters used to create the Datasource and
Connection Factories in Creating Datasource and Connection Factories section of this document. If
you used the same parameters, then you can make the exact change as above. If not, then you will
need to modify the location and connection name to match to what you used when initially creating
the datasource and connection factories.
Save the change made.

The QueryOrgId_db.jca will be configured to use the previously created Data Source and DbAdapter
Outbound Connection pool for the SOA server, created in the Creating Datasource and Connection
Factories Section. Edit QueryOrgId_db.jca by editing the following line as follows:
<connection-factory location="eis/DB/otm_EbsDbAdapter" UIConnectionName="otm_EbsDbAdapter"

adapterRef="">
Save the change made.

The composite.xml will need to be modified to configure the correct location of the
OtmVoucherUserExitService WSDL which was previously deployed. The location parameter for the web
service should be modified as follows (line 69 of the composite.xml file):
location="http://<soa_server_hostname>:<soa_managed_server_port>/soa-
infra/services/default/OtmVoucherUserExit/OtmVoucherUserExitService?WSDL"
Note: Do not make the same exact change as displayed in the screenshot above as this is used for
example purposes only. The port to be used is NOT the same port for which the WebLogic Admin
Server listens on. If you are unsure of what the port is, access the WebLogic Admin Console through
http://<server_host_name>:<weblogic_port>/console. Click on Environment ->Servers. The Listen
Port highlighted below for the SOA Server is what should be used in the change made to the
composite.xml.

The Voucher_To_ApInvoice_Transform.xsl file defines mapping relationship between OTM Voucher and
EBS Invoice. It also contains reference to the datasource that will be used to connect to the database.
The Voucher_To_ApInvoice_Transform.xsl file will be modified to point to the datasource created in the
Creating Datasource and Connection Factories Section. It will also be modified to include the
relationship mapping between OTM and EBS for VENDOR_NUM and VENDOR_SITE_CODE data elements
as this is not included in the xsl file by default. Edit Voucher_To_ApInvoice_Transform.xsl by editing the
following line as follows:
<xsl:variable name="CONN">jdbc/CustomerDBConnectionDS</xsl:variable>

The following highlighted section of Voucher_To_ApInvoice_Transform.xsl will need to be
uncommented AND edited to include the relationship mapping between OTM and EBS for
VENDOR_NUM and VENDOR_SITE_CODE data elements.
The resulting change should be as follows EXACTLY:
For ease of modification, the resulting modified portion of the XML has been included below (which can
be copied and pasted):
<xsl:for-each select="ns1:Shipment">

<xsl:if
test='ns1:ShipmentHeader/ns1:ServiceProviderAlias[ns1:ServiceProviderAliasQualifierGid/ns1:Gid/ns
1:Xid = "VENDOR_NUM"]/ns1:ServiceProviderAliasValue'>
<vendorNum>
<xsl:value-of
select='ns1:ShipmentHeader/ns1:ServiceProviderAlias[ns1:ServiceProviderAliasQualifierGid/ns1:Gid/
ns1:Xid = "VENDOR_NUM"]/ns1:ServiceProviderAliasValue'/>
</vendorNum>
</xsl:if>
<xsl:if
test='ns1:ShipmentHeader/ns1:ServiceProviderAlias[ns1:ServiceProviderAliasQualifierGid/ns1:Gid/ns
1:Xid = "VENDOR_SITE_CODE"]/ns1:ServiceProviderAliasValue'>
<vendorSiteCode>
<xsl:value-of
select='ns1:ShipmentHeader/ns1:ServiceProviderAlias[ns1:ServiceProviderAliasQualifierGid/ns1:Gid/
ns1:Xid = "VENDOR_SITE_CODE"]/ns1:ServiceProviderAliasValue'/>
</vendorSiteCode>
</xsl:if>
</xsl:for-each>
Save the changes made to Voucher_To_ApInvoice_Transform.xsl. Save the entire

sca_OtmVoucherToOracleApInvoice_rev1.0.jar to save changes made to the entire archive for all files in
the .jar file.

The remaining change needed to be done is for the deployPlan.xml which is contained in the deploy
folder for the unzipped OtmVoucherToOracleApInvoice_11g.zip archive. The deployPlan.xml will be
used when deploying the sca_OtmVoucherToOracleApInvoice_rev1.0.jar to point to the location of the
OtmVoucherUserExit web service. Edit deployPlan.xml by editing the following line as follows:
<replace>http://<soa_server_hostname>:<soa_managed_server_port>/soa-
infra/services/default/OtmVoucherUserExit/OtmVoucherUserExitService?WSDL</replace>
Note: Do not make the same exact change as displayed in the screenshot above as this is used for
example purposes only. The port to be used is NOT the same port for which the WebLogic Admin
Server listens on. If you are unsure of what the port is, access the WebLogic Admin Console through
http://<server_host_name>:<weblogic_port>/console. Click on Environment ->Servers. The same
change for the port should be made as what was done for the composite.xml.
Save the change to deployPlan.xml.

Access the Enterprise Manager console through a browser using the WebLogic Admin user credentials.
http://<server_host_name>:<weblogic_port>/em

From the left hand menu, select SOA -> soa-infra.

Select the SOA Infrastructure menu -> SOA Deployment -> Deploy…

If the modified sca_OtmVoucherToOracleApInvoice_rev1.0.jar is located on your local desktop, select
‘Archive is on the machine where this web browser is running’. Otherwise, if the .jar file is located on
the SOA server, select ‘Archive on the server where Enterprise Manager is running’.
Browse for the sca_OtmVoucherToOracleApInvoice_rev1.0.jar file and select the archive location.
If the modified deployPlan.xml select ‘Configuration plan is on the machine where this web browser is
running’. Otherwise, if the file is located on the SOA server, select ‘Configuration plan is on the server
where Enterprise Manager is running’.
Browse for the deployPlan.xml file and select the file location.
Click Next.

Select default for the SOA Partition and click Next.

Select Deploy as default revision and click ‘Deploy’.

If successfully deployed, you will receive a similar confirmation as below for the
OtmVoucherToOracleApInvoice composite:
‘Composite “OtmVoucherToOracleApInvoice [1.0]” has been successfully deployed’

The deployed composites for the OTM Voucher to EBS Account Payables integration flow should now be
visible under the ‘Deployed Composites’ in Enterprise Manager for SOA:
This completes the minimum setup and configuration of SOA/BPEL required for EBS – OTM integration.

E-Business Suite Integration with OTM – Technical Guide
April 2017
Author: Ahmed Abdallah

Oracle OTM-EBS Integration Technical Guide v1

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Oracle OTM-EBS Integration Technical Guide v1

Încărcat de

Drepturi de autor:

Formate disponibile

Oracle Transportation Management

E-Business Suite Integration with OTM – Technical Guide

ORACLE WHITE PAPER | APRIL 2017

2 | E-Business Suite Integration with OTM – Technical Guide

3 | E-Business Suite Integration with OTM – Technical Guide

You should see the following screens:

Select Create to create a new repository

4 | E-Business Suite Integration with OTM – Technical Guide

5 | E-Business Suite Integration with OTM – Technical Guide

6 | E-Business Suite Integration with OTM – Technical Guide

7 | E-Business Suite Integration with OTM – Technical Guide

8 | E-Business Suite Integration with OTM – Technical Guide

9 | E-Business Suite Integration with OTM – Technical Guide

10 | E-Business Suite Integration with OTM – Technical Guide

11 | E-Business Suite Integration with OTM – Technical Guide

12 | E-Business Suite Integration with OTM – Technical Guide

13 | E-Business Suite Integration with OTM – Technical Guide

14 | E-Business Suite Integration with OTM – Technical Guide

15 | E-Business Suite Integration with OTM – Technical Guide

16 | E-Business Suite Integration with OTM – Technical Guide

17 | E-Business Suite Integration with OTM – Technical Guide

18 | E-Business Suite Integration with OTM – Technical Guide

19 | E-Business Suite Integration with OTM – Technical Guide

To start the configuration wizard:

Once the wizard is started, select to create a new WebLogic domain:

20 | E-Business Suite Integration with OTM – Technical Guide

21 | E-Business Suite Integration with OTM – Technical Guide

22 | E-Business Suite Integration with OTM – Technical Guide

23 | E-Business Suite Integration with OTM – Technical Guide

24 | E-Business Suite Integration with OTM – Technical Guide

25 | E-Business Suite Integration with OTM – Technical Guide

Starting WebLogic Administration Server and Configuring Node Manager Port

Navigate to $ORACLE_HOME /wlserver_10.3/common/nodemanager and edit the

Save the nodemanager.properties file with the change.

export ADMIN_URL_HTTP=`cat ${DOMAIN_HOME}/bin/startManagedWebLogic.sh | awk '/ADMIN_URL=\"http/

export ADMIN_URL_T3=`cat ${DOMAIN_HOME}/bin/stopManagedWebLogic.sh | awk '/ADMIN_URL=\"t3/

26 | E-Business Suite Integration with OTM – Technical Guide

nohup ./startWebLogic.sh -Dweblogic.management.username=${WLS_USER} -

Access the WebLogic Admin console through a browser:

27 | E-Business Suite Integration with OTM – Technical Guide

28 | E-Business Suite Integration with OTM – Technical Guide

29 | E-Business Suite Integration with OTM – Technical Guide

nohup ./startNodeManager.sh >nodemanager.out&

30 | E-Business Suite Integration with OTM – Technical Guide

31 | E-Business Suite Integration with OTM – Technical Guide

32 | E-Business Suite Integration with OTM – Technical Guide

33 | E-Business Suite Integration with OTM – Technical Guide

34 | E-Business Suite Integration with OTM – Technical Guide

Step 2: Run the following ant script

The following is an example of the command with sample values:

The ant script performs the following:

35 | E-Business Suite Integration with OTM – Technical Guide

 EBS-BPEL payload file: $APPLRGF/TXK/EBS_BPEL_payload.zip

Set the Required Environment Variables in the WebLogic Environment

export BEA_HOME /u01/Integration/SOAMW_Home

Configuring EbsBpelGlobal11g.properties file

36 | E-Business Suite Integration with OTM – Technical Guide

Creating Datasource and Connection Factories

37 | E-Business Suite Integration with OTM – Technical Guide

The following is an example of the ant command to be used for OTM:

ant -f EbsBpelMasterBuild11g.xml createConnections \

The above command will create otm_EbsAQAdapter, otm_EbsAppsAdapter, and otm_EbsDbAdapter

If the command executed successfully, a similar output should be seen as follows: