Tools Menu

Management Console

Launch the Management Console in a web browser, which enables you to view the current status of the engine, to start or stop specific routes or communication points, and to view messages currently held in the engine.

EDI Designer

EDI Designer is used to create the definition of the messaging system that you want to parse or create.

The message definition defines the structure and separators of the messaging system and is the information that engines need to create valid messages. The definition also contains information on how to validate incoming messages. Once completed, the message definition can then be loaded into EDI Explorer, or used to create a parser control file (for use in the C++, COM or Java dynamic engines), a dynamically generated Active X object, or certain static Java classes.

EDI Explorer

EDI Explorer allows the visual creation and testing of messages. It requires a message definition (for example, a definition created in EDI Designer), and follows the structure defined in that definition. EDI Explorer can connect to an external system to send and receive messages over TCP/IP.

EDI Explorer is an easy to use application used for building and testing EDI messages. Explorer will load a Symphonia 3 message definition file (an S3D file), and allow the user to create messages from the definition. It allows these messages to be placed in a text file, or to be sent over a communications system, such as TCP.

Map Designer

Map Designer (Mapper) enables you to quickly create mapping specifications between input hierarchical data type definitions and output hierarchical data type definitions. Currently, these hierarchical data type definitions may be XML schemas, XML DTDs, or EDI message definitions.

The mapping specification can then be used to map actual input instances to output instances. An instance of an EDI message definition refers to a flat wire message, while an instance of an XML, schema or DTD refers to an XML document. The Mapper supports the following EDI messaging standards: HL7, X.12, HIPAA, EDIFACT, UB92, ASTM, NCPDP as well as custom definitions. Map Designer also supports XML W3C DTDs and Microsoft® compatible schemas.

Many applications refer to the same information using different labels. For example, a patient's cultural background may be called 'Ethnicity' in one application but referred to as 'Race' by another. Map Designer efficiently maps message structures to each other so the information they contain can be understood by all applications that refer to them.

The use of the Mapper is summarized as follows:

• Once a message structure has been defined by EDI Designer, it is imported into the Map Designer.
• Map Designer hosts two panels, one displaying the input message structure and the other the output structure. The user then drags a component from the input panel to its equivalent in the output panel.
• When all components have been connected this way, a Mapper Definition file (*.MDF file) is generated which maps information in an Input message to its equivalent location in the Output file.

XSD Generator

XSD Generator takes an XML document as input and generates an XSD schema based on the XML document. This utility is useful when using a Rhapsody component that generates an XML document based on the configuration of the component. For example, the Database communication point.

XSD Generator can also take an instance of the XML document and create the schema required for use in the Mapper or another component.