MD200 WHC SOA Composite Migration V1.2

Enterprise Services ESA
MD120: Application Interfaces

Migration Technical Guide
Enterprise Services ESA WHC SOA Composites Migration Document
Author:
CTS
Work stream: WHC 17 Nov 201028/01/03 10:10

Creation Date:
17 Nov 2010
Last Updated: 17 Nov 201011

Version:
Draft 1a
Approvals
Name
Position
Approved by:
Approved by:
Approved by:
SOA Deployment - User Guide

Company Confidential For internal use only
Signatur
e
Date
Document Control
Change Record
Date
15 Nov 2010
15 Dec 2010
08 Feb 2011
Change Originator
Somesh Purohit
Soumyoshis
Poddar
Somesh Purohit
Version
Initial
Description of change
Initial version created
Worklist DVM Creation added
Reviewed by
Date
Name
Position
Reviewed by:
Reviewed by:
Reviewed by:
Distribution
Copy No.
1.
Name
Library Master
Location
IRI Program Library
Related Documents
Document Reference
Related Document Names
Contents
Document Control................................................................................................... ii
Contents................................................................................................................. iii
1
Introduction..................................................................................................... 4
1.1 Topical Essay...............................................................................................4
1.2 Scope of this document...............................................................................4
2
Pre-requisites for the SOA migration...............................................................5
2.1 JMS Configuration in Weblogic Console........................................................5
2.2 DB Adapter Configuration in Weblogic Console...........................................8
2.3 FTP Adapter Configuration in Weblogic Console..........................................8
2.4 Deployment should be completed for the common services such as the
worklist, Email Services.......................................................................................8
3
AIA-MDS Repository update for Custom EBOs.................................................9
3.1 Setting up the AIA_HOME environment........................................................9
3.2 Migrate the Custom EBOs to AIA File system repository..............................9
3.3 Update the Custom EBOs to AIA MDS........................................................10
4
Configuration Plan......................................................................................... 11
4.1 Generating the configuration plan.............................................................11
4.2 Editing the generated configuration plan..................................................12
5
SOA Composite Migration..............................................................................18
5.1 Inbound Composite List.............................................................................18
5.2 Outbound Composite List..........................................................................21
5.3 Common FTP Composite List.....................................................................24
5.4 Order of Deployments...............................................................................24
5.5 Deployment of the composites through Ant..............................................24
6
Configurable variables of the composite.......................................................27
6.1 Inbound Operations...................................................................................27
6.2 Outbound Operations................................................................................28
6.3 Common Operations..................................................................................30
6.4 How to change the above from EM Console...............................................31
6.5 Variables and their default values.............................................................34
7
Worklist DVM Set up in SOA Composer..........................................................35
7.1 IR_WORKLIST_SUPPORT_GROUP S DVM Entry............................................35
8
Post Deployment changes to be done manually............................................40
1 Introduction
1.1
Topical Essay
In order to migrate the SOA composites to various environments there is a
need to develop a deployment guide. This document will be referred by the
server administrators to migrate the composites to the required
environment. Also this can be referred by the people who want configure
the JCA properties for the file and ftp adapters if required.
1.2
Scope of this document
The pre-requisites needed for the migration of the inbound and

outbound composites are within the scope of this document.
This document covers the generation and modification of the
configuration plans for the required composite.
It covers the details of the entire inbound and outbound composites
and their migration process.
The JCA properties of the various file and ftp adapters which are
configurable from the EM Console are within the scope of this
document.
The migration of the common service except the FTP Services is out
of scope of this document.
The details of the common composites are out of scope of this
document.
The configuration and creation of the different JNDIs are out of
scope of this document.

4
2 Pre-requisites for the SOA migration

2.1
JMS Configuration in Weblogic Console
Following needs to be created in the target environment.

For Inbound Operations
WhcInJMSModule
eis/wls/whcInQ
JMS module name:

JNDI for JMS adapter:
Name
Type
JNDI Name
Subdeployment
Targets
3PLJMSPackQSource
Queue
eis/wls/3PLPackJMSQ
3PLJMSPackQSource
WhcJMSSer
ver
CAPSJMSInvQSource
Queue
eis/wls/CAPSInvJMSQ
CAPSJMSInvQSource
WhcJMSSer
ver
CAPSJMSOnHandQSo
urce
Queue
eis/wls/CAPSOnHandJMSQ
CAPSJMSOnHandQSo WhcJMSSer
urce
ver
CAPSJMSPackQSourc
e
Queue
eis/wls/CAPSPackJMSQ
CAPSJMSPackQSourc
e
WhcJMSSer
ver
CAPSJMSPOQSource
Queue
eis/wls/CAPSPOJMSQ
CAPSJMSPOQSource
WhcJMSSer
ver
CAPSJMSShipQSourc
e
Queue
eis/wls/CAPSShipJMSQ
CAPSJMSShipQSourc
e
WhcJMSSer
ver
CAPSJMSWorkOrderQ
Source
Queue
eis/wls/CAPSWorkOrderJMS CAPSJMSWorkOrderQ WhcJMSSer

Q
Source
ver
EbizJMSPackQSource
Queue
eis/wls/EbizPackJMSQ
EbizJMSPackQSource
WhcJMSSer
ver
EbizJMSShipQSource
Queue
eis/wls/EbizShipJMSQ
EbizJMSShipQSource
WhcJMSSer
ver
InvCAPSConnFactory
Connect
eis/wls/InvCAPSConnFactor
ion
InvCAPSConnFactory
y
Factory
WhcJMSSer
ver
InvITSConnFactory
Connect
ion
eis/wls/InvITSConnFactory
Factory
WhcJMSSer
ver
InvTRMConnFactory
Connect
ion
eis/wls/InvTRMConnFactory InvTRMConnFactory
Factory
WhcJMSSer
ver
InvTROConnFactory
Connect
ion
eis/wls/InvTROConnFactory InvTROConnFactory
Factory
WhcJMSSer
ver
ITSJMSInvQSource
Queue
eis/wls/ITSInvJMSQ
ITSJMSInvQSource
WhcJMSSer
ver
ITSJMSOnHandQSour
ce
Queue
eis/wls/ITSOnHandJMSQ
ITSJMSOnHandQSour
ce
WhcJMSSer
ver
InvITSConnFactory

5
WhcJMSSer
ver
ITSJMSPOQSource
Queue
eis/wls/ITSPOJMSQ
ITSJMSPOQSource
ITSJMSWorkOrderQSo
urce
Queue
eis/wls/ITSWorkOrderJMSQ
ITSJMSWorkOrderQSo WhcJMSSer
urce
ver
OnHandCAPSConnFa
ctory
Connect
eis/wls/OnHandCAPSConnF OnHandCAPSConnFa
ion
actory
ctory
Factory
WhcJMSSer
ver
OnHandITSConnFact
ory
Connect
eis/wls/OnHandITSConnFac OnHandITSConnFact
ion
tory
ory
Factory
WhcJMSSer
ver
OnHandTRMConnFac
tory
Connect
eis/wls/OnHandTRMConnFa OnHandTRMConnFac
ion
ctory
tory
Factory
WhcJMSSer
ver
OnHandTROConnFac
tory
Connect
eis/wls/OnHandTROConnFa OnHandTROConnFac
ion
ctory
tory
Factory
WhcJMSSer
ver
OTMJMSPackQSource
Queue
eis/wls/OTMPackJMSQ
OTMJMSPackQSource
WhcJMSSer
ver
OTMJMSShipQSource
Queue
eis/wls/OTMShipJMSQ
OTMJMSShipQSource
WhcJMSSer
ver
Pack3PLConnFactory
Connect
eis/wls/Pack3PLConnFactor
ion
Pack3PLConnFactory
y
Factory
WhcJMSSer
ver
PackCAPSConnFactor
y
Connect
eis/wls/PackCAPSConnFact
ion
ory
Factory
PackCAPSConnFactor WhcJMSSer
y
ver
PackEbizConnFactory
Connect
eis/wls/PackEbizConnFacto
ion
ry
Factory
PackEbizConnFactory
PackOTMConnFactor
y
Connect
eis/wls/PackOTMConnFacto PackOTMConnFactor
ion
ry
y
Factory
PackTRMConnFactory
Connect
eis/wls/PackTRMConnFacto
WhcJMSSer
ion
PackTRMConnFactory
ry
ver
Factory
POCAPSConnFactory
Connect
eis/wls/POCAPSConnFactor
ion
y
Factory
POCAPSConnFactory
WhcJMSSer
ver
POITSConnFactory
Connect
ion
eis/wls/POITSConnFactory
Factory
POITSConnFactory
WhcJMSSer
ver
POTRMConnFactory
Connect
ion
eis/wls/POTRMConnFactory POTRMConnFactory
Factory
WhcJMSSer
ver
POTROConnFactory
Connect
ion
eis/wls/POTROConnFactory POTROConnFactory
Factory
WhcJMSSer
ver
ShipCAPSConnFactor
y
Connect
eis/wls/ShipCAPSConnFact
ion
ory
Factory
ShipCAPSConnFactor
y
WhcJMSSer
ver
ShipEbizConnFactory
Connect
eis/wls/ShipEbizConnFactor
ion
ShipEbizConnFactory
y
Factory
WhcJMSSer
ver
ShipOTMConnFactory
Connect
eis/wls/ShipOTMConnFacto
WhcJMSSer
ion
ShipOTMConnFactory
ry
ver
Factory

6
WhcJMSSer
ver
WhcJMSSer
ver
ShipTRMConnFactory
Connect
eis/wls/ShipTRMConnFacto
ion
ry
Factory
ShipTRMConnFactory
WhcJMSSer
ver
TRMJMSInvQSource
Queue
eis/wls/TRMInvJMSQ
TRMJMSInvQSource
WhcJMSSer
ver
TRMJMSPackQSource
Queue
eis/wls/TRMPackJMSQ
TRMJMSPackQSource
WhcJMSSer
ver
TRMJMSPOQSource
Queue
eis/wls/TRMPOJMSQ
TRMJMSPOQSource
WhcJMSSer
ver
TRMJMSShipQSource
Queue
eis/wls/TRMShipJMSQ
TRMJMSShipQSource
WhcJMSSer
ver
TRMJMSWorkOrderQ
Source
Queue
eis/wls/TRMWorkOrderJMS
Q
TRMJMSWorkOrderQ
Source
WhcJMSSer
ver
TRMOnHandJMSQ
Queue
eis/wls/TRMOnHandJMSQ
TRMOnHandJMSQ
WhcJMSSer
ver
TROJMSInvQSource
Queue
eis/wls/TROInvJMSQ
TROJMSInvQSource
WhcJMSSer
ver
TROJMSPOQSource
Queue
eis/wls/TROPOJMSQ
TROJMSPOQSource
WhcJMSSer
ver
TROOnHandJMSQ
Queue
eis/wls/TROOnHandJMSQ
TROOnHandJMSQ
WhcJMSSer
ver
WorkOrderCAPSConn
Factory
Connect
eis/wls/WorkOrderCAPSCo
ion
nnFactory
Factory
WorkOrderCAPSConn WhcJMSSer
Factory
ver
WorkOrderITSConnFa
ctory
Connect
eis/wls/WorkOrderITSConn
ion
Factory
Factory
WorkOrderITSConnFa WhcJMSSer
ctory
ver
WorkOrderTRMConnF
actory
Connect
eis/wls/WorkOrderTRMCon
ion
nFactory
Factory
WorkOrderTRMConnF WhcJMSSer
actory
ver
For outbound operations
WhcJMSModule
eis/wls/whcQ
JMS module name:

JNDI for JMS adapter:
Name
Type
ASNConnFactory
JNDI Name
Subdeployment
Targets
Connect
ion
eis/wls/ASNConnFactory
Factory
ASNConnFactory
WhcJMSSer
ver
POConnFactory
Connect
ion
eis/wls/POConnFactory
Factory
POConnFactory
WhcJMSSer
ver
ShippingConnFactory
Connect
eis/wls/WhcShippingConnF
WhcJMSSer
ion
ShippingConnFactory
actory
ver
Factory
WhcConnFactory
Connect
ion
eis/wls/WhcConnFactory
Factory
WhcConnFactory
WhcJMSSer
ver
WhcJMSASNQSource
Queue
eis/wls/WhcASNJMSQ
WhcJMSASNQSource
WhcJMSSer
ver
WhcJMSPOQSource
Queue
eis/wls/WhcPOJMSQ
WhcJMSPOQSource
WhcJMSSer
ver

7
2.2
WhcJMSSer
ver
WhcJMSQSource
Queue
eis/wls/WhcJMSQ
WhcJMSQSource
WhcJMSShippingQSo
urce
Queue
eis/wls/WhcShippingJMSQ
WhcJMSShippingQSo WhcJMSSer
urce
ver
WhcJMSWorkOrderQ
Source
Queue
eis/wls/WhcWorkOrderJMS
Q
WhcJMSWorkOrderQ
Source
WorkOrderConnFacto
ry
Connect
eis/wls/WhcWorkOrderCon
ion
nFactory
Factory
WhcJMSSer
ver
WorkOrderConnFacto WhcJMSSer
ry
ver
DB Adapter Configuration in Weblogic Console
The following JNDI should be created for the DB Adapters in the target
environment through weblogic console.
3PL Database: eis/DB/IrWhc3PL
Mercury Database: jdbc/CCT_MERCURY_8i_DB
E-Biz Database: eis/DB/IrWhcEbizDB
2.3
FTP Adapter Configuration in Weblogic Console

The following JNDI should be created for the FTP Adapters in the target environment through
weblogic console.
CAPS Server: eis/Ftp/ES_CAPSMFGPRO
2.4 Deployment should be completed for the common

services such as the worklist, Email Services.

8
3 AIA-MDS Repository update for Custom

EBOs
3.1
Setting up the AIA_HOME environment
In this step, AIA_HOME will be set up to execute MDS update ant scripts.
i.
Log into SOA middleware application tier back end with user credentials having
R/W/X permission in AIA_HOME.
ii.
Move to $AIA_HOME/aia_instances/<aia instance>/bin .
iii.
Set up the environment variables by running he following script - . aiaenv.sh
3.2
Migrate the Custom EBOs to AIA File system repository
In this step the custom EBOs (attached below in the zip file) will be migrated to the AIA file system
repository. Below are the paths where the corresponding EBOs will be migrated:-
1.CustomCommonComponents
$AIA_HOME/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Core/Custom/Commo
n/V2
2.CustomItem
$AIA_HOME/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Core/Custom/Commo
nEBO/V1
3.CustomShipmentRequestEBO
$AIA_HOME/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Core/Custom/EBO/S
hipmentRequest/V1
4.CustomPurchaseOrderEBO
$AIA_HOME/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Core/Custom/EBO/P
urchaseOrder/V1
5.CustomWorkOrderEBO
$AIA_HOME/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Core/Custom/EBO/W
orkOrder/V1
6.CustomAdvanceShipmentNoticeEBO
$AIA_HOME/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Core/Custom/EBO/A
dvanceShipmentNotice/V1
7.CustomInventoryTransactionEBO
$AIA_HOME/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Core/Custom/EBO/In
ventoryTransaction/V1
9
8.CustomItemBalanceEBO
$AIA_HOME/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Core/Custom/EBO/It
emBalance/V1
9.CustomShipmentReceiptEBO
$AIA_HOME/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Core/Custom/EBO/S
hipmentReceipt/V1
EBO_TO_UPLOAD.zi
p
Upload the UpdateMetaDataDP.xml (attached in the zip file, in

GENERIC_UPDATEDB_SCRIPT folder) in the following path:$AIA_HOME/config/
3.3
Update the Custom EBOs to AIA MDS
Step 1: Move to the path mentioned below to execute the ant script:$AIA_HOME/Infrastructure/Install/scripts
Step 2: Execute the script mentioned below:ant -f $AIA_HOME/Infrastructure/Install/AID/AIAInstallDriver.xml
-DDeploymentPlan=$AIA_HOME/config/UpdateMetaDataDP.xml
-DPropertiesFile=$AIA_HOME/aia_instances/<aia
instance>/config/AIAInstallProperties.xml
N.B. Please modify the directory name <aia instance> with the original aia instance
name. E.g. <aia instance> = aiauat

10
4 Configuration Plan
4.1
Generating the configuration plan
In this step generate the configuration plan for the required environment e.g. Test environment. Please
refer the below screenshots.
Screenshot -1
Screenshot -2
Click on OK. The required configuration plan is generated in the < PROJECT-HOME
> directory where PROJECT-HOME is your required project folder.
11
4.2
Editing the generated configuration plan
The required configuration plan is generated in the previous step needs to be edited for the required
target environment.
For example, CreateWorkOrderCapsMfgProReqABCSImpl_TEST_cfgplan.xml.
When this plan is generated from the dev environment it contains the url and the
properties related to the dev environment. But for migration of this composite to
the next level environment, we need to edit this plan as below.
Step 1: Editing the import section of the configuration plan.
<import>
<searchReplace>
<search>Source-environment URL</search>
<replace>Target-environment URL</replace>
</searchReplace>
<searchReplace>
<search>Source-environment Port No </search>
<replace>Target-environment Port No </replace>
</searchReplace>
</import>
12
Where
Source-environment URL= URL of the source environment (e.g. Dev)
Target-environment URL= URL of the Target environment (e.g. Test)
Source-environment Port No= Port no of the source environment (e.g. Dev)
Target-environment Port No= Port no of the source environment (e.g. Test)
Please refer the below screenshot for more details.
What this step does?

It replaces the host and port name in the import sections of composite.xml file.
Please see the below screenshot for your reference.

13
Step 2: Editing the Property section below the import section.

This step is needed if the composite.xml contains the properties for the .jca file of
the file or ftp adapter. In the replace section initially it contains the property
values of the source environment. This needs to be changed to point to the target
environment directory path. Please refer the below screenshot.

14
It replaces the input, output and archive file path sections of composite.xml file.
Please see the below screenshot for your reference.
Step 3: Editing the Reference section below the Service section.

In this step we will edit the location attribute of the binding section inside the
reference section. Initially it contains the url of the source environment. This
needs to be changed to point to the target environment url. Please refer the below
screenshot.

15
It replaces the url in the reference-binding sections of composite.xml file. Please

see the below screenshot for your reference.
Step 4: Editing the wsdlAndSchema section below the reference section.

< wsdlAndSchema >
<searchReplace>
<search>Source-environment URL</search>
<replace>Target-environment URL</replace>
</searchReplace>
<searchReplace>
<search>Source-environment Port No </search>
<replace>Target-environment Port No </replace>
</searchReplace>
</ wsdlAndSchema >
Where
Source-environment URL= URL of the source environment (e.g. Dev)
Target-environment URL= URL of the Target environment (e.g. Test)
Source-environment Port No= Port no of the source environment (e.g. Dev)
Target-environment Port No= Port no of the source environment (e.g. Test)
16
Please refer the below screenshot for more details.

It replaces the host and port name for the imported wsdls in the project.

17
5 SOA Composite Migration

5.1
Inbound Composite List
Interface No: INT181/ INT185

Name: Pick and Ship Confirmation/Carrier Selection and Rate details
Composite Name: OTMPackShipConfirmRoutingService
Composite Type: Mediator
Configuration Plan: OTMPackShipConfirmRoutingService_<ENV>_cfgplan.xml
Partition Name: ES_ORA_OM
Composite Name: Oracle3PLPackConfirmReqABCSImpl
Composite Type: Requester
Configuration Plan: Oracle3PLPackConfirmReqABCSImpl_<ENV>_cfgplan.xml
Composite Name: Oracle3PLShipConfirmReqABCSImpl
Configuration Plan: Oracle3PLShipConfirmReqABCSImpl_<ENV>_cfgplan.xml
Composite Name: ShipConfirmJmsPushABCSImpl
Composite Type: JMSPush
Configuration Plan: ShipConfirmJmsPushABCSImpl_<ENV>_cfgplan.xml
Composite Name: EbizShipConfirmJmsProvABCSImpl
Composite Type: JMSProvider
Configuration Plan: EbizShipConfirmJmsProvABCSImpl_<ENV>_cfgplan.xml
Composite Name: OTMShipConfirmJmsProvABCSImpl
Configuration Plan: OTMShipConfirmJmsProvABCSImpl_<ENV>_cfgplan.xml
Composite Name: EbizShipConfirmProvABCSImpl
Composite Type: Provider
Configuration Plan: EbizShipConfirmProvABCSImpl_<ENV>_cfgplan.xml
Composite Name: OTMShipConfirmProvABCSImpl
Configuration Plan: OTMShipConfirmProvABCSImpl_<ENV>_cfgplan.xml
Composite Name: ShipConfirmJmsProvABCSImpl
Configuration Plan: ShipConfirmJmsProvABCSImpl_<ENV>_cfgplan.xml
18
Composite Name: ShipConfirmProvABCSImpl

Configuration Plan: ShipConfirmProvABCSImpl_<ENV>_cfgplan.xml
Composite Name: OTMPackConfirmJmsPushABCSImpl
Configuration Plan: OTMPackConfirmJmsPushABCSImpl_<ENV>_cfgplan.xml
Composite Name: OTMPackConfirmJmsProvABCSImpl
Configuration Plan: OTMPackConfirmJmsProvABCSImpl_<ENV>_cfgplan.xml
Composite Name: OTMPackConfirmProvABCSImpl
Configuration Plan: OTMPackConfirmProvABCSImpl_<ENV>_cfgplan.xml
Composite Name: OTMPackConfirmProvResponseABCSImpl
Configuration Plan: OTMPackConfirmProvResponseABCSImpl_<ENV>_cfgplan.xml
Composite Name: OTMPackConfirmOtmResponseJmsProvABCSImpl
Configuration Plan:
OTMPackConfirmOtmResponseJmsProvABCSImpl_<ENV>_cfgplan.xml
Composite Name: OTMResponsePackConfirmProvABCSImpl
Configuration Plan: OTMResponsePackConfirmProvABCSImpl_<ENV>_cfgplan.xml
Interface No: INT183
Name: PO and RMA Interface Data coming from 3PL
Composite Name: Oracle3PLPOASNRMAReqABCSImpl
Configuration Plan: Oracle3PLPOASNRMAReqABCSImpl_<ENV>_cfgplan.xml
Partition Name: ES_ORA_PO
Composite Name: CreatePOASNRMAJmsPushInboundABCSImpl

Configuration Plan: CreatePOASNRMAJmsPushInboundABCSImpl_<ENV>_cfgplan.xml
Composite Name: CreatePOASNRMAJmsProvABCSImpl
19

Configuration Plan: CreatePOASNRMAJmsProvABCSImpl_<ENV>_cfgplan.xml
Composite Name: CreatePOASNRMAProvABCSImpl
Configuration Plan: CreatePOASNRMAProvABCSImpl_<ENV>_cfgplan.xml
Name: Work Order Completion
Composite Name: Oracle3PLWorkOrderReqABCSImpl
Configuration Plan: Oracle3PLWorkOrderReqABCSImpl_<ENV>_cfgplan.xml
Partition Name: ES_ORA_WIP
Composite Name: Oracle3PLWorkOrderJmsPushABCSImpl
Configuration Plan: Oracle3PLWorkOrderJmsPushABCSImpl_<ENV>_cfgplan.xml
Composite Name: Oracle3PLWorkOrderJmsProvABCSImpl
Configuration Plan: Oracle3PLWorkOrderJmsProvABCSImpl_<ENV>_cfgplan.xml
Composite Name: Oracle3PLWorkOrderProvABCSImpl
Configuration Plan: Oracle3PLWorkOrderProvABCSImpl_<ENV>_cfgplan.xml
Name: On Hand Balance Interface Coming from 3PL
Composite Name: Oracle3PLOnHandBalTransReqABCSImpl
Configuration Plan: Oracle3PLOnHandBalTransReqABCSImpl_<ENV>_cfgplan.xml
Partition Name: ES_ORA_INV
Composite Name: Oracle3PLOnHandBalTransJMSPushABCSImpl
Configuration Plan: Oracle3PLOnHandBalTransJMSPushABCSImpl_<ENV>_cfgplan.xml
Composite Name: Oracle3PLOnHandBalTransProvABCSImpl
Composite Type: JMSProvider and Provider
Configuration Plan: Oracle3PLOnHandBalTransProvABCSImpl_<ENV>_cfgplan.xml
Name: Inventory Transactions
Composite Name: Oracle3PLInvTxactionReqABCSImpl
20

Configuration Plan: Oracle3PLInvTxactionReqABCSImpl_<ENV>_cfgplan.xml
Composite Name: CreateInvTxactionJmsPushABCSImpl
Configuration Plan: CreateInvTxactionJmsPushABCSImpl_<ENV>_cfgplan.xml
Composite Name: CreateInvTxactionJmsProvABCSImpl
Configuration Plan: CreateInvTxactionJmsProvABCSImpl_<ENV>_cfgplan.xml
Composite Name: CreateInvTxactionProvABCSImpl
Configuration Plan: CreateInvTxactionProvABCSImpl_<ENV>_cfgplan.xml
Note: In the configuration plan name <ENV> indicates the target environment.
5.2
Outbound Composite List

Name: Item Synchronization
Composite Name: CreateItemEbizReqABCSImpl
Configuration Plan: CreateItemEbizReqABCSImpl_<ENV>_cfgplan.xml
Composite Name: CreateItemCapMfgProReqABCSImpl
Configuration Plan: CreateItemCapMfgProReqABCSImpl_<ENV>_cfgplan.xml
Composite Name: CreateItemMercuryReqABCSImpl
Configuration Plan: CreateItemMercuryReqABCSImpl_<ENV>_cfgplan.xml
Composite Name: CreateItemJmsPushABCSImpl
Configuration Plan: CreateItemJmsPushABCSImpl_<ENV>_cfgplan.xml
Composite Name: CreateItemEbizProvABCSImpl
Composite Type: JMSProvider and Provider
Configuration Plan: CreateItemEbizProvABCSImpl_<ENV>_cfgplan.xml
Name: Picking and Shipping Instruction
21
Composite Name: CreateShippingReqABCSImpl

Configuration Plan: CreateShippingReqABCSImpl_<ENV>_cfgplan.xml
Composite Name: CreateShippingMercuryReqABCSImpl
Configuration Plan: CreateShippingMercuryReqABCSImpl_<ENV>_cfgplan.xml
Composite Name: CreateShippingCAPSMfgProReqABCSImpl
Configuration Plan: CreateShippingCAPSMfgProReqABCSImpl_<ENV>_cfgplan.xml
Composite Name: CreateShippingJmsProvABCSImpl
Composite Type: JMSPush and JMSProvider
Configuration Plan: CreateShippingJmsProvABCSImpl_<ENV>_cfgplan.xml
Composite Name: CreateShipmentReqEbizProvABCSImpl
Configuration Plan: CreateShipmentReqEbizProvABCSImpl_<ENV>_cfgplan.xml
Name: PO and RMA Interface Data going to 3PL
Composite Name: CreatePOEbizReqABCSImpl
Configuration Plan: CreatePOEbizReqABCSImpl_<ENV>_cfgplan.xml
Composite Name: CreateRMAEbizReqABCSImpl
Configuration Plan: CreateRMAEbizReqABCSImpl_<ENV>_cfgplan.xml
Composite Name: CreatePOCAPSMfgProReqABCSImpl
Configuration Plan: CreatePOCAPSMfgProReqABCSImpl_<ENV>_cfgplan.xml
Composite Name: CreateRMACAPSMfgProReqABCSImpl
Configuration Plan: CreateRMACAPSMfgProReqABCSImpl_<ENV>_cfgplan.xml
Composite Name: CreatePORMAMercuryReqABCSImpl
Configuration Plan: CreatePORMAMercuryReqABCSImpl_<ENV>_cfgplan.xml
Composite Name: CreatePORMAJmsProvABCSImpl
22

Configuration Plan: CreatePORMAJmsProvABCSImpl_<ENV>_cfgplan.xml
Composite Name: CreatePORMAEbizProvABCSImpl
Configuration Plan: CreatePORMAEbizProvABCSImpl_<ENV>_cfgplan.xml
Name: Work Order Kitting
Composite Name: CreateWorkOrderReqABCSImpl
Configuration Plan: CreateWorkOrderReqABCSImpl _<ENV>_cfgplan.xml
Composite Name: CreateWorkOrderCapsMfgProReqABCSImpl
Configuration Plan: CreateWorkOrderCapsMfgProReqABCSImpl_<ENV>_cfgplan.xml
Composite Name: CreateWorkOrderMercuryABCSImpl
Configuration Plan: CreateWorkOrderMercuryABCSImpl_<ENV>_cfgplan.xml
Composite Name: CreateWorkOrderJmsProvABCSImpl
Configuration Plan: CreateWorkOrderJmsProvABCSImpl_<ENV>_cfgplan.xml
Composite Name: CreateWorkOrderEbizProvABCSImp
Configuration Plan: CreateWorkOrderEbizProvABCSImp_<ENV>_cfgplan.xml
5.3
Common FTP Composite List
Interface No: Common Service

Name: Common CAPS FTP Service
Composite Name: CapsMfgProFTPService
Composite Type: Requester and Provider
Configuration Plan: CapsMfgProFTPService_<ENV>_cfgplan.xml
Partition Name: ES_UTILITIES

23
5.4
Order of Deployments
Each of the above composite of the respective interface should be deployed in the following
order.
Step 1: The provider
Step 2: The JMSProvider
Step 3: The JMSPush
Step 4: The Requester
For example, please refer the below section.
5.5
Deployment of the composites through Ant

Step -1
Run the below commands to set the environment variables
export JAVA_HOME=<Java installed directory>
export ANT_HOME=<Ant installed directory>
export PATH=$PATH:< Ant installed directory>/bin
Step -2
Go to the Ant file directory. Run the following command to deploy the composite.
ant -f ant-sca-deploy.xml
-DserverURL=<HostName>:<Port No>
-DsarLocation=<Location of the SAR (.jar) file>
-Doverwrite=true
-Duser=<UserName of the server>
-Dpassword=<Password of the server>
-DforceDefault=true
-Dconfigplan=<Location of the configuration plan file>
-Dpartition=<Name of the partition to which composite is deployed>
For example:
ant -f ant-sca-deploy.xml
-DserverURL= http://10.160.4.143:17002
-DsarLocation=
/Ant_Deployment/CreateWorkOrderCapsMfgProReqABCSImpl/deploy/sca_CreateWorkOrde
rCapsMfgProReqABCSImpl_rev1.0.jar
-Doverwrite=true
-Duser=weblogic
-Dpassword=welcome1
-DforceDefault=true
-Dconfigplan=
/Ant_Deployment/CreateWorkOrderCapsMfgProReqABCSImpl/CreateWorkOrderCapsMfgPr
oReqABCSImpl_TEST_cfgplan.xml
-Dpartition= ES_ORA_WIP
Step -3

24
Validate the response code (200 success / 500 error).

If 200, check the SOA environment to checkout process
If 500, Deployment is not successful. Please correct the issue.

25
6 Configurable variables of the composite

6.1
Inbound Operations
Interface No: INT181/INT185

Name: Pick and Ship Confirmation/Carrier Selection and Rate details
Composite Name
FileAdapterServiceName
Operation
Logical Output Directory
OutputDirectory
Composite Name
Operation
PackConfirmPath
ShipConfirmProvABCSImpl
CallCAPSFileWriteService
Write
Configurable properties
Naming Pattern
INT181SHIPCNF_%yyMMddHHmmssSS%.txt
OTMResponsePackConfirmProvABCSImpl
CallPackConfirmFileAdapter
Write
Naming Pattern
INT181_%ddMMyyyyHHmmss%.txt

Name: PO and RMA Interface Data coming from 3PL
Composite Name
Operation
INT183POInDir
CreatePOASNRMAProvABCSImpl
CallCAPSFileService
Write
Naming Pattern
INT183POASNRMACAPS_%SEQ%.txt

Name: Work Order Completion
Composite Name
Operation
OutputDirectory
Oracle3PLWorkOrderProvABCSImpl
CallWriteFileService
Write
Naming Pattern
INT186%yyMMddHHmmssSS%.txt

Name: On Hand Balance Interface Coming from 3PL
Oracle3PLOnHandBalTransProvABCSI
Composite Name
26
mpl
CAPSMfgproOnHandBalFileService
Write
Naming Pattern
CAPSMfgproOnHandBalFilePath
INT_187_%ddMMyyyyHHmmss%.txt
Operation

Name: Inventory Transactions
Composite Name
Operation
InvTxactionPath
CreateInvTxactionProvABCSImpl
CallInvTxactionFileAdater
Write
Naming Pattern
INT188_%ddMMyyyyHHmmss%.txt
Where value of Logical Output Directory = /u02/tmp/INBOUND/INBOUND_<ENV>_CAPSFILES

for all the inbound interfaces.
<ENV> = Target environment name
6.2
Outbound Operations

Name: Item Synchronization
CreateItemCapMfgProReqABC
SImpl
CreateItemReqABCSImpl
Read
Composite Name
Operation
Logical Intput
Directory
InputDirectory
Logical
Archive
Directory
ArchiveDirecto
ry
Naming Pattern
Delete File
INT179.*\.txt
true
Polling
Freq
(Sec)
10
Min File
Age
(Sec)
6

Name: Picking and Shipping Instruction
CreateShippingCAPSMfgProRe
qABCSImpl
CallShippingFileService
Read
Composite Name
Operation
Logical Intput
Directory
ShipmentRequestIn
putDir
Logical
Archive
Directory
ShipmentReque
stArchiveFileD
Naming Pattern
Delete File
INT180.*\.txt
true

27
Polling
Freq
(Sec)
10
Min File
Age
(Sec)
6
ir
Name: PO and RMA Interface Data going to 3PL
CreatePOCAPSMfgProReqABC
SImpl
CreatePO
Read
Composite Name
Operation
Logical Intput
Directory
INT182POInDir
Logical
Archive
Directory
INT182POArc
Dir
Naming Pattern
Delete File
INT182_PO.*\.txt
Operation
INT182RMAInDir
Min File
Age
(Sec)
0
CreateRMACAPSMfgProReqAB
CSImpl
RcvRMAFile
Read
Composite Name
Logical Intput
Directory
true
Polling
Freq
(Sec)
5
Logical
Archive
Directory
INT182RMAA
rcDir
Naming Pattern
Delete File
INT182_RMA.*\.
txt
true
Polling
Freq
(Sec)
5
Min File
Age
(Sec)
0

Name: Work Order Kitting
CreateWorkOrderCapsMfgProR
eqABCSImpl
CapsMfgProFileReadService
Read
Composite Name
Operation
Logical Intput
Directory
InputDirectory
Logical
Archive
Directory
ArchiveDirecto
ry
Naming Pattern
Delete File
INT184.*\.txt
true
Polling
Freq
(Sec)
10
Min File
Age
(Sec)
5
Where
Value of Logical Input Directory = /u02/tmp/OUTBOUND/OUTBOUND _<ENV>_CAPSFILES for
all the outbound interfaces.
Value of Logical Archive Directory = /u02/tmp/OUTBOUND/OUTBOUND _<ENV>_ARCHIVE for
all the outbound interfaces.
6.3
Common Operations
Interface No: Common Service

28
Name: Common CAPS FTP Service

CapsMfgProFTPService
CapsMfgProInFileService
Read
Composite Name
Operation
Logical Intput
Directory
InputDirectory
Logical
Archive
Directory
ArchiveD
irectory
Logical
Naming
Delete File
Outtput
Pattern
Directory
None
INT.*\.txt
true
None
Logical
Archive
Directory
None
Logical
Naming
Delete File
Outtput
Pattern
Directory
OutputDir INT_
None
ectory
%yyMMddH
Hmmss%.txt
InputDirectory
Logical
Archive
Directory
ArchiveD
irectory
Logical
Naming
Delete File
Outtput
Pattern
Directory
None
INT.*\.txt
true
None
None
Min File
Age
(Sec)
None
Polling
Freq (Sec)
10
Min File
Age
(Sec)
0
CapsMfgProOutFileService
Write
Composite Name
Operation
Logical Intput
Directory
Polling
Freq (Sec)
CapsMfgProOutFTPService
Get
Composite Name
Operation
Logical Intput
Directory
10
Min File
Age
(Sec)
6
CapsMfgProInFTPService
Put
Composite Name
Operation
Logical Intput
Directory
Polling
Freq (Sec)
Logical
Archive
Directory
None
Logical
Naming
Delete File
Outtput
Pattern
Directory
OutputDir INT_
None
ectory
%yyyyMMd
d%
Where
Value of Logical Input Directory in case of Get= Path in the CAPS Server.
Value of Logical Archive Directory in case of Get= Path in the CAPS Server
Value of Logical Input Directory in case of Read =
/u02/tmp/INBOUND/INBOUND_<ENV>_CAPSFILES.
Value of Logical Archive Directory in case of Read =
29
Polling
Freq (Sec)
None
Min File
Age
(Sec)
None
/u02/tmp/INBOUND/INBOUND_<ENV>_ARCHIVE
Value of Logical Output Directory in case of Write = /u02/tmp/OUTBOUND/OUTBOUND
_<ENV>_CAPSFILES.
Value of Logical Output Directory in case of Put = Path in the CAPS Server
6.4
How to change the above from EM Console
Login to the EM Console of the required environment. Click on the + sign of the desired partition.
Inside that select your required composite by clicking on it. Then go towards the bottom of the page
and find the Services and References in the right hand side. There check your required File Service in
the Name column and click on it. Please refer the below screenshot.
Now click on Properties

30
Change the desired values and click on Apply Yes Ok
*Note: The values changed here and saved are reset to their default values on server restart. So
after server restart again the required changes if any should be done.
31
6.5
Variables and their default values

Please refer the below excel file for the MBean browser variables and their default values.
IR_inbound_and_Ou
tbound_Variable_List.xlsx

32
7 Worklist DVM Set up in SOA Composer

7.1
IR_WORKLIST_SUPPORT_GROUP S DVM Entry

Following DVM entries needs to be created for the IR_WORKLIST_SUPPORT_GROUPS
dvm. Please follow the below steps to create the required DVM entries.
INTERFACE
INT187Tech
INT187CAPSTech
INT187TRMTech
INT179
INT179CapsTech
INT179Tech
INT179TrmTech
INT179TroTech
INT187TROTech
INT179Tro
INT187TRO
WORKLIST_GROUP
EbizITSTechnicalSupportGr
p
MfgproCapsTechnicalSuppo
rtGrp
TRMTechnicalSupportGrp
EbizITSInventorySupportGr
p
MfgproCapsTechnicalSuppo
rtGrp
EbizITSTechnicalSupportGr
p
TRMTechnicalSupportGrp
TROTechnicalSupportGrp
TROTechnicalSupportGrp
TROInventorySupportGrp
TROInventorySupportGrp
Step 1
Login to the SOA composer in PROD with administration credentials in the below URL.
http://fmwprd.ingerrand.com:48001/soa/composer/faces/login.jspx

33
Step 2
Click on OPEN. Then Open DVM.
Step 3
Select the IR_WORKLIST_SUPPORT_GROUPS.dvm from the Pop up and click on OPEN.

34
Step 4
In the next page click on edit to edit the dvm entry list.
Step 5
In the next page click + to add the required dvm entry to the list.

35
Step 6
In the pop up please give the requires interface name and the support group and click on OK. Then add
the other required dvms in the same way as stated.
Step 7
Then click on Save.

36
Step 8
Then click on Commit.

37
8 Post Deployment changes to be done

manually
None

38

MD200 WHC SOA Composite Migration V1.2

Uploaded by

Document Information

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

MD200 WHC SOA Composite Migration V1.2

Uploaded by

Copyright:

Available Formats

Enterprise Services ESA

MD120: Application Interfaces

Enterprise Services ESA WHC SOA Composites Migration Document

Work stream: WHC 17 Nov 201028/01/03 10:10

Last Updated: 17 Nov 201011

SOA Deployment - User Guide

Enterprise Services ESA

SOA Deployment - User Guide

Related Document Names

Company Confidential For internal use only

Enterprise Services ESA

SOA Deployment - User Guide

Company Confidential For internal use only

Enterprise Services ESA

Scope of this document

The pre-requisites needed for the migration of the inbound and

SOA Deployment - User Guide

Enterprise Services ESA

2 Pre-requisites for the SOA migration

JMS Configuration in Weblogic Console

Following needs to be created in the target environment.

JMS module name:

eis/wls/CAPSWorkOrderJMS CAPSJMSWorkOrderQ WhcJMSSer

SOA Deployment - User Guide

Enterprise Services ESA

SOA Deployment - User Guide

Enterprise Services ESA

For outbound operations

JMS module name:

SOA Deployment - User Guide

Enterprise Services ESA

DB Adapter Configuration in Weblogic Console

FTP Adapter Configuration in Weblogic Console

2.4 Deployment should be completed for the common

SOA Deployment - User Guide

Enterprise Services ESA

3 AIA-MDS Repository update for Custom

Setting up the AIA_HOME environment

Migrate the Custom EBOs to AIA File system repository

Enterprise Services ESA

Upload the UpdateMetaDataDP.xml (attached in the zip file, in

Update the Custom EBOs to AIA MDS

SOA Deployment - User Guide

Enterprise Services ESA

Generating the configuration plan

Enterprise Services ESA

Editing the generated configuration plan

Enterprise Services ESA

What this step does?

SOA Deployment - User Guide

Enterprise Services ESA

Step 2: Editing the Property section below the import section.

What this step does?

Enterprise Services ESA

Step 3: Editing the Reference section below the Service section.

What this step does?

Enterprise Services ESA

It replaces the url in the reference-binding sections of composite.xml file. Please

Step 4: Editing the wsdlAndSchema section below the reference section.

Enterprise Services ESA

Please refer the below screenshot for more details.

What this step does?

SOA Deployment - User Guide

Enterprise Services ESA