Modify a community

For a description of communities, see Communities.

To add a new community, see Add a community.

For a description of how to limit the number of displayed communities, see Use the community search tool.

After you create a community, you can view and modify the community's characteristics.

To view and modify an existing community:

  1. In the user interface, from the Trading configuration menu select Manage trading configuration.
  2. From the list of communities, click the name of a community to display the Summary screen for that community.
  3. At the top of the Summary page is a community navigation graphic for the community. This graphic represents the parts of the community and provides active links to pages on which you manage these parts.
  4. Navigation graphic for a community
  5. In the user interface, place your cursor over a label and a red box appears around that part of the graphic. Click inside the red box to go to the page that the label references.
  6. You can use the community graphic links to view and edit the following user interface pages for the community:
    • Summary — Reports trading activity for the period you specify. The default period of activity is the last hour. This page also shows the default delivery exchange for receiving messages from partners and certificate information.
    • Properties — Displays:
      • The name of the community
      • A country code that indicates the community location
      • Any attributes associated with the community for processing or search purposes. You can change the value for one or more of the optional attributes on that page. You can define optional attributes in one of three states:
        • Empty text box and empty checkbox — this attribute is ignored at runtime.
        • Completed text box and empty checkbox — this attribute is evaluated at runtime.
        • Disabled text box (grayed out) and selected checkbox — this attribute may exist for other agreements, but is negated at runtime for this particular agreement.
    • Certificates — Displays certificates associated with this community. You also can add a certificate. For more information see Certificates pages.
    • Routing IDs — Displays the routing IDs associated with this community. A community routing ID is the “from” address used in message trading. A community can have one or more routing IDs. For more information see Routing IDs.
    • Contacts — Identifies the principal contact person for the community. Other information can be added, including a phone number and notes.
    • Application delivery — Displays the available delivery exchanges that the community can use to send documents and messages to back-end applications.
    • Application pickup — Displays the available pickup exchanges that the community can use to consume documents and messages from back-end applications.
    • Delivery settings — Displays routing criteria and specific file-handling behavior that the community uses to deliver messages to back-end applications. You can set different routing criteria and handling specifications for each application delivery the community uses.
    • Message handler — Enables you to set up message actions, such as re-routing, triggered by specified conditions. For more information see Message handler.
    • Message validation — Enables you to specify whether a community accepts or rejects EDI messages with duplicate control IDs. You also can specify whether a community accepts or rejects signed or encrypted messages. For more information see Inbound message validation rules.
    • Collaboration settings — Enables you to set up encryption, signing and other rules for messages a community sends. Provided a community uses a certificate, the default settings are adequate in many cases. For more information see Collaboration settings.
    • Trading pickup — Displays the message protocols and transports that partners use to send messages to the community and how the community retrieves the sent messages. A community with trading pickups gives partners multiple avenues for sending messages. For more information see Community trading pickups and partner deliveries.
    • HTTP proxy — Enables you to define a global HTTP proxy through which all outbound HTTP traffic is routed, if needed. All communities use this proxy. For more information see HTTP outbound proxy.
    • Trading partners — Enables you to view the Trading partners page. This page shows the partners that belong to a community. It displays the status of messages traded with each partner. You can use commands on this page to add partners to the community, and to display collaboration settings between the community and its partners.

Additional community summary page features

Tasks to complete

If an important step in the community configuration is not yet completed, the interface displays this task and provides a link to the page where you can complete the task.

Related tasks list

The community summary page provides a task list with hyperlinks to the following commonly-preformed tasks:

  • Add a partner to this community
  • Show community-to-partner collaboration settings
  • Change embedded transport server
  • Enable all exchanges for receiving partner messages
  • Manage CPAs
  • Export this community as a partner profile
  • Back up this community and its partners
  • Delete this community

Related topics

Related Links