JP5041633B2 - EDI translation system with translation function as agent and server system and client system used in this system - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to an agent server system, an agent client system, and an EDI translation system including them for an electronic data exchange system performed between governments, between companies, and between governments.
[0002]
[Prior art]
According to the Ministry of International Trade and Industry's definition of the “Computer Interoperability Environment Development Committee” (Heisei 1), EDI (Electronic Data Interchange) is defined as “standard messages for transactions between different organizations via communication lines. Exchange between computers (including terminals) using common rules (as widely agreed as possible). In other words, EDI is the exchange of information necessary for establishing negotiations and transactions between organizations such as companies between parties based on standard rules using computers and communication lines (“ EDI Basics "published by the Industrial Information Promotion Center). That is, the EDI system is a systemization of the concept of EDI.
[0003]
Conventionally constructed EDI systems have a message conversion function based on various rules, a communication function via a communication line, and a registration function / inquiry function related to its operation. For this reason, EDI could not be introduced without prior arrangements between the parties based on standard rules.
[0004]
The EDI system is introduced in a form in which an EDI center is prepared and the parties (client agent computer) are connected via the EDI center (central management), and each party (client agent) has EDI. There is a form (distributed management) in which the same functions as the center are provided and the parties are directly connected.
[0005]
In the case of centralized management, there is an operational problem that the operation status between the EDI center and the other party cannot be grasped. In the case of distributed management, since the standard contract between the parties is managed by each party, there is a problem in operation management in which consistency between the parties must be ensured when there is a change.
[0006]
[Problems to be solved by the invention]
In conventional data communication operations using EDI, standard rules are defined in the layer of transfer procedures and data conversion methods, and a part to be selected and applied from the contract among the traders, a part to be negotiated independently EDI is made by adjusting the EDI, and EDI is performed based on it.
[0007]
Specifically, “preparation of EDI regulations” and “procedures and arrangements regarding introduction and operation” as preparatory work, “management of EDI regulations” and “management of EDI operation status and response to failures” after the start of work. As an adjustment item. These four items make the introduction and operation of EDI difficult.
[0008]
The “EDI Agreement Arrangement” and the “Procedure and Arrangement Regarding Installation and Operation” require coordination among the connected users, leading to longer and more complicated time to install, making EDI installation difficult. In particular, when the business relationship of EDI is multiple (N) vs. multiple (M), there are multiple “management of EDI rules”, making operation management difficult.
[0009]
As a solution, a method of centrally managing the EDI center in the middle of data exchange in order to realize “management and unification of EDI rules” is currently used. However, in terms of the introduction, although it was reduced by conforming to the standard, the coordination between the connected parties, such as the agreement (mapping) of the data conversion method between the connected parties, was not lost. In addition, since the connection person is connected to the EDI center, only the failure with the EDI center can be recognized, and it cannot be detected that the EDI partner has failed with the EDI center. Could not be found in a short time.
[0010]
The present invention has been made to solve such problems, and uses an agent technology that has both ease of introduction and operation in an EDI mechanism performed among a plurality of persons based on an agreement through a network. An object of the present invention is to provide an EDI system.
[0011]
[Means for Solving the Problems]
An agent server system according to the present invention comprises an EDI system for exchanging electronic data between a sender and a receiver, a data dictionary unit for managing data items handled by EDI conversion as a common dictionary, and a user Dictionary providing means for receiving data dictionary from data dictionary part, conversion center table part for storing and managing user translation rules, conversion method registering means for receiving application for conversion method from user, data dictionary Conversion management means for managing the consistency between the copy section and the conversion center table section, an address information section for managing users and their locations and use environments, a transfer management means for delivering user data to the user's hand, and use A history log section that stores the processing / operation status of the user and a log management means that manages the conversion / transfer operation status as a log Centralized management of data dictionaries when users use EDI and provision to users, information registration and centralized management for each individual conversion in the conversion center table, centralized management of user network information, transmission of users It is characterized by centralized management of usage information of the entire EDI system by transfer control for sending data to the receiving party, and accumulation and management of operation status logs.
[0012]
In the EDI system for exchanging electronic data between a sender and a receiver, the agent client system according to the present invention is a dictionary that receives a data dictionary from a server and passes it to the user when the user requests downloading of the data dictionary. Transfer means, conversion management means for registering and managing the conversion method between the user's business system and data dictionary, an individual conversion table section for storing the conversion method, business data format conversion and translation agent from the business system EDI transmission conversion means for transmitting data to the server, EDI reception conversion means for receiving business data from the translation agent server and converting business data format and providing business data to the business system, and use Log the conversion / transfer operation status It can be used as a window function for design, use application, and transmission / reception work when users use EDI, and at the start of use, a data dictionary is delivered to the user for conversion design, and a conversion method is provided. Registers and manages the conversion table, converts and transfers business data from the business system on the client side when used, and introduces EDI by providing a function to notify an error when an error is detected. It is easy to use and is characterized by distributed management of individual functions for each user.
[0013]
The present invention further relates to an EDI translation system for exchanging electronic data between a sender and a receiver. This system includes the server system and the client system described above, and serves as an EDI server. It is a translation function that combines the centralized management function and distributed management function as a client by combining agent technology and a simple operation protocol.
[0014]
The translation agent server according to the present invention is the translation agent server used in an EDI system including a sender system, a receiver system, and a translation agent server. A data dictionary part storing common data items, first correspondence data describing a correspondence relation between data items of data transmitted from the sender system and common data items stored in the data dictionary part, and the data A conversion table storing second correspondence data describing the correspondence between common data items stored in the dictionary section and data items of data to be transmitted to the receiver system, data transmitted from the sender system Receiving means for receiving data including items, common data stored in the data dictionary unit for data items of data transmitted from the sender system based on the first correspondence data stored in the conversion table First conversion means for converting into items, and the first conversion based on the second correspondence data stored in the conversion table A second conversion means for converting the common data item converted by the stage into a data item of data to be transmitted to the recipient system, and a data item to be transmitted to the recipient system converted by the second conversion means. Transmitting means for transmitting data including data items to the recipient system is provided.
[0015]
Another translation agent server according to the present invention is used in an EDI system including a sender system, a receiver system, and a translation agent server, and has a first data format. The first conversion means for converting the data of the second data format into the data of the second data format, the second conversion means for converting the data of the second data format into the data of the third data format, the sender system Receiving means for receiving data of the first data format transmitted from the first data format and data of the second data format received by the first converting means for receiving the data of the first data format received by the receiving means. And convert the data in the second data format to the second The switch means is converted into the data of the third data format, the data of the third data format and a transmitting means for transmitting to the receiver system.
[0016]
The present invention further provides a method for controlling the above-described translation agent server.
[0017]
DETAILED DESCRIPTION OF THE INVENTION
Embodiments of the present invention will be described below with reference to the accompanying drawings.
[0018]
FIG. 1 shows the overall configuration of an EDI (Electronic Data Interchange) translation agent system, and FIG. 2 shows the details of the EDI translation agent system shown in FIG.
[0019]
The EDI translation agent system (hereinafter referred to as EDI system) includes a translation agent server 3, a sender system 1 connected to the translation agent server 3 via a network, and a receiver system. 2 is included. In general, a plurality of sender systems 1 and a plurality of receiver systems 2 are connected to one translation agent server 3. Here, for convenience of explanation, one sender system 1 and one receiver system 2 are connected to the translation agent server 3. The sender system 1 has a business system 6, a design / conversion registration system 4, and a translation agent client 5. The receiver system 2 also has a business system 9, a design / conversion registration system 7, and a trans-agent client 8. The sender system 1 and the receiver system 2 exchange business data using the translation agent server 3 via the network.
[0020]
The translation agent server 3 centrally manages the format information, the user exchange information, and the connection information of the connection person. The translation agent clients 5 and 8 distribute and manage the support for introducing and using the EDI of the sender and the receiver and the exchange information for each user. The translation agent server 3 and the translation agent clients 5 and 8 work together to perform EDI electronic data exchange processing and management.
[0021]
First, the sender analyzes the transmission work, designs the rules used by the sender system 1 of EDI, and registers the designed rules in the design / conversion registration system 4.
[0022]
The receiver also analyzes the reception work, designs the rules used by the EDI receiver system 2, and registers the designed rules in the design / conversion registration system 7.
[0023]
When the individual registration work of the sender and the receiver is completed, the translation agent server 3 is linked with the translation agent client 5 on the sender side and the translation agent client 8 on the receiver side. The business system 6 of the sender system 1 and the business system 9 of the receiver system 2 can exchange data using the EDI system.
[0024]
A specific detailed flow will be described with reference to FIG. 2 based on a flow from introduction of EDI to operation management.
[0025]
First, a detailed flow for introducing EDI will be described.
[0026]
When the sender system 1 introduces EDI, it starts from the work of designing a conversion rule and registering the conversion rule in the design conversion registration system 4.
[0027]
At the time of design conversion registration, first, a data dictionary for each business ID is applied to the dictionary delivery means 17. The data dictionary is managed as a translation agent system, and information serves as a collection of items commonly used by each user, and is provided for each business ID.
[0028]
The dictionary delivery unit 17 requests the data dictionary for each business ID from the dictionary providing unit 26, receives the data dictionary for each business ID from the data dictionary unit 22, and provides the data dictionary to the design conversion registration system 4.
[0029]
The design conversion registration system 4 refers to the data dictionary provided from the dictionary providing means 26, associates the business data with the data dictionary, determines the use items of the data dictionary, and determines the conversion method of the business data and the data dictionary. I do. For example, it is assumed that there is an item “sales product number” in the business data and an item “product number” in the data dictionary. “Product number” in the data dictionary is determined as a use item, and it is determined to convert data on “sales product number” in business data into data on “product number”.
[0030]
In the design conversion registration system 4, the conversion management means 18 applies for a conversion method (data dictionary use item number, business data item number, and business ID).
[0031]
The conversion management means 18 registers the requested conversion method in the individual conversion table section 20 and issues a management request to the conversion method registration means 27, issues a conversion ID to the design conversion registration system 4, and thereafter With this ID, it is possible to recognize the conversion method between the item number of the data dictionary and the item number of the sender's business data.
[0032]
The conversion method registration unit 27 registers the conversion method and the user in the conversion center table unit 23, and registers the physical address and logical address of the translation agent client 5 in the user address information unit 24.
[0033]
When the receiver system 2 also introduces EDI, it starts from conversion rule design and registration to the design conversion registration system 7.
[0034]
At the time of design conversion registration, first, a data dictionary for each business ID is applied to the dictionary delivery means 34.
[0035]
The dictionary delivery unit 34 requests a dictionary for each business ID from the dictionary providing unit 26, receives the data dictionary for each business ID from the data dictionary unit 22, and provides the data dictionary to the design conversion registration 7.
[0036]
The design conversion registration system 7 refers to the data dictionary, associates the business data with the data dictionary, determines the items used in the data dictionary, and determines the conversion method between the business data and the data dictionary. For example, it is assumed that there is an item “purchased product number” in the business data and an item “product number” in the data dictionary. “Product number” in the data dictionary is determined as a use item, and it is determined to convert the data about “product number” into “purchased product number” in the business data.
[0037]
The design conversion registration system 7 applies to the conversion management means 35 for a conversion method (data dictionary use item number, business data item number, and business ID), and the conversion management means 35 applies it to the individual conversion table section 37. And a management request is made to the conversion method registration means 27.
[0038]
The conversion method registration means 27 registers the conversion method and user in the conversion center table unit 23, and registers the physical address and logical address of the translation agent client 8 in the user address information unit 24. SDI and recipient EDI are possible.
[0039]
The conversion method is a method in which each user is distributedly managed by a client, and information managed by the client is centrally managed by a server.
[0040]
The above is a flow when a sender and a receiver start anew. As a feature of this system, the exchange of business data between the sender and the receiver has been registered in the conversion management means of both. There is no need to synchronize, and there is no work even if the number of business partners for data exchange increases, and the conversion method can be changed if it is already registered in the conversion management means. Even from time to time, there is no influence on the conversion method of the business partner, and there is no need for an agreement on the data conversion method between the connected parties, and the complicated "procedures and arrangements for installation and operation". It becomes a released method.
[0041]
Next, an operation flow of the translation agent when the sender and the receiver perform EDI between each other is shown.
[0042]
When the business data and the conversion ID created by the business system 6 on the sender side are sent to the EDI transmission conversion means 19, the EDI transmission conversion means 19 sends a conversion table including the conversion ID from the individual conversion table unit 20 using the conversion ID. A search is performed, the business data is converted into a standard format in the agent by using the searched conversion table, and the transfer management means 30 is transferred. For example, when business data created in the business system 6 is created in a format unique to the business system 6, the EDI transmission conversion means 19 converts the unique format into an XML (eXtensible Markup Language) format. . The business data in the XML format is transferred to the transfer management means 30.
[0043]
The standard format is composed of a header part and a data part. In the header part, the logical address of the EDI transmission conversion means 19, the logical address of the EDI reception conversion means 36, the transmission time, and the business ID are set. , Business data, item information, and data dictionary use item number are set.
[0044]
Within the translation agent, business data is transferred in this standard format.
[0045]
The transfer management unit 30 requests the user address information unit 24 from the logical address of the EDI reception conversion unit 36 in the header portion of the standard format to receive a physical address, and transfers the business data from the physical address to the EDI reception conversion unit 36. .
[0046]
The EDI reception conversion means 36 confirms that the logical address of the EDI reception conversion means 36 in the header portion of the standard format is business data addressed to itself.
[0047]
Next, the individual conversion table unit 37 is retrieved from the business ID in the header part, and the business data in the data part in the standard format is converted into a format for the business system 9 using the retrieved conversion table to convert the EDI reception. Accumulated in the means 36. For example, business data in XML (eXtensible Markup Language) format is converted by the EDI reception conversion means 36 into a unique format used in the business system 9. The original format of the business system 9 may be the same as or different from the original format of the business system 6.
[0048]
The business system 9 of the recipient can make a reception request to the EDI reception conversion means 36 with the business ID and receive business data from the EDI reception conversion means 36.
[0049]
The operation flow when an error occurs when the receiver system 2 passes business data to the receiver system 2 is shown below.
[0050]
If an error occurs when the EDI reception conversion unit 36 passes the business data to the business system 9, the EDI reception conversion unit 36 notifies the transfer management unit 30 of the error information by a system message 39.
[0051]
The transfer management means 30 notifies the EDI transmission conversion means 19 of the sender system 1 of error information as a system message 40, and notifies the log management means 29 of error information of the EDI reception conversion means 36 of the business system 9, The log management unit 29 accumulates information in which an error has occurred in the EDI reception conversion unit 36 of the recipient system 2 in the history log unit 25.
[0052]
The business system 6 of the sender system 1 can recognize that the business data has not arrived at the receiver by receiving the notification of the error information from the EDI transmission conversion means 19 by the system message 41, so that the EDI counterpart It becomes possible to solve the problem in the case of performing centralized management in which it was not possible to detect that a failure has occurred between the destination and the EDI center.
[0053]
Further, the operation status such as error information of the receiver and the sender is accumulated and managed in the history log unit 25, so that the business system 9 confirms the information in which the error has occurred in the translation agent client 8 of the receiver system. be able to.
[0054]
When the business system 9 inquires the operation management unit 38 about the history log, the operation management unit 38 requests the log management unit 29 to provide the history log.
[0055]
The log management unit 29 extracts a history log from the history log unit 25 and provides the history log to the operation management unit 38, and the operation management unit 38 provides the history log to the business system 9.
[0056]
The business system 9 can discover problems between the business system 9 and the translation agent client 8 by analyzing the history log information, and improve the operability by addressing the problems. Can be planned.
[0057]
The operation flow of the sender system 1 and the receiver system 2 when the format of the business data created by the business change of the business system 6 of the sender system 1 is changed is shown below.
[0058]
When the configuration of business data created by a business change in the business system 6 of the sender system 1 is changed, the changed business data is associated with the data dictionary in the design conversion registration 4, and the data dictionary usage item number is changed. And the change of the conversion method of the item number of the business data and the usage item number of the data dictionary is determined.
[0059]
In the design conversion registration 4, the conversion management means 18 is requested to change the conversion method (data dictionary use item number, business data item number, and business ID).
[0060]
The conversion management means 18 updates the updated conversion method to the individual conversion table unit 20 and makes an update request to the conversion method registration means 27 by the conversion method and the user. The conversion method between the number and the item number of the sender's business data can be used in the updated method.
[0061]
When the business data created by the business system 6 of the sender system 1 and the conversion ID are requested to be sent to the EDI transmission conversion means 19, the EDI transmission conversion means 19 searches the individual conversion table unit 20 by the conversion ID, and the conversion thus found is searched. The business data is converted into a standard format in the agent using the table, and the transfer management means 30 is transferred.
[0062]
Although the data to be transferred is business data whose items have been changed, it is converted into a standard format and transferred within the translation agent. Therefore, the translation agent server 3 and the translation agent client 8 on the receiver side are transferred. Is converted and accumulated as before the change, and is not affected by the format change of the sender system 1.
[0063]
As described above, even when the sender system 1 changes the business system 6 due to the change of the business system 6, the receiver system 2 can be dealt with only by changing the sender system 1 without any change. It solves the problem of “management of EDI rules” that must ensure the consistency between the parties in the event of a conflict, and improves operability.
[0064]
The operational flow of the recipient system 2 and the operation flow of the translation agent when the recipient system 2 moves from the operational location and resumes EDI are shown below.
[0065]
When the recipient system 2 moves from the operating location, when the translation agent client 8 of the recipient system 2 is stopped and restarted, a system message 39 of activation notification is transmitted to the transfer management means 30.
[0066]
At that time, the logical address and physical address of the recipient system 2 are notified as information of the system message 39, and the transfer management means 30 sends the logical address of the recipient system 2 from the user address information section 24 based on the system message 39. Check the physical address.
[0067]
The transfer management means 30 detects that the physical address of the recipient system 2 is different from the user address information unit 24 and updates the physical address.
[0068]
As described above, when the recipient system 2 moves from the operation location, the physical address changes, and the EDI operation management work that the recipient requests the EDI operator to change the physical address and performs the work is performed. By automating with the agent function, the simplicity of management work is raised with respect to the problem of “management of EDI rules”.
[0069]
As described above, according to the present invention, in the case of centralized management, it is impossible to detect that a failure has occurred between the EDI center and the counterpart of the EDI. Easily solves the problems of EDI installation and operation that are complicated and difficult, such as "procedures and arrangements for installation and operation", "management of EDI regulations", "management of EDI operation status and response to failures" EDI can be realized.
[0070]
【Effect of the invention】
As described above, according to the present invention, the dictionary and user information for electronic data exchange are centrally managed by the agent server as common management, and the user when the user introduces and uses electronic data exchange. The conversion application management function and individual conversion function, which are interfaces, are distributed and managed on the client side, and the electronic data exchange can be used in conjunction with the server and client. This simplifies installation and operation when users use electronic data exchange. For example, it is possible to easily start electronic data exchange even between individual companies, and to newly join a procedure. Is simple, leading to expansion of the range of electronic data exchange between companies.
[Brief description of the drawings]
FIG. 1 is a block diagram showing a configuration of a translation agent system.
FIG. 2 is a block diagram showing in detail the translation agent system shown in FIG. 1;
[Explanation of symbols]
1 Sender system
2 Recipient system
3 Translation Agent Server
4,7 Design / conversion registration system
5,8 Translation Agent Client
6,9 Business system
17, 34 Dictionary delivery means
18, 35 Conversion management means
19, 36 EDI transmission conversion means
20, 37 Individual conversion table section
21,38 Operation management means
22 Data dictionary part
23 Conversion center table section
24 User address information section
25 History log section
26 Dictionary provision means
27 Conversion method registration means
28 Conversion management means
29 Log management means
30 Transfer management means
39, 40, 41 System message

Claims (1)

In a translation agent server used in an EDI system for exchanging electronic data between a sender and a receiver,
A data dictionary part for managing data items handled by EDI conversion as a common dictionary;
A dictionary providing means for a user to receive a data dictionary from the data dictionary part;
A conversion center table for storing and managing user translation rules;
A conversion method registration means for accepting a conversion method application from a user;
An address information section for managing the location and environment of the user;
A transfer management means for delivering data from one user to the other user;
A history log section that stores the processing and operation status of users;
Log management means for managing the operation status of conversion / transfer as a log,
The transfer management means further receives error information notified when an error occurs on the other user side, notifies the one user, and notifies the log management means of the error information. To do,
The log management means further accumulates the error information in the history log section.
Translation agent server.

Images