Abstract:
A method for translating to and from an hierarchical information system, comprises identifying a non-hierarchical information system containing information stored in a non-hierarchical manner; developing a translation map that identifies organizational and content based rules for translating the non-hierarchical information into an hierarchical information system; and translating the non-hierarchical information for storage into the hierarchical information system according to the rules for translating.

Description:
COPYRIGHT REFERENCE  
         [0001]    Two Appendixes are included in this application that contain material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the Appendixes, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever.  
         BACKGROUND OF THE INVENTION  
         [0002]    The present invention relates to a system and method for translating information, to or from, an hierarchical information system.  
           [0003]    Legacy systems are systems that support business function, many of which have been in use for many years. These systems usually store information, and communicate with each other, using non-hierarchical information systems, such as linear strings (i.e. legacy messages).  
           [0004]    Modern systems often use an hierarchical system to store information and communicate with each other. Hierarchical system typically store information in a tree structure of objects, each object having specific attributes, and where each object may be linked to other objects. XML (Extensible Markup Language) is an example of an hierarchical system.  
           [0005]    The need arises for an interface to translate information between systems. Simple systems that translate between linear strings are well known. However, there is a need for products that can read the objects of an hierarchical system and perform the required data transformations. MERCATOR, for example, could be used if first the object model were translated into a standard, predictable data stream. However, the effort to translate the object model into this intermediate format is similar to the effort required to translate the object model into a form directly usable by the legacy system. In addition, MERCATOR is implemented as a single-threaded DLL (Dynamic Linked Library) in Windows NT, which may have an adverse impact on overall system performance and throughput.  
         BRIEF SUMMARY OF THE INVENTION  
         [0006]    A first aspect of the invention is a method for translating to and from an hierarchical information system, comprising identifying a non-hierarchical information system containing information stored in a non-hierarchical manner; developing a translation map that identifies organizational and content based rules for translating the non-hierarchical information into an hierarchical information system; and translating the non-hierarchical information for storage into the hierarchical information system according to the rules for translating.  
           [0007]    A second aspect of the invention is computerized method for translating to and from an hierarchical information system.  
           [0008]    A third aspect of the invention is a system for translating to and from an hierarchical information system, comprising means for identifying a non-hierarchical information system containing information stored in a non-hierarchical manner; means for developing a translation map that identifies organizational and content based rules for translating the non-hierarchical information into an hierarchical information system; and means for translating the non-hierarchical information for storage into the hierarchical information system according to the rules for translating.  
           [0009]    A fourth aspect of the invention is a system for translating to and from an hierarchical information system, comprising a first computer system having a memory for storing information in an hierarchical information system; an interface coupled to the first computer system, the interface having means for identifying a non-hierarchical information system containing information stored in a non-hierarchical manner, developing a translation map that identifies organizational and content based rules for translating the non-hierarchical information into an hierarchical information system, and translating the non-hierarchical information for storage into the hierarchical information system according to the rules for translating; and a second computer system coupled to the interface, the second computer system having a memory for storing information in a non-hierarchical information system.  
           [0010]    A fifth aspect of the invention is a method for translating to and from an hierarchical information system, comprising translating data from an object model into a legacy message.  
           [0011]    A sixth aspect of the invention is a method for translating to and from an hierarchical information system, comprising translating data from a legacy message model into an object.  
           [0012]    A seventh aspect of the invention is a method for translating to and from an hierarchical information system, comprising identifying an hierarchical information system containing information stored in an hierarchical manner; developing a translation map that identifies organizational and content based rules for translating the hierarchical information into an non-hierarchical information system; and translating the hierarchical information for storage into the non-hierarchical information system according to the rules for translating.  
           [0013]    An eighth aspect of the invention is a computerized method for translating to and from an hierarchical information system, comprising identifying an hierarchical information system containing information stored in an hierarchical manner; developing a translation map that identifies organizational and content based rules for translating the hierarchical information into an non-hierarchical information system; and translating the hierarchical information for storage into the non-hierarchical information system according to the rules for translating.  
           [0014]    A ninth aspect of the invention is a system for translating to and from an hierarchical information system, comprising means for identifying an hierarchical information system containing information stored in an hierarchical manner; means for developing a translation map that identifies organizational and content based rules for translating the hierarchical information into a non-hierarchical information system; and means for translating the hierarchical information for storage into the non-hierarchical information system according to the rules for translating.  
           [0015]    A tenth aspect of the invention is a system for translating to and from an hierarchical information system, comprising a first computer system having a memory for storing information in a non-hierarchical information system; an interface coupled to the first computer system, the interface having means for identifying an hierarchical information system containing information stored in an hierarchical manner, developing a translation map that identifies organizational and content based rules for translating the hierarchical information into a non-hierarchical information system, and translating the hierarchical information for storage into the non-hierarchical information system according to the rules for translating; and a second computer system coupled to the interface, the second computer system having a memory for storing information in an hierarchical information system. 
       
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0016]    These and other features and advantages of the invention will become apparent upon a review of the following detailed description of the presently preferred embodiments of the invention, when viewed in conjunction with the appended drawings.  
         [0017]    [0017]FIG. 1 shows the application architecture and components of an interface.  
         [0018]    [0018]FIG. 2 shows the application architecture and components of another interface.  
         [0019]    [0019]FIG. 3 is an illustration showing the transformation of attributes from an hierarchical system to a non-hierarchical system, and the reverse. 
     
    
     DETAILED DESCRIPTION OF THE INVENTION  
       [0020]    The present invention includes an interface that supports the specific data transformation requirements of translating information from a specific hierarchical system (also referred to as an object model), such as XML data, into a non-hierarchical system, such as linear strings (i.e., custom legacy messages), or into a different specific hierarchical system. The interface performs the mapping, lookups and derivations necessary to format legacy messages in a manner consistent with the legacy applications.  
         [0021]    The application architecture and components of the interface are shown in FIG. 1. The components, and additional optional components, are shown in FIG. 2. As will be apparent to those of ordinary skill in the art, the interface may be software implemented on a general purpose computer, or may be dedicated hardware, or a combination thereof. Furthermore each individual component may be software implemented on a general purpose computer, or may be dedicated hardware, or a combination thereof. All components of the interface are described first, followed by a section describing the application flow. A subsequent section includes a summary of the data transformations supported by the interface.  
         [0022]    As schematically shown in FIG. 1, the interface  1  includes a coordinator  2 , a searcher  4 , and a writer  5 . Also shown in the figure are a map file  3 , a toolkit  7 , a technical architecture framework  8 , a legacy system  9 , and a server  6 .  
         [0023]    In addition to those parts shown in FIG. 1, FIG. 2 schematically shows another server  12  that may use a different object model, a toolkit  7 ′ for this different object model, a searcher  4 ′ for this different object model, a second legacy system  9 , a ruler  10 , and a responder  11 .  
         [0024]    The map file defines the attributes that are to be obtained from the object or IDL (interface definition language) structure and used in the construction of legacy messages. The map file defines the attribute location (in each object in the object model), the format of the attribute values as they should appear in the legacy message, and the order in which the attribute values should appear in the legacy message. The map file may be viewed as a series of commands, which instruct the coordinator on how to construct the legacy message from the objects.  
         [0025]    The coordinator controls the process of reading the map file and using the searcher and optional ruler to obtain information to send to the writer. The coordinator orchestrates the translation, resolution, derivation, message construction, and message delivery processes. The coordinator includes a map interpreter, which interprets the commands in the map file. Preferably the coordinator is developed using JAVACC, a SUN MICROSYSTEMS product. Given a grammar that describes the syntax used in the map file, JAVACC can be used to create the coordinator and allow map files to contain commands that access the searcher, ruler and writer.  
         [0026]    The searcher provides an interface that is used by the coordinator and the ruler to obtain attribute information within each object. The coordinator uses commands from the map file to translate data (attributes) from an object model to the legacy system attributes. The coordinator executes rules as they are read from the map file. The coordinator uses the searcher to locate attributes used in a command. For example, if a command requires a calculation using attributes in an object, the coordinator would use the searcher to obtain these attributes and perform the calculation.  
         [0027]    The writer formats attributes passed by the coordinator and uses them to the construct the message that is sent to the legacy system.  
         [0028]    The optional responder returns confirmations from the legacy system to the system that initiated the transaction. If the initiating system is a server, the responder converts the legacy response to an XML message. For example, systems using the IDL interface will receive responses in the form of IDL structures.  
         [0029]    The following is an example of how the system shown in FIG. 2 may operate. A request is made of the interface via a CORBA IDL interface. Upon receipt of the request, the interface creates a new coordinator passing either the XML string or the IDL defined structure, and starts the coordinator.  
         [0030]    The coordinator creates a new searcher, passing in the object model to be searched. The coordinator creates a new ruler, passing in the previously created searcher. The ruler will use the searcher if necessary during execution of its rules.  
         [0031]    The coordinator then requests the target system identifier (e.g. legacy system) of the searcher. The coordinator will create a new writer, passing the target system identifier. The target system identifier is required so that the writer deposits the constructed message on the appropriate legacy queue.  
         [0032]    The coordinator requests the map file of the map loader. If the map loader has the requested map file cached, the memory-resident map file is returned to the coordinator. If the map is not loaded, the map loader loads it and returns it to the coordinator. The map loader is an optional component that only carries out this function, and advantageously prevents the need to reload map files that have been previously loaded.  
         [0033]    The coordinator (via the map interpreter) reads the map file and determines that an attribute from an object model is needed. The coordinator (via the map interpreter) makes a request of the searcher to get the needed attribute information. The searcher finds and returns the requested attribute.  
         [0034]    The coordinator (via the map interpreter) tells the writer to add the obtained attribute information to the message under construction. The writer formats the attribute information as defined by the map file and then appends the formatted attribute to the message under construction.  
         [0035]    The coordinator reads the map file and may encounter a command that invokes a rule. In this case, the coordinator makes a request of the ruler to execute the specified rule. The ruler makes a request of the searcher to get, if necessary, attribute information needed during execution of the rule. The searcher finds and returns the requested attribute. The coordinator tells the writer to add the obtained attribute information to the message under construction. The writer formats the attribute information as defined by the map file and then appends the formatted attribute to the message under construction.  
         [0036]    At the end of the map file, the coordinator tells the writer to complete the message under construction and to send it to the appropriate legacy system. The writer makes a request of the technical architecture (also referred to as an underlying architecture) to package the message, for example, as a queued message (for IBM MQ Series, or MICROSOFT MSMQ), and deposit it on the appropriate legacy system queue. The technical architecture creates a new message using the application-defined message content and deposits the message on the appropriate legacy queue.  
         [0037]    In a preferred embodiment, the memory address of each object is retained as a legacy message is constructed, reducing the time necessary for the reading of additional attributes needed to construct the legacy message.  
         [0038]    [0038]FIG. 3 is an illustration showing the transformation of attributes (data) from an hierarchical system (left) to a non-hierarchical system (right), which in this illustration is a linear string. The individual attributes of the objects in the hierarchical system are represented by letters, while attributes in the linear string are represented by numbers. The interface can read the attributes of the objects, and translate them (from letters to number in this illustration), and write them into a linear string. The linear string may then be passed to a legacy system. As illustrated, the reverse is also possible.  
         [0039]    Once the message has been processed by the legacy system, an optional response is returned to the technical architecture via a message queue. The technical architecture retrieves the message from the queue and creates an optional responder. The technical architecture passes the data portion of the message to the responder and instructs the responder to execute the process of returning the response.  
         [0040]    The responder creates an object and populates the object with data (attributes) expected by the server. This data includes attributes such as a group identifier that is generated by the legacy system, for example group enrollment of an insurance plan. In the case where the object model is XML, once the object has been populated, the responder creates an XML message. The responder queries the Proxy Pool Manager for a secure proxy to the appropriate server. The responder then uses the secure proxy to send the XML message response to the server.  
         [0041]    If, after a predefined number of tries, the proxy cannot be used to send the results to the server, a return code is passed back to the technical architecture and the message is sent to a resend queue to be delivered at a later time. Once the response has been successfully delivered to the server, a return code is passed back to the technical architecture and the message is deleted from the queue.  
         [0042]    The application architecture is designed to handle the following categories of data transformations: simple mapping, constants, code lookups, derived rule, multiple source locations (plan modeling), and rate information fields (when the data contains information relating to a service, such as insurance).  
         [0043]    Simple mapping means mapping fields that can be mapped directly from an object attribute to a legacy message field without any additional mapping logic.  
         [0044]    Constants are fields in the legacy message that are required and are always populated with the same information. For example, a field that describes the type of transaction would always contain an ‘E’ for electronic since the framework is an electronic means of creating the message.  
         [0045]    Code lookups are fields that require a translation from how an attribute is described in the hierarchical system, and how the same attribute is described in a legacy message.  
         [0046]    A derived rule is a field that is extracted from the object model and translated to the legacy message fields based on rules (such as business rules) as defined in the ruler.  
         [0047]    Multiple source locations are fields that involve the same process of a simple map. However, the source attribute may be located in different areas of the Vendor object model.  
         [0048]    Rate information fields are fields that are a specialized form of derivation rules that use name/value pairs. Unlike basic derived fields that rely on class names to find attributes in the object model, data values are used to search for rate attributes in the object model.  
         [0049]    The map file contains commands, which are defined in the order that the legacy message needs to be constructed. The following are examples of the script used for the different categories of data translations contained in a map file:  
         [0050]    Simple Mapping:  
         [0051]    write (search (case.member:CompanyName), “s30”);  
         [0052]    write (search (case.member:SubscriberNumber), “s9”);  
         [0053]    write (search (case.application:Deposit), “s10”);  
         [0054]    write (search (case.application:SubjectToErisa), “s1”);  
         [0055]    write (search (case: CaseInstallationID), “s20”);  
                                                                                                                                                                                             Use of Constants:                write (“ ”, “s5”);           write (“00000”, “s5”);           write (“H”, “s1”);           write (“999999”, “s6”);           write (“01”, “s2”);            Value Lookup:                table trans_table {                “1”, “0”; // None           “2”, “1”; // Life           “3”, “3”; // Health           “4”, “2”; // Both           default, “*”                };           string sval, Ival;           sval = search (case.caseinstallation:RetiredCoverageType);           Ival = lookup (trans_table, sval);           write (Ival, “s1”);           release (trans_table);            Derived Values:                if (search (case:PriorEffectiveDateCoverage) ==“”)                sval = “N”;                else                sval = “Y”;                write (sval, “s1”);            Occurrences:                int i, j;           i = count (case.member);           j = 1;           while (j &lt;= 1)           {                write (search(case.member(j):City), “s15”);           write (search(case.member(j):State), “s2”);           j = j + 1;                }            Other Operations:                //specialrule7 is defined in the Business Ruler class           write (ruler (specialrule7)),“s30”);           i = stringlength (sval);           Ival = midstring (sval, pos, length);           i = tointeger (sval);                      
 
         [0056]    The data from hierarchical information system may be sent to the interface from a specific vendor&#39;s server, where the vendor may be the same or different from the owner or user of the legacy system. Furthermore, multiple vendors, each having one or more servers, each containing data in one or more hierarchical systems, may send data to the interface. The interface may translate the data into a non-hierarchical system, such as a legacy system, or a different hierarchical system. Examples of hierarchical systems include XML and ChannelPoint (CP XML).  
         [0057]    Specifically, the interface may carry out one or more of the following:  
         [0058]    Retrieve values (data) from Vendor object model, using the Vendor toolkit (note: this model is not static between invocations).  
         [0059]    Concurrently support a different, dynamic map file for each legacy system output format.  
         [0060]    Support simultaneous access from server components.  
         [0061]    A toolkit is used to interpret the hierarchical system data exported from a server to the interface. Each toolkit may be specific to each hierarchical system, for example the MICROSOFT XML toolkit is specific to XML. On receipt of the exported hierarchical system data stream, the toolkit creates a copy of the original object (or objects). Data is then read out of this object (or objects) for translation into a custom legacy message.  
         [0062]    The present invention interface has a number of advantages:  
         [0063]    Adaptability to different legacy systems, including future systems.  
         [0064]    Extensibility to other applications requiring access to legacy systems.  
         [0065]    Maintainability and streamlined operational capability.  
         [0066]    Scalability to handle production-level volume requirements.  
         [0067]    Performance requirements to support multiple servers, using multiple Vendors.  
         [0068]    Re-usability to reduce complexity and implementation timeline.  
         [0069]    It is to be understood that a wide range of changes and modifications to the embodiments described above will be apparent to those skilled in the art and are contemplated. It is therefore intended that the foregoing detailed description be regarded as illustrative, rather than limiting, and that it be understood that it is the following claims, including all equivalents, that are intended to define the spirit and scope of the invention.