Replicating Data as BODs to Other BOD-Enabled Applications

This application can use Infor BOD formatted XML documents to replicate data to and from other BOD-enabled applications. These prerequisites must be met:

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 apply to replication with applications that are not BOD-enabled.
For those products, see Replicating Data to External Systems That Do Not Use Infor BOD Formatted XMLs.
The generic External Financial Interface does not use this process.
The Infor CloudSuite Industrial Enterprise Financials interface does not use this process. See the documentation for that product.

To set up this application to work with BODs:

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:
- In the Replicator/Inbound Bus Configurations field, specify all of the configurations that can receive inbound or outbound messages from other sites on the intranet. The Replication Document Outbox form at each site collects outbound BODs for that site. The Replication Document Inbox form at each site collects inbound BODs for that site.
- In the ReplQListener Queue Servers field, set up a queue server name for every intranet in your system.
  Generally, the queue server name is set to localhost\private$ which uses the standards private message queues named inbound and outbound on the utility server. However, if you have specified a Queue Server Name on the Intranets form, that name is used to build a path. For example, utilityserver3\private$\MyQueues results in the use of the queue names MyQueues_inbound and MyQueues_outbound.
Note: If you are upgrading from a previous version and you already have replication set up through a “bootstrap” site, it will still work as it did in the previous version. The Replicator/Inbound Bus Configurations field contains one site set as the Master Site, and the ReplQListener Queue Servers field has the Default field selected.
On the Intranets form, create a new intranet for Infor ION (bus). Specify this information:

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 theConfiguration Guide for Xi Platform.
On the Sites or Sites/Entities form, create a logical "site" for Infor ION. Specify this information:

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.

Type

Specify Site.

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 CloudSuite Industrial 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.
On the Sites or Sites/Entities form, configure the local site recordto generate and/or receive business object documents (BODs. Specify this information):

Message Bus Logical ID

Specify the logical ID for the site, which identifies the CloudSuite Industrial site to ION. Make sure it is set up as specified in Formatting Infor Logical IDs. The logical ID specified here must match the application type and instance defined in ION Connect for this site.

Tenant ID

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.
On the Replication Categories form, the ESB category is used for replicating BODs.

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

See 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.
On the Replication Rules form, create a new rule. Specify this information:

Source Site

Specify the local site that you configured in Step 4.

Target Site

Specify the ION site you created in Step 3.

Category

Specify ESB.

Interval Type

Specify any option except Transactional.
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.

Note:

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.
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.