Editing RosettaNet attribute values

For RosettaNet support, an action type document flow definition has a specific set of attributes. These attributes provide information used to validate the PIP message, to define the roles and services used in the PIP, and to define the response to the action. The PIP packages provided by WebSphere Partner Gateway automatically define values for these attributes and you typically do not need to change them.

To edit the RosettaNet attributes of an action document flow definition, perform the following steps:

  1. Click Hub Admin > Hub Configuration > Document Flow Definition.
  2. Click the Expand icons to individually expand a node to the appropriate document flow definition level or select All to expand the entire tree.
  3. The Actions column for each action contains an Edit RosettaNet Attribute Values icon. Click this icon to edit the RosettaNet attributes of the action. The Community Console displays a list of defined attributes under RosettaNet Attributes.
  4. Complete the following parameters under RosettaNet Attributes. (These attributes are defined automatically when a PIP is uploaded to the system.)
    Table 36. RosettaNet attributes
    RosettaNet attribute Description
    DTD Name Identifies the name of the action of the PIP in the DTD provided by RosettaNet
    From Service Contains the network component service name of the participant or back-end system that is sending the message
    To Service Contains the network component service name of the participant or back-end system that is receiving the message
    From Role Contains the role name of the participant or back-end system that is sending the message
    To Role Contains the role name of the participant or back-end system that is receiving the message
    Root Tag Contains the name of the root element in the XML document associated with the PIP
    Response From Action Name Identifies the next Action to perform in the PIP
    Note: If the Console displays the No attributes were found message, the attributes have not been defined.
  5. If the Console displays this message for a lower-level definition, the definition might still work, because it inherits the attributes of the higher-level definition. Adding attributes and their values overrides the inherited attributes and changes the function of the document flow definition.
  6. Click Save.

Copyright IBM Corp. 2003, 2005