webMethods Software Deployment Document

INS_CISCO LSS (Large Scale Services) for Penang

[201539]

41740-03 (7869.3)

Document Change Control Log

The following information is used to control and track modifications made to this document:
Versio
n
01

Date
03.06.2013

Description of
change
Build deployment:
1.1.33-p01,
1.1.36-p01,
1.1.37-p03,
1.1.43-p01

Developer, SM & DM
Name
Sathish Kumar ,
Shivakumar Gangaiyah,
Joo Lee Khoo

Remarks

Components to be
deployed are
highlighted in
YELLOW
Components to be
deployed are
highlighted in
YELLOW

02

2013-0620

1.1.49-p01 for 7724.1

and config change for
3C7

Aishwarya, Sathish,
Shivakumar, Rananjoy,
Joo Lee

03

2013-0627

Patch deployment :
1.1.53-p01 and
configuration
changes

Aishwarya, Sathish,
Shivakumar, Rananjoy,
Joo Lee

Components to be
deployed are
highlighted in
YELLOW

Table of Contents
webMethods Software Deployment Document..................................................................1
INS_CISCO LSS (Large Scale Services) for Penang [201539]..........................................1
41740-03 (7869.3).................................................................................................................. 1
Table of Contents.................................................................................................................1
1. Introduction....................................................................................................................... 3
2. Project Summary............................................................................................................... 4
3. Deployment Instructions..................................................................................................5
4. Additional Instructions...................................................................................................13
5. Appendix A...................................................................................................................... 14

Document Owner: GSSSATHK

1/14

Modification Date: 03.06.2013

6. Appendix B...................................................................................................................... 14
7. Appendix C...................................................................................................................... 14

Document Owner: GSSSATHK

2/14

Modification Date: 03.06.2013

1. Introduction
The following document is used to guide the OPS Team to handle a specific software
deployment, where it will contain all necessary detailed instructions to ensure a smooth
software deployment.
For more detailed instructions on how to build and/or to deploy any software components in
general, please refer to the common build/deployment process manual provided on our SVN
server.
SVN Build/Deployment Documentation Location:
https://subversion.flextronics.com/svn/EIS/webMethods%207.x/Builds/Doc/BuildDeployment.doc
NOTE 1: Only add information as of chapter 2.
NOTE 2: Please remove any empty sections after applying all details This will help to
retrieve just the important instructions, hence it will avoid browsing thru empty sections and
making it easier while preparing for any deployment.

Document Owner: GSSSATHK

3/14

Modification Date: 03.06.2013

2. Project Summary
2.1.

Build Image

To specify the build image use below table by using the specific row, specifying the
package/component and modifying the version number accordingly.
Delete any unused rows and create new ones if required.

Package/Component
Flex_CISCO_LSS.maps.outbound.purchaseOrderConfirmation.Baa
n:mapBaanHoldFAToPip3A8vV1114

Version

Target

1.1.33-p01

B2B

Package/Component

Version

Target

Flex_CISCO_LSS.maps.outbound.returnProductConfirmation.BAI:
mapBAIRPConfirmationToPip3C9V110000

1.1.36-p01

B2B

Package/Component

Version

Target

1.1.37-p03

B2B

Flex_CISCO_LSS.maps.outbound.purchaseOrderConfirmation.Baa
n:mapBaanPOConfirmationToPip3A4vV1114
Flex_CISCO_LSS.maps.outbound.purchaseOrderConfirmation.Baa
n:mapBaanPORecommitToPip3A4vV1114
Flex_CISCO_LSS.maps.inbound.returnProductRequest.BAAN:map
Pip3C8vV1100ToBAIOrders

Flex_CISCO_LSS.maps.inbound.purchaseOrderCancellationReque
st.Baan:mapPip3A9vV1101ToBaanPOCancellationRequest
Flex_CISCO_LSS.maps.inbound.purchaseOrderRequest.Baan:map
Pip3A4vV1114ToBaanPurchaseOrderRequest
Flex_CISCO_LSS.maps.inbound.holdReleaseNotification.Baan:ma
pHoldReleaseNotificationToBaanPOChange
Flex_CISCO_LSS.maps.outbound.advanceShipmentNotification.Ba
an:mapBaanASNToPip3B2v1102
Flex_CISCO_LSS.maps.inbound.selfBillingInvoiceNotification.BAA
N:mapPIP3C7v1104ToBaanSelfInvoice
Flex_CISCO_LSS.maps.inbound.FunctionalAcknowledgment:map3
Document Owner: GSSSATHK

4/14

Modification Date: 03.06.2013

B2FAToEmailNotification
Flex_CISCO_LSS.maps.outbound.purchaseOrderConfirmation.Baa
n:mapBaanHoldFAToPip3A8vV1114
Flex_CISCO_LSS.maps.outbound.functionalAcknowledgment.BAA
N:mapNegativeFAToCISCOPip3A4vV1114
Flex_CISCO_LSS.maps.inbound.packoutFA:mapCiscoPackoutFAT
oFF
Flex_CISCO_LSS.maps.outbound.packOut:mapFFPackoutToCisco

Flex_CISCO_LSS.maps.outbound.requestEngineeringChange.Agile
:mapAgileLECOToPip2C2vR1101

1.1.49-p01

B2B

Flex_CISCO_LSS.maps.outbound.packOut:mapFFPackoutToCisco

1.1.53-p01

B2B

Package/Component

Version

Target

Flex_CISCO_LSS.maps.inbound.distributeProductCatalogInformati
on:mapPip2A1vV1100ToAuxCisItm_Ascii

1.1.43-p01

B2B

Version information: 1.0-f01 = Full Build | 1.0.1-p01= Partial/Patch Build

2.2.

Additional Information

2.3.

Migration Order

3. Deployment Instructions
Note: Instead of providing any manual deployment instructions, please provide builds
according our build/deployment process instead, wherever possible.
Highlight the points in Yellow color which needs to be deployed, if it is not a full deployment
to clearly identify any changes.

Document Owner: GSSSATHK

5/14

Modification Date: 03.06.2013

Build Name

F_CISCO_LSS_WMSD2-HKD IS_ExportedBuild_1.1.33-p01

SVN Path

https://subversion.flextronics.com/svn/EIS/webMethods
%207.x/Builds/DEV/Flex_CISCO_LSS/

Build Name

F_CISCO_LSS_WMSD2-HKD IS_ExportedBuild_1.1.36-p01

SVN Path

https://subversion.flextronics.com/svn/EIS/webMethods
%207.x/Builds/DEV/Flex_CISCO_LSS/

Build Name

F_CISCO_LSS_WMSD2-HKD IS_ExportedBuild_1.1.37-p03

SVN Path

https://subversion.flextronics.com/svn/EIS/webMethods
%207.x/Builds/DEV/Flex_CISCO_LSS/

Build Name

F_CISCO_LSS_WMSD2-HKD IS_ExportedBuild_1.1.43-p01

SVN Path

https://subversion.flextronics.com/svn/EIS/webMethods
%207.x/Builds/DEV/Flex_CISCO_LSS/

3.1.

Trading Networks Requirements [DocTypes,PR,TPA and

Others]

Note: Use http://intranet.flextronics.com/it/wmtam/public/Deployment-Templates/Connectivity

%20Documents%20and%20templates for new Profile requests.

Docu
ment
Type
s
Name

Details

Profile Details

Corporation
Name
Document Owner: GSSSATHK

6/14

Modification Date: 03.06.2013

Unit Name
Partner Type
External IDs
2

Corporation
Name
Unit Name
Partner Type
External IDs

TN Document type:
For TN document type (doc_Xml_PIP_3C7SelfBillingInvoice_V_11_04) extract the
below attribute
In the Extract tab, Add
Name: ApplicationMessageType
Query:
/
prefix0:SelfBillingInvoiceNotification[0]/ssdh:DocumentHeader[0]/ssdh:DocumentInformation[
0]/ssdh:DocumentIdentification[0]/ssdh:StandardDocumentIdentification[0]/ssdh:Version[0]

7869.3 (41740-03)
Document Owner: GSSSATHK

7/14

Modification Date: 03.06.2013

For TN document type: (doc_Xml_PackOut_CustomXMLOut_Cisco)

1. Remove PACKOUT from the TN document type Query. (Refer to the
screenshot below)
/
prefix0:AsBuiltAndPackoutNotification[0]/prefix0:PackoutInformation[0]/prefix0:DocumentTyp
e[0]
Value: PACKOUT
2. Remove BD_PartnerOrderNumber and BD_SiteID attribute from Extract tab
(Refer to the screenshot below)

3. Add XREF entry for UNPACK OUT as below:

Table

OutboundPartnerConfig

Source

AGILE

Target

BLANK

Group

Cisco LSS

Input

Output

SenderID

015980580

ReceiverID

153804570

MessageType

UNPACKOUT

PassThrough

false

MapType

straight

ServiceName

Flex_CISCO_LSS.maps.outbound.packOut:mapFFPackoutToCisco

ProcessName

ShippingSchedule_OUT

DeliveryMethod

CUSTOM_ROUTE

Processing Rules
Please delete the below processing rule
Rule Name

processCISCO_LSS MDN Message

Rule Description

Custom Rule for processCISCO_LSS MDN Message

3.2.

Xref Details

Document Owner: GSSSATHK

8/14

Modification Date: 03.06.2013

The Below Xref Already available in PROD. Change only the Output parameters highlighted
as below
Table

InboundPartnerConfig

Source

XML

Target

BLANK

Group
Input

Output

Cisco LSS
SenderID

153804570

ReceiverID

015980580

DocumentType

doc_Xml_PACKOUTFunctionalAcknowledgement_CustomXML_Cisco

PassThrough

False

MapType

Straight

ServiceName

Flex_CISCO_LSS.maps.inbound.packoutFA:mapCiscoPackoutFAToFF

Table

FlexCompanyToDirectory

Source

Any

Target

Infimacs

Group
Input

Cisco LSS
Company

PEN

Directory

/WMI/app/mes/to_app/pickup

The Below Xref Already available in PROD. Change only the Output parameters highlighted
as below
Table

OutboundPartnerConfig

Source

AGILE

Target

BLANK

Group
Input

Output

Cisco LSS
SenderID

015980580

ReceiverID

153804570

MessageType

PACKOUT

PassThrough

False

MapType

Straight

ServiceName

3.3.

Flex_CISCO_LSS.maps.outbound.packOut:mapFFPackoutToCisco

ProcessName

ShippingSchedule_OUT

DeliveryMethod

EDIINT

Property Group

Document Owner: GSSSATHK

9/14

Modification Date: 03.06.2013

Group Name

3.4.

Property Name

Property Value

Database Requirements

SVN DB Location:
https://subversion.flextronics.com/svn/EIS/webMethods%207.x/DB%20Objects/
Script

3.5.

Revisi
on

Schema/User

Comments

Process Models / Optimize for Process Requirements

3.5.1.

Process models

Note: This needs to be deployed to the target environment first before deploying event
maps.
Deployer - DeploymentSet type should be selected as "Process Model"
Model Name

Version

3.5.2.

Project/Folder

Comments

Event maps

Note: The corresponding process model (mentioned above) need to be deployed to the
target environment first before deploying this.
Deployer - DeploymentSet type should be selected as "Optimize"
Process Name

Event Map

Comments

3.6 TPA
Create the Below TPA
Sender
Receiver

CISCO LSS (E2Open)

FLEXTRONICS (Corporate IT)

Document Owner: GSSSATHK

10/14

Modification Date: 03.06.2013

Agreement
ID
fileOptions

MDN-INBOUND-TPA
docType
senderID
receiverID
fileNameForm
at
Content
Template
routingInfo

Any
Any
Any
PKTW-%MimeHeaderFileNameNoExtension%.txt
%MimeHeaderFileName%|%MDNBizdoc/DocTimestamp
% %TimeZoneOffsetHours%:%TimeZoneOffsetMinutes%
type
fileName
action
save
sequence
1
level
entirePayload
mask
^PKTW\-PKTR\-PEN.*\.txt
isLastAction Default
transportInf save
o
Locatio /
n
WMI/app/mes/to_app/pickup
type
action
sequence
level
mask
isLastActio
n

fileName
ignore
2
entirePayload
.*
Default

Please delete the below File Option from EDIINT-INBOUND-TPA

Sender:
CISCO LSS (E2Open)
Receiver:
Flextronics(Corporate IT)
Agreement ID: EDIINT-INBOUND-TPA
Doctype :
SenderID:
ReceiverID:

doc_Xml_PACKOUTFunctionalAcknowledgement_CustomXML_Cisco
153804570
015980580

3.6.

Broker Requirements

3.7.

My webMethods Requirements

Document Owner: GSSSATHK

11/14

Modification Date: 03.06.2013

3.8.

Adapter Config

3.9.

IS Scheduler Jobs / Ports

3.10.

FTP Alias

Note: Use this template to provide all details

3.11.

LOB Jobs / Configurations

3.12.

UNIX / NFS Requirements

3.13.

Optimize for Infrastructure Configurations

3.14.

Miscellaneous Tasks

Document Owner: GSSSATHK

12/14

Modification Date: 03.06.2013

4. Additional Instructions
4.1.

Post Deployment

4.2.

Line of Business (LOB) Application Interface Configuration

4.3.

External Dependencies

4.4.

Additional Notes

Document Owner: GSSSATHK

13/14

Modification Date: 03.06.2013

5. Appendix A
Support Escalation Matrix

6. Appendix B
External References (Functional, Technical Requirements Document, Design &
Development Specifications, Process Support Document etc)

7. Appendix C
External Connectivity Details

Document Owner: GSSSATHK

14/14

Modification Date: 03.06.2013