JP2014032543A - Service cooperation device and service cooperation program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide means for suppressing an increase in memory consumption of a component used in an ESB.SOLUTION: A service cooperation device 101 includes a component X or the like connected to a service, routing definition 1211 describing kinds and parts of endpoints in order of services to be executed, endpoint management information 151 describing a component that can use the endpoints, a routing endpoint 121 for specifying the kind of an endpoint and parts of the endpoint in order of services to be executed with reference to the routing definition 1211 when receiving a request from a service requester 2, and an endpoint manager 15 for generating the specified endpoint and parts, specifying components that can use the generated endpoint with reference to the endpoint management information 151, and storing the generated endpoint and parts in a memory area to be used by the component.

Description

  The present invention relates to a service cooperation apparatus and a service cooperation program for linking services.

  As a method of creating a new function by using data and functions of a plurality of systems, an SOA (Service Oriented Architecture) that publishes the data and functions of each system as a service such as a Web service and links the published services with each other. Service-oriented architecture). As middleware for linking a plurality of services in this SOA, there is software called ESB (Enterprise Service Bus). This ESB has a group of parts called components (Non-patent Document 1 “4.3 High-Level Architecture”). A component is a group of parts for calling a service to be activated or performing processing such as code conversion. When services are linked, data is exchanged between components. Data passed between components is stored in a message called a normalize message. For example, when data acquired from a service is passed from one component to another for service cooperation, the acquired data is stored in a normalized message and the message is transmitted. The component that has received the message performs processing using the stored data. Message reception and processing is performed by a component called an endpoint in the component.

  Each component and endpoint uses an area secured on the memory, and when the number of components and endpoints increases, the amount of memory consumption increases. Even if the components and the endpoints in them are of the same type, different settings may be required for each service to be called, and components and endpoints are prepared for each setting. That is, each consumes memory. In service cooperation, a component called a routing component is used. The routing component is used to control the activation order of other components, and according to the set order, the activation order of services is controlled by transmitting a message to a component required by the routing component. This control flow is called routing. By defining the routing, a new function in which data and functions of a plurality of systems are linked is created. In the definition of routing, there are a method of directly specifying an end point for a service to be used, and a method of specifying a type of service to be used in routing as in Patent Document 1. Patent Document 1 discloses a technique for selecting an appropriate service from among a plurality of services that can perform the same processing.

JP 2009-169793 A

Java Business Integration 1.0 <http: // jcp. org / aboutJava / communityprocess / final / jsr208 / index. html> (accessible as of July 17, 2012) (Java is a registered trademark)

  Patent Document 1 discloses a method of automatically selecting an alternative service even when one service is stopped when there are a plurality of services that perform the same processing. Therefore, when there are many services that perform the same processing, fault tolerance can be increased. However, a component that is a connection part with a service is required for each service, and there is a problem that the memory consumption of the ESB increases.

  An object of the present invention is to suppress an increase in memory consumption by commonly using components and endpoints even when the number of components used in the ESB increases.

The service cooperation apparatus of this invention is
At least one service connection unit connected to at least one service;
An information storage unit having a memory area for storing information used by the service connection unit;
Service execution order information in which, in the order of the services to be executed, the types of service execution programs that execute the services, the service execution program type that indicates the service to be executed is described together with the control information that controls the operation of the service execution program A service execution order information storage unit for storing
A service execution program management information storage unit that stores service execution program management information in which a correspondence relationship with the service connection unit that can use the service execution program is described for each service execution program of a plurality of service execution programs;
A receiver for receiving a service execution request;
When the receiving unit receives the request, by referring to the service execution order information in the service execution order information storage unit, the type of service execution program to be executed and the service execution program to be executed A service execution program identification unit that identifies control information corresponding to the type;
The service execution program of the type specified by the service execution program specification unit is generated by referring to the service execution program management information in the service execution program management information storage unit. A storage execution unit for specifying the service connection unit that can use the program, and storing the generated service execution program and the control information in the memory area of the information storage unit used by the specified service connection unit;
Execution result obtained by causing the service execution program stored in the information storage unit to execute the service indicated by the type of the service execution program and acquiring the execution result of the service from the executed service execution program And an acquisition unit.

  According to the present invention, an increase in memory consumption of components used in ESB can be suppressed.

FIG. 2 is a block configuration diagram of a service cooperation apparatus 101 according to the first embodiment. FIG. 6 is a diagram showing a routing definition 1211 according to the first embodiment. FIG. 5 is a diagram showing endpoint management information 151 according to the first embodiment. 5 is a flowchart showing the operation of the service cooperation apparatus 101 according to the first embodiment. FIG. 4 is a block configuration diagram of a service cooperation apparatus 102 according to a second embodiment. FIG. 10 is a diagram illustrating endpoint state information 152 according to the second embodiment. 9 is a flowchart showing an operation of the service cooperation apparatus 102 according to the second embodiment. 9 is a flowchart illustrating an operation for securing an endpoint according to the second embodiment. 9 is a flowchart illustrating an end point release operation according to the second embodiment. FIG. 6 is a block configuration diagram of a service cooperation apparatus 103 according to a third embodiment. The figure which shows the part status information 153 of Embodiment 3. FIG. 10 is a flowchart illustrating processing for securing an endpoint according to the third embodiment. 10 is a flowchart showing an operation of a parts set to an end point according to the third embodiment. 10 is a flowchart illustrating endpoint release processing according to the third embodiment. 10 is a flowchart showing an operation for returning the parts of the third embodiment to the parts pool 17; The figure which shows the external appearance of the service cooperation apparatus 101 grade | etc., Of Embodiment 4. FIG. The figure which shows hardware constitutions, such as the service cooperation apparatus 101 of Embodiment 4. FIG.

Embodiment 1 FIG.
FIG. 1 is a block configuration diagram of the service cooperation apparatus 101 according to the first embodiment. In FIG. 1, a service cooperation apparatus 101 is software for linking a plurality of services. Each “˜unit” in the service cooperation apparatus 101 is stored in a storage device as described later in the fourth embodiment. The same applies to the service cooperation apparatuses 102 and 103 described in the second and third embodiments. The service cooperation apparatus 101 is often realized as software (for example, ESB) on a computer such as a personal computer or a server apparatus, but a dedicated apparatus may be used.

  The service requester 2 is a device or application (application program) that uses a service published by the service cooperation device 101.

  Service A31, service B32, service C33, and service D34 are services that the service cooperation apparatus 101 calls.

  The service collaboration apparatus 101 creates a new function by linking these services. The service requester 2 uses the function.

(Communication component 11)
The communication component 11 in the service cooperation apparatus 101 is a component that is in the service cooperation apparatus 101 and receives a service execution request from the outside. The communication end point 111 (reception unit) is a component of the communication component 11 and accepts a request from the service requester 2 according to a determined procedure such as HTTP (Hyper TextT Protocol).

(Routing component 12)
The routing component 12 is a component for controlling the service activation order in order to perform service cooperation. The routing component 12 receives the message sent from the communication component 11 and performs routing. The message is received by the routing endpoint 121 (service execution program identification unit, execution result acquisition unit). The routing endpoint 121 transmits a message to a necessary component in accordance with a routing definition 1211 (service execution order information) described later in the description of FIG.

(Component X13 etc.)
The component X13 and the component Y14 are parts (service connection unit) for executing a service. Each has an endpoint (service execution program), and the service is executed by these endpoints. The endpoint creates a request to execute the service from the received message, extracts data from the response of the service, and stores it in the message. The end point A131 and the end point B132 are parts of the component X13, and the service A31 and the service B32 are executed using the part a1311 (control information) and the part b1321 (control information), respectively.

(Parts a etc.)
Part a 1311 and part b 1321 hold operation settings and the like, and are control information for controlling the operation of the endpoint A 131 and the endpoint B 132. That is, the operation of the endpoint is determined by the type of endpoint and the parts used therein. For example, even when the end point A 131 and the end point B 132 are the same type of part, the process can be changed by changing the part.

(Component Y14 etc.)
The component Y14, the end point C141, the end point D142, the part c1411, and the part d1421 are the same as the component X13. In FIG. 1, two components X and Y are illustrated, but the actual service cooperation apparatus 101 is not limited to two components. There may be one or more components. The same applies to the end points and parts.

(Endpoint Manager 15)
The endpoint manager 15 (storage execution unit, deletion unit) is a component that manages endpoints used for execution of services, and endpoint management information 151 (service execution program) that manages endpoint types that can be used for the components. Management information).

(Routing definition 1211, end point management information 151)
FIG. 2 is a diagram illustrating an example of the routing definition 1211 included in the routing component 12. The routing definition 1211 describes the types of endpoints (service execution program types) for executing the services and their execution settings in the order of the services to be executed. The “type” of the endpoint is the type of the endpoint itself that executes the service, and indicates the service to be executed. That the endpoint is of type A indicates that the service executed by this endpoint is “service A”.
FIG. 3 is a diagram illustrating an example of the endpoint management information 151. The end point management information 151 describes correspondence information between the types of end points used on the service cooperation apparatus 101 and components that can use the end points.

Next, the operation of the service cooperation apparatus 101 according to the first embodiment will be described with reference to FIG.
FIG. 4 is a flowchart showing the operation of the service cooperation apparatus 101. Here, consider a case where the routing definition 1211 and the endpoint management information 151 are set as shown in FIGS. Further, it is assumed that the types of the end point A131 and the end point D142 are A and D, respectively.

  Here, the types of endpoints are A and D, respectively, that the endpoints of type A execute service A, and the endpoints of type D execute service D. For example, as described above, the processing content when the type A endpoint executes the service A differs depending on the parts set in the type A endpoint.

  Step S1001 of START in FIG. 4 represents the start of processing of the service cooperation apparatus 101. In this process, a “service execution request” is transmitted from the service requester 2 to the service cooperation apparatus 101.

  In step S1002 for request reception, the communication endpoint 111 receives a request transmitted from the service requester 2, and creates a normalized message based on the request. Then, the created normalize message is transmitted to the routing endpoint 121.

  In step S1003 of the routing endpoint, the routing endpoint 121 that has received the normalization message refers to the routing definition 1211 and the type of the endpoint to be executed first is A, and part a is used as the setting. Get (specify) information that The routing endpoint 121 refers to the routing definition 1211 in response to the “service execution request” from the service requester 2. In this case, for example, the “service execution request” from the service requester 2 has a corresponding relationship with the routing definition 1211, and the routing endpoint 121 refers to the routing definition 1211 corresponding to the “service execution request”. .

(Endpoint A creation: S1004)
In step S1004 for creating an endpoint A, the routing endpoint 121 requests the endpoint manager 15 to create an endpoint that is of type A and uses part a as a setting.
(1) The requested endpoint manager 15 creates an endpoint A 131 as an endpoint of type A.
(2) Further, the endpoint manager 15 creates a part a1311 and sets it in the endpoint A131.
(3) Next, the endpoint manager 15 refers to the endpoint management information 151, and stores the created endpoint A131 (part a is already set) in the component X13. That is, the endpoint manager 15 refers to the endpoint management information 151 and stores the endpoint A 131 in which the part a is set in the “memory area of the storage device” for the component X 13 to use the endpoint. Here, the storage device includes both a nonvolatile memory and a volatile memory, which will be described later in Embodiment 4. In S1006, which will be described later, when the endpoint A131 is deleted, the endpoint manager 15 deletes the endpoint A131 from the memory area. Then, the end point manager 15 transmits the address information of the end point A 131 to the routing end point 121.

(Execution of end point A: S1005)
In step S1005 of execution of the endpoint A, the routing component 12 transmits a message to the endpoint A 131 based on the address information acquired from the endpoint manager 15. When the endpoint A 131 receives the message, the endpoint A 131 creates a request message for executing the service A 31 based on the received message, and activates the service A 31. Next, the endpoint A 131 extracts data from the response of the service A 31, stores it in a message, and transmits the message as a “reply” to the routing endpoint 121. As described above, the routing end point 121 executes the service A via the end point A131, and acquires the execution result of the service A (a reply including response data) from the service A.

(Deletion of end point A: S1006)
In step S1006 for deleting the endpoint A, the routing endpoint 121 requests the endpoint manager 15 to delete the endpoint A131 when receiving a reply from the endpoint A131. When requested, the endpoint manager 15 deletes the endpoint A131.

(Endpoint D creation, execution, deletion: S1007 to S1009)
In step S1007 for creating the endpoint D, the routing endpoint 121 refers to the routing definition 1211, acquires information about the endpoint to be activated next, and creates the endpoint D142 in the same manner as in S1004. In step S1008 for executing endpoint D and in step S1009 for deleting endpoint D, endpoint D is executed and deleted in the same manner as in step S1005 for executing endpoint A and step S1006 for deleting endpoint A.

  In step S <b> 1010, which is the end of the routing endpoint, since the execution of the endpoint to be executed is completed, the routing endpoint 121 sends a reply to the communication endpoint 111.

  In step S1011 of response transmission, the communication end point 111 that has received a reply from the routing end point 121 creates a response for replying to the service requester 2, and transmits the response.

  In step S1012 of END, the service requester 2 receives the response, and the service execution by the service cooperation apparatus 101 ends.

  As described above, according to the first embodiment, the routing end point 121 uses the end point manager 15 to create only an end point necessary for service execution, and deletes the end point when the service ends. As a result, the memory consumed by the endpoint in the service cooperation apparatus 101 can be reduced.

Embodiment 2. FIG.
The service cooperation apparatus 102 according to the second embodiment will be described with reference to FIGS. The service cooperation apparatus 102 according to the second embodiment does not create and delete the endpoint every time the service is executed, and reuses the created endpoint.

  FIG. 5 is a configuration diagram of the service cooperation apparatus 102. In the service cooperation apparatus 102 according to the second embodiment, an endpoint pool 16 is provided in addition to the service cooperation apparatus 101 according to the first embodiment. The endpoint pool 16 is a component for holding endpoints created by the endpoint manager 15. Of course, the endpoint pool 16 is stored in a memory area different from the endpoint stored in the component in the storage device.

The endpoint pool 16 holds an endpoint E161 and an endpoint F162 created by the endpoint manager 15, for example, as shown in FIG. Further, in order to manage the endpoint, the endpoint manager 15 is provided with endpoint status information 152.
FIG. 6 is an example of information managed by the endpoint state information 152. The endpoint status information 152 manages the type of the endpoint (information indicating the service to be executed by the endpoint) and whether it is in use for the created endpoint.

  FIG. 7 is a diagram illustrating the operation of the service cooperation apparatus 102. The difference from FIG. 4, which is the processing flow of the service cooperation apparatus 101 of the first embodiment, is that in FIG. 7, the end point execution (S2005 and S2008) is the end point securing and end point release. is there. The operation of securing the endpoint and releasing the endpoint will be described.

(Endpoint reservation: S2004)
In securing the endpoint in S2004, the endpoint manager 15 creates a new endpoint or uses the unused endpoint to secure the endpoint requested by the routing endpoint 121.

FIG. 8 is a diagram illustrating an operation of securing an endpoint by the endpoint manager 15.
(1) First, in S3001, the endpoint manager 15 refers to the endpoint status information 152 to check whether there is an unused endpoint of the type requested by the routing endpoint 121. To do. Based on the confirmation result, the endpoint manager 15 performs endpoint creation S3002 or unused endpoint status update S3003 to secure the endpoint.
(2) Endpoint creation S3002 is an operation when there is no unused one. In creating an endpoint, the endpoint manager 15 creates an endpoint of the type requested from the routing endpoint 121 and adds the information of the endpoint to the endpoint status information 152 as being in use.
(3) When there is an unused endpoint, in the unused endpoint status update S3003, the endpoint manager 15 “uses” the information of the endpoint status information 152 corresponding to the found endpoint. Update to

  Next, in endpoint setting change S3004, the endpoint manager 15 performs the setting requested from the routing endpoint 121 for the secured endpoint. For example, when the endpoint A is used in the example of FIG. 2, the endpoint manager 15 creates a part a according to the setting and sets it in the endpoint A. Finally, in endpoint address transmission S3005, the endpoint manager 15 stores the endpoint in the component (stores the component in the corresponding memory area) so that the routing endpoint 121 can use the reserved endpoint. Then, the address is transmitted to the routing end point 121, and the process ends.

  FIG. 9 is a diagram illustrating the operation of releasing the endpoint. In releasing the endpoint, the used endpoint is returned to the endpoint pool 16.

  First, in step S4001 for returning an endpoint to the endpoint pool, the endpoint manager 15 receives a used endpoint release request from the routing endpoint 121. The endpoint manager 15 retrieves the target endpoint from the component, deletes the parts in the endpoint, and stores them in the endpoint pool 16.

  Next, in update S4002 of the endpoint status information 152, the endpoint status information 152 sets the information regarding the target endpoint (the endpoint stored in the pool) in the endpoint status information 152 to “unused”. Change and exit.

  As described above, according to the service cooperation apparatus 102 of the second embodiment, instead of fixing and allocating an endpoint to a service, the endpoint is reused and the endpoint is allocated when necessary. Can reduce the number of endpoints created, and can reduce memory consumption. Further, by using the created endpoint, the processing time overhead due to the creation of the endpoint can be reduced as compared with the case where the endpoint is created each time as in the service cooperation apparatus 101 of the first embodiment.

Embodiment 3 FIG.
The service cooperation apparatus 103 of Embodiment 3 is demonstrated with reference to FIGS. The service cooperation apparatus 103 according to the third embodiment does not create or delete parts used in the endpoints every time execution is performed on the service cooperation apparatus 102 according to the second embodiment. (Embodiment 2) Recycle parts.

  FIG. 10 is a configuration diagram illustrating the service cooperation apparatus 103 according to the third embodiment. In the service cooperation apparatus 103 according to the third embodiment, a parts pool 17 is provided in addition to the service cooperation apparatus 102 according to the second embodiment. The parts pool 17 is a part for holding parts created by the endpoint manager 15. Similar to the endpoint pool 16, the parts pool 17 is stored in a memory area different from the endpoint stored in the component in the storage device.

In order to manage the endpoint, the endpoint manager 15 is provided with part status information 153.
FIG. 11 is an example of information managed by the part status information 153. In the part status information 153, the type of part and the presence / absence of use are managed for the created part.

  The third embodiment is different from the second embodiment in securing the endpoint (S2004 and releasing the endpoint (S2006, S2009) performed in the second embodiment.

  FIG. 12 is a diagram illustrating an endpoint securing process in the service cooperation apparatus 103. The difference from the end point securing in the service cooperation apparatus 102 according to the second embodiment is that the end point setting change is changed from S3004 to the end point part set S5004, and the parts used for the end point setting are secured when the end point is secured. This is the point that the parts secured by using the parts pool 17 are used without being created.

In the parts set to the end point, the end point manager 15 confirms whether or not the part already exists in the part pool 17, and then secures the part and stores it in the end point.
FIG. 13 is a diagram showing the operation of the parts set to the endpoint by the endpoint manager 15.

  First, in the unused part presence / absence confirmation S6001, the endpoint manager 15 refers to the part status information 153 and confirms whether there is an unused part with the setting requested by the routing endpoint 121. Based on the confirmation result, the endpoint manager 15 performs part creation S6002 or unused part status update S6003 to secure the part. Part creation S6002 is an operation when there is no unused part. In creating the part, the end point manager 15 creates a part for realizing the setting requested from the routing end point 121, and adds the information of the part as “in use” to the part state information 153. If there is an unused part, the endpoint manager 15 updates the information of the part state information 153 corresponding to the found part during use in the unused part state update S6003.

  Next, in the storing of parts into the endpoint S6004, the endpoint manager 15 sets the secured parts in the endpoint. For example, when the end point A is used in the example of FIG. 2, the end point manager 15 secures the part a according to the setting and sets it in the end point A.

FIG. 14 is a diagram illustrating endpoint release processing in the service cooperation apparatus 103 according to the third embodiment. The difference from the endpoint release in the second embodiment is that the parts are returned to the parts pool 17 (S7001) before the endpoints are returned to the endpoint pool 16. In returning to the parts pool 17, the endpoint is returned to the pool and the state information is updated.
FIG. 15 is a diagram illustrating an operation of returning parts to the parts pool 17.

  Store parts in parts pool 17 In step S8001, the endpoint manager 15 extracts parts from the endpoints and stores them in the parts pool 17. In update S8002 of the part state information 153, the endpoint manager 15 updates the part state information 153 and makes the returned part state unused.

  As described above, according to the service cooperation apparatus 103 of the third embodiment, the endpoints are not assigned to the service in a fixed manner, but are reused and assigned to the endpoints when necessary. Therefore, the number of created endpoints can be reduced, and the memory consumption can be reduced. Further, by using the created endpoint, it is possible to reduce the processing time overhead due to the creation of the endpoint as compared with the case where the endpoint is created each time as in the first embodiment. Furthermore, by using the parts created at the time of securing the endpoint, the processing time overhead due to the parts creation can be reduced.

  Although the first to third embodiments have been described above, two or more of these embodiments may be combined and implemented within a consistent range. Alternatively, one of the first to third embodiments may be partially implemented. Alternatively, two or more of these Embodiments 1 to 3 may be combined and implemented within a consistent range. In addition, this invention is not limited to these embodiment, A various deformation | transformation is possible as needed.

Embodiment 4 FIG.
The fourth embodiment will be described with reference to FIGS. 16 and 17. Embodiment 4 demonstrates the hardware constitutions of the service cooperation apparatuses 101-103 which are computers.
FIG. 16 is a diagram illustrating an example of the appearance of the service cooperation apparatuses 101 to 103 which are computers.
FIG. 17 is a diagram illustrating an example of hardware resources of the service cooperation apparatuses 101 to 103.

  In FIG. 016 showing the appearance, the service cooperation apparatus 101 or the like includes a system unit 830, a display apparatus 813 having a CRT (Cathode / Ray / Tube) or LCD (liquid crystal) display screen, a keyboard 814 (Key / Board: K / B). ), A mouse 815, and a compact disk device 818 (CDD: Compact Disk Drive). These hardware resources are connected by cables and signal lines. The system unit 830 is connected to the network.

  In FIG. 17 showing hardware resources, the service cooperation apparatus 101 or the like includes a CPU 810 (Central Processing Unit) that executes a program. The CPU 810 is connected to a ROM (Read Only Memory) 811, a RAM (Random Access Memory) 812, a display device 813, a keyboard 814, a mouse 815, a communication board 816, a CDD 818, and a magnetic disk device 820 via a bus 825. Control hardware devices. Instead of the magnetic disk device 820, a storage device such as an optical disk device or a flash memory may be used.

  The RAM 812 is an example of a volatile memory. Storage media such as the ROM 811, the CDD 818, and the magnetic disk device 820 are examples of nonvolatile memories. These are examples of a storage unit, a storage unit, and a buffer (these are collectively referred to as a storage device). Storage unit (an example of information storage unit, service execution order information storage unit, service execution program management information storage unit, service execution program storage unit, control information storage unit, etc.) is a storage unit, storage unit, buffer, etc. The endpoints and parts created by the point manager 15 are stored. At this time, as shown in the first to third embodiments, the end points and parts are deleted after use (first embodiment), or the unused end points and parts are reused (second embodiment). 3) Therefore, the memory usage can be reduced. Further, these storage devices store routing definition 1211, end point management information 151, end point state information 152, part state information 153, and the like.

  The communication board 816, the keyboard 814, and the like are examples of an input unit and an input device. The communication board 816, the display device 813, and the like are examples of an output unit and an output device. The communication board 816 is connected to the network.

  The magnetic disk device 820 stores an operating system 821 (OS), a window system 822, a program group 823, and a file group 824. The programs in the program group 823 are executed by the CPU 810, the operating system 821, and the window system 822.

  The program group 823 stores programs that execute the functions described as “˜units” in the description of the above embodiments. The program is read and executed by the CPU 810.

  In the description of the above embodiment, the file group 824 includes “to determination result”, “to calculation result”, “to extraction result”, “to generation result”, and “to processing result”. The described information, data, signal values, variable values, parameters, and the like are stored as items of “˜file” and “˜database”. The “˜file” and “˜database” are stored in a recording medium such as a disk or a memory. Information, data, signal values, variable values, and parameters stored in a storage medium such as a disk or memory are read out to the main memory or cache memory by the CPU 810 via a read / write circuit, and extracted, searched, referenced, compared, and calculated. Used for CPU operations such as calculation, processing, output, printing, and display. Information, data, signal values, variable values, and parameters are temporarily stored in the main memory, cache memory, and buffer memory during the CPU operations of extraction, search, reference, comparison, operation, calculation, processing, output, printing, and display. Is remembered.

  In the description of the embodiment described above, the data and signal values are the memory of the RAM 812, the compact disk of the CDD 818, the magnetic disk of the magnetic disk device 820, the other optical disk, the mini disk, and the DVD (Digital Versatile Disk). Or the like. Data and signals are transmitted on-line via the bus 825, signal lines, cables, and other transmission media.

  In the above description of the embodiment, what has been described as “to part” may be “to means”, and “to step”, “to procedure”, and “to processing”. May be. That is, what has been described as “˜unit” may be implemented by software alone, a combination of software and hardware, or a combination of firmware. Firmware and software are stored as programs in a recording medium such as a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, and a DVD. The program is read by the CPU 810 and executed by the CPU 810. That is, the program causes the computer to function as the “˜unit” described above. Alternatively, the computer executes the procedure and method of “to part” described above.

  In the above embodiment, the service cooperation apparatus has been described. However, it is clear from the above description that the service cooperation apparatus can be grasped as a service cooperation program or a service cooperation method performed by the service cooperation apparatus.

In the above embodiment, the service cooperation apparatus having the following characteristics has been described.
A service cooperation device that has a function to dynamically secure and release service cooperation components according to the routing definition.

In the above embodiment, the service cooperation apparatus having the following characteristics has been described.
A service cooperation apparatus having a function of storing a service cooperation component that has been processed without discarding, and a function of managing the state of the service cooperation component.

In the above embodiment, the service cooperation apparatus having the following characteristics has been described.
A service cooperation apparatus having a function for holding a part for changing processing of a service cooperation part and a function for changing processing of a service cooperation part using a part for changing the processing of the service cooperation part.

  101, 102, 103 Service cooperation device, 2 Service requester, 31 Service A, 32 Service B, 33 Service C, 34 Service D, 11 Communication component, 111 Communication endpoint, 12 Routing component, 121 Routing endpoint, 1211 Routing definition , 13 Component X, 131 Endpoint A, 1311 Part a, 132 Endpoint B, 1321 Part b, 14 Component Y, 141 Endpoint C, 1411 Part c, 142 Endpoint D, 1421 Part d, 15 Endpoint Manager, 151 Endpoint management information, 152 Endpoint status information, 153 Parts status information, 16 Endpoint pool, 161 End Into E, 162 endpoint F, 17 parts pool, 19 storage unit.

Claims (5)

At least one service connection unit connected to at least one service;
An information storage unit having a memory area for storing information used by the service connection unit;
Service execution order information in which, in the order of the services to be executed, the types of service execution programs that execute the services, the service execution program type that indicates the service to be executed is described together with the control information that controls the operation of the service execution program A service execution order information storage unit for storing
A service execution program management information storage unit that stores service execution program management information in which a correspondence relationship with the service connection unit that can use the service execution program is described for each service execution program of a plurality of service execution programs;
A receiver for receiving a service execution request;
When the receiving unit receives the request, by referring to the service execution order information in the service execution order information storage unit, the type of service execution program to be executed and the service execution program to be executed A service execution program identification unit that identifies control information corresponding to the type;
The service execution program of the type specified by the service execution program specification unit is generated by referring to the service execution program management information in the service execution program management information storage unit. A storage execution unit for specifying the service connection unit that can use the program, and storing the generated service execution program and the control information in the memory area of the information storage unit used by the specified service connection unit;
Execution result obtained by causing the service execution program stored in the information storage unit to execute the service indicated by the type of the service execution program and acquiring the execution result of the service from the executed service execution program A service cooperation apparatus comprising an acquisition unit. The service cooperation apparatus further includes:
A service execution program storage unit for storing the service execution program generated by the storage execution unit;
The storage execution unit
When the service execution program specifying unit specifies the type and control information of the service execution program, it is determined whether a service execution program that can be used as the specified type of service execution program is stored in the service execution program storage unit, The service cooperation apparatus according to claim 1, wherein if the service execution program is determined to be stored, the service execution program determined to be stored is used without generating the service execution program. The service cooperation apparatus further includes:
A control information storage unit for storing the control information generated by the storage execution unit;
The storage execution unit
When the service execution program specifying unit specifies the type of service execution program and the control information, it is determined whether or not control information that can be used as the specified control information is stored in the control information storage unit. 3. The service cooperation apparatus according to claim 2, wherein when the determination is made, the control information determined to be stored is used without generating the control information. The service cooperation device
When the execution result acquisition unit acquires the execution result, a deletion unit that deletes the service execution program from which the execution result is acquired and the control information of the service execution program from the memory area of the information storage unit The service cooperation apparatus according to claim 1, further comprising: Computer
At least one service linking unit linked to at least one service;
An information storage unit having a memory area for storing information used by the service connection unit;
Service execution order information in which, in the order of the services to be executed, the types of service execution programs that execute the services, the service execution program type that indicates the service to be executed is described together with the control information that controls the operation of the service execution program Service execution order information storage unit for storing
A service execution program management information storage unit for storing service execution program management information in which a correspondence relationship with the service connection unit capable of using the service execution program is described for each service execution program of a plurality of service execution programs;
A receiving unit that receives a service execution request,
When the receiving unit receives the request, by referring to the service execution order information in the service execution order information storage unit, the type of service execution program to be executed and the service execution program to be executed A service execution program identification unit that identifies control information corresponding to the type,
The service execution program of the type specified by the service execution program specification unit is generated by referring to the service execution program management information in the service execution program management information storage unit. A storage execution unit for specifying the service connection unit that can use the program and storing the generated service execution program and the control information in the memory area of the information storage unit used by the specified service connection unit;
Execution result obtained by causing the service execution program stored in the information storage unit to execute the service indicated by the type of the service execution program and acquiring the execution result of the service from the executed service execution program Service linkage program to function as an acquisition unit.

Images