uCosminexus Service Platform, Basic Development Guide
Deployment definition means determining the cluster (or single HCSC server) in which to deploy the defined HCSC component.
In the system configuration definition list displayed in the tree view, a HCSC component displayed at a lower order than a cluster (or single HCSC server) is defined to be deployed in that cluster (or single HCSC server). You define deployment by adding (or deleting) the HCSC components to be deployed to (or from) a lower order than the cluster (or single HCSC server) in the system configuration definition list in the tree view. The following figure shows an example of adding and deleting HCSC components. The following figure shows an example of adding and deleting HCSC components:
Figure 7-3 Adding and deleting HCSC components
With their deployment defined in the development environment, HCSC components are deployed to the cluster (or single HCSC server) in the operating environment according to the contents of the updated system configuration definition. For details about how to deploy HCSC components to a cluster (or single HCSC server), see the sections related to the deployment of service adapters and business processes in the manual Cosminexus Service Platform System Setup and Operation Guide.
The following subsections explain how to define deployment by adding (or deleting) HCSC components to (or from) a cluster (or single HCSC server).
Note that in some cases, you might not be able to define deployment depending on the combination of the server configuration that is defined in the system configuration definition and services. The following table describes whether the deployment can be defined based on the combination of the server configuration that is defined in the system configuration definition and services:
Table 7-1 Deployment can be defined or not
Item No. | Server configuration defined in the system configuration definition | Service type | Deployment can be defined or not | |
---|---|---|---|---|
Database usage | Cosminexus RM usage | |||
1 | Used | Used | All | Y |
2 | Not used | Not used | Business processes (to be made persistent) | -- |
3 | Business processes (not to be made persistent) | Y | ||
4 | SOAP adapter | Y | ||
5 | SessionBean adapter | Y | ||
6 | MDB (WS-R) adapter | -- | ||
7 | MDB (database queue) adapter | -- | ||
8 | DB adapter | Y | ||
9 | TP1 adapter | Y | ||
10 | File adapter | Y | ||
11 | Object Access adapter | Y | ||
12 | Message Queue adapter | Y | ||
13 | FTP adapter | Y | ||
14 | File operations adapter | Y | ||
15 | Mail adapter | Y | ||
16 | HTTP adapter | Y | ||
17 | Custom adapter | Y | ||
18 | Used | Not used | Business processes (to be made persistent) | -- |
19 | Business processes (not to be made persistent) | Y | ||
20 | SOAP adapter | Y | ||
21 | SessionBean adapter | Y | ||
22 | MDB (WS-R) adapter | -- | ||
23 | MDB (database queue) adapter | -- | ||
24 | DB adapter | Y | ||
25 | TP1 adapter | Y | ||
26 | File adapter | Y | ||
27 | Object Access adapter | Y | ||
28 | Message Queue adapter | Y | ||
29 | FTP adapter | Y | ||
30 | File operations adapter | Y | ||
31 | Mail adapter | Y | ||
32 | HTTP adapter | Y | ||
33 | Custom adapter | Y |
All Rights Reserved. Copyright (C) 2015, Hitachi, Ltd.