Creating a new custom BOD

You can create a new custom BOD, that is not a standard BOD.

  1. Create a new custom session with rules in Event Analytics Rules (EAR), for outbound BODs. See Activating a rule.
  2. Add a new custom BOD in BP, for outbound BODs. See Enabling BODs.
  3. Create a new custom BOD mapping in IEC. Publish the mapping and generate a custom agreement. Activate the custom agreement.

    The prerequisite of this step is that the mapper is already downloaded and configured to connect to the IEC server.

    You must download and install the MEC mapper to create custom BODs. The Downloading Mapper gives information on MEC Mapper installation.

    Once the mapper setup is complete, you must create a new map. See Creating a mapping.

    There are restrictions when creating a new map as this needs to be followed when creating a custom BOD map.

    1. Provide naming rules. See BOD naming rules.
    2. Provide details on Adding control properties
    3. Provide details on Configuring check order settings

    Once the map is ready, publish the map to the IEC server. Publishing mappings explains how you can publish the mappings. If you are working on a valid BOD map based on the rules and guidelines provided previously, a custom BOD partner agreement is generated in the IEC server. This is stated in the confirmation message.

    To activate the custom BOD, see Activating a new partner agreement. This action automatically triggers a reload of the needed IEC communication channels and messages are accepted in the IEC server for this agreement and map.
    Note: You can also use standard error mappings and customize the error flow.
  4. This custom BOD agreement is used for new messages. Check the result in ION for outbound BODs or in M3 for inbound BODs.
    Completing these steps results in a new custom BOD that works just as a standard BOD of the same type.