multi-instance ebs to otm integration - aioug multiple ebs...multi-instance ebs to otm integration...
TRANSCRIPT
Multi-Instance EBS to OTM Integrationg
How to setup and operate multiple EBS instances to a p p psingle OTM instance
Deepak Morey & Bhavesh PanchalDeloitte Consulting India Pvt. Ltd.D 9 2011Dec 9, 2011
Contents
Introduction 3
Single Instance EBS Configuration Review 8
Multiple Instance EBS Configuration 12
Scalability, SOA 11g and Additional Considerations 21y g
Contact Information 25
Introduction
Standard EBS-OTM Integrated Environment
The standard integration between EBS and OTM consists of the following applications and supports a single-domain configuration.
with
one
OTM
inst
ance
.ppt
x
- 4 - Inte
grat
ing
Mul
tiple
EB
S in
stan
ces
Limitations with current configuration
Hardware costsHardware costs
Redundancy
with
one
OTM
inst
ance
.ppt
x
Business Limitations
- 5 - Inte
grat
ing
Mul
tiple
EB
S in
stan
ces
Multiple EBS Instances to a Single OTM Instance
Integrating multiple instances of EBS (or any ERP) to a single instance of OTM can overcome the mentioned limitations.
with
one
OTM
inst
ance
.ppt
x
- 6 - Inte
grat
ing
Mul
tiple
EB
S in
stan
ces
Functional Benefits of Multiple Domains for Shippers and Logistics Providers
Integrate with multiple
customer’s dorder
management systems
Allows for different
workflows within differentwithin different
business operations
Provides security to limit visibility from
with
one
OTM
inst
ance
.ppt
x
one customer to the next
Allows transportation and trade to
separate itself from the ERP
Utilize GTM across multiple divisions of the
same
Single source of
transportation and trade
- 7 - Inte
grat
ing
Mul
tiple
EB
S in
stan
ces from the ERP
strategycorporationacross business units
Single Instance EBS Configuration Review
Oracle EBS Setup
EBS System Profiles define the behavior of EBS. In terms of OTM, they identify specific instance and domain EBS will be connected to. There are two types of profiles to set up here, WSH Profiles and OTM Profiles.
The WSH: BPEL Domain nameThe WSH: BPEL Domain name defines which BPEL domain will talk to EBS.
Defines the domain in OTM that will receive information from EBS.
This is the integration user name password at the domain level for
with
one
OTM
inst
ance
.ppt
x
OTM.
This is the integration user name
- 9 - Inte
grat
ing
Mul
tiple
EB
S in
stan
ces
gid at the domain level for OTM.
BPEL Configuration
The BPEL domain configuration contains BPEL processes which will be interacting with EBS and OTM.
Each BPEL process is code which transforms the data between EBS and OTM.
There are multiple BPEL processes which perform specific tasks.
with
one
OTM
inst
ance
.ppt
x
- 10 - Inte
grat
ing
Mul
tiple
EB
S in
stan
ces
OTM Configuration
OTM External Systems defines the external systems that OTM will send data.
For SOA the external system defines the BPEL process to which it sends dataFor SOA, the external system defines the BPEL process to which it sends data.
with
one
OTM
inst
ance
.ppt
x
- 11 - Inte
grat
ing
Mul
tiple
EB
S in
stan
ces
Multiple Instance EBS Configuration
Multiple Domain Application Overview
Multiple instances of EBS will be connected to OTM via SOA. The configuration will require multiple domains within SOA and OTM.
with
one
OTM
inst
ance
.ppt
x
- 13 - Inte
grat
ing
Mul
tiple
EB
S in
stan
ces
EBS System Profile Modifications
Modify the EBS System Profiles to point to each BPEL Domain and OTM Domain.
EBS Instance 1 is pointed to OTM Domain 1 and BPEL Domain 1EBS Instance 1 is pointed to OTM Domain 1 and BPEL Domain 1
EBS Instance 2 is pointed to OTM Domain 2 and BPEL Domain 2
EBS 1 EBS 2
with
one
OTM
inst
ance
.ppt
x
- 14 - Inte
grat
ing
Mul
tiple
EB
S in
stan
ces
SOA Integration Modifications
There are required modifications at the SOA level to enable the integration from multiple instances of EBS to a single instance of OTM.
Oracle SOA Suite Enterprise Manager– Create two JNDI names, one for each Oracle EBS Instance
BPEL Domain 1– All the BPEL processes should refer JNDI 1, to connect to database of EBS 1
BPEL Domain 2BPEL Domain 2– All the BPEL processes should refer JNDI 2, to connect to database of EBS 2
with
one
OTM
inst
ance
.ppt
x
- 15 - Inte
grat
ing
Mul
tiple
EB
S in
stan
ces
BPEL Modifications
Ensure the following BPEL processes are configured properly to ensure integration between the correct EBS instance to the associated OTM domain.
1. WshReceivePShipmentFromOtm - Should point to specific EBS JDNI to update planned shipment from OTM for the deliveries.p p
2. WshSendDlvyToOtmService - Should point to specific EBS JNDI to get the delivery information from the EBS.
3. WshSendItemRefDataToOtm - Should point to specific EBS JNDI to get the item p p ginformation from the EBS.
4. WshSendLocRefDataToOtm - Should point to specific EBS JNDI to get the location information from the EBS.
5. WshSendRefDataStlToOtm - Should point to generic OTM web service for sending carrier information to OTM.
6. WshSendTripToOtmService - Should point to specific EBS JNDI to get the Actual
with
one
OTM
inst
ance
.ppt
x
p p p gTrip information from the EBS.
7. WshSendTxnToOtmService - Should point to generic OTM web service for sending delivery/actual shipment information to OTM.
- 16 - Inte
grat
ing
Mul
tiple
EB
S in
stan
ces
8. Additional BPEL processes based on custom requirements
OTM Configuration
Configuring OTM to integrate to multiple instances of EBS will vary depending on the reasons for the architecture.
Shippers integrating a single instance of OTM to multiple ERP production environments.
Shippers integrating a single instance of OTM to multiple non-production ERP environments.
3PL’s integrating a single instance of OTM to multiple customer ERP3PL s integrating a single instance of OTM to multiple customer ERP environments.
with
one
OTM
inst
ance
.ppt
x
- 17 - Inte
grat
ing
Mul
tiple
EB
S in
stan
ces
Integrated Solution Diagram for Shippers with Multiple ERP Instances in Production
- Service providers, locations, orders and shipments in the sub domain.- External systems for outbound integration y gpointing to the proper BPEL domain should be in the sub domain
EBS Prod 1EBS Prod 1
with
one
OTM
inst
ance
.ppt
xCommon configuration of rate offerings, rate records, and power data can be setup in the
EBS Prod 2
- 18 - Inte
grat
ing
Mul
tiple
EB
S in
stan
ces can be setup in the
master domain.
Integrated Test Solution Diagram for Shippers with a Single ERP Instance
- All the master data should be mirrored in both the domains
EBS DevEBS Dev
with
one
OTM
inst
ance
.ppt
x
EBS QA
- 19 - Inte
grat
ing
Mul
tiple
EB
S in
stan
ces
Integrated Solution Diagram for 3PL’s
- Service providers, locations, orders and shipments in the sub domain.- External systems for outbound integrationExternal systems for outbound integration pointing to the proper BPEL domain should be in the sub domain
with
one
OTM
inst
ance
.ppt
xCommon configuration of rate offerings, rate records, and power data can be setup in the
- 20 - Inte
grat
ing
Mul
tiple
EB
S in
stan
ces can be setup in the
master domain.
Scalability, SOA 11g and Additional ConsiderationsConsiderations
Scalability of Solution
More than two EBS instances can be integrated with a Single OTM instance on a single SOA Suite.– The limit of total EBS instances that could be integrated depends on the hardware
capacity of servers on which the SOA Suite and OTM applications are installed.
Could be scaled for the integration on clustered environment of SOA and/orCould be scaled for the integration on clustered environment of SOA and/or scalability enabled environment of OTM with the following changes:– Set the URL of SOA Suite and/or OTM instance in round robin based load balancing
with a physical load balancer at the entrywith a physical load balancer at the entry.– The URLs do not change in the case of content switch based load balancing. The load
is distributed from the first server based on the incoming/outgoing traffic dynamically.
with
one
OTM
inst
ance
.ppt
x
- 22 - Inte
grat
ing
Mul
tiple
EB
S in
stan
ces
Extending this approach from 10g to 11g
11g offers more capabilities to improve this approach.
There are two ways to achieve this on 11gThere are two ways to achieve this on 11g– Have two managed servers each server having the same composites but pointing to
two different JNDIs from two managed serversUtilize two partitions in the same managed server having the same composites but– Utilize two partitions in the same managed server having the same composites but pointing to two different JNDIs from two partitions
Customization is required on EBS concurrent requests to point to composites.
with
one
OTM
inst
ance
.ppt
x
- 23 - Inte
grat
ing
Mul
tiple
EB
S in
stan
ces
Additional Considerations
Outages of the SOA Suite will result in downtime of all the integrations for all the EBS instances.
Proper care should be taken in customization/deployment of BPEL processes as they are different for different domains in SOA Suite.
Performance impact on SOA suite during heavy load of transactional processing. This is generally not a problem because in this approach we will not be mixing PROD integration with DEV or TEST integration.
with
one
OTM
inst
ance
.ppt
x
- 24 - Inte
grat
ing
Mul
tiple
EB
S in
stan
ces
Never mix integration of PROD with DEV or QA
EBS ProdEBS Prod
with
one
OTM
inst
ance
.ppt
x
EBS QA
- 25 - Inte
grat
ing
Mul
tiple
EB
S in
stan
ces
Q & AQ & A
with
one
OTM
inst
ance
.ppt
x
- 26 - Inte
grat
ing
Mul
tiple
EB
S in
stan
ces
Th k Y !Thank You!
with
one
OTM
inst
ance
.ppt
x
- 27 - Inte
grat
ing
Mul
tiple
EB
S in
stan
ces
Contact Information
Contact Information
Consulting Resources
Photo
Dan SedoreSenior Manager - VCE
dsedore@deloitte [email protected]
Bhavesh PanchalManager - VCE
Deepak Morey
PhotoManager VCE
Photo
Deepak MoreySenior Consultant - VCE
with
one
OTM
inst
ance
.ppt
x
Photo
Vijay Sai SomisettiSenior Consultant - VCE
- 29 - Inte
grat
ing
Mul
tiple
EB
S in
stan
ces Photo