The SEF File

While you can use the EDI to XML module to convert individual EDI documents to XML, the module's main purpose is to allow you to develop a set of conversion settings that can be captured and then reused to convert to XML other EDI documents with the same structure. These settings are saved in a Standard Exchange Format (SEF) file (.sef) that is created when you save your work in the EDI to XML editor.

The SEF file contains information about any EDI definitions that you might have imported and changed, as well as changes to the XML Converter properties default values. The structure information for supported EDI dialects and versions remains with the XML Converter, ensuring that the SEF file remains very small.

Once you create a SEF file, you can use it to convert other EDI documents in one of these ways:

Referencing it in the converter:EDI URI scheme - the user= property allows you to specify the URI of a SEF file. (The easiest way to make changes to the converter: URI scheme is through the XML Converter properties. See Specifying XML Converter Properties and EDI XML Converters Properties Reference for more information on these topics.)

Invoking the setEDIExtension() method that is part of the XML Converter API. This method is available in both Java and .NET interfaces. See How XML Converters are Used in Stylus Studio for more background information on the DataDirect XML Converter in Stylus Studio, or refer to the DataDirect XML Converter documentation that is part of your Stylus Studio installation - \components\XML Converters for .NET and \components\XML Converters for Java where you installed Stylus Studio.

Open the SEF file in Stylus Studio and create a new scenario using a new EDI document as the source document you want to convert to XML.

< Previous| Next >

The SEF File

Building Workflow Applications with XML

ADO to XML

Biotechnology & Pharmaceuticals

Building DataDirect XML Converter Applications with Stylus Studio

Stylus Most Wanted