Checklist for community configuration

The following are items to consider when configuring a community.

  1. Does your community have at least one routing ID? This is the unique identifier for a community in e-commerce trading. See Routing IDs.
  2. If you plan to trade ebXML documents, enter an ebXML party ID type only if the routing ID is not a URI. See Routing ID for ebXML.
  3. What kind of certificate do you want to use: self-signed or CA? See Manage certificates.
  4. What integration exchange do you want to use for picking up messages from a back-end system? See Application pickups and Application deliveries.
  5. What trading exchange do you want to use for receiving messages from partners? See Community trading pickups and partner deliveries.
  6. What integration exchange do you want to use for routing messages received from partners to a back-end system? See Community trading pickups and partner deliveries.
  7. Have you added a trading partner, either by importing a profile file or manually configuring a profile? See Add a partner.
  8. Have you determined whether messages sent or received by you or partners must pass through proxy servers, firewalls, or load balancers? If so, take steps to adjust the trading engine configuration to accommodate unhindered message traffic. See Firewalls and proxy servers and, if applicable, HTTP outbound proxy.
  9. Do you want the community to use default or custom collaboration settings? These are rules for how outbound messages are packaged. A packaged message is one that has been signed and encrypted and also MIME-wrapped with sender and receiver information along with other data. See Collaboration settings.
  10. Have you viewed the collaboration settings between your community and your partner to make sure security and packaging are aligned? See Search and display collaboration settings.
  11. What document packaging rules do you want to enforce for the messages your community receives from partners? If trading EDI documents, do you want the community to accept or reject duplicate documents? See Inbound message validation rules.
  12. Do you want to set up a post-processing script for special handling of documents before sending to partners or after receiving them from partners? For example, inbound documents can be channeled to a specific integration directory with a post-processing script. See Post-processing configuration.
  13. Do you want to set up conditions for re-routing, copying, or rejecting messages? See Message handler.
  14. Have you configured the global external SMTP server for sending email messages? See Configure the global external SMTP/SMTPS server.
  15. How long do you want to retain records of processed messages? Delivery exchanges by default are set to back up all messages passing through them. Messages must be backed up to use Message Tracker properly. You can set a schedule for how long records are retained. See Data storage, backups, and purging.

Related topics

Related Links