String The full URL of the SEF file from which you want to create a flat file schema. For example, if the SEF file is located in the /pub directory of the WmEDIProduction package on the Rubicon server, you type:

If the SEF file is on a local file system, use the SEFfilename input parameter instead of url and method.

String The HTTP method; specify GET. If you specify url, you must specify method.

Document (optional) Authorization information that the HTTP service will submit if the resource specified in url is protected. The format of auth is:

String Type of authentication you want the HTTP service to use when it submits this request.

Currently, only basic authentication is supported. If you are accessing a protected resource, set auth to Basic.

String The user name that the SEFParse service will submit when requesting a protected resource.

String The password associated with user.

Document (optional) Data that you want the HTTP service to submit with the HTTP request. Specify your data in one of the following elements:

Document An IS document (IData object) that contains the name/value pairs that you want the HTTP service to submit to the resource in url. Create one element for each name/value pair, where name is the element's name and value is the value of the element.

Note that when you use args, the HTTP service will:

String A string of text that you want the HTTP service to submit to the resource in url.

If you use string to submit data, make sure that you specify the string exactly as you want it presented in the HTTP request. Also make sure you url-encode the contents of string.

String Table Data that the HTTP service will use to construct a query string to submit to the resource specified in url. Note that the bytes, input parameter is similar to args, but bytes allows you to submit unnamed values in a query string, not just name/value pairs.

Specify each value you want to submit in a separate row in the String Table. When you specify the String, ensure:

Note that when you use bytes, the HTTP service will:

Document (optional) Fields that you want to explicitly override in the HTTP request header that the HTTP service issues.

Specify one element in the headers IS document (IData object) for each header field that you want to set, where:

If you do not set headers, the HTTP service will use its default header values.

String (optional) The full path and file name of the SEF file on your local file system. If the SEF file is located on a Web server, use the url and method parameters instead of SEFfileName.

String The EDI transaction set name (e.g., 850) or TRADACOMS file name (e.g., INVOIC), for which you want to create a flat file schema. Specify only a single value.

String (optional) Whether you want the SEFParse service to create envelope segments in the output flat file schema objects.

The SEFParse service does not create the envelope segments (i.e., ISA/IEA, GS/GE, UNB/UNZ, UNG/UNE, STX/END, BAT/EOB, MHD/MTR) in the output flat file schema object. This is the default.

The SEFParse service does create the envelope segments in the output flat file schema object.

String (optional) Whether you will use the generated flat file schema to parse documents that are considered large. Specify false or true. For more information about large document handling, see the webMethods Module for EDI Installation and User’s Guide.

You will not use the generated flat file schema to parse large documents. This is the default.

You will use the generated flat file schema to parse large documents.

String (optional) The version of the EDI standard. For TRADACOMS, specify the version of the TRADACOMS File document type.

String The fully qualified name that you want to assign the flat file schema that you are creating. For all supported EDI standards except TRADACOMS, use the following naming convention for targetSchema:

where:

For example: EDIFFSchema.X12.V4010:T850

For the TRADACOMS EDI standard, the wm.b2b.edi:SEFParseservice creates a temporary flat file schema. Use the following naming convention for targetSchema:

where:

This temporary flat file schema contains all the messages contained in the TRADACOMS file. Because the flat file parser (the wm.b2b.edi.tradacoms:convertToValues service) cannot always properly parse this temporary flat file schema, you should then execute the wm.b2b.edi.tradacoms.ui:modifyTradacomsSchema service to split the flat file schema into one flat file schema per MHD segment in the TRADACOMS file. This temporary flat file schema will be deleted upon successful execution of the wm.b2b.edi.tradacoms.ui:modifyTradacomsSchema service.

If you use the migration utilities to move templates from version 4.x to flat file schemas in 6.0.x, the utility creates the flat file schemas using the naming convention described above. For more information about migrating 4.x templates to flat file schemas, see webMethods Module for EDI Installation and User’s Guide.

String The name of the Integration Server package in which to create the flat file schema.

String The name of the flat file dictionary to hold the record, field, and composite definitions for this flat file schema.

String (optional) Whether you want the SEFParse service to overwrite entries in the target dictionary if they already exist.

Do not overwrite flat file dictionary entries in the target dictionary if the entries already exist. This is the default.

Overwrite existing dictionary entries with values specified by this SEF file. If you specify true for overwriteDictionary, the SEFParse service ignores the sourceDictionaries parameter.

String List (optional) Names of flat file dictionaries in which to search for definitions of records, fields, and composites. If a definition already exists, refer to it instead of creating a new entry in the targetDictionary.