Creating requisites for non-transactional replication

Non-transactional replication refers to replication based on XML-formatted documents. This includes both BOD-based replication and non-BOD-based replication.

To enable non-transactional replication, set up the system using this process.

Use the Service Configuration Manager to specify one or more "bootstrap" configurations.
Use the Replication Categories form to verify that a replication category exists that meets your needs for replication.
For non-transactional replication, you can use the ESB category that is provided.
If no category exists that meets your requirements, or if the ESB category is being used for a different type of replication on your system, you must create a new category.
Caution:
We strongly recommend that you contact Infor Consulting Services for assistance before creating (or attempting to create) your own replication categories.

Verify that the Replication Transfer Type field is set to IDO XML.
Use the Intranets form to create an intranet to be used specifically for transactions based on XML-formatted documents.

Any intranet used for non-transactional replication must have these specifications, at a minimum:

Intranet

Specify the name to identify the intranet, for example: InforBUS

Description

Optionally, provide an appropriate description.

External

Select this check box.

Transport

Select the basic mode of transport to use for replication transactions: ESB or HTTP.

ION Transfer Type

If you selected ESB as the mode of Transport, select ION Messaging.
If you selected HTTP as the mode of Transport, select ION Outbox.

Other active fields on the Intranets form are optional. For information about them and how they are used, see the help topics for the individual fields.
Use the Sites form to create a logical "site" to be used for BOD transactions.

At a minimum, provide this information:

Site

Specify a name to identify this site as your BOD-based site; for example: InforBUS.

Site Name and Description

Optionally, provide an appropriate site name and description.

On the System Info tab, make these settings:

Time Zone

Select the time zone to be used by this site.

Intranet Name

Select the intranet you created in the previous step.

Message Bus Logical ID

Optionally, provide the logical ID for this site.
The logical ID is the identifier by which this site is recognized in all transactions involving BODs. For more information, including the format to use for this entry, see Formatting logical IDs.

On the Site User Map tab, make these settings:

From Site

Specify the local site, for example, DEFAULT.

User Name

Specify the user ID that is to be used to send replication documents to the application's outbox. 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 Vendor or Site Developer editing permissions.

Other active fields on the Sites form are optional.
On the Replication Rules form, create a new rule.
At a minimum, provide this information:

Source Site

From the drop-down list, select the local site (typically, DEFAULT).

Target Site

From the drop-down list, select the site that you configured in the previous step.

Category

From the drop-down list, select the replication category you are using (as defined on the Replication Categories form.

Description

Optionally, provide a brief description to be used internally to help identify the purpose or use of the rule.

Interval Type

Specify any option EXCEPT Transactional.

Optionally, provide addition information using the other fields and options on this form.
Regenerate the replication triggers.

Note:

In some cases (for example, when initializing an integration), you might need to manually generate certain BODs. To do this, use the Replication Document Manual Request Utility.
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.