uCosminexus Service Platform, Basic Development Guide

[Contents][Glossary][Index][Back][Next]

7.5.1 Flow of processes from deploying to starting HCSC components

The following are the flow of the series of processes from deploying HCSC components on the HCSC server until starting them, the range of the HCSC components to be operated and the differences in processing according to the type of HCSC components:

Organization of this subsection
(1) Flow of processes
(2) HCSC components to be operated
(3) Differences in processing according to the type of HCSC components

(1) Flow of processes

The following figure shows the flow of the processes from deploying HCSC components on the HCSC server until starting them. Note that if you perform operations in the development environment, steps 2 to 6 of the figure will execute automatically.

Figure 7-4 Flow of processes from deploying to starting HCSC components

[Figure]

  1. Perform batch execution of operations in the development environment.
  2. In the development environment, the HCSC components are packaged and saved in a repository.
  3. Deployment is defined, and the system configuration definition within the repository is updated.
  4. The repository of the development environment is transferred to the operating environment.
  5. Based on the system configuration definition updated in the development environment, HCSC components are deployed from the operating environment onto the HCSC server of the execution environment.
  6. The HCSC components deployed on the HCSC server of the execution environment are started.

(2) HCSC components to be operated

The HCSC components to be operated when only the selected HCSC components are deployed on the HCSC server and started are different from the HCSC components to be operated when all the HCSC components are deployed on the HCSC server and started. HCSC components to be operated imply the HCSC components for which the series of processes from deployment to startup is to be executed.

Deploying the selected HCSC components on the HCSC server and starting them
The HCSC components selected in the development environment are to be operated. If the selected HCSC component is a business process, the HCSC components (business processes, service adapters, and user-defined receptions) defined in that business process will also be operated.
The following figure shows the range of HCSC components to be operated when a business process is selected:

Figure 7-5 Range of HCSC components to be operated (When a business process is selected)

[Figure]

Here, Referencing HCSC Components indicates the use of other HCSC components depending on the addition of a user-defined reception and specification in the invoke service activity.

Note
Because a user-defined reception is processed simultaneously with the business process in the development environment, a user-defined reception cannot be operated alone.

Deploying all the HCSC components in the HCSC server and starting them
All the HCSC components defined in the development environment are to be operated.

(3) Differences in processing according to the type of HCSC components

The processing, when the HCSC component to be operated is a service adapter, is different from the processing when the HCSC component to be operated is a business process.

For a service adapter
Packaging and deployment definition are not performed again for a service adapter if the service adapter is already packaged and the deployment is defined (public).

For a business process
Because the Java classes might have been changed, packaging and deployment definition are performed again.