Ensemble EDIFACT Development Guide
Additional Steps
[Back] [Next]
Go to:

This chapter discusses the additional steps needed to add EDIFACT routing interfaces to a production. It includes the following topics:

Be sure to perform these tasks in the same namespace that contains your production. When you create rule sets, transformations, and search tables, do not use reserved package names; see Reserved Package Names in Developing Ensemble Productions.
Also see Overriding the Validation Logic in Ensemble Virtual Documents.
Loading EDIFACT Schemas into Ensemble
To load an EDIFACT schema into Ensemble, use the EDIFACT Schema Structures page, described in the chapter Available Tools.”
For information on creating custom schema categories, see Creating Custom Schema Categories in Ensemble Virtual Documents.
Defining Routing Rule Sets for EDIFACT
For general information on defining business rules, see Developing Business Rules.
When you create a routing rule set for an EDIFACT routing interface:
Defining DTL Data Transformations for EDIFACT
Your routing rules might need one or more data transformations.
For general information on defining DTL data transformations, see Developing DTL Transformations.
When you create a DTL data transformation for EDIFACT documents:
Use the EDIFACT Document Viewer Page to test your transformations, as described in the chapter Available Tools.”
To integrate the DTL data transformation in the production, enter its full package and class name in the Transform field of a routing rule set.
Defining EDIFACT Search Tables
The EDIFACT search table class, EnsLib.EDI.EDIFACT.SearchTable, automatically indexes the EDIFACT document ID, which it gives the name Identifier.
If you need more items to search, you can create a subclass. The subclass inherits the Identifier property, plus the infrastructure that makes search tables work. For details, see Defining a Search Table Class in Ensemble Virtual Documents.
Note the following points specific to EDIFACT: