I will be there in Oracle Open World - 2008. Are you, if so lets plan on meeting there.
Thursday, August 28, 2008
Friday, August 8, 2008
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:
- Prevent BPEL to send multiple files there by reducing the traffic on
BPEL-B2B and also in the B2B.
- 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
- This is an event driven approach to handle the multiple messages to various trading partner
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 -> CreateP.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
Posted by Dheeraj Kumar M at 6:04 AM
Tuesday, August 5, 2008
Very often i am hearing Deque issues in Oracle B2B and the root cause for the same is due to the mismatch in the namespace and is resulted due to old XSD file or the legacy option used to export the schemas from Ecs file.
To address this issue, apply the latest patch and regenerate the ecs and xsd using OracleAS Integration B2B Option. Please make sure to set the Dynamicnamespace in
before regenerating the ecs/xsd file. Use the generated ecs file in B2B and XSD in BPEL.
Posted by Ramesh Nittur at 4:41 AM
Sunday, August 3, 2008
For performance reason, we have introduced a notion of TPA Caching for B2B Application which has a better Hardware Infrastructure especially Physical memory.
When this property is enabled all the TPA details will be read from the cache instead of runtime repository.
If the Agreement details is not available in the cache, B2B Engine will refer to the meta data repository and cache for subsequent use.
P.S Make sure to increase the heap size in opmn.xml as caching consumes more memory. This is applicable for both Document/Business action based Identification.