Agreement Identification in ebMS

TPA Identification details

Following are the various mechanisms with which the agreement would be identified using ebMS protocol.

Outbound scenario:

1) From, To, Document Type and Document Revision: In Oracle AS B2B, it is possible to identify the agreement using these attributes.

2) Service based Identification
If document Type and Document Revision is not present and if the ebMS service is available, which is enqueued using the ACTION attribute, then the ebMS service attribute is used to identify the Document Type and Document Revision and identify the agreement based on step 1.

3) Action based Identification
If document Type and Document Revision is not present and if the ebMS Action is available, which is enqueued using the ACTION attribute, then the ebMS action attribute is used to identify the Document Type and Document Revision and identify the agreement based on step 1.


Inbound Scenario

1) From, To, Document Type and Document Revision: In Oracle AS B2B, it is possible to identify the agreement using these attributes. Since Oracle AS B2B supports custom over ebMS Business protocol, the custom Document Type and Document Revision can be retrieved by applying the Xpath expression on the payload.

2) Action based Identification
If the Business Action matches with the ebMS header Action of the incoming message, then the respective Document Type and Document Revision will be used to identify the agreement based on step 1.

3) CPAId based Identification
The following property in tip.properties, “oracle.tip.adapter.b2b.ebms.IdentifyAgreement.cpaId=true” indicates then the incoming document’s agreement Identification will be based on ebMS header CPAId with the Agreement ID. If this value is set true, then this overrides all the above mechanisms for inbound agreement identification, as this is a global setting.

Rejection Based on Duplicate Control Number

Stay tuned..

10.1.2.3.0 Patch Install

Every time there is a new release we often come across may patches.
10.1.2.3.0 is also a one such patch for 10.1.2.0.2 oracle AS server. 10.1.2.3.0 has 2 options, which need to be selected during installation. Below are the steps to install 10.1.2.3.0 and the option we need to select to make 10.1.2.3.0 successful installation.

NOTE:
Pre-requisite
1. 101202 infra, Midtire and b2b should be installed
2. Please make sure that Midtire is shutdown before starting Patch installation


How to install 10.1.2.3.0 Patch

1. Download 10.1.2.3.0 Patch from metalink
2. Click on "Next" button welcome screen
3. Select "Midtire home” in “specify location” screen and click Next button
4. Select the 1st radio button, which is "Oracle Application Server and Developer Suite 10g Rel2 Software update 10.1.2.3.0" and proceed to next screen(refer screen shot below)


5. Specify IAS_ADMIN password and proceed to next screen

6. Review summary page and Click on the "Install" button
7. This will complete 10.1.2.3.0 patch installation




What happens if we choose second option i.e "Oracle Application Server 10g Metadata Repository Update 10.1.2.3.0" ?

If we choose "Oracle Application Server 10g Metadata Repository Update 10.1.2.3.0" we cannot complete the installation we will hit this issues "Metadata Repository update cannot be run from the selected OH. the update must be run from either an identity management with metadata repository installation or a portal and wireless middle tire or a business intelligence and forms middle tier. Running this update on either an oracleAS middle tire or identity management with metadata repository installation allows updating of any of the metadata repositories registered with your Internet directory”

Customizing Control Version in EDIFACT

By default oracle B2B generates the CONTROL message using D3 version. If there is a requirement to customize the version of CONTROL message use the following tip.properties.

oracle.tip.adapter.b2b.edi.FAMessageVersionNumber
oracle.tip.adapter.b2b.edi.FAMessageReleaseNumber
oracle.tip.adapter.b2b.edi.FAAssocAssignedCode

If FAMessageVersionNumber, FAMessageReleaseNumber, FAAssocAssignedCode is specified in tip.properties, we replace those values in generated CONTROL message.

Overdue Acknowledgements - Identify and Take action

How to Handle Overdue Acknowledgments?

Oracle AS B2B provides a feature to configure a timeout value with in which the Functional Acknowledgment has to be received for Outbound business messages.

After successful transmission of EDI Message, B2B must wait for Functional Acknowledgment for configured time. If FA is not received, B2B will enqueue an Error message to B2B Inbound Queue.

set oracle.tip.adapter.b2b.FAWaitTimeOut= time

where time is in minutes.

With FAwaitTimeOut configuration, B2B inserts a Timeout event. If FA is not received with in the time out period, B2B will enqueue an error message.

It is possible to develop a BPEL process to listen on to B2B Inbound queues with B2BERRORUSER and send further notification in the form of fax/phone/SMS etc.

Multiple Private Keys in Oracle B2B

Stay tuned..

Is batching a Mandatory for Grouping the Transaction set

Even though EDI Batching is the preferred way of grouping the transaction set, it is also possible to handle it by sending multiple transaction set as edifecs XML. B2B accept the multiple transaction set, translate it into EDI document by adding the envelope details to it.

If you find any limitations in this approach , please shoot a mail to ramesh.anantharamaiah@oracle.com

New Blogs for - EDI and HL7 Users

EDIGurus.com and HL7gurus.org

Stay tuned to get more. This is a place to ask anything and everything on EDI and HL7.

CPP/CPA feature in ebMS

Introduction

Oracle B2B is a critical component of Oracle Fusion middleware which supports various Standard based B2B protocol for Trading Partner Integration. Standards supported by B2B protocols spreads across several Business verticals and involve various Document, Exchange standard (Exchange standard incorporates both Transport, packaging and security protocols).

To support multiple protocols Oracle B2B has a notion of canonical meta data model to accommodate the meta data of various protocols. CPA Import process maps the incoming CPA Specific metadata to Oracle B2B canonical model and the CPA Export process do the reverse of mapping from canonical model to CPA model.


This document talks about the import /export aspect of EBXML metadata, which is captured as Collaboration Protocol Profile CPP and Collaboration protocol Agreement CPA and is widely used in EBXML community.

In ebXML, a Collaboration Protocol Profile (CPP) will describe message exchange capabilities of a party. A Collaboration Protocol Agreement (CPA) will describe the agreement between two parties


The CPP and CPA contains details of transport, messaging, security constrains, and bindings to a Business Process Specification (BPSS) document that contains the definition of the interactions between the two Parties while engaging in a message exchange.

This document explains CPP/CPA features, steps to configure using Oracle AS B2B and the runtime behavior of CPP/CPA.


Salient features:

1. CPA import with selective BPSS specification: This utility provides the option to the user to selectively add the BPSS specification while importing the CPA. One or more BPSS documents can also be imported. This is done by adding all the BPSS documents separated by “;”.

2. Auto Creation of Business Action: This feature automatically creates all the BPSS specification business actions to Oracle AS B2B business actions. This will facilitate the user to create Business Action in bulk.


3. Grouping of Business action into an agreement based on endpoint
This feature combines all the business action pertaining to an endpoint under one agreement.


4. Selective usage of Common Business Actions. This feature helps the user to selectively add the common business actions while importing, depending on the business requirement

We are referring ReceiptAcknowledgement, AcceptanceAcknowledg-ement as Common business action i.e one which can be used in multiple services.
One time definition of Common Business Actions: All the common business actions that are using common schema can be defined only once and gets used/referred to all the other BPSS’s while importing, thereby simplifies the CPP/CPA import.

The definition used for the common business actions like ReceiptAcknowledgement, AcceptanceAcknowledgement will have the common schemas.

6. Auto Import/Export of security details: The required security credentials will be taken from CPP/CPA document to Oracle AS B2B as part of CPA import process, also the security details gets exported from Oracle AS B2B to CPP/CPA,

7. CPA Export of Multiple BPSS files from Oracle AS B2B: This feature exports the Oracle AS B2B specific metadata to CPP/CPA specific metadata .For every Business Action, it creates a corresponding BPSS during export.


8. CPA Export of Multiple CPA files from Oracle AS B2B: This feature allows the multiple CPA export. Typically it creates a different agreement for every CPA based on the Trading partner.

9. Log Level can be configured as Debug or Info or Error.
10. Log files can be of type text or xml.




Pre-requisites:

1 Business knowledge of Custom over ebMS Exchange

2 Knowledge of ebXML 2.0

3 As part of Pre-CPA import steps, it is required to create the Internal Delivery Channels in Oracle B2B, and the same has to be referred in the cppcpa.properties. This gets used in CPA Import steps


User Experience

IMPORTANT: Please take backup of your existing B2B configurations.

Steps to run CPP/CPA Import:

1) Set the environment for Oracle AS B2B by executing the setenv script available at $ORACLE_HOME/ip/install
2) Configure all the necessary import values in the cppcpa.properties located in $ORACLE_HOME/ip/tutorial/.
3) From $ORACLE_HOME/ip/tutorial run the below command
java oracle.tip.adapter.b2b.utility.EBMSUtility <location of cppcpa.properties>

Steps to run CPP/CPA Export:

1) Set the environment for Oracle AS B2B by executing the setenv script available at $ORACLE_HOME/ip/install
2) Configure all the necessary export values in the cppcpa.properties located in $ORACLE_HOME/ip/tutorial/.
3) Make sure the property “oracle.tip.adapter.b2b.ebms.CPADocument” is commented. – This property is used while importing the CPP/CPA to Oracle AS B2B
4) Provide the Host Party Name in “oracle.tip.adapter.b2b.ebms.Host” property.
5) Provide the Host Endpoint URL in “oracle.tip.adapter.b2b.ebms.HostEndPoint” property.
6) From $ORACLE_HOME/ip/tutorial run the below command
java oracle.tip.adapter.b2b.utility.EBMSUtility <location of cppcpa.properties>

Configuration Details:

CPA Import Properties:

1 oracle.tip.adapter.b2b.ebms.BPSSDocument
This property holds the absolute path for BPSS Document. It is an optional property, which will be used to get the BPSS document details to be import into Oracle B2B repository. If the property does not exist then the values will be imported from CPA. Multiple BPSS documents are separated by “;”

2 oracle.tip.adapter.b2b.ebms.CPADocument
This mandatory property will be used to get the absolute path of the CPA document to be import into Oracle B2B repository.

3 oracle.tip.adapter.b2b.ebms.xsdLocation
This optional property will be used to specify the absolute path of the schema file location. This schema file will be used for document validation.

When BPSS document is not specified then it will use for the common definition for all Business Actions.

4 oracle.tip.adapter.b2b.ebms.CertificateDirectory
This is a mandatory property in case of secured message transfer. This directory will be used to store the certificates specified in the CPP/CPA document, which will be used in ebXML secured message transfer.

5 oracle.tip.adapter.b2b.ebms.internalDeliveryChannel.InBound
This mandatory property will be used in Oracle B2B Configuration. Specify the already created inbound internal delivery channel or specify the default inbound internal delivery channels like B2B Inbound or XML Gateway Inbound. The specified channel name MUST be present in Oracle AS B2B before importing the CPP/CPA

6 oracle.tip.adapter.b2b.ebms.internalDeliveryChannel.OutBound
This mandatory property will be used in Oracle B2B Configuration. Specify the already created outbound internal delivery channel or specify the default outbound internal delivery channels like B2B Inbound or XML Gateway Inbound. . The specified channel name MUST be present in Oracle AS B2B before importing the CPP/CPA.

7 oracle.tip.adapter.b2b.ebms.CommonBusinessAction
Add the common business actions separated comma. These are the business actions that are used multiple times in CPA.

E.g.: ReceiptAcknowledgementException, ReceiptAcknowledgement, AcceptanceAcknowledgementException, AcceptanceAcknowledgement. It is an optional property.

In case of CPA import along with BPSS document common business action schema can be defined like below,

#oracle.tip.adapter.b2b.ebms.<Business Action Name>.Definition = <location of xsd>
# e.g. oracle.tip.adapter.b2b.ebms.ReceiptAcknowledgementException.Definition = <location of xsd>

8 Oracle.tip.adapter.b2b.ebms.GroupAgreement
This optional Boolean property will be used to group the business action in an agreement.


CPA Export Properties:

9 oracle.tip.adapter.b2b.ebms.OutputFolder
This mandatory property will be used to place the generated CPP/CPA files in the specified location.

10 oracle.tip.adapter.b2b.ebms.Host
This mandatory property will be used to set the Host Trading Partner.

11 oracle.tip.adapter.b2b.ebms.HostEndPoint
This mandatory property will be used to set the host endpoint while generating the CPP/CPA export.

12 oracle.tip.adapter.b2b.ebms.HostCertificateAlias
In case of secure message transfer, this property will be used to get the host certificate details to the CPP/CPA export.

13 oracle.tip.adapter.b2b.ebms.TPCertificateAlias
In case of secure message transfer, this property will be used to get the trading partner certificate details to the CPP/CPA export.

14 oracle.tip.adapter.b2b.ebms.BPSSExport
This optional Boolean property will be used to generate the BPSS document.

Common Properties:
15 oracle.tip.adapter.b2b.ebms.LogDirectory
This mandatory property will be used to store the log files.

16 oracle.tip.adapter.b2b.ebms.LogLevel
This mandatory property will be used to specify the mode of logs like DEBUG|INFO|ERROR.

17 oracle.tip.adapter.b2b.ebms.LogType
This mandatory property will be used to specify the log file will be stored as text/xml.

Note : More details including configuration settings would be available soon, stay tuned.

Attachment feature in ebMS using Oracle AS B2B 10g

These steps help in sending attachments in ebMS.

1. Create an xml in UNIX FILE FORMAT. Here is the sample xml file,

<?xml version="1.0" encoding="UTF-8"?>
<Attachments xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="AttachmentsDescriptor.xsd" version="1.0" boundary="boundary---">
<AttachmentPart>
<Location>file:///scratch/nansrini/test.pdf</Location>
<Content-Type>
<Top-Level-Type>application</Top-Level-Type>
<Sub-Type>pdf</Sub-Type>
</Content-Type>
</AttachmentPart>
</Attachments>


2. Edit the enq.properties to provide the file name for the "attachment" attribute as the above file(sample xml).

3. Provide directory name in tip.properties for the key "oracle.tip.adapter.b2b.attachments.dir" where the file will be stored in the inbound scenario.
4. Restart the server and enqueue the Message.
5. By Default oracle.tip.adapter.b2b.MimeType accepts only below types,

@ application/xml
@ application/octet-stream
@ application/EDIFACT
@ application/EDI-X12
@ application/jpg
@ image/jpeg
@ application/gzip
@ application/x-gzip
@ application/pkcs7-signature

If you want more options, Then you must modify tip.properties in
$ORACLE_HOME/ip/config directory to include your MimeTypes also, For example,
You want to include pdf attachments, Then your tip.properties would look like,

oracle.tip.adapter.b2b.MimeType=application/xml : application/octet-stream : application/EDIFACT : application/EDI-X12 : application/jpg : image/jpeg :
application/gzip : application/x-gzip : application/pkcs7-signature :
application/pdf

Ensure the above property in single line.

Add a new content type such as application/pdf restart opmn and re-try testcase.

PGP Encrypted File Transfer

This feature enables transferring of the externally PGP encrypted message. This can be done by setting below tip.properties. The default value is false.

oracle.tip.adapter.b2b.BinaryTransfer=true

High Availability with SFTP (SSH FTP) adapter

B2B SFTP adapter can also operate on HA topology like File and FTP adapters. Enabling SFTP adapter on HA environment is fairly simple and the process is as same as in File/FTP HA deployment.

Please refer the HA configuration guidelines for non-transactional transports here, http://www.b2bgurus.com/2008/02/high-availability-with-fileftp-adapter.html

B2B Installation fundamentals

Installation of B2B on Windows machine

Download B2B: Get this from oracle metalink

Step1: Install Oracle Infrastructure

1. Go to Shiphome location and click on setup.exe
2. Provide necessary oracle home for this Infrastructure installation
3. Complete the installation.

Step 2: j2ee/midtire/OC4J installation

1. Go to Shiphome location and click on setup.exe
2. Provide a separate middleware home. This is different from step1
3. Complete the installation.

Step 3: post installation activity

1. Open a cmd prompt and set the oracle home, An example is shown below
C:\101202\infra_0306> set path=C:\101201\infra_0306\bin;%path%
C:\101202\infra_0306> set ORACLE_HOME= C:\101201\infra_0306
C:\101202\infra_0306> set path=%ORACLE_HOME/bin;%path%
C:\101202\infra_0306> set ORACLE_SID=orcl0306

2. Unlock the b2b user if Meta Data repository is used and shutdown the database
C:\ sqlplus /as sysdba
SQL> alter user b2b identified by b2b account unlock; ; // donot execute for IM –OID installation

SQL> alter system set aq_tm_processes=5 scope=spfile;
SQL> alter system set job_queue_processes=5 scope=spfile;
SQL> alter system set open_cursors=500 scope=spfile;
SQL> commit;
SQL> shutdown immediate;

3. Take the backup of database from oradata directory and name it as orcl_b2b_before

4. Login to database and startup again
C:\ sqlplus /as sysdba
SQL> startup;

5. On j2ee/ midtire terminal start the j2ee server before the installation of b2b
c: /101201/j2ee_0306/opmn/bin/> opmnctl startall

Step 4: B2B installation

1. Go to Shiphome location and click on setup.exe
2. Select the middleware home for b2b installation( Note: Middleware home same as step2)
3. Complete the installation.
4. Once the installation is completed then go to j2ee_0306/ip/config dir and open the tip properties file and change debug levels from ERROR to DEBUG and
change Logtype = text

5. Stop the j2ee server
6. Go back to infra terminal, shutdown the database and take a backup of database and start the database again
c:/ sqlplus /as sysdba
SQL> shutdown immediate;
SQL> quit;
7. Take a backup of database and start the database as orcl_b2b_after.
8. Go to midtire terminal and start the server.

HTTP Basic Authentication

Oracle AS B2B Support HTTP Basic authentication based on Userid and password.

How to Configure basic Authentication.

1. Go to the Transport server section, specify user id and password.
2. In the additional Transport header specify

authtype=basic#realm=myRealm

where myRealm is the realm of the remote trading partner site.

Oracle B2B Downloads

1. http://www.oracle.com/technology/software/htdocs/devlic.html?url=/technology/software/products/ias/htdocs/101202.html

2. Accept and click on next.

3. Select Application Server Integration(10.1.2.0.2) , download B2B for Appropriate OS

4. Install the latest patch. Follow http://www.b2bgurus.com/2008/07/10123-latest-b2b-patch-details.html

p.S You need to install 10.1.2.0.2 infrastructure database and application server before installing oracle AS B2B.

Oracle USA "Deal of the Week" -- First ebXML B2B Sale -- Oracle Reference

http://standupsales.com/node/21

Oracle B2B in Retail Industry - Use case scenario

Stay tuned..

Oracle B2B Wiki

Please enhance this Oracle B2B Wiki with case studies used in various business verticals. Thanks in advance.

Oracle B2B on Vista

Oracle B2B is certified on vista. Please refer to this link on details about B2B installation on vista.

http://www.oracle.com/technology/software/products/ias/files/as_certification_r2_101202.html

Rgds,Ramesh

Oracle B2B in Chemical Industry - B2B and E-Business suite

Read stories about BPEL & B2B Synergies Reduce Supplier Enablement Costs
Helena Chemical Company Deploys New Technology & Techniques


Helena Chemical deploys Oracle AS, B2B ebXML

B2B Startup Issues for a listening End point

Oracle AS B2B will not start if it failed to initialize any of the transport listening end point during start up. Listening end point mean, any end point which has a polling interval.

The user community feels that just for a failure in initialization of some of the listening end points , it is in-appropriate not to start the B2B. This might also results in a huge impact in the business and is justfied in a use case with large number of listening end point. Failure in some of the end point should be ignored and B2B should be started by necessary logging of the failed end points.

With this fix B2B will start even in the following cases.

1) If any receiving delivery channel is misconfigured, such as username and password is not specified for FTP transport.

2) During initialization time, B2B is not able to connect to dataource.

B2B will log the error message as "transport could not be initialized" in b2b.log and the transport logs with the details about the listening end point in the following format

TRANSPORT_SERVER_NAME < TRANSPOR_PROTOCOL_NAME > < TRADING_PARTNER_NAME >

Log also carries information about the delivery channel which failed to initialize.

How To handle two Business Action of Same Name in B2B

One of the popular use case is to Support Business Action with same name and different revision. Follow the below steps.

1. Apply the latest MLR on 10.1.2.3
2. While defining the business action Use appropriate Name and Revision.
3. Use the appropriate business action and revision for creating Operational capability.
4. Use the appropriate business action and revision for creating Agreement.
5. Deploy and exchange the messages.

Runtime Functionality.

Please follow the post for outbound and inbound user experience for processing business action with same name and different revision.

Business Action with same Name and Different Revision

Interview with Thomas Kurian - Oracle’s acquisition of BEA Systems

Finally, Oracle’s B2B engine provides a way to hook up your SOA, not just within your company but outside the organization, and Oracle Enterprise Manager becomes the management framework. If you want to read more..

http://www.oracle.com/technology/oramag/oracle/08-sep/o58interview.html

Internal Properties in Oracle B2B

For every EDI document Processing in B2B, there is a need to configure the Envelope information by using Document Protocol parameters in B2B. This information is used by XEngine,

1. To create the envelope for the document sent by Back end application. Xengine create the envelope (Interchange and Group) ,embed the Transaction set and send it to Trading partner.

2. To identify the Incoming Document Type and revision, there by identifying the business action for Agreement Identification.


What is Internal Properties

For every XML schema generated per ecs file while modeling the document in B2B Document editor, it defines Internal Properties. Internal Properties are used to

1. Send the Envelope information to the back end application in case of Inbound flow. By default, XEngine strip off the Envelope information and send only the Transaction set to back end appliction.

2. Override the Document Protocol parameter which is defined in B2B, which is used by B2B to create the envelope.

set oracle.tip.adapter.b2b.edi.FAInternalProperties=true

in tip.properties to avail this feature.

B2B Generates FA/Control messages

Consider the case of B2B generating the Acknowledgment, by default B2B always uses Document protocol parameters to generate the envelope for sending FA/Control. By setting the

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

it is possible to make use of the envelope details of the inbound business document while generating the FA/Control.

Oracle B2B Booth in OOW-2008

There are interesting Retail and Health care use cases are getting demoed in B2B Booth. Do visit...

Sync Response

This feature introduces a Synchronous response to any of the incoming Business Document. Sync HTTP response essentially mean, sending the response using the same http connection as the incoming business message.


There is an introduction of a new URI b2b/SYNCResponseServlet to handle the Sync response in B2B. Every business message which is received in this URI, it is expected to send the response using the same http connection with in the time out time. The time out time is configured in tip.properties using

oracle.tip.adapter.b2b.httpSyncReplyWaitTime=

Use case : Globalchips to receive 270 EDI request from Acme over HTTP and respond with 271 EDI synchronously.

Implementation :

1. Acme Side

a. For both Acme and Globalchips, supported business action(270,271) must have

Functional Acknowledgement required? should be set to NO.

b. Configure the following in the additional transport header for GlobalChips.

http.sync=true#timeout=300000

c. End point URI for GlobalChips is selected as b2b/SYNCResponseServlet

2. Global Chips side.

a. For both Acme and Globalchips, supported business action(270,271) must have

Functional Acknowledgement required? should be set to NO.

b. web.xml in $ORACLE_HOME/j2ee/OC4j_B2B/applications/b2b/ip/WEB-INF/ must be modified to include the following servlet-mapping for transportServlet.

<servlet-mapping>
<servlet-name>transportServlet</servlet-name>
<url-pattern>SYNCResponseServlet</url-pattern>
</servlet-mapping>

c. Configure the following tip.properties

oracle.tip.adapter.b2b.httpSyncReplyWaitTime = wait time in minutes.

d. Also set

oracle.tip.adapter.b2b.ReplyToAsRequest=true

Back end application such as BPEL is required to send the response i.e 271 with replyToMsgID value of the original message. B2B message ID of the request message 270 should be sent as replyToMsgID of the Synchronous response 271

Please note in Oracle 10g, this feature is not High availability enabled i.e it is not possible to get the request in one instance of B2B and send the Sync Response in another.

Interesting Macros in EDI and HL7

Macros play an important role in XEngine, when there is an use case to fill this data in the B2B Layer, instead of sending it from the Back end application.

1. controlNumber.

In case of Outbound Messages, B2B Generates the control number only in case the Back end application send the EDI message with the Keyword #controlNumber for e.g.

#ControlNumber#

Oracle AS B2B fills in the unique number for Interchange and Transaction set Control Number and uses it for correlating the incoming Control messages.

2. SegmentCount

Segment count for the current EDI Document. Xengine will replace with the approprite values. e.g #SegmentCount#

3. MessageSendingFacility

MSH Position 4.1 e.g #Property(MessageSendingFacility)#

4. MessageSendingApp

MSH Position 3.1 e.g #Property(MessageSendingApp)#

5. MessageReceivingApp

MSH Position 5.1 e.g #Property(MessageReceivingApp)

6. MessageReceivingFacility

MSH Position 6.1 e.g #Property(MessageReceivingFacility)#

How to enable b2b_idc_transport.log

The below two tip.properties used to control the transport logs,

For External Delivery Channel :
oracle.tip.adapter.b2b.transportTraceLogLevel

For Internal Delivery Channel :
oracle.tip.adapter.b2b.appTransportTraceLogLevel

The possible values could be,
WARNING | STATUS | DEBUG | ERROR

For backward compatibility, we have made assumption that if old properties
are defined, logLevel will be assumed to be DEBUG

The new Properties for Transport Logger overrides old properties.

If none of the properties (old and new) for Transport Logger is specified,
default log level is ERROR

The new transport log files will be created in the same directory in which
b2b log file is created.
Example: $ORACLE_HOME/ip/log/b2b

For Internal delivery channel b2b_idc_transport.log

For External delivery channel b2b_dc_transport.log

Attending OOW-2008

I will be there in Oracle Open World - 2008. Are you, if so lets plan on meeting there.

Broadcast feature in Oracle AS B2B 10g

Broadcast feature of Oracle AS B2B 10g enables the users to send the same message to multiple trading partners. This gives the flexibility to the users to create their own groups of trading partners specific to the business needs. The back-end application can then send a message to the group and B2B will send the message to all the members of the group.

The salient points of the feature are:

1. Prevent BPEL to send multiple files there by reducing the traffic on
   BPEL-B2B and also in the B2B.
2. Bring the concept of trading partner groups in B2B and use it for
   broadcasting. This will prevent BPEL user to know about Trading partner details as well as the Group as this is B2B specific meta data
3. This is an event driven approach to handle the multiple messages to various trading partner
   

This is an optional feature which can used on a need basis by specifying the group name as part of "actionName" attribute. The "actionName" attribute would look like

actionName = Grouping:<name of the group>

This feature requires an additional identifier to be added for the Trading partner indicating the group. This can be achieved by creating a new custom Identifier and associating the same for the required trading partners

Steps to create a custom Identifier in B2B UI:

Administration -> Design -> Trading Partner Identification Types -> Create

P.S: Every New trading partner Identification requires a redeployment of the Agreement

This is available as part of MLR 10.1.2.3.0 - # 3
Patch # 7184219