7.3 Defining Deployment of HCSC Components

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

[Figure]

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 definitionService typeDeployment can be defined or not
Database usageCosminexus RM usage
1UsedUsedAllY
2Not usedNot usedBusiness processes (to be made persistent)--
3Business processes (not to be made persistent)Y
4SOAP adapterY
5SessionBean adapterY
6MDB (WS-R) adapter--
7MDB (database queue) adapter--
8DB adapterY
9TP1 adapterY
10File adapterY
11Object Access adapterY
12Message Queue adapterY
13FTP adapterY
14File operations adapterY
15Mail adapterY
16HTTP adapterY
17Custom adapterY
18UsedNot usedBusiness processes (to be made persistent)--
19Business processes (not to be made persistent)Y
20SOAP adapterY
21SessionBean adapterY
22MDB (WS-R) adapter--
23MDB (database queue) adapter--
24DB adapterY
25TP1 adapterY
26File adapterY
27Object Access adapterY
28Message Queue adapterY
29FTP adapterY
30File operations adapterY
31Mail adapterY
32HTTP adapterY
33Custom adapterY
Legend:
Y: Deployment can be defined.
--: Deployment cannot be defined..

Organization of this section
7.3.1 Clusters (or Single HCSC Servers) to Which HCSC Components Can Be Deployed
7.3.2 Adding HCSC Components to a Cluster
7.3.3 Deleting HCSC Components from a Cluster