Handling Multiple Group ID - Multiple Departments of the same Enterprise

Consider a case where in the Enterprise GlobalCust has Two internal Department with name GlobalChips and GlobalCorp. Trading partner Acme wants to send messages to the two department by referring GlobaclChips and GlobalCorp in the Group ID.

1. Create two Identifier of Type EDI Group ID .
2. One with value GlobalChips and Another with GlobalCorp.
3. Add oracle.tip.adapter.b2b.edi.identifyFromTP = Group in the tip.properties and
restart B2B.
4. Create an Agreement with EDI Group ID as value GlobalChips.
5. Turn off the validation.

Send two message with Application Recipient Code as GlobalChips and GlobalCorp. Both of these messages should be accepted by B2B Engine with the To Party as GlobalCust.

P.S For generating FA similar to Inbound Business message please set

oracle.tip.b2b.edi.FAInternalProperties=true in tip.properties

P.S Make sure to disable the validation.

Another way of enabling this feature is by using the following tip.property.

oracle.tip.adapter.b2b.edi.ignoreValidation=<values>

Provide those identifier which will be different from the configured one.

Few of the sample identifiers are as follows:
InterchangeReceiverID,InterchangeSenderID,GroupReceiverID,GroupSenderID,GroupSenderQual,GroupReceiverQual,InterchangeSenderQual,InterchangeReceiverQual

Performance Tips to handle Large number of configuration

Performance Tips to handle Multiple configuration is to enable the following tip.properties and restart B2B

oracle.tip.configuration.ignoreValidation=true

or

oracle.tip.buslogic.validation.ModelValidation=off

Please ensure to be on 10.1.2.3 and latest patch.

RFP Support

Leave your question/Clarification on RFP by using option "Post a Comment" . I shall get back to you on this.

10.1.2.3 - Latest B2B Patch Details

Going forward , install only 10.1.2.3 application server as all the patches will be developed for this version.

Please download 10123 AS Patch set from meta link http://metalink.oracle.com

Navigate:
1) On Patches & Update Page, click Link (Quick Links to the Latest Patchsets, Mini Packs, and Maintenance Packs)
2) On this page Click Link (Oracle Application Server Products)
3) Click Patch Number (5983622)
4) From this Page you can download Patchset for required platform.

Once 10.1.2.3.0 AS Patchset is applied, you can move to latest MLR#7184219 for B2B (10.1.2.3.0)

For Document Editor use 5550097.

Multiple Instances on the same box - RMI port conflict

Typically there is the RMI Port conflict when multiple instances of B2B are installed on the same box. Typically first instance will take the RMI Port as 5110 and hence the second instance is forced to take next available port which is 5111.

Even though this value is part of the tip.properties same is not updated in the web application.

How To Address this problem

1. Navigate to /ORACLE_HOME/j2ee/OC4J_B2B/applications/b2b/ip/WEB-INF. Take a backup of web.xml.
2. Identify the rmiport in the initParam, and edit the value to 5111 instead of 5110

In the web.xml file, alter the following

From
-----------
<init-param>
<param-name>rmiPort<param-value>5110</init-param>

To
---
<init-param>
<param-name>rmiPort<param-value>5111</init-param>

3. Make sure the same is reflected in tip.properties using
oracle.tip.adapter.b2b.RMIPort = 5110

4. Restart B2B