JP2013025769A - Message transmission/reception system using soap communication - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a message transmission/reception system which is suitably used for a circulation BMS correspondence EDI system for efficiently transmitting/receiving a message.SOLUTION: A transmission side SOAP client 10 transmits an input message to be transmitted to an SOAP server 13, and the server 13 notifies a Push mail server 15 of the arrival of the message. The mail server 15 confirms the content of the message, and then transmits Push mail for making a message reception request to a reception side SOAP client 18, and the reception side client 18 receives the Push mail, and then registers incoming information in a message registration history DB19 owned by itself, and determines whether or not the message is a reception object message according to the message classification priority of the registered message by referring to a message classification priority parameter owed by itself on the basis of the registered message classification, and when the message is the reception object message, acquires the reception object message from the SOAP server, and notifies a terminal 22 of a reception side manager of the result.

Description

  The present invention relates to a message transmission / reception system using SOAP communication, and in particular, receiving processing of various messages including ordering processing using SOAP communication of a distribution BMS compatible EDI (Electronic Data Interchange) system for distribution industry. The present invention relates to a message transmission / reception system using SOAP communication automated according to the above.

  The above-mentioned distribution BMS (Business Message Standard) is part of the “Distribution System Standardization Project” of the Ministry of Economy, Trade and Industry. This defines the message items that are necessary when dealing with a transaction.

  In general, the specification of SOAP communication reception processing is a PULL type that requires an inquiry from the reception side. One of the standard communication methods of the distribution BMS compatible EDI system is SOAP communication. However, in the above-described SOAP communication reception specification, in a system using SOAP communication, even if a message to be received exists in the server. If the client does not access the server, the message cannot be found on the server. In the ordering business where processing speed is important in the distribution business, the above-mentioned specification of SOAP communication becomes a bottleneck in performing the business.

  As a technique related to the present invention, a technique related to an “order receiving system using a network” is described in Patent Document 1 and the like.

JP 11-39396 A

  The above-mentioned distribution BMS EDI system using the conventional SOAP communication has a problem that it cannot know that a message exists in the server unless the client side accesses the server. Since it is not determined whether or not the message should be received immediately, there is a problem that the message cannot be efficiently transmitted and received.

  The object of the present invention is to solve the problems of the distribution BMS compatible EDI system using the conventional SOAP communication technology described above, and to send and receive messages efficiently and suitably for use in the distribution BMS compatible EDI system. The object is to provide a message transmission / reception system using SOAP communication.

  According to the present invention, the object is that a sending-side SOAP client, an EDI center including a SOAP server and a Push mail server, a receiving-side SOAP client, and a terminal used by a receiving-side administrator are connected via a network. In the message transmission / reception system using SOAP communication, the transmitting-side SOAP client transmits the input message to be transmitted to the SOAP server, and the SOAP server notifies the Push mail server of the arrival of the message, After confirming the content of the message, the Push mail server sends a Push mail for message reception request to the receiving-side SOAP client, and when the receiving-side SOAP client receives the Push mail, the message registration status of its own client is received. Incoming information is registered in the database, and based on the registered message type, referring to the message type priority parameter file of the client, whether the message is a reception target message according to the message type priority of the registered message If the message is a reception target message, the reception target message is acquired from the SOAP server, and notification is sent to the terminal used by the reception side administrator that the message is registered.

  According to the present invention, it is possible to efficiently perform message reception processing with the shortest lead time.

It is a block diagram which shows the structural example of the message transmission / reception system using SOAP communication by one Embodiment of this invention. It is a figure which shows the structure of the log | history table of the message registration log | history database with which a receiving-side SOAP client is provided. It is a figure which shows the example of the parameter file which set the priority level for every message classification. It is a figure which shows the example of the property file which set the threshold of the priority level of the message classification for every supplier information. It is a flowchart explaining operation | movement until the message transmitted from the transmission side SOAP client is received by the reception side SOAP client.

  Hereinafter, embodiments of a message transmission / reception system using SOAP communication according to the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a block diagram showing a configuration example of a message transmission / reception system using SOAP communication according to an embodiment of the present invention.

  The message transmission / reception system using SOAP communication shown in FIG. 1 receives and holds a message from the SOAP client 10 and a transmission-side SOAP client 10 that transmits an input message to be transmitted to a network such as the Internet 11. EDI center 12 having SOAP server 13 and Push mail server 15 to be transmitted to a network such as the Internet 17, and messages sent from Push mail server 15 of EDI center 12 are received and registered, and the priority for each message type is checked. As a result, the reception-side SOAP client 18 for notifying the terminal 22 used by the reception-side administrator that the message is registered via the network such as the Internet 21 and the terminal used by the reception-side administrator 22 and Equipped and are configured.

  As described above, the SOAP server 13 provided in the EDI center 12 has the reception monitoring program 14, and the Push mail server 15 has the Push mail transmission WEB service 16. The reception-side SOAP client 18 includes a message registration history database 19 and a reception monitoring program 20.

  In the above description, the SOAP clients 10 and 18 on the transmission side and the reception side are not shown, but are information represented by a PC including a CPU, a main memory, a storage device such as an HDD, an input device such as a keyboard and a mouse, and a display device. A processing device, which is stored in a storage device, loads a program necessary for the present invention into the main memory, and the CPU executes the program, thereby constructing functions in the embodiments of the present invention described later. The SOAP server 13 and the Push mail server 15 installed in the EDI center 12 are also information processing apparatuses having the same configuration as described above, and are necessary for the present invention stored in the storage device as described above. By loading the program into the main memory and executing the program by the CPU, functions in the embodiments of the present invention described later are constructed.

  Further, in the configuration example of the message transmission / reception system using the SOAP communication according to the embodiment of the present invention shown in FIG. 1, three different networks such as the Internet are provided, but these networks may be the same network. .

  FIG. 5 is a flowchart for explaining the operation until the message transmitted from the transmission-side SOAP client 10 is received by the reception-side SOAP client 18, which will be described next.

(1) The transmitting-side SOAP client 10 transmits a message to the SOAP server 13 in the EDI center 11 using the HTTP PUT method to register it (step 50).

(2) The incoming call monitoring program 14 of the SOAP server 13 in the EDI center 11 detects the registration of the message, and uses the supplier information, message type, and registration time as arguments of the Push mail transmission WEB service 16 of the Push mail server 15. After setting, the Push mail transmission WEB service 16 of the Push mail server 15 is called (step 51).

(3) The Push mail server 15 causes the Push mail transmission WEB service 15 to check the content of the message, and transmits the information of the destination notified from the SOAP server 13 to the receiving SOAP client 18 as the Push mail of the message reception request. (Step 52).

(4) When the incoming monitoring program 20 of the receiving-side SOAP client 18 detects the arrival of the Push mail, it registers the detected incoming information of the Push mail in the message registration history database 19. The configuration of the message registration history database 19 will be described later with reference to FIG. 2 (step 53).

(5) After registering the message information in the message registration history database 19, the receiving-side SOAP client 18 checks whether the priority level according to the message type is equal to or higher than the threshold (step 54).

(6) If it is determined in step 54 that the priority level of the registered message according to the message type is equal to or greater than the threshold value, the uploading / receiving SOAP client 18 sends an HTTP GET method to the SOAP server 13 of the EDI center 12. Is requested to acquire a message, and the message is acquired, and the record of the corresponding message in the message registration history database 19 is updated. The priority based on the message type will be described later with reference to FIGS. 3 and 4 (steps 55 and 56).

(7) If it is determined in step 54 that the priority level of the registered message according to the message type is less than the threshold value, the receiving-side SOAP client 18 refers to the message registration history database 19 and performs reception history check processing. Do. The check processing here is based on the data from the previous month of the current month in the message registration history database 19 to obtain the average reception time of message reception using the registered message type ID as a key, and the obtained average This is a process of comparing the reception time with the current time and checking whether or not the current time has passed the average reception time (step 57).

(8) If it is determined in step 57 that the current time has not passed the average reception time, nothing is done and the current time is the same as the average reception time, or if the current time has passed the average reception time, reception is performed. The side SOAP client 18 refers to the message registration history database 19 and checks the set incoming notification date (steps 58 and 59).

(9) If it is determined in step 59 that the current date / time is outside the incoming call notification time, an e-mail is sent to the terminal 22 used by the receiving administrator that the message is registered at the latest incoming call notification time from the current date / time. (Step 60).

(10) If it is determined in step 59 that the current date and time is within the incoming call notification time, a notification that the message is registered is immediately sent to the terminal 22 used by the receiving administrator by mail (step 61).

(12) After sending the incoming notification that the message is registered to the receiving-side administrator by the processing of step 60 or 61, the receiving-side SOAP client 18 receives the incoming notification time of the corresponding record in the message registration history DB 19 Is updated (step 62).

  FIG. 2 is a diagram showing the structure of the history table of the message registration history database 19 provided in the receiving-side SOAP client 18.

  The data in the history table of the message registration history database 19 shown in FIG. 2 is registered by the incoming call monitoring program 20 upon detecting the arrival of a Push mail. The illustrated history table includes a transmission source GLN (Global Location Number) that is a carrier code of the message transmission source, a message type ID indicating the type of the message, the date and time when the message was registered, and the set reception side administrator. A plurality of records each having a notification date and time that is an incoming notification time for notifying the arrival of a message and a message reception date and time are stored.

  FIG. 3 is a diagram showing an example of a parameter file in which a priority level for each message type is set. This parameter file is a file that the receiving-side SOAP client 18 has.

  The parameter file of the priority level for each message type shown in FIG. 3 stores a plurality of records in which the message type ID and its priority level are paired. In the illustrated example, the priority level of the message with the message type ID “001” is “5”, and the priority level of the message with the message type ID “002” is “2”. A record that the priority level of the message with the type ID “003” is “3.5” is stored.

FIG. 4 is a diagram illustrating an example of a property file in which a threshold level threshold of a message type for each supplier information is set. This property file is a file that the receiving-side SOAP client 18 has, and is provided for each message type for each supplier information. And in the example shown in FIG.
In the property file in which the threshold of the priority level of the message type for each supplier information shown in FIG. 4 is set, the incoming notification time and the message type ID, which are information on the date and time for notifying that the customer has received an incoming call. The message automatic reception priority level, which is information on the threshold of the priority level, is held. The example shown in FIG. 4 is an example of a property file having a message type ID “003”, and is registered with a message priority level threshold of 3.

  The receiving-side SOAP client 18 refers to the files shown in FIGS. 3 and 4 in the processing from step 54 to step 56 in the flow shown in FIG. 5, and in this case, the setting example shown in FIGS. When a message with the message type ID “003” is registered, since the priority level is 3.5 and the threshold is 3, the message is automatically received.

  In addition, when the message with the message type ID “002” is registered in FIGS. 3 and 4, the receiving-side SOAP client 18 receives the message automatically because the priority level is 2 and the threshold is 3. Without processing, the processing of the next step 57 is performed.

DESCRIPTION OF SYMBOLS 10 Transmission side SOAP client 11, 17, 21 Internet 12 EDI center 13 SOAP server 14 Incoming monitoring program 15 Push mail server 16 Push mail transmission WEB service 18 Receiving side SOAP client 19 Message registration history database 20 Incoming monitoring program 22 Receiving side administrator Used by

Claims (2)

In a message transmission / reception system using SOAP communication in which a sender SOAP client, an EDI center including a SOAP server and a Push mail server, a receiver SOAP client, and a terminal used by a receiver administrator are connected via a network.
The sender SOAP client sends the inputted message to be sent to the SOAP server,
The SOAP server notifies the Push mail server of the arrival of the message,
After confirming the content of the message, the Push mail server sends a Push mail requesting message reception to the receiving SOAP client,
When the receiving SOAP client receives the Push mail, it registers incoming information in the message registration history database of the client, and refers to the message type priority parameter file of the client based on the registered message type. Then, according to the message type priority of the registered message, it is determined whether the message is a reception target message. If the message is a reception target message, the reception target message is acquired from the SOAP server, and the message is registered. A message transmission / reception system using SOAP communication, characterized in that a terminal administrator uses a notification that the reception side administrator is informed.   When the registered SOAP client is not a reception target message, the reception side SOAP client obtains an average reception time of message reception based on data from one month before the current month of the reception date and time of the message registration history database, Compare the obtained average reception time with the current time, and if the current time is the same as the average reception time, or if the current time has passed the average reception time, check the incoming notification date in the message registration history database, 2. The terminal according to claim 1, wherein, when the date and time is outside the incoming notification time, the terminal administrator uses the notification that the message is registered at the latest incoming notification time from the current date and time. A message transmission / reception system using SOAP communication.

Images