Document Provisioning - way towards Onboarding Trading partner?
By Ramesh Nittur Anantharamaiah on Nov 08, 2010
First of all my apologies for not being active in this blogs for quite sometime.
I have decided to write something about Oracle B2B at least on a weekly basis and keep you updated about the latest features, road map, competition etc as earlier in b2bgurus.com.
I remember my implementation days for one of the largest Retailer in france as an Architect when configuration management was not just a painful, time consuming activities but also error prone and costly. This can be very well addressed through Self service on boarding of trading partner feature which is part of the community management feature in B2B.
what this feature offers,
1. Self service way of creating configuration through trading partner.
2. Trading partner can create their own configuration, Profile, Identifier etc.
3. Trading partner to monitor and view the report. This would allow trading partner to view only the payload they are authorized and not anything else.
4. Connectivity testing with Trading partner.
How this works.
Self service on boarding of trading partner in Oracle B2B implemented using
a. Document Provisioning in Design time - this feature would provision a document for a specific remote Administrator who can manage and configure the document in the design time. For details related to configuration and usage refer to Document provisioning feature in Oracle B2B.
b. Document obfuscation in Run time - this feature would ensure only the authorized remote user to view the payload and no one else. For details related to configuration and usage refer to Obfuscation feature in Oracle B2B
What is the stretch goal.
1 . Import the configuration specific to trading partner. This is done by providing a template excel sheet to the trading partner to fill in the configuration for batch loading.
2. Validate the payload in the design time against the configuration.
3. Test message generation and exchange with the trading partner along with message level security use case.