The following example illustrates using FMS between two business trading partners using the ebXML V3.0 message protocol. The example takes a step by step approach in configuring, establishing a link, and communicating a business message between the producer and a consumer trading partner. The business document (invoice) is based on the Universal Business Language UBL version 2.0 format.
The example assumes that the producer machine has a TCP/IP number of 192.168.0.102 and that the consumer machine has a TCP/IP number of 192.168.0.128.
The first step is to install FMS as discussed in the Section called FMS Installation in the Chapter called Installation. Once FMS is installed and running invoke the FMC as discussed in the Chapter called Configuring FMS. Leave any settings not included below at default or blank.
The following interface configuration steps are required on the producer side.
Set up the keystore including private and public keys for the producer as per the Section called Keystore Setup and Examples in the Chapter called Installation.
Open the Interface Configuration tab in the FMC and select HTTP - ebXML - UBL in the Interface Name pane.
Select Enabled in the corresponding configuration form to the right.
Select the required Payload Security Level eg. SIGN_ENCRYPT.
Select the required Transport Security Level eg. SIGN_ENCRYPT.
Select the name of the output directory eg. delivered-content.
Select the Usage required eg. TEST.
Only enable Non-Repudiation if the database has been installed and configured as detailed in the Section called Database Server in the Chapter called Installation.
Select the ebXML RemoteIn button in the HTTP -ebXML - UBL Connections form and set the HOST attribute to the TCP/IP number of the machine on which the producer FMS is hosted eg. 192.168.0.102. Both TCP/IP V4 and TCP/IP V6 are supported. If DNS is enabled then set HOST to the domain name.
The following partner configuration steps are required on the producer side for the local partner identifier.
Select partner identifier 000000000 in the Partner Identifiers pane in the Interface Configuration section of the FMC.
Set the Identifier Value to Producer in the corresponding form. The partner identifier in the Partner Identifiers pane will change accordingly.
Set the Partner Type to LOCAL PARTNER from the drop down list.
The following partner configuration steps are required on the producer side for the remote partner identifier.
Select partner identifier 999999999 in the Partner Identifiers pane in the Interface Configuration section of the FMC.
Set the Identifier Value to Consumer in the corresponding form. The partner identifier in the Partner Identifiers pane will change accordingly.
Set the Keystore Alias to consumer_fmsrns.
Set the Endpoint URL/MPC to the url of the remote host eg.https://192.168.0.128/ebXML.
Set the Partner Type to REMOTE PARTNER from the drop down list.
The following processing mode configuration steps are required on the producer side.
Select the Processing Modes pane in the Interface Configuration section of the FMC.
Select the General form and set the Identifier attribute to inv-producer-consumer. This can be set to any text string but must correspond with the consumer processing mode.
Set the Agreement to blank unless a CPA is required.
Set the Conversation ID to 1.
Set the Initiating Partner Party to Producer.
Set the Responding Partner Party to Consumer.
Select the Request tab in the P-Mode Events form and ensure that the following settings are configured. Note that these are also known as P-Mode Legs.
Set the protocol Address/Endpoint to https://192.168.0.128/ebXML.
Set the business information Service to Service-Mapping-UBL from the drop down list.
Set the business information Action to Invoice.
Right click in the business information Payload Profiles field and select New to open the Payload Profile selection window.
Select UBL-Invoice-2.0.xsd from the Schema File drop down list.
Select application/xml from the MIME Type drop down list.
Select EXPECTED from the Requirement drop down list.
Select the Done button to close the Payload Profile selection window.
Select the Error Handling form by scrolling down to the bottom of the P-Mode-Events request tab form.
Set the Sender Errors To to https://192.168.0.102/ebXML.
Set the Receiver Errors To to https://192.168.0.128/ebXML.
Set all 4 Notify selections.
Once all the above has been configured select the Save button. Then select the Administration pane and load the configuartion into FMS as follows.
Select the Administration menu option and select Open Admin Connection.
Select the Administration menu option and select Connect to Logger.
Select the Tools menu option and select Reload Connections.
The following interface configuration steps are required on the consumer side.
Set up the keystore including private and public keys for the consumer as per the Section called Keystore Setup and Examples in the Chapter called Installation.
Open the Interface Configuration tab in the FMC and select HTTP - ebXML - UBL in the Interface Name pane.
Select Enabled in the corresponding configuration form to the right.
Select the required Payload Security Level eg. SIGN_ENCRYPT.
Select the required Transport Security Level eg. SIGN_ENCRYPT.
Select the name of the output directory eg. delivered-content.
Select the Usage required eg. TEST.
Only enable Non-Repudiation if the database has been installed and configured as detailed in the Section called Database Server in the Chapter called Installation.
Select the ebXML RemoteIn button in the HTTP -ebXML - UBL Connections form and set the HOST attribute to the TCP/IP number of the machine on which the consumer FMS is hosted eg. 192.168.0.128. Both TCP/IP V4 and TCP/IP V6 are supported. If DNS is enabled then set HOST to the domain name.
The following partner configuration steps are required on the consumer side for the local partner identifier.
Select partner identifier 000000000 in the Partner Identifiers pane in the Interface Configuration section of the FMC.
Set the Identifier Value to Producer in the corresponding form. The partner identifier in the Partner Identifiers pane will change accordingly.
Set the Keystore Alias to producer_fmsrns.
Set the Partner Type to REMOTE PARTNER from the drop down list.
The following partner configuration steps are required on the consumer side for the remote partner identifier.
Select partner identifier 999999999 in the Partner Identifiers pane in the Interface Configuration section of the FMC.
Set the Identifier Value to Consumer in the corresponding form. The partner identifier in the Partner Identifiers pane will change accordingly.
Set the Partner Type to LOCAL PARTNER from the drop down list.
The following processing mode configuration steps are required on the consumer side.
Select the Processing Modes pane in the Interface Configuration section of the FMC.
Select the General form and set the Identifier attribute to inv-producer-consumer. This can be set to any text string but must correspond with the producer processing mode.
Set the Agreement to blank unless a CPA is required.
Set the Conversation ID to 1.
Set the Initiating Partner Party to Producer.
Set the Responding Partner Party to Consumer.
Select the Request tab in the P-Mode Events form and ensure that the following settings are configured. Note that these are also known as P-Mode Legs.
Set the protocol Address/Endpoint to https://192.168.0.102/ebXML.
Set the business information Service to Service-Mapping-UBL from the drop down list.
Set the business information Action to Invoice.
Right click in the business information Payload Profiles field and select New to open the Payload Profile selection window.
Select UBL-Invoice-2.0.xsd from the Schema File drop down list.
Select application/xml from the MIME Type drop down list.
Select EXPECTED from the Requirement drop down list.
Select the Done button to close the Payload Profile selection window.
Select the Error Handling form by scrolling down to the bottem of the P-Mode-Events request tab form.
Set the Sender Errors To to https://192.168.0.102/ebXML.
Set the Receiver Errors To to https://192.168.0.128/ebXML.
Set all 4 Notify selections.
Once all the above has been configured select the Save button. Then select the Administration pane and load the configuartion into FMS as follows.
Select the Administration menu option and select Open Admin Connection.
Select the Administration menu option and select Connect to Logger.
Select the Tools menu option and select Reload Connections.
Once the above configuration settings have been made using the FMC and subsequently loaded into FMS, business documents corresponding to the configuration settings can be communicated from the producer trading partner to the consumer trading partner. This may be achieved using the fms-client utility from the FMS installation directory as follows.
\ \java -jar client/fms-client.jar -c inv-producer-consumer -d consumer -e request \ \ -f test/UBL/xml/UBL-Invoice-2.0-Example.xml -P 29450 -O finest \ \ |
where the client utility command line options are described in the Section called Invocation in the Chapter called RosettaNet/ebXML Application Configuration.
| <<< Previous | Home | Next >>> |
| CPP/A Configuration | RosettaNet Example |