3.1.9 Importing the HCSC component definition files into the operating environment
This section describes how to import the definition files of the following HCSC components into the operating environment by using the -operation get option of the csccmctl command:
-
DB adapter
-
TP1 adapter
-
File adapter
-
Object Access adapter
-
Message Queue adapter
-
FTP adapter
-
File operations adapter
-
Mail adapter
-
HTTP adapter
-
Command adapter
-
SFTP adapter
-
Custom adapter
-
SOAP reception
-
TP1/RPC reception
-
FTP reception
-
HTTP reception
-
Message queue reception
-
File event reception
-
Custom reception
After developers develop the preceding HCSC components and specify their deployment definitions, the operator uses the preceding option when importing the definition files into the operating environment.
Note that the definition files are not set up in the operating environment the moment the files are obtained. To set up the definition files in the operating environment, you must use the -operation set option after obtaining the files. For details about how to set up the definition files, see 3.1.10 Setting and updating the HCSC component definition files in the operating environment.
- Organization of this subsection
(1) Examples of command usage
The following is an example of using the command for obtaining the definition files. For details on the csccmctl command, see "csccmctl (Managing definition files)" in "Service Platform Reference Guide".
- Example 1
-
To obtain the definition file "csccustomadapter.properties" with cluster name "CLS1" and service ID "ADP1" in the directory beneath "C:\tmp":
csccmctl -cluster CLS1 -name ADP1 -targetfilename csccustomadapter.properties -basedir C:\tmp -operation get
- Example 2
-
To obtain the communication definition file "adptp1_config.xml", which is set in the TP1 adapter and has the cluster name "CLS1" and service ID "ADP1", in the directory beneath "C:\tmp"
csccmctl -cluster CLS1 -name ADP1 -targetfilename adptp1_config.xml -basedir C:\tmp -operation get
(2) Points to be considered
-
If the definition file with the same specified file name already exists in the directory, the file in the directory is overwritten.
-
In the following cases, the command terminates abnormally:
-
If the directory specified in the -basedir option does not exist
-
If a directory with the same name as the specified file name exists
-
If writing to the file fails
-