Tuesday Nov 27, 2012

Customisation / overriding of the Envelop ecs files

There are few usecases where the requirement is to customise the envelop information (Interchange/Group ecs file).
Such scenarios might be required to be used for only few of the customers.
Hence, in addition to the default seeded envelop definitions, it also required to upload the customised definitions.

Here is the steps for achieving the same.
1. Create only the Interchange ecs and save
2. Create only the group ecs and save
3. Use the same in B2B

1. Create only the Interchange ecs and save :
      Open the document editor and select the required version and doctype. During creating new ecs, ensure to select the checkbox for insert envelop.
      Once created, delete the group and transactionset nodes and retain only the Interchange ecs nodes, including both header and trailer. Save this file.

2. Create only the group ecs and save
      After creating the ecs file as mentioned in steps of Interchange creation, delete the Interchange and transactionset nodes and retain only the group ecs nodes, including both header and trailer. Save this file.


3. Use the same in B2B
      These newly created ecs can be used in B2B by 2 ways.
             a. By overriding at the trading partner Level:
             This will be very useful when the configuration is complete and then need to incorporate the customisation. In this case, just select the Trading partner -> document -> select the document which need to be customised.
             Upload the newly created Interchange and group ECS files under the Interchange and group tabs respectively and re-deply the associated agreement.
             The advantage of this approach is
             - Flexibility to add customised envelop definitions to the partners
             - Save the re-work of design time effort.

             b. By adding another document definition in Administration -> document screen:
             This scenario can be used if there is no configuration done at the trading partner level. Create the required document revision and overtide the Interchange and group ECS files under the Interchange and group tabs respectively. Add the document in Trading partner -> document. Create and deploy the agreements

Monday Nov 12, 2012

B2B communication using IBM MQ



Oracle B2B 11g, provides the out-of-the box ability to connect to IBM MQ to exchange the message. This is support is provided via JMS offering of Oracle B2B.


This is an addition to the stack of existing communication capabilities of B2B with trading partners.

There are 2 ways of connecting to IBM MQ using B2B

1. Credential based connectivity
2. .bindings based connectivity

As a pre-requisite to connect to IBM MQ, it is required to provide the following libraries in classpath:

a. com.ibm.mqjms.jar
b. dhbcore.jar
c. com.ibm.mq.jar
d. com.ibm.mq.jmqi.jar
e. mqcontext.jar
f. com.ibm.mq.pcf.jar
g. com.ibm.mq.commonservices.jar
h. com.ibm.mq.headers.jar
i. fscontext.jar
j. jms.jar

Add the above jars into domain library directory and the directory usually located at $DOMAIN_DIR/lib.

The jars located in this($DOMAIN_DIR/lib) directory will be picked up and added dynamically to the end of the server classpath at server startup.

For eg. <$fmwhome>/user_projects/domains//lib/

Alternatively the above jar’s can also be added as part of the setDomainEnv.sh

Credential based connectivity :

Outbound: : Configure the trading partner delivery channel for using "Generic JMS" protocol

Inbound: : Configure the internal delivery channel for using "Generic JMS" protocol
with the following details:








Parameter NameDescription
Destination NameMQ Queue Name
Connection FactoryMQ Queue Manager Name
Destination Providerjava.naming.factory.initial=com.ibm.mq.jms.context.WMQInitialContextFactory;java.naming.provider.url=<host>:<QM Listen port>/<MQ Channel Name>;
User NameMQ User Name
passwordMQ password

.bindings based connectivity

As a pre-requisite, get/generate the .bindings file in MQServer. This can be done by MQ Administrator
Set the following values in the respective delivery channel for outbound / inbound






Parameter NameDescription
Destination NameMQ Queue Name
Connection FactoryMQ Queue Manager Name
Destination Providerjava.naming.factory.initial=com.ibm.mq.jms.context.WMQInitialContextFactory;java.naming.provider.url=file:///<location of .bindings file>;

About

To Discover and discuss the capability of B2B in the world of Trading Partner Integration. This blog is primarily intended to share thoughts on Oracle B2B Product and to share best practices in performance, scalability and various topologies.

Search

Archives
« November 2012 »
SunMonTueWedThuFriSat
    
1
2
3
4
5
6
7
8
9
10
11
13
14
15
16
17
18
19
20
21
22
23
24
25
26
28
29
30
 
       
Today