Abstract:
A message transformation selection tool and method for use in a distributed message processing system running applications on subsystems using incompatible message formats, selects the most appropriate output message format for a given input message format. Firstly, the tool determines compatibility of each field of the input message format with fields of all possible output message formats. Next, it statistically analyses the values of message fields in messages stored in message logs for each of the subsystems. On the basis of this analysis, the tool selects the best fit output message into which to transform a given input message.

Description:
FIELD OF THE INVENTION  
         [0001]    The present invention relates to the transformation of message formats between components of a distributed data processing system and, in particular, to a tool for selecting message transformations.  
         BACKGROUND OF THE INVENTION  
         [0002]    Distributed data processing systems communicate by the exchange of messages. Various products are known which allow messages to be transmitted between heterogeneous platforms, such as IBM&#39;s MQSeries products “IBM” and “MQSeries” are both trade marks of International Business Machines Corporation). Such transmission is not intelligent in that neither the data content nor the internal format of the messages are transformed so as to be intelligible to applications on the receiving platform. This is because the format of these messages may be inherent to particular nodes of the system or the format may be determined by the specific different applications which are running on the system. In both cases, it is necessary to transform message formats originating from one system component (operating system or application) to formats compatible with other system components. Such transformations have long been known in the art, for example, conversion between different date conventions (DD/MM/YY to MM/DD/YYYY, say).  
           [0003]    Although such conversion could be performed by the application programs themselves, in one recent development in the message processing art, so-called message brokers have been developed to route messages intelligently between nodes and to transform the message formats as required.  
           [0004]    Two recent message broker products from IBM, MQSeries Integrator Versions  1  and  2 , both include a so-called “formatter” which transforms messages from one application format into another The formatter used in both the IBM products is based on one licensed from New Era of Networks, Inc ( NEON) and is described in International Patent Application WO 98/30962 “Method for content based dynamic formatting for interoperation of computing and EDI systems”. As one example, these products can transform messages in fixed format, (where each message, and each field within the message, has a specified length in bytes) into standard XML BOD (Business Object Descriptor) messages (XML is the abbreviation for Extended Markup Language).  
           [0005]    A general illustration of message transformation is shown in FIG. 1 from which it can be seen that transformation includes both mapping (i.e. relocating) fields in an output message and translation (i.e. expressing values in a different code or convention). An input message  10  originating in a first application consists of four fields  11 , named FIELD 1  to FIELD  4 . A formatter  12 , with access to prestored format definitions and transformation rules for different applications in a database  13 , maps FIELDS  1 ,  2  and  3  to different relative positions in an output message  14 , converting them and FIELD  4  as necessary to a different form which will be recognised by a second application. The reformatted output message  14  may then be passed to and processed by the second application.  
           [0006]    However, in these systems, the transformations between different types of messages must be predetermined manually and loaded into the transformation engine (formatter and database). This can lead to a very large number of transformations having to be considered as the number of message formats and types of message, even in one system or application, can be very large, particularly if every conceivable transformation must be explicitly recorded. The NEON system reduces this problem somewhat by breaking down messages into basic named canonical (meta-data) components, common to different applications and formats and by using matching of canonical data to determine the appropriate output message conversion. Even this information about transformations at the canonical level, although cutting down the sheer volume of individual transformation pairs to be stored, must still be determined in advance and entered manually. This task is usually performed by a System Administrator using a graphical user interface to enter complete message definitions for different applications and the specific correspondence with format meta-data components into the formatter&#39;s database. Typical meta-data could include such terms as “floating point number”, “tag” or “delimiter”.  
         SUMMARY OF THE INVENTION  
         [0007]    There is thus a need to reduce the burden on the system administrator of defining and manually entering permitted message transformations within the business application architecture.  
           [0008]    Accordingly, the present invention provides a message transformation selection tool for use in a distributed message processing system, said system including message transformation means for transforming an input message in any of a plurality of formats recognised by one component of said system into an output message in one of a plurality of different formats recognised by another component of said system and a message log for storing representative samples of messages processed by the respective system components; said selection tool comprising: means for determining compatibility of each field of each of said plurality of input message formats with one or more fields of said plurality of output message formats; means for statistically analysing numerical values of message fields in messages stored in said message log; and selection means responsive to said compatibility determination and said statistical analysis to select the best fit output message field into which to transform a given input message field.  
           [0009]    Preferably, the tool is implemented as a computer program.  
           [0010]    Although the tool may be provided separately, the invention may also be incorporated within a message broker and the invention comprises message brokers including such a tool.  
           [0011]    According to another aspect, the present invention also provides a method of selecting a message transformation in a distributed message processing system, said system including message transformation means for transforming an input message in any of a plurality of formats recognised by one component of said system into an output message in one of a plurality of different formats recognised by another component of said system and a message log for storing representative samples of messages processed by the respective system components; said selection tool comprising: means for determining the compatibility of each field of each of said plurality of input message formats with one or more fields of said plurality of output message formats; means for statistically analysing the values of message fields in messages stored in said message log; and selection means responsive to said compatibility determination and said statistical analysis to select the best fit output message field into which to transform a given input message field.  
           [0012]    Preferably, the tool and method of the invention statistically analyse the numerical distribution (i.e. rate of occurrence) of values in the message fields, equivalent to producing a histogram. The values can be anything which may be coded in the fields, such as colors or sizes of goods. Alternatively, they may be prices or other numerical ranges. Selection is on the basis of the best fit distribution for all compatible fields.  
           [0013]    The tool may entirely determine the transformation to be used or it may simply rank the output message fields in accordance with the statistical analysis, leaving it to the system administrator to make the final selection.  
           [0014]    Compatibility is most easily determined from meta-data, which may be stored for the various fields in a message repository manager which is part of the overall system. This meta-data may include the range of numerical values found in particular fields and may also include the full value distribution statistics for the field.  
           [0015]    A basic check for compatibility, based on meta-data, can compare the types of field. Thus, “char”, “short”, “int” and “long” are all potentially compatible field types, “float” and “double” are compatible types, “char[ 32 ]”, “char[ 256 ]” and “string” are also examples of compatible character types.  
           [0016]    Additionally, a looser compatibility selection could be made on the basis of field names being identical, synonymous or otherwise lexically similar. 
       
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0017]    The invention will now be described by way of example only, with reference to a preferred embodiment thereof, as illustrated in the accompanying drawings, in which:  
         [0018]    [0018]FIG. 1 illustrates the operation of a known formatter with which the present invention may be used;  
         [0019]    [0019]FIG. 2 is a block diagram of a message transformation selection tool according to the present invention and of a message broker system with which the tool is designed to work;  
         [0020]    [0020]FIG. 3 is a flow diagram illustrating the operation of a message analyser forming part of the selection tool of FIG. 2.  
         [0021]    [0021]FIG. 4 shows a typical histogram of the rate of occurrence of possible values in a message field; and  
         [0022]    [0022]FIG. 5 is a flow diagram illustrating the operation of a semi-automated messager reformatter for selecting the best fit output message field for a given input message field, according to the present invention. 
     
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT  
       [0023]    In FIG. 2, a message broker  20 , which may be IBM&#39;s MQSeries Integrator, Version  2 , is employed by an enterprise to integrate two systems A and B, shown at  21  and  22 , from different suppliers in order to be able to run applications which together perform a business transaction such as an order entry or an update of customer details.  
         [0024]    Taking a concrete example, let us say that we wish to integrate an application running under the IBM CICS transaction processing environment, written in Cobol running on System A, with one from another ERP (Enterprise Resource Planning) system supplier, running on System B (‘CICS’ is a trademark of International Business Machines Corporation.) The Cobol application sends a message in a proprietary (fixed) format whereas the other supplier uses the self-defining XML (Extended Markup Language) message format, to represent a business transaction as a Business Object Descriptor (BOD), which is a standard of the Open Applications Group (http://www.openapplications.org/) and which builds on XML.  
         [0025]    Part of the task of the enterprise&#39;s system administrator is to define message transformations which map between the message formats used on one system and those used in the other system.  
         [0026]    This person has to:  
         [0027]    1. Decide which COBOL applications need to communicate with which business application on the other ERP system;  
         [0028]    2. Decide which set of fixed format messages to use to send the information out of the Cobol application;  
         [0029]    3. Decide which BODs to send to the other ERP system;  
         [0030]    4. Decide on the detailed reformatting from the data fields held in the Cobol, fixed format message to fields in the BOD, and implement this reformatting by specialising a message broker processing node.  
         [0031]    The invention assists the administrator in taking the decision about which fields match each other in step 4 and thus acts as a productivity tool.  
         [0032]    Returning to FIG. 2, type metadata (eg ‘string’, ‘lint’, ‘float’) etc is available for each field in the message to be mapped and is stored in a message repository manager  25 , which is part of the broker. This metadata is augmented by a message analyser  26  which statistically analyses the contents of logs  27  and  28  which contain representative samples of messages in systems A and B respectively. Such logs are routinely kept in messaging systems.  
         [0033]    The operation of the Message analyser  26  is as follows, as further illustrated in the flow diagram of FIG. 3  
         [0034]    For each message format selected in step  30 :  
         [0035]    Load message format description (step  31 );  
         [0036]    Open the appropriate ‘message warehouse’ logs  27  or  28 , which contain a representative sample of messages ( step  32 ) in the respective system.  
         [0037]    For each field (step  33 ):  
         [0038]    Discover the range of values in the field ( step  34 ). For numbers this will be a numeric range. For strings this may simply catalogue the different strings which occur. If a string field is known to contain ‘strings which represent numeric values’ like “21”, then a conversion can be done on those values;  
         [0039]    Record statistics about the rate of occurrence of the each value in the field (step  35 ) to produce data equivalent to the histogram shown in FIG. 4;  
         [0040]    Using the statistics, decide what other field types the data in this field is compatible with step  36 ). For example, any number which can be represented as a ‘short integer’ could also be represented by an ‘integer’ or a ‘long integer’ (but the reverse is not true).  
         [0041]    Augment the message meta-data in the message repository manager  25  for that field with the respective statistics and information about compatibility (step  37 ).  
         [0042]    The metadata from MRM  25  is applied, together with an input message from System A, to a semi-automated message reformatter consisting of compatibility determination means  23 , transformation selection means  24  and a conventional message format mapping component  29 , which supplies the appropriate output message field. Although shown as part of the message broker  20 , the compatibility determination means  23 , transformation selection means  24  and message analyser  26  could be a tool, separate from the main message broker for assisting a manual selection by the system administrator.  
         [0043]    The operation of the reformatter is described in the flow diagram of FIG. 5.  
         [0044]    In response to receipt of an input message from system  21   
         [0045]    (step  51 ), a message format description for Message Format A is loaded (step  52 );  
         [0046]    Message format descriptions for messages recognisable by system  22  (Message Format B) are effectively read from the Message Repository Manager  25  ( step  54 );  
         [0047]    For each field Fa from Message Format A ( step  53 ):  
         [0048]    For each field Fb in Message Format B:  
         [0049]    if the type of Fa is compatible with the type of Fb (step  55 ), then perform a ‘value comparison’ (step  56 ). This compares the statistics recorded for the values in Fa for the values in Fb, and assigns a numerical score for compatibility ;  
         [0050]    Rank the fields in Message Format B with respect to Fa using the numerical score (step  57 ); in most cases only one field will have a high score; all the others will have a score close to zero: in that case the highest ranked Fa can safely be mapped to Fb.  
         [0051]    There are a variety of ways of measuring the similarity of two sets of data values; they are usually based on the idea of comparing the statistical distributions of values in each of the datasets.  
         [0052]    For example, if we characterise the statistics of the logs for :  
         [0053]    Field a in Log  1  as the histogram Ha 1 (x);  
         [0054]    Field b in Log  2  as the histogram Hb 2 (x);  
         [0055]    where Hmn(x) is just the count of occurrences of x in field m of Log n,  
         [0056]    then there are many ways of creating a similarity measure sim(Ha 1 , Hb 2 ).  
         [0057]    One known approach would be to use Bayes theorem to define the sim(Ha 1 , Hb 2 ) as the probability that Hal and Hb 2  both come from the same source distribution.  
         [0058]    In summary, in the example of the invention described with reference to the drawings, compatible fields are first selected. Then a similarity measure for each pair of fields is derived, based on the statistical analysis of the contents of the two logs. For each field in the input message log, the output message fields are then ranked in order of decreasing similarity. Finally, the transformation is either automatically made to the most similar field or the administrator is allowed to select from the most promising candidates.