JP6392380B2 - Service support system, service support method, and service support program - Google Patents

Description

  The present invention relates to a service support system, a service support method, and a service support program for performing a service in a system configured by a plurality of environments.

  In a computer system, a plurality of processes may be linked to perform one business process (see, for example, Patent Document 1). In the system described in this document, when a return message “communication error” is received with respect to the transmitted message, the control unit adds the number of detours and retransmits while the number of detours does not exceed the reference value. . Such a system is used for a transaction service or the like performed with a customer by linking a plurality of product services.

  In view of this, a timeout monitoring system for early detection of timeout when a request process is executed in cooperation with a plurality of processes has been studied (for example, see Patent Document 2). In the technique described in this document, the timer monitoring unit of the process device specifies a transaction request and specifies a timer value according to the transaction request. The process device transmits a message including a timer value to each subsequent process device, and the timer monitoring unit executes an event monitoring process. The timer monitoring unit determines normal completion or time-out, and executes time-out report processing when time-out is determined.

JP 2009-237789 A JP 2012-138015 A

  By the way, the service support system may be composed of a plurality of system environments. As described above, when business systems in a plurality of different system environments are linked, it is necessary to perform message conversion (for example, character code conversion) according to the system environment, and overhead when transmitting a request message or a response message May increase. In such a system, the system load becomes large, and there is a possibility that quick response becomes difficult.

  The present invention has been made to solve the above-described problems, and an object of the present invention is to provide a service support system, a service support method, and a service support program for efficiently performing a service in a system configured by a plurality of environments. Is to provide.

  The service support system that solves the above problems includes a first system configured in the first system environment and a second system configured in the second system environment. In the second system, a plurality of service function units and a composite unit that calls the plurality of service function units are provided, and the second system acquires a request message from the first system, and requests the composite unit. When a message is acquired, the service function unit associated with the composite unit is sequentially called to execute service processing, the execution result is returned to the first system, and a request message for each service function unit is acquired. If so, the service function unit is called to execute service processing, and the execution result is returned to the first system. Thus, by compositing a plurality of services, the services can be efficiently provided in a plurality of systems having different system environments.

  In the service support system, when the request message for the composite part is acquired, exclusive control of the database related to the request message is executed, and in the service processing related to the request message, the service processing is permitted, and the request message is It is preferable that the exclusive control is terminated after all the related service processes are terminated. As a result, the individual services related to the same composite service can be updated without being exclusively controlled.

  In the service support system, it is preferable that the operation system is different between the first system environment and the second system environment. Thereby, even when the operation systems are different, the service can be efficiently provided.

  In the service support system, it is preferable that the first system environment and the second system environment have different character code systems. Thereby, even when the character code is different, the service can be efficiently provided.

  ADVANTAGE OF THE INVENTION According to this invention, in the system comprised by several environment, a service can be performed efficiently.

The system schematic of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. It is explanatory drawing of the process sequence of this embodiment, Comprising: (a) is a single service, (b) is explanatory drawing of a composite service. Explanatory drawing of the process sequence of other embodiment.

  DESCRIPTION OF EMBODIMENTS Hereinafter, embodiments embodying the present invention will be described with reference to FIGS. In the present embodiment, a service support system that connects a plurality of business systems (product management systems) that manage each product in a financial institution will be described. This service support system is constructed by a hub and spoke system, and a business system connected to the hub system functions as a spoke system. The hub system distributes messages to destinations and controls transaction processing. In this embodiment, the hub system is a core system (first system environment) centered on a general-purpose computer system (mainframe) used for a company's core business system, and the business system is an open system (second system). Environment). For this reason, the hub system performs protocol conversion according to different system environments (OS, character codes, etc.).

  The outline of the service support system will be described with reference to FIG. The service support system includes a channel layer 10, a common system 20 as a first system, and a product layer 30 as a second system.

The channel layer 10 is a system that accepts transactions with customers, such as store terminals, automatic teller machines (ATMs), and Internet banking servers.
The common system 20 is a computer system that manages processes (common tasks) commonly performed in transactions with customers. The common system 20 includes a main frame, and manages common accounts, customer numbers, commissions, and the like as common work. The common system 20 holds a flow definition table for calling each service (product service or composite service) of the product layer 30 described later. In this flow definition table, the service to be called is registered corresponding to the transaction type.

  The product layer 30 is a computer system that manages each product (finance, foreign exchange, trust, time deposit, etc.) provided by a financial institution. The product layer 30 is configured by a product service control 31 including an open environment system. For one commodity (for example, foreign exchange), a plurality of commodity services (for example, screen input, foreign currency calculation, check, database writing, etc.) are used. For this reason, one product service control 31 manages a product service A (for example, foreign currency calculation) for each product. The other product service control 31 manages the product service B (for example, database writing).

  One transaction may relate to a plurality of products. In this case, a plurality of product service controls 31 are used for one transaction request message acquired from the channel layer 10. Thus, the composite control 32 is provided in the product layer 30 for the composite service using a plurality of product services. The composite control 32 is activated by executing a service support program and calls each product service. In this case, each product service is called in a predetermined order to link a plurality of product services.

  In the present embodiment, it is assumed that the common system 20 that has acquired the transaction request message from the channel layer 10 calls the service of the product layer 30. Here, when calling an individual product service, a request message is transmitted to the target product service control 31 in the product layer 30. In this case, the common system 20 transmits a request message using a protocol that can be used in the product layer 30.

  On the other hand, when using the composite service in the product layer 30, the common system 20 transmits a request message to the composite control 32. In this case, the common system 20 transmits a request message to the composite control 32 using a protocol that can be used in the product layer 30. The composite control 32 stores each product service used in the composite service and the service execution order. For example, the composite control 32 that combines the product services A to C calls the product service controls 31 of the product services A to C in the order stored in the system environment of the same product layer 30.

  Further, the product layer 30 includes a database device 35 that stores data for realizing each product service. The database device 35 uses the same data by another product service control 31 while one product service control 31 is using the data so that a plurality of product service controls 31 do not use the same data at the same time. Perform exclusive control to limit.

  Next, a case where the common system 20 configured in the first system environment executes a transaction service using the product service of the product layer 30 configured in the second system environment will be described with reference to FIG. .

  First, the common system 20 executes a request message transmission process (step S1-1). Specifically, when a transaction is performed with a customer, a transaction request message is transmitted from the channel layer 10 to the common system 20. The common system 20 that has received the transaction request message from the channel layer 10 transmits a processing request message to the product layer 30 based on the transaction content of the transaction request message. In this case, the common system 20 specifies the service to be called using the flow definition table based on the transaction type of the transaction request message. Then, the service identifier of this service is set in the request message.

  Then, the product layer 30 executes a request message acquisition process from the common system 20 (step S1-2). In this case, processing differs depending on the composite service or the single product service.

  When “single service” is called, the product layer 30 executes product service processing (step S1-3). Then, the product service control 31 executes a process according to the product service request using the product service number.

  When the product service process is completed, the product service control 31 of the product layer 30 executes a response message return process (step S1-8). Specifically, the product service control 31 returns a response message corresponding to the product service request message to the common system 20. This response message includes the processing result of the product service.

  On the other hand, when “composite” is called, the composite control 32 of the product layer 30 executes a product service specifying process (step S1-4). The composite control 32 specifies the product service that constitutes the composite service.

  Next, the composite control 32 of the product layer 30 executes a calling process for the product service (step S1-5). Specifically, the composite control 32 makes a product service request to the specified product service control 31 using the composite number.

  In this case, the product service control 31 executes product service processing (step S1-6). The merchandise service control 31 executes processing corresponding to the merchandise service request using the composite number. In this case, the composite control 32 temporarily records the finished product service.

  Then, the composite control 32 of the product layer 30 executes a determination process as to whether or not all services have been terminated (step S1-7). Specifically, the composite control 32 determines whether or not the processing for all the product services constituting the composite service has been completed.

  When it is determined that all the product services have not ended (in the case of “NO” in step S1-7), the composite control 32 of the product layer 30 executes a call process for an unprocessed product service (step S1- 5).

  On the other hand, when it is determined that all services have been terminated (in the case of “YES” in step S1-7), the composite control 32 of the product layer 30 executes a response message return process (step S1-8).

  Then, the common system 20 executes a response message acquisition process (step S1-9). Specifically, the common system 20 acquires a response message including a processing result from the product layer 30. In this case, it is determined whether or not the product service corresponding to the transaction service request message acquired from the channel layer 10 has been terminated. If an unprocessed product service remains, the common system 20 transmits an unprocessed service request message to the product layer 30. On the other hand, when all the product services are completed, the common system 20 returns a response message of the transaction service to the channel layer 10.

Next, the processing when using the composite service will be described in detail with reference to FIG.
First, the composite control 32 performs preprocessing (step S2-1). In this pre-processing, each process of merchandise service information check, service block check, item block check, transaction status check, exclusive control, and journal setting is executed.

The product service information check is a process of confirming the product service constituting the composite service.
The service blockage check is a process for confirming the operating status of the specified product service. For example, it is confirmed whether or not the service provision has been stopped due to the service provision time or system maintenance.

The detail blockage check is a process of confirming the status of a transaction service request message target (for example, an account).
The transaction status check is a process for confirming the status of the transaction.
The exclusive control is a process for performing exclusive control on the storage area of the database device 35 used for the service.
The journal setting is a process for securing an area for recording a service provision history.

  Then, the composite control 32 executes main processing (step S2-2). Here, the product service necessary for the composite service and the processing order of each product service are specified.

  Next, the composite control 32 executes a calling process (step S2-3). Here, the composite control 32 calls each predetermined product service control 31 in the composite service.

  In this case, the product service control 31 performs preprocessing (step S3-1). In this pre-processing, each process of product service information check, composite number acquisition, context information registration, and journal setting is executed.

The product service information check is a process for confirming the product service to be processed.
The composite number acquisition is processing for acquiring the composite number included in the request message acquired from the composite control 32.
The context information registration is a process of temporarily storing context information such as arguments used for the product service.
The journal setting is a process for securing an area for recording a service provision history.

  Then, the merchandise service control 31 executes main processing (step S3-2). Here, the product service control 31 executes product service processing.

  Next, the product service control 31 executes a call process (step S3-3). Specifically, the product service control 31 updates the database device 35 based on the request message. In this case, the product service control 31 accesses the database device 35 using the composite number acquired from the composite control 32.

  Then, the product service control 31 performs post-processing (step S3-4). In this post-processing, journal information registration and context sub-information clear processing are executed.

Journal information registration is a process of recording a service provision history.
The context sub information clear is a process of deleting the context information used for the composite service.

Next, when all the product services are finished, the composite control 32 executes post-processing (step S2-4). In this post-processing, optimistic exclusive control and context information clear processing are executed.
The optimistic exclusive control is a process for performing control that enables data update when the exclusive control of itself is continued.
The context information clear is a process for deleting the context information used for the product service.

Next, exclusive control in the database apparatus 35 will be described with reference to FIG.
FIG. 4A is an explanatory diagram of processing in a single product service.
Here, in the product service control 31, when the product service pre-processing (step S4-1) is executed, the database device 35 executes a lock process for the product service (step S4-2). In this case, the database device 35 performs exclusive control using the product service number recorded in the service request. Then, access to the product service control 31 and the composite control 32 other than the product service number is excluded. On the other hand, in the case of access by the product service control 31 of the same product service number (step S4-3), the database device 35 permits data update.

  Then, in the product service control 31, when the product service post-processing (step S4-4) is executed, the database device 35 executes lock release processing (step S4-5).

On the other hand, FIG. 4B is an explanatory diagram of processing in the composite service.
When pre-processing (step S5-1) is executed in the composite control 32, the database device 35 executes lock processing for this composite service (step S5-2). In this case, the database device 35 performs exclusive control using the composite number recorded in the service request. Then, exclusive access control is performed by the product service control 31 and the composite control 32 other than the composite number.

  When one product service is called in the composite control 32 (step S5-3), the database device 35 allows the data update of each product service control 31 called from the composite control 32. In this case, the product service control 31 accesses the database device 35 using the composite number. Then, the database device 35 allows data update by access from the product service control 31 using the same composite number.

  Even when another product service is called in the composite control 32 (step S5-4), the database device 35 allows the data update of the product service control 31 called from the same composite control 32. Also in this case, the product service control 31 accesses the database device 35 using the composite number. And even if it is access from other goods service control 31, the database apparatus 35 will accept | permit data update, as long as the same composite number as the time of locking is used.

  When all the product services are finished, the composite control 32 executes post-processing (step S5-5). In this case, the database device 35 executes a lock release process (step S5-6).

As described above, according to the present embodiment, the following effects can be obtained.
(1) In this embodiment, when using a composite service, the common system 20 transmits a request message to the composite control 32. In this case, the common system 20 transmits a request message to the composite control 32 using a protocol that can be used in the product layer 30. Here, when the system environment in the common system 20 and the system environment in the product layer 30 are different, if the common system 20 calls a plurality of product services in the product layer 30 individually, the processing load due to the difference in environment increases. Become. Therefore, as in this embodiment, by using a composite service, a plurality of product services can be combined and efficiently processed.

  (2) In the present embodiment, the composite control 32 performs preprocessing (step S2-1). In this pre-processing, each process of merchandise service information check, service block check, item block check, transaction status check, exclusive control, and journal setting is executed. Thereby, the environment in the case of using a plurality of product services can be prepared.

  (3) In this embodiment, when pre-processing (step S5-1) is executed in the composite control 32, the database device 35 executes lock processing for this composite service (step S5-2). . When one product service is called in the composite control 32 (steps S5-3 and S5-4), the database device 35 allows data update of each product service control 31 called from the composite control 32. . Thereby, a plurality of product services included in the common composite service can be updated without exclusive control.

In addition, you may change the said embodiment into the following aspects.
In the above-described embodiment, the service support system includes the common system 20 and the product layer 30 constructed by the hub and spoke method. The service support system is not limited to the above-described form as long as it is a system configured by a plurality of system environments. The present invention can also be applied to an online system that requires high-speed response, stability, and safety.

  In the above embodiment, the composite service is configured to call a plurality of product services. Here, the composite service may call another composite service. Further, a plurality of composite services may be called in one transaction service.

  In the above embodiment, the composite control 32 is provided for a composite service that uses a plurality of product services. Here, it may be determined whether or not the composite service needs to be mounted using a service design support apparatus. This design support apparatus is connected to a transaction history information storage unit that records past transaction histories.

A design process in the design support apparatus will be described with reference to FIG.
First, the design support apparatus executes a service history acquisition process (step S6-1). Specifically, the design support apparatus outputs a designating screen for a transaction service to be designed on a display. Here, the person in charge inputs the transaction service to be designed on the designation screen. In this case, the design support apparatus acquires the usage history of the transaction service to be designed from the transaction history information storage unit.

  Next, the design support apparatus executes a service processing load prediction process (step S6-2). Specifically, the design support apparatus specifies a product service necessary for realizing the transaction service. Then, the design support apparatus calculates the load when the common system 20 calls the product service of the product layer 30 individually. In this case, the service processing load is calculated by adding the overhead when a request message is transmitted from the common system 20 to the product layer 30.

  Next, the design support apparatus executes a mounting candidate specifying process (step S6-3). Specifically, the design support apparatus identifies a mounting candidate that combines a plurality of product services. For example, when the transaction service is composed of product services A, B, and C, the following implementation candidates are generated.

-Composite services (A, B, C): All product services are composited.
Composite service (A, B) and product service C: Composite product services A and B.
Product service A and composite service (B, C): Product services B and C are composited.
Product service A, product service B, product service C: Not composited.

Next, the design support apparatus repeats the following processing for each mounting candidate.
A determination process is performed as to whether or not the existing composite can be used (step S6-4). Specifically, the design support apparatus searches for an existing composite and determines whether or not a composite service included in a processing target implementation candidate is recorded.

  When it is determined that the existing composite can be used (in the case of “YES” in step S6-4), the design support apparatus executes processing for specifying a product service other than the existing composite (step S6-5). Specifically, the design support device specifies the remaining product service obtained by subtracting the product service included in the composite service from the product service included in the transaction service. When it is determined that the existing composite cannot be used (“NO” in step S6-4), the design support apparatus skips the product service specifying process (step S6-5) other than the existing composite.

  Next, the design support apparatus executes an overhead calculation process (step S6-6). Specifically, the design support apparatus calculates a load when a request message is transmitted from the common system 20 to the product layer 30. In this case, a request message required to call an individual product service or composite service is specified, and an overhead required for the request message is calculated.

Next, the design support apparatus executes a performance calculation process (step S6-7). Specifically, the design support apparatus calculates a system load and a delay time based on the calculated overhead.
The design support apparatus repeats until all the mounting candidates are finished.

Then, the design support apparatus executes an evaluation result output process (step S6-8). Specifically, the design support apparatus outputs a table in which the calculated performance is associated for each mounting candidate.
Thereby, the necessity of a composite service can be determined in consideration of a transaction history.

  Furthermore, the necessity of the composite service may be determined in consideration of a combination of product services used in all transaction services. In this case, a plurality of product services that are commonly used in the transaction services of a plurality of transaction types are specified. Then, a composite service is constructed using these product services.

  DESCRIPTION OF SYMBOLS 10 ... Channel layer, 20 ... Common system, 30 ... Product layer, 31 ... Product service control, 32 ... Composite control, 35 ... Database apparatus.

Claims (5)

A service support system including a first system configured in a first system environment and a second system configured in a second system environment,
In the second system functioning as a spoke system, a plurality of service function units executing service processing in response to a request from the first system functioning as a hub system, and a group of the plurality of service function units A composite part that calls the service function part,
The second system comprises:
Obtaining a request message from the first system;
When the request message for the composite unit is acquired, the operating status of each service function unit associated with the composite unit is confirmed, and the exclusive control of the database used by the service function unit is performed using the composite number. The service function unit is sequentially called , and the service function unit executes the service process in the spoke system while acquiring the composite number and updating the database . After execution, the exclusive control by the composite number is canceled in the database, and the execution result is returned to the first system,
When a request message for an individual service function unit is acquired, the service function unit is called to execute a service process, and an execution result is returned to the first system. The service support system according to claim 1 , wherein an operation system is different between the first system environment and the second system environment. The service support system according to claim 1 or 2 , wherein the first system environment and the second system environment have different character code systems. A method for supporting a service using a service support system including a first system configured in a first system environment and a second system configured in a second system environment,
In the second system functioning as a spoke system, a plurality of service function units executing service processing in response to a request from the first system functioning as a hub system, and a group of the plurality of service function units A composite part that calls the service function part,
The second system comprises:
Obtaining a request message from the first system;
When the request message for the composite unit is acquired, the operating status of each service function unit associated with the composite unit is confirmed, and the exclusive control of the database used by the service function unit is performed using the composite number. The service function unit is sequentially called , and the service function unit executes the service process in the spoke system while acquiring the composite number and updating the database . After execution, the exclusive control by the composite number is canceled in the database, and the execution result is returned to the first system,
When a request message for an individual service function unit is acquired, the service function unit is called to execute a service process, and an execution result is returned to the first system. A program for supporting a service using a service support system including a first system configured in a first system environment and a second system configured in a second system environment,
In the second system functioning as a spoke system, a plurality of service function units executing service processing in response to a request from the first system functioning as a hub system, and a group of the plurality of service function units A composite part that calls the service function part,
The second system;
Obtaining a request message from the first system;
When the request message for the composite unit is acquired, the operating status of each service function unit associated with the composite unit is confirmed, and the exclusive control of the database used by the service function unit is performed using the composite number. The service function unit is sequentially called , and the service function unit executes the service process in the spoke system while acquiring the composite number and updating the database . After execution, the exclusive control by the composite number is canceled in the database, and the execution result is returned to the first system,
A service support program that, when a request message for an individual service function unit is acquired, calls the service function unit to execute service processing, and functions as a means for returning an execution result to the first system. .

Images