Adaptive transaction message format display interface for use in a message data exchange system

#This invention concerns a system for adaptively displaying transaction message data for use with an integration engine exchanging data between different computer systems using different data formats.

#Known systems monitor communication of messages in an integration engine (a system for exchanging data between different computer systems using different data formats) using trace data. The trace data typically contains either a view of message data in a Hex representation or a view of the data in a non-Hex (e.g., an ASCII) representation without providing a user with an option to select the type of representation for display. Additionally, in known integration engines, a trace function is typically turned on and off via a command line interaction. A user desires to look at trace data without Hex characters (non-Hex trace data) currently included in trace data as an easy to read representation of message data being communicated by an integration engine. The non-Hex trace data is also used to facilitate troubleshooting and may be provided to message source or destination entities for review. Conversely, support personnel use a Hex trace data representation of message data being transmitted for troubleshooting and debugging purposes.

#In known systems, both Hex and textual (e.g., ASCII) representations of message data being transmitted are typically included in the same file and in order to produce a desired output it is necessary to manually copy individual portions of trace data and paste the individual pieces back together. Also known systems typically require user command line intervention to debug program or trace execution steps. Further known systems require a user to manipulate command line programming to gather data and decide prior to initiating a trace function how message trace data is to be represented (if there is a choice). Known systems further provide only one view of traced message data that is traced and do not have the flexibility to readily present the same data in different views. Alternatively known systems only provide a view of message trace data in a format that includes both Hex and non-Hex format data. A system according to invention principles addresses these deficiencies and related problems.

#FIG. 1 shows a system for adaptively displaying transaction message data for use with a data exchange system for exchanging data between different computer systems using different data formats, according to invention principles.

#FIG. 2 shows a flowchart of a process for switching between Hex and non-Hex message data representations employed by a system for adaptively displaying transaction message data, according to invention principles.

#FIG. 3 shows a flowchart of a process for saving non-Hex trace message data employed by a system for adaptively displaying transaction message data, according to invention principles.

#A system adaptively displays transaction message data for use with an integration engine debugging and trace function that enables a user to view message trace information, via a Graphical User Interface (GUI), in either Hexadecimal (Hex) or character (ASCII) or Binary representations. An integration engine is a system for exchanging data between different computer systems using different incompatible data formats. The GUI enables flexibility in capture of the trace data and enables a user to toggle between alternate representations of the data. This enables different users of an integration engine who have different requirements for receiving information and format of received information, to dynamically identify data to be collected as well as the format in which the collected data is to be represented. The GUI trace function enables a user to dynamically toggle between image views with and without Hex representation of data. Specifically, the system supports dynamic toggling between the Hex representation with text data, Hex representation without text data, text data without Hex representation and a binary view of data via a graphical user interface.

#The system automatically generates message trace data and provides a user with multiple views of the data (e.g., including one or more of binary, character or Hex representation of message data) without the need for a source of a message to retransmit the message with particular integration engine processing operations, e.g., selected by setting particular message data indicators. This advantageously reduces time involved in troubleshooting a message transaction performed by an integration engine. A user is also able to establish a configuration preference indicating a default display data format representation and view for presenting data upon initiating access to the system. A view preference is maintained for each individual user thereby eliminating a need for a user to repetitively select a preferred view. A default display data format representation may comprise one or more of, binary, character or Hex representation of message data. The system advantageously provides an adaptive view of message data facilitating faster more efficient troubleshooting and associated problem solving concerning message data processing.

#A processor, as used herein, operates under the control of an executable application to (a) receive information from an input information device, (b) process the information by manipulating, analyzing, modifying, converting and/or transmitting the information, and/or (c) route the information to an output information device. A processor may use, or comprise the capabilities of, a controller or microprocessor, for example. The processor may operate with a display processor or generator. A display processor or generator is a known element for generating signals representing display images or portions thereof. A processor and a display processor may comprise a combination of hardware, firmware, and/or software.