Replicating Data as BODs to Other Infor BOD-Enabled Applications

This application can use BODs in order to replicate data to and from other BOD-enabled applications.

Before You Start

• Make sure you have all the necessary software installed and configured. For more information, refer to the appropriate installation and integration guides.
• If you are using custom business object documents (BODs), make sure they are defined using the Replication Document forms.
• Be aware that this process does not currently apply to:
  • Applications that are not Infor BOD-enabled - See Replicating Data to External Systems That Do Not Use Infor BOD Formatted XMLs.

Set Up This Application to Work with BODs

1. If multiple sites on an intranet will send or receive BODs, specify the "bootstrap" configurations on the Replication tab of the Service Configuration Manager utility, on the utility server:
   • Specify a Replcator Configuration that is the collection site for all outbound messages from sites on the intranet. This site's Replication Document Outbox will collect BODs for all sites on the intranet.
   • Specify an Inbound Bus Configuration that is the collection site for all inbound messages from sites on the intranet. This site's Replication Document Outbox will collect BODs for all sites on the intranet.

   These two configurations can point to the same site database. In many cases, the inbound and outbound sites will be the same site.

2. On the Intranets form, create a new intranet for Infor ION (bus). Specify these values:
   • Intranet: Specify the name to identify the intranet, for example: InforBUS
   • Description: Specify an appropriate description, for example: Infor ION connection
   • External: Select this check box.
   • Transport: Select ESB.
   • Tenant ID: To use the same tenant ID for all sites on this intranet, specify it here. You can also leave it blank here and specify the tenant ID on the local site records, or leave that field blank to use the default tenant ID value of infor. The tenant ID can be a maximum of 22 characters. For more information about how the tenant ID is used with ION, see the ION Connect Administration Guide.
3. On the Sites form, create a logical "site" for Infor ION:
   • Site: Specify a name to identify this site as your ION site, for example: InforBUS.
   • Site Name and Description: Specify an appropriate site name and description.
   • Intranet Name: Select the intranet you created in Step 1.
   • From Site: On the Site User Map tab, specify the local site, for example, oh.
   • User Name: Specify the user ID used to send replication documents to the  Factory Track outbox for ION to retrieve. This user must already be set up on the Users form at the local site. We recommend that you specify the repl_user here, if it is defined.  Otherwise, specify a user with Full User editing permissions.
4. On the Sites form, configure the local site record to generate and/or receive business object documents (BODs):
   • Specify the Message Bus Logical ID for the site. This identifies the Factory Track site to ION. Make sure it is set up as specified in Formatting Infor Logical IDs.

     Note: The logical ID specified here must match the application type and instance defined in ION Connect for this site.

   • (Optionally) Specify a tenant ID for the local site. If no tenant ID is specified here or in the Intranets form, the tenant ID defaults to infor.
5. On the Replication Categories form, the ESB category is used for replicating BODs.

   If you are adding a new BOD, you must add to the ESB category the table or method being used to generate the BOD.

   Examples

   NOTE: For BODs created with TABLE!, you must select the Skip Delete check box. Otherwise, a BOD will be created with null values on deletion.

6. On the Replication Rules form, create a new rule:

   1. Source Site: Specify the local site that you configured in Step 4.

   2. Target Site: Specify the ION site you created in Step 3.

   3. Category: Specify ESB.

   4. Interval Type: Specify any option except Transactional.

7. On the Replication Management form, click Regenerate Replication Triggers.

The next time a user action triggers BOD generation, the BOD XML will be created automatically and placed in the Replication Document Outbox.

Generating Specific BODs through a Utility

In some cases (for example, when initializing an integration), you may need to manually generate certain BODs. You can use the Replication Document Manual Request Utility to do this.

Preventing a BOD From Replicating

If you have a BOD that is still under development, you can include it in the ESB replication category but select Skip Method or Skip Table, as appropriate, to prevent it from replicating.

Related Topics

Maintaining BODs

Deleting BODs

Viewing Received and Sent BODs

Behind the Scenes: How the System Generates a BOD

Replicating Data to External Systems That Do Not Use Infor BOD Formatted XMLs