JP2006031173A - Compilation device and method and its program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To generate an executable program under the consideration of the balance of data storage and the processing performance of a business process from business process definition. <P>SOLUTION: A business process definition analyzing means 21 analyzes business process definition inputted from an input device 1, and an intermediate code generating means 22 generates an intermediate code. A Java(R) code generating means 23 generates a Java(R) code corresponding to the EJB of J2EE from an intermediate code generated by the intermediate code generating means 22. A Java(R) code compiling means 24 compiles a Java(R) code generated by the Java(R) code generating means 23, and generates an executable process execution program. In the case of an event classified as a long task, the processing of the generated process execution program is temporarily interrupted between the start processing of the event and the end processing of the event, and the data at the time of execution are stored. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a compiling device, method, and program, and more particularly, to a compiling device, method, and program that analyze a business process definition to generate an intermediate code and generate an executable program.

  Conventionally, in preparation for the occurrence of a failure, data being processed is stored in a database, a storage device, or the like during the execution of a program.

  For example, Patent Document 1 describes that a code for holding a state is automatically generated, and the automatically generated code for state management is processed in the execution of the method. That is, the state change management means statically analyzes a state that may be changed in each method based on the original program, and passes the analysis result to the state management code generation means. The state management code generation means automatically generates a code for holding the state based on the original program describing the interface definition information of the object created in advance and the processing provided by the interface. The program is executed by program execution means. The code for state management automatically generated by the state management code generation means is also processed in the execution of the method.

JP-A-10-320206

  However, the background art described above has the following problems.

  That is, in Patent Document 1, when the state of an object changes, attribute values that are the state of the object are automatically recorded and held in an external storage device. It means that it falls.

  In this way, if the saving process is emphasized, the execution speed of the process is sacrificed, and if the execution speed of the process is emphasized, the number of processes to be re-executed when a failure occurs increases. There is a trade-off between minimizing information lost in the event of failure and execution performance, and finding the optimal balance point has been a challenge.

  SUMMARY OF THE INVENTION An object of the present invention is to provide a compiling apparatus and method for generating an executable program in consideration of the balance between data storage and business process processing performance from a business process definition that solves the above problems and describes execution control. To provide a program.

  A compiling device according to a first aspect of the present invention is a compiling device for generating a program executable by inputting a business process definition, and means for analyzing an element group described in the business process definition; In the case of processing that completes in time (short task event), means for generating intermediate code indicating continuous execution, and in the case of processing (long task event) in which the element can cause a long waiting time Means for generating an intermediate code indicating that data is stored when processing is executed, and means for generating an executable program by compiling the generated intermediate code.

  A compiling device according to a second aspect of the present invention provides an intermediate code representing that the long task event is divided into an event start process and an event end process in the first invention, and the event start process and the event end process. Means for generating an intermediate code indicating that the data is stored between.

  A compiling device according to a third invention of the present application is a means for generating Java (registered trademark) code from the generated intermediate code in the first or second invention, and compiling and executing the generated Java (registered trademark) code Means for generating a possible program.

  The compiling device according to a fourth invention of the present application is characterized in that, in the first, second or third invention, the business process definition is described in Business Process Execution Language for Web Services (BPEL4WS).

  The compiling device according to the fifth invention of the present application is the Java (registered trademark) code corresponding to the Java (registered trademark) mechanism capable of persisting the object at the time of execution in the third or fourth invention. It is a registered trademark) code.

  The compiling device according to the sixth invention of the present application is a Java (registered trademark) mechanism that can perform object persistence at the time of execution in the third, fourth, or fifth invention. The Java (registered trademark) 2 Platform, It is characterized by being Enterprise Java (registered trademark) Beans (EJB) of Enterprise Edition (J2EE).

  A compiling method according to a seventh aspect of the present invention is a compiling method for generating an executable program by inputting a business process definition, the step of analyzing an element group described in the business process definition; In the case of processing that completes in time (short task event), a step of generating intermediate code indicating continuous execution, and in the case of processing (long task event) in which the element can generate a long waiting time Generating an intermediate code indicating that data is stored when the long task event is executed; and generating an executable program by compiling the generated intermediate code. .

  The compiling method according to the eighth invention of the present application is the intermediate code representing that the long task event is divided into an event start process and an event end process in the seventh invention, and the event start process and the event end process. And generating an intermediate code representing data storage between them.

  The compiling method of the ninth invention of the present application is a step of generating Java (registered trademark) code from the generated intermediate code in the seventh or eighth invention, and compiling and executing the generated Java (registered trademark) code Generating a possible program.

  A compiling method according to a tenth invention of the present application is characterized in that, in the seventh, eighth or ninth invention, the business process definition is described in Business Process Execution Language for Web Services (BPEL4WS).

  The compiling method of the eleventh invention of the present application is the Java (registered trademark) code in the ninth or tenth invention, wherein the Java (registered trademark) code corresponds to a Java (registered trademark) mechanism capable of persisting an object at the time of execution. It is a registered trademark) code.

  The compiling method of the twelfth invention of the present application is the Java (registered trademark) mechanism that can perform the persistence of the object at the time of execution in the ninth, tenth, or eleventh invention. Java (registered trademark) 2 Platform, Enterprise It is an Enterprise Java (registered trademark) Beans (EJB) of Edition (J2EE).

  A program of a thirteenth invention of the present application is a program of a compiling device that inputs a business process definition and generates an executable program, and the compiler device has a function of analyzing an element group described in the business process definition, In the case of a process that completes the element in a short time (short task event), a function that generates an intermediate code indicating continuous execution, a process that can cause a long waiting time for the element (long task event) In some cases, a function of generating an intermediate code indicating that data is saved at the time of execution of processing and a function of generating an executable program by compiling the generated intermediate code are realized.

  According to a fourteenth aspect of the present invention, there is provided a program according to a thirteenth aspect of the present invention, in which the long task event is divided into an event start process and an event end process and is executed, and between the event start process and the event end process. This realizes a function for generating an intermediate code indicating that data is stored.

  The program of the fifteenth aspect of the present application is a function for generating Java (registered trademark) code from the intermediate code generated in the thirteenth or fourteenth aspect of the invention, and can be executed by compiling the generated Java (registered trademark) code Realize the function to generate the program.

  An advantage of the present invention is that an executable program can be generated in consideration of the balance between data storage and business process performance.

  The reason is that events that complete processing in a short time are executed continuously, and events that can generate a long waiting time are generated as intermediate code indicating that data is stored in accordance with the execution timing. is there.

  As knowledge management and information sharing are progressing within the company, cooperation with existing systems and partner company systems is being pursued in order to improve operational efficiency and plan new services. In recent years, in order to perform such system cooperation, Web services for using existing systems and services have been provided, and business process definitions that describe new services by combining these Web services and There is a need for a system that interprets this and performs processing.

  The business process definition describes processing and execution control of data exchanged with the Web service to be used, and the process execution control unit executes processing based on the business process definition. In particular, there is an increasing demand for the process execution control unit to be able to promptly perform processing and recovery in the event of an abnormality or failure in order to improve service reliability. Therefore, in order to realize execution of a business process over a long period of time, data at the time of execution of a process execution program is stored in a database or a storage device during execution of the business process.

  The present invention analyzes a business process definition to generate an intermediate code, generates Java (registered trademark) code from the intermediate code, compiles it, and generates an executable program. At this time, the business process definition is analyzed to find an optimal balance point between the amount of information lost due to the occurrence of a failure and the execution speed, and an intermediate code reflecting that is generated.

  As described above, since an executable program that minimizes information lost due to the occurrence of a failure and secures an execution speed is generated, data storage at the time of execution of the generated program can be optimized.

  Note that the business process definition handled in the present invention is a language that can express a process that ends in a short time (short task) and a process that can generate a long waiting time (long task). One example is Business Process Execution Language for Web Services (BPEL4WS). BPEL4WS will be described later. Further, the Java (registered trademark) code to be generated is Java (registered trademark) code corresponding to the Java (registered trademark) mechanism capable of persisting the object at the time of execution. An example of a Java (registered trademark) mechanism capable of persisting an object at runtime is Enterprise Java (registered trademark) Beans (EJB) of Java (registered trademark) 2 Platform, Enterprise Edition (J2EE). .

Next, the best mode for carrying out the present invention will be described in detail with reference to the drawings.
FIG. 1 is a diagram showing the configuration of the present invention.
FIG. 2 is a diagram showing an example of a business process definition described according to BPEL4WS.

  Before describing the configuration of the compiling device of this embodiment, first, the business process definition handled by the compiling device will be described. In the business process definition, events such as a web service call and data copy are described. The format is not particularly specified, but as the format of the business process definition handled by this embodiment, OASIS Web Services Business Process Language Language TC, Business Process Execution Language Language Web Service, and the Web Service Services Web Service, 4 and 4 Is used. FIG. 2 shows an example of a business process definition described according to BPEL4WS.

  In BPEL4WS, a process element is defined as a root element of a business process definition, and elements representing events and variables are described therein.

  In the present embodiment, variable elements, partnerLink elements, and correlationSet elements defined in BPEL4WS are treated as persistent target variables. Also, elements defined as activities are handled as events.

In the following description, among the activities of BPEL4WS, the following are handled as short task events.
Sequence element (executes activities defined in child elements in the order described).
Flow element (executes activities defined in child elements in parallel).
• While element (repeatedly executes the activity defined in the child element during the specified condition).
Switch element (executes an activity branched according to a specified condition).
Assign element (copy specified data from one to the other).
Reply element (returns the specified message to the transmission source of the message received by the receive element).
Empty element (does nothing).
Terminate element (ends a business process)

The following are handled as long task events.
Receive element (receives the specified message).
Invoke element (sends a specified message and receives a response).
Wait element (waits for a specified period of time).

  The Java (registered trademark) code generated from the intermediate code corresponds to Enterprise Java (registered trademark) Beans (hereinafter referred to as EJB) of Java (registered trademark) 2 Platform, Enterprise Edition (hereinafter referred to as J2EE). Java (registered trademark) code.

  Next, the configuration of the compiling device of this embodiment will be described with reference to FIG.

  Referring to FIG. 1, an embodiment of a compiling device according to the present invention includes an input device 1 such as a keyboard, a compiling unit 2 that generates an executable program, an output device 3 such as a display device and a printing device, and information. Is stored. The compiling device also includes a CPU (central processing unit, not shown) that controls the whole and a main storage device (not shown) that stores programs executed by the CPU and various data. Operate. In addition, the compiling device may include program execution means (not shown) for executing the generated executable program.

  The input device 1 is a device for inputting a business process definition, and is a keyboard device or the like.

  The compiling unit 2 generates intermediate code and Java (registered trademark) code from the input business process definition, and generates an executable process execution program. The compiling unit 2 includes a business process definition analyzing unit 21, an intermediate code generating unit 22, a Java (registered trademark) code generating unit 23, and a Java (registered trademark) code compiling unit 24. In this embodiment, BPEL4WS is used as the format of the business process definition.

  The business process definition analysis unit 21 analyzes the business process definition input from the input device 1, converts the business process definition into data (business process definition conversion data) used by the intermediate code generation unit 22, and stores the data in the storage device 4. In the example of the business process definition described in accordance with BPEL4WS shown in FIG. 2, there is information of a process element as head data, and the process element includes an attribute value of the process element, and a partnerLinks element, variables element, and sequence element as child elements thereof. To hold. The business process definition conversion data is obtained by converting the described business process definition into a form that can be easily processed internally (for example, a process such as symbolization). The business process definition analysis means 21 includes a business process definition represented by BPEL4WS shown in FIG. 2 with a process element of the root element, a variable element such as partnerLink or variable, and an event element such as receive or assert as the business process definition. Data that retains the same relationship as the nested structure described in (Business process definition conversion data) is generated. Further, the business process definition analyzing means 21 displays a message on the output device 3 when a grammatical error in the business process definition is detected during the analysis.

  The intermediate code generation unit 22 reads the business process definition conversion data from the storage device 4 and generates an intermediate code used by the Java (registered trademark) code generation unit 23 based on the business process definition conversion data. The generated intermediate code is stored in the storage device 4. For example, the business process definition conversion data generated from the business process definition shown in FIG. 2 is input, the process element information is acquired as the top data, and the child element data with respect to the top data is acquired, whereby partnerLinks and variables are acquired. In addition, information on the sequence element is acquired. Intermediate code generation processing is performed until there are no child elements. Further, the intermediate code generation means 22 displays a message on the output device 3 when detecting missing or mistakes of necessary data during intermediate code generation. The intermediate code generation unit 22 includes an element determination unit 221, a class declaration intermediate code generation unit 222, a permanent variable definition intermediate code generation unit 223, a short task intermediate code generation unit 224, and a long task intermediate code generation unit 225. have.

The element discriminating unit 221 classifies the elements described in the business process definition as follows. Note that the short task and long task classification policies focus on processing related to message transmission and reception and timer processing.
(1) Root element.
(2) Permanent target variable element.
(3) An event (long task event) executed over a long period of time, such as message exchange via the network or waiting for the timer to start.
(4) An event (short task event) in which processing is completed in a short time such as data copying or data value evaluation.

  The class declaration intermediate code generation unit 222 generates intermediate code for outputting a code corresponding to a Java (registered trademark) class declaration from the element determined by the element determination unit 221 as a root element.

  The persistent target variable definition intermediate code generation unit 223 generates intermediate code for declaring data to be persisted from the elements determined by the element determination unit 221 as the persistent target variable elements.

  The short task intermediate code generation means 224 represents the meaning of generating an intermediate code corresponding to the contents to be processed by the event element from the event elements determined by the element determination means 221 as a short task, and executing them continuously. Generate intermediate code.

  The long task intermediate code generation unit 225 divides the intermediate code corresponding to the content to be processed by the event element into event start processing and event end processing from the event element determined by the element determination unit 221 as a long task. Generate intermediate code that represents execution.

  When there are no more elements to be processed by the intermediate code generation unit 22, the Java (registered trademark) code generation unit 23 inputs the intermediate code generated by the intermediate code generation unit 22 from the storage device 4, and the Java (registered) from the intermediate code. (Trademark) code. The generated Java (registered trademark) code is stored in the storage device 4. A message is displayed on the output device 3 when a missing or missing data is detected during Java (registered trademark) code generation. The Java (registered trademark) code generation means 23 generates a Java (registered trademark) code corresponding to J2EE EJB.

  The Java (registered trademark) code compiling unit 24 inputs the Java (registered trademark) code generated by the Java (registered trademark) code generating unit 23 from the storage device 4 and compiles it to generate an executable process execution program. . The generated executable process execution program is stored in the storage device 4. If an error occurs during compilation, a message is displayed on the output device 3. In addition, when the generated process execution program is executed, the generated process execution program continues the next event without performing data storage processing at the end of the event classified as a short task. To run. In the case of an event classified as a long task, the process is temporarily interrupted between the event start process and the event end process, and data is stored at the time of execution.

  The output device 3 is a device from which the compiling means 2 outputs a message, such as a printer device or a display device.

  The storage device 4 is a device in which each means included in the compiling means 2 stores various data, such as a magnetic disk device. An executable process execution program generated by compiling by the Java (registered trademark) code compiling means 24 is also stored.

  Next, the operation of the best mode for carrying out the present invention will be described in detail with reference to FIGS.

First, an outline of the operation of the compiling means 2 will be described with reference to FIGS.
FIG. 3 is a diagram showing the flow of the compiling means 2.

  In step A <b> 1, the business process definition analyzing unit 21 analyzes the business process definition supplied from the input device 1 and converts it into data processed by the intermediate code generating unit 22.

  In step A2, the business process definition analyzing means 21 evaluates the result analyzed in step A1. If the format or grammar of the supplied business process definition is incorrect, the error content is displayed on the output device 3 (step A10), and the subsequent processing is not executed.

  In step A <b> 3, the intermediate code generation unit 22 generates intermediate code handled by the Java (registered trademark) code generation unit 23 using the analyzed data representing the business process definition supplied from the business process definition analysis unit 21.

  In step A4, it is evaluated whether the intermediate code generation means 22 has succeeded in generating the intermediate code. If it fails, the contents are displayed on the output device 3 (step A10), and the subsequent processing is not executed.

  In step A5, the Java (registered trademark) code generation unit 23 generates a Java (registered trademark) code corresponding to the J2EE EJB from the intermediate code generated by the intermediate code generation unit 22.

  In step A6, it is evaluated whether the Java (registered trademark) code generation unit 23 has successfully generated the Java (registered trademark) code. If it fails, the contents are displayed on the output device 3 (step A10), and the subsequent processing is not executed.

  In step A7, the Java (registered trademark) code compiling unit 24 compiles the Java (registered trademark) code generated by the Java (registered trademark) code generating unit 23 to generate an executable program.

  In step A8, it is evaluated whether the Java (registered trademark) code compiling means 24 has successfully generated the executable program. If it fails, the contents are displayed on the output device 3 (step A10), and the subsequent processing is not executed.

  In step A9, the Java (registered trademark) code compiling means 24 stores the generated executable program in the storage device 4.

Next, the operation of the intermediate code generation means 22 for generating the intermediate code will be described with reference to FIG. 1, FIG. 4, and FIG.
FIG. 4 is a diagram showing a flow in which the intermediate code generation means 22 generates an intermediate code.
FIG. 10 is a diagram illustrating a configuration example of the intermediate code.

  The intermediate code includes one class declaration method and a plurality of task methods, and the class declaration method and the task method have a configuration in which fragments are stored. FIG. 10 shows a configuration example of the intermediate code.

  In step B1 of FIG. 4, the intermediate code generation unit 22 acquires the data (business process definition conversion data) generated by the business process definition analysis unit 21.

  In step B2, step B4, and step B6, the element determination unit 221 takes out the element of the business process definition from the acquired data, and is one of the BPEL4WS process element, persistent target variable element, short task event, or long task event. To evaluate.

  If the extracted element is a process element, the process proceeds to step B3.

  If the extracted element is a permanent target variable element, the process proceeds to step B5.

  If the extracted element is a long task event (for example, a receive element of BPE4WS), the process proceeds to step B7.

  If the extracted element is a short task event (for example, an assign element of BPEL4WS), the process proceeds to step B8.

  In step B3, processing by the class declaration intermediate code generation means 222 is performed. That is, an intermediate code that outputs a code corresponding to a Java (registered trademark) class declaration is generated (see the intermediate code class declaration method shown in FIG. 10).

  In step B5, processing by the persistent target variable definition intermediate code generation means 223 is performed. That is, an intermediate code for declaring data to be persisted is generated (see intermediate codes H2 and H3 shown in FIG. 10).

  In step B7, processing by the long task intermediate code generation means 225 is performed. That is, an intermediate code indicating that a long task event is divided into an event start process and an event end process is generated (see H4 to H5, H6 to H7, etc. of the intermediate code shown in FIG. 10).

  In step B8, processing by the short task intermediate code generation means 224 is performed. That is, an intermediate code representing the meaning of continuously executing the short task event is generated (see intermediate codes H14 to H15, H16 to H17, etc. shown in FIG. 10).

  After the process of step B3, step B5, step B7 or step B8 is completed, it is evaluated in step B9 whether unprocessed data exists in the acquired data. If unprocessed data exists, the process returns to step B4 and the same process is repeated. The process ends when there is no unprocessed data.

Next, the processing of the class declaration intermediate code generation unit 222 will be described with reference to FIG.
FIG. 5 is a diagram showing a processing flow of the class declaration intermediate code generation means 222.

  In step C1 of FIG. 5, the class declaration intermediate code generation means 22B generates a class declaration method in the intermediate code.

  In step C2, a method selection fragment is generated. This method selection fragment is used to select a task method generated by an event element.

  In step C3, the method selection fragment generated in step C2 is added to the class declaration method generated in step C1.

  In step C4, a new task method is generated in the intermediate code.

  In step C5, the task method generated in step C4 is designated as the editing method of the intermediate code, and the process ends.

Next, the processing of the persistent target variable definition intermediate code generation unit 223 will be described with reference to FIG.
FIG. 6 is a diagram showing a processing flow of the persistent target variable definition intermediate code generation means 223.

  In step D1 of FIG. 6, the persistent target variable definition intermediate code generating unit 223 generates a persistent target variable definition fragment. This persistent target variable definition fragment represents data that is made permanent between the event start process and the event end process of the long task event.

  In step D2, the persistent target variable definition fragment generated in step D1 is added to the end of the class declaration method, and the process ends.

Next, the processing of the short task intermediate code generation means 224 will be described with reference to FIG.
FIG. 7 is a diagram showing a flow in which the short task intermediate code generation means 224 generates a short task event execution intermediate code.

  In step E1 in FIG. 7, it is determined whether the short task event is an event that causes conditional branching, such as a BPEL4WS switch element.

  If it is evaluated as a conditional branch event in step E1, the process proceeds to step E2.

  If it is determined in step E1 that the event is not a conditional branch, the process proceeds to step E3.

  In step E3, an event execution fragment representing the processing of the corresponding event is generated. For example, when the assign element of BPEL4WS is designated, a fragment for copying data is generated.

  In step E4, the event execution fragment generated in step E3 is added to the end of the editing method of the intermediate code, and the process ends.

  In step E2, a conditional branch event execution fragment is generated.

Next, the conditional branch event execution fragment generation process performed in step E2 will be described with reference to FIG.
FIG. 8 is a diagram showing a processing flow for generating a conditional branch event execution fragment.

  In step F1 of FIG. 8, the editing method possessed by the intermediate code is stored.

  In step F2, a new task method is generated. The task method generated here is executed continuously after the event of the child element is executed when the condition evaluation event is established.

  In step F3, a no-wait long task fragment that calls the task method generated in step F2 is generated. This no-wait long task fragment is an intermediate code that indicates that the specified task method is continuously executed and the event is continuously executed without performing the persistence processing of the persistence target variable even if the task method is divided. .

  In step F4, a condition evaluation start fragment for starting condition evaluation is generated.

  In step F5, the condition evaluation start fragment generated in step F4 is added to the end of the task method stored in step F1.

  In step F6, a new task method is generated. The task method generated here stores the event fragment of the child element when the condition evaluation event is established, and is executed continuously after the condition evaluation is established.

  In step F7, the task method generated in step F6 is designated as the editing method of the intermediate code.

  In step F8, a fragment of a child element of the condition evaluation event is generated. The processing in step F8 is the same as the processing after step B6 in FIG. 4 (nesting processing is performed).

  In step F9, the no-wait long task fragment generated in step F3 is added to the end of the editing method of the intermediate code.

  In step F10, a condition evaluation end fragment representing the end of the condition evaluation is generated.

  In step F11, the condition evaluation end fragment generated in step F10 is added to the end of the task method stored in step F1.

  In Step F12, it is evaluated whether the conditional branch event holds other conditional branches. If another conditional branch exists, the processing from step F4 is repeated. If no other conditional branch exists, the process ends.

Next, the processing of the long task intermediate code generation means 225 will be described with reference to FIG.
FIG. 9 is a diagram showing a flow in which the long task intermediate code generation means 225 generates a long task event execution intermediate code.

  In step G1 of FIG. 9, an event start process execution fragment is generated. The event start process execution fragment represents, for example, a process of waiting until a message of a specified destination arrives when a BPEL4WS receive element is specified.

  In step G2, the event start process execution fragment generated in step G1 is added to the end of the editing method of the intermediate code.

  In step G3, the intermediate code editing method is terminated. When the compiled code is executed, the contents of the persistent target variable are persisted when this method ends.

  In step G4, a new task method is generated. This task method stores a fragment corresponding to event end processing of a long task event.

  In step G5, the task method generated in step G4 is designated as the editing method of the intermediate code.

  In step G6, an event end processing fragment of the long task event is generated. For example, the event end processing fragment generated for the receive element of BPEL4WS stores the received message in the persistent target variable.

  In step G7, the event end process fragment generated in step G6 is added to the end of the method being edited in the intermediate code, and the process ends.

  Next, the intermediate code will be described with reference to FIG.

  A schematic diagram of the intermediate code generated by the intermediate code generation unit 22 from the business process definition described in BPEL4WS shown in FIG. 2 is as shown in FIG.

  A process in which the intermediate code generation unit 22 finds a long task event and generates an intermediate code by dividing the process into event start and end will be described with reference to FIG. 10 using the receive element of FIG. 2 as an example. It is divided into an event start process execution fragment (H4 in FIG. 10) and an event end process fragment (H5 in FIG. 10), which are represented by portions stored in task method 0 and task method 1, respectively.

  The no-wait long task fragment (H9, H12, H15, and H17 in FIG. 10) indicates that when it is executed, the designated task method fragment is continuously executed. For example, when a no-wait long task of H15 is executed, an event execution fragment of H18 of task method 5 is executed following task method 3.

Next, an operation in which the Java (registered trademark) code generation unit 23 generates the Java (registered trademark) code from the intermediate code of FIG. 10 generated by the intermediate code generation unit 22 will be described with reference to FIGS. I will explain.
FIG. 11 is a diagram showing an example of the generated Java (registered trademark) code.
FIG. 12 is a diagram showing an example of the generated Java (registered trademark) code.

  An example in which the Java (registered trademark) code generation unit 23 generates Java (registered trademark) code from the intermediate code of FIG. 10 generated by the intermediate code generation unit 22 is shown in FIGS.

  First, when receiving the intermediate code generated by the intermediate code generating unit 22, the Java (registered trademark) code generating unit 23 generates the Java (registered trademark) code of FIG. The generated contents are almost the same regardless of the intermediate code, and the only difference is the Java (registered trademark) class name JobFlowCore in I1 of FIG. The Java (registered trademark) class, JobFlowCore, indicates the Java (registered trademark) code of FIG. 12 generated by the Java (registered trademark) code generation unit 23. 11 and FIG. 12 are generated in pairs. In addition, the Java (registered trademark) code generation unit 23 generates some Java (registered trademark) code that conforms to the J2EE framework, but is not the essence of the Java (registered trademark) code generation unit 23. I will omit the explanation.

  Next, the Java (registered trademark) code generation unit 23 generates the Java (registered trademark) code of FIG. 12 based on the intermediate code generated by the intermediate code generation unit 22. The Java (registered trademark) code generation unit 23 outputs the declaration of JobFlowCore which is the class name of FIG. 12 from the class declaration method of FIG. 10, and outputs the method declaration of the constructor of J1 of FIG.

  Next, the fragments H1 to H3 stored in the class declaration method of FIG. 10 are processed. From the fragment of H1, the onMessage method, invoke method, and selectAndInvoke method of J2 in FIG. 12 are output. The case statement in the selectAndInvoke method is output according to the number of task methods in FIG. From the fragment of H2 and H3 in FIG. 10, the definition of the persistent target variable of J1 in FIG. 12 is output. Here, the arrangement of H2 and H3 in the class declaration method of FIG. 10 does not depend on the appearance order of partnerLink and variable in the business process definition of FIG.

  Next, in accordance with task method 0 to task method 5 in FIG. 10, methods taskMethod0 to taskMethod5 indicated by J3 in FIG. 12 are output. The contents of each method of J3 in FIG. 12 are determined by the fragments stored in the task method of FIG. For example, a Java (registered trademark) code corresponding to the message reception request process specified by the receive element of taskMethod0 of J3 in FIG. 12 is output from the H4 fragment of task method 0 in FIG.

  The Java (registered trademark) code in FIG. 11 is an instance of the class represented by the Java (registered trademark) code in FIG. 12, and the instance variable of the class represented by the Java (registered trademark) code in FIG. Becomes a permanent target. That is, the variable indicated by J1 in FIG. 12 is permanent data. Data is made permanent when the onMessage method of I1 in FIG. 11 is called and ends normally, that is, when the onMessage method of J2 in FIG. 12 ends normally. The part where the onMessage method of J2 in FIG. 12 ends corresponds to the end of execution of the event start process of the long task event of the business process definition, and the data designated as the permanent target is saved at this timing. Also, when executing a short task event, the task method may be divided by a conditional branch event or the like, but the onMessage method of J2 in FIG. 12 is not limited as long as data remains in the mNoWaitLongTaskQueue of J1 of FIG. The process of selecting and executing one task method with the selectMethodAndInvoke method of 12 J2 is repeated.

  In this way, task methods can be executed continuously. This is a portion expressed by a no-wait long task fragment in the intermediate code.

  The generated process execution program is continuously executed at the end of an event classified as a short task, without storing data at the time of execution, and between the start process and the end process of an event classified as a long task The process is temporarily interrupted, and the data at the time of execution is saved at this timing.

  In this way, by detecting the balance point of data persistence focusing on the execution of long tasks, information lost due to failures occurring during the execution of business processes is reduced, and the execution speed of process execution programs is ensured. It becomes possible to do. More specifically, the process execution program generated by the compiling device can continuously execute events that complete processing in a short time, such as data copying and value evaluation. In addition, an event that may cause a long waiting time such as message transmission / reception in a timer process or a process using an external Web service is that data can be stored in accordance with the execution timing. As a result, since the process execution program is executed with a reduced number of data storage processes, the time spent for storage can be suppressed from affecting the execution of the business process, and the execution speed can be improved. . The reason for this is that after the business process definition describing the series of processes is analyzed by the business process definition analysis means, the intermediate code generation means determines the process that ends in a short time and the process that can cause a long waiting time, and determines the intermediate code From this intermediate code, Java (registered trademark) code generating means can generate Java (registered trademark) code that saves data at a place where a long waiting time can occur. is there.

  In the above-described embodiment according to the present invention, a program or the like for executing the processing operation of the compiling device is recorded as data on a recording medium (not shown) such as a magnetic disk or a ROM of the compiling device. This data is used to read the data and operate the compiling device. As described above, the function of the compiling device can be realized by recording the data for operating the compiling device according to the present invention on the recording medium and installing the recording medium.

  INDUSTRIAL APPLICABILITY According to the present invention, the present invention can be applied to the use of a system cooperation device using a web service or the generation of a program that operates on a device that provides a new service by combining multiple web services.

The figure which shows the structure of this invention The figure which shows the example of the business process definition described according to BPEL4WS Diagram showing compiler flow The figure which shows the flow which an intermediate code production | generation means produces | generates an intermediate code Diagram showing the processing flow of the class declaration intermediate code generation means The figure which shows the processing flow of the permanent object variable definition intermediate code generation means The figure which shows the flow which the short task intermediate code generation means generates the short task event execution intermediate code The figure which shows the generation processing flow of conditional branch event execution fragment The figure which shows the flow in which long task intermediate code generation means generates long task event execution intermediate code Diagram showing an example of the structure of the intermediate code A diagram showing an example of generated Java (registered trademark) code A diagram showing an example of generated Java (registered trademark) code

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Input device 2 Compile means 3 Output device 4 Storage device 21 Business process definition analysis means 22 Intermediate code generation means 23 Java (registered trademark) code generation means 24 Java (registered trademark) code compilation means 221 Element determination means 222 Class declaration intermediate code Generation means 223 Permanent object variable definition intermediate code generation means 224 Short task intermediate code generation means 225 Long task intermediate code generation means

Claims (15)

A compiling device for generating an executable program by inputting a business process definition,
Means for analyzing an element group described in the business process definition;
Means for generating intermediate code representing continuous execution in the case of a process (short task event) in which the element is completed in a short time;
Means for generating an intermediate code indicating that data is stored at the time of execution of the process when the element is a process (long task event) in which a long waiting time may occur;
Means for compiling the generated intermediate code to generate an executable program,
A compiling device characterized by that. An intermediate code indicating that the long task event is divided into an event start process and an event end process and executed, and an intermediate code indicating that data is stored between the event start process and the event end process are generated. With means,
The compiling device according to claim 1. Means for generating Java (registered trademark) code from the generated intermediate code;
Means for compiling the generated Java (registered trademark) code to generate an executable program;
The compiling apparatus according to claim 1 or 2, characterized in that The business process definition is
It is described in Business Process Execution Language for Web Services (BPEL4WS).
4. The compiling device according to claim 1, 2, or 3. The Java (registered trademark) code is:
Java (registered trademark) code corresponding to a Java (registered trademark) mechanism capable of persisting an object at the time of execution.
The compiling apparatus according to claim 3 or 4, characterized in that The Java (registered trademark) mechanism capable of persisting an object at the time of execution is as follows:
It is Enterprise Java (registered trademark) Beans (EJB) of Java (registered trademark) 2 Platform, Enterprise Edition (J2EE).
6. The compiling device according to claim 3, 4 or 5. A compilation method for generating an executable program by inputting a business process definition,
Analyzing an element group described in the business process definition;
Generating intermediate code representing continuous execution in the case of a process (short task event) in which the element is completed in a short time; and
When the element is a process (long task event) in which a long waiting time may occur, generating an intermediate code indicating that data is stored when the long task event is executed;
Compiling the generated intermediate code to generate an executable program,
A compiling method characterized by the above. An intermediate code indicating that the long task event is divided into an event start process and an event end process and executed, and an intermediate code indicating that data is stored between the event start process and the event end process are generated. Including steps,
8. The compiling method according to claim 7, wherein: Generating Java (registered trademark) code from the generated intermediate code;
Compiling the generated Java (registered trademark) code to generate an executable program,
9. The compiling method according to claim 7 or 8, wherein: The business process definition is
It is described in Business Process Execution Language for Web Services (BPEL4WS).
10. The compiling method according to claim 7, 8, or 9. The Java (registered trademark) code is:
Java (registered trademark) code corresponding to a Java (registered trademark) mechanism capable of persisting an object at the time of execution.
11. The compiling method according to claim 9 or 10, wherein: The Java (registered trademark) mechanism capable of persisting an object at the time of execution is as follows:
It is Enterprise Java (registered trademark) Beans (EJB) of Java (registered trademark) 2 Platform, Enterprise Edition (J2EE).
The compiling method according to claim 9, 10 or 11. A compiling device program that inputs a business process definition and generates an executable program,
In the compiler device,
A function of analyzing a group of elements described in the business process definition;
A function for generating an intermediate code indicating continuous execution in the case of a process (short task event) in which the element is completed in a short time;
A function for generating an intermediate code indicating that data is stored when the process is executed in the case of a process (long task event) in which the element may have a long waiting time;
A function for generating an executable program by compiling the generated intermediate code;
A program to realize An intermediate code indicating that the long task event is divided into an event start process and an event end process and executed, and an intermediate code indicating that data is stored between the event start process and the event end process are generated. function,
The program according to claim 13 for realizing the above. A function of generating Java (registered trademark) code from the generated intermediate code;
A function for generating an executable program by compiling the generated Java (registered trademark) code;
The program of Claim 13 or 14 for implement | achieving.

Images