RosettaNet Example

Fictional Example for Configuration and Communication between two business partners using FMS and RosettaNet^TM.

Bob runs a manufacturing company, while Mary runs a retail store which distributes and sells Bob's products.

Since Bob's manufacturing company runs a Business 2 Business (B2B) integration server which supports RosettaNet, Mary has realized that the quoting and product ordering process could be streamlined by using the B2B integration specification RosettaNet provided by FMS-Starter Edition.

Mary initiates the B2B process by communicating with Bob and discussing the integration. Bob sends Mary:

• his supported Parter Interface Process (PIP) list

• the RosettaNet business dictionary for a glossary of terms

• his DUNS number (000000001)

• his physical location

• his B2B integration server hostname (https://ebusiness.bob.org/RosettaNet)

• as well as his Public Key (Certificate).

Mary subscribes to the RosettaNet PIP cluster 3 which is 'Order Management' which controls processes such as:

\
\Cluster 3: Order Management
\  Segment 3A: Quote and Order Entry
\    PIP3A1: Request Quote
\    PIP3A2: Request Price and Availability
\    PIP3A3: Request Shopping Cart Transfer
\    PIP3A4: Request Purchase Order
\    PIP3A5: Query Order Status
\    ...
\
\      

Mary is only really interested in PIP3A1 and PIP3A4 but all of the other options are available in this PIP cluster.

Mary then applies for a Data Universal Numbering System or DUNS number from http://www.dnb.com/US/duns_update/ for use with the RosettaNet specification which uniquely identifies her company by a number. Mary receives the DUNS number 000000002 for her company.

Mary now installs the FMS distribution on her company's server. She refers to the manual for installation steps:

1. Install FMS

2. Obtain a licence key from the FMS distributer

3. Generate a Private and Public Key pair in the keystore 'certs'

4. Import Bob's Public Key (Certificate) into the server keystore 'certs' under the alias 'bob.alias'

5. Add Bob's PartnerIdentifier (000000001), alias (bob.alias), and endpoint hostname (https://rn.bob.org) to the PartnerIdentifier section in the configuration file ConnectionConfiguration.xml for return mapping purposes

6. Copy the unrestricted Java policy files into the $JAVA_HOME/lib/security/ directory to allow for 1024 bit encryption keys

7. Configure the logging system

8. Start the server and check logs for error messages

9. Export the server's Public Key (Certificate) for use with the client application during SSL transmission

10. Copy the server's Public Key to the client machine running the Management Application that will be sending the RosettaNet requests

11. Install the Client distribution on the client machine

12. Import the server's Public Key (Certificate) into the client machine's keystore

13. Configure the client script with the correct DUNS numbers (Recipient '000000001' and Sender '000000002'), Bob's server hostname 'https://rn.bob.org', the local server hostname to connect to, and the physical location names for both Mary and Bob

14. Send Mary's Public Key (Certificate), her physical location, and her DUNS number to Bob who then inputs them into his system

15. Modify the Business Application to generate a Quote into the XML standard provided by the PIP3A1 specification

16. Execute the client script from the Business Application with the XML, Message Tracking ID, supporting documents, and Schema Type ('Request Quote') as arguments and wait for a response from Bob's B2B integration server

Mary then repeats the last two steps but with PIP3A4 for 'Request Purchase Order' for ordering of stock.

Mary now enjoys a seamless quoting and ordering experience with Bob's Manufacturing Company, thereby increasing productivity and reducing stress levels at work.