Configuring the Production
This article describes how to configure a production to include an EDIFACT routing interface. It discusses tasks that you perform on the Interoperability > Configure > Production page. The following article describes additional tasks.
Adding EDIFACT Business Services
Add one EDIFACT business service for each document type that the production will receive. If this document type arrives via multiple communication modes (for example, via FTP in addition to TCP), you will need a business service for each communication mode.
Adding EDIFACT Routing Processes
To add a routing process to a production, use the Business Process Wizard as usual; see Configuring Productions. Select EnsLib.MsgRouter.VDocRoutingEngineOpens in a new tab from the Process Class list.
Adding EDIFACT Business Operations
Add an EDIFACT business operation for each output destination.
You might also want to add business operations to handle bad messages (for background, see “Business Processes for Virtual Documents” in Using Virtual Documents in Productions).
Connecting the EDIFACT Business Hosts
After you add the EDIFACT business hosts, connect these items as follows:
For the routing rule set, make sure that the Target field is the EDIFACT business operation.
Configuring the Business Hosts
You should examine all the settings listed in “Reference for Settings” and set them as needed.
A couple of key settings for an EDIFACT business service are as follows:
Doc Schema Category — Specifies the schema category to assign to the inbound documents. InterSystems IRIS® requires this information for validation and for search table indexing.
Search Table Class — Specifies the class to use to index virtual properties in the inbound documents.
For a File or FTP business service, also consider whether you need to configure the Reply Target Config Names field.
Also be sure to configure the Separators setting.