Work with specific protocols and standards > RosettaNet > RosettaNet configuration outline

RosettaNet configuration outline

The following outlines the steps for configuring a community to trade via the RosettaNet protocol.

  1. Install Activator.
  2. Log on to the user interface.
  3. Add and configure your community. This includes setting up delivery and a public-private key certificate for secure trading. The user interface and documentation provide guidance for creating and configuring a community. See Communities.
  4. For the trading pickup for receiving messages from partners, select RosettaNet 1.1 or RosettaNet 2.0 as the message protocol. See Community trading pickups and partner deliveries.
  5. If you need to produce message metadata documents (MMDs) when routing messages from partners to a back-end file system, select File system with message metadata as the application delivery transport. If you do not need MMDs, you can use any other application delivery transport. See Application deliveries.
  6. If a partner uses Interchange or Activator 4.x, be aware of the following: If the community profile you export has trading pickups for both RNIF 1.1 and 2.0, the partner’s trading engine ignores one of the exchanges upon importing the profile. Consult with your partner about which exchange to use, and inform the partner to edit the partner information accordingly.
  7. Set up partners by importing profiles or manually adding them. Associate the partners with your community. See Add a partner. Make sure the message protocol for sending messages to partners is RosettaNet 1.1 or RosettaNet 2.0. If a partner uses Interchange or Activator4.x, the partner profile you import has trading deliveries for sending messages for both RNIF 1.1 and 2.0. Consult with your partner about which exchange to use, and delete the unused exchange in the profile.
  8. Consult with your trading partners on the PIPs to use.
  9. Add PIPs. For DTD-based PIPs, Add PIP DTDs to the dtds directory. See Add DTD-based PIP. For schema-based PIPS, add PIP schemas to the schemas directory. See Add schema-based PIP.
  10. Check collaboration settings for document encrypting and signing options of outbound documents. You can configure settings by partner rather than use default settings. See RNIF 1.1 default settings or RNIF 2.0 default settings.
  11. Define the PIPs in the pipdefinitions.xmlfile. See Configure pipdefinitions.xml file. The community now is ready to begin trading messages.

Related topics