4.6.1 Adding and updating a repository using component as a unit

Execute the cscrepctl command by specifying the -import option to add (import) or update a repository using component as a unit. You can validate whether the HCSC components within the specified repository ZIP file can be imported in the repository of the operating environment by executing the cscrepcheck command prior to import operation.

Organization of this subsection

(1) Validation of possibility of import prior to import operation (cscrepcheck command)
(2) Importing a repository using component as a unit (cscrepctl command)

(1) Validation of possibility of import prior to import operation (cscrepcheck command)

Use the cscrepcheck command to check information of the HCSC components of the repository of the operating environment and status of these components, to validate the following contents and display the validation result. For details on the cscrepcheck command, see "cscrepcheck (Verifying importability)" in "Service Platform Reference Guide".

Whether it is possible to import the repository ZIP file
Whether it is possible to import the HCSC components within the repository ZIP file using component as a unit

The repository is not imported when you use the cscrepcheck command. Execute the cscrepctl command to import the repository.

(a) Cases in which the possibility of import cannot be validated

The possibility of importing the repository information cannot be validated in the following cases:

If the current repository information of the operating environment and the repository information to be validated do not have a single cluster configuration
If the SOAP mode is different in the current repository information of the operating environment and the repository information to be validated

If the settings related to the option of whether to use the database and Reliable Messaging are different

The following table describes the possibility of validating import when the settings are different:

Table 4‒6: Settings to be performed when the possibility of import can be validated and when it cannot be validated
Settings to be performed in the current repository information of the operating environment	Settings to be performed in the repository information to be validated
	Use database as well as Reliable Messaging	Use database and do not use Reliable Messaging	Do not use database as well as Reliable Messaging
Use database as well as Reliable Messaging	Y	Y	Y
Use database and do not use Reliable Messaging	N	Y	Y
Do not use database as well as Reliable Messaging	N	N	Y

Legend:

Y: The possibility of import can be validated.

N: The possibility of import cannot be validated.

(b) Validating the possibility of import

An example of validating the possibility of importing the specified repository by executing the cscrepcheck command is as follows. In this example, it is a prerequisite that the user ID and password of HCSC-Manager are defined in HCSC-Manager command definition file.

Example 1 of command execution

The possibility of importing the entire repository.zip is to be validated.
```
cscrepcheck -repfile D:\tmp\repository.zip
```
Example 2 of command execution

The possibility of importing repository.zip using component as a unit is to be validated.
```
cscrepcheck -repfile D:\tmp\repository.zip -compo
```
Example 3 of command execution

The possibility of importing service ID "1" in repository.zip is to be validated.
```
cscrepcheck -repfile D:\tmp\repository.zip -compo -name 1
```

(c) Result of validating the possibility of import

An example of validation result displayed by executing the cscrepcheck command is as follows:

When import is possible

Messages indicating start and end of validation are displayed and the command ends successfully.

KEOS52322-I cscrepcheck will now start.
Command Edit Time: YYYY/MM/DD hh:mm:ss.SSS
KEOS50237-I Verification of the repository to be imported will now be started.
KEOS50238-I Verification of the repository to be imported has ended successfully.
KEOS52323-I cscrepcheck ended normally.

When import is not possible

After a message indicating start of validation is displayed, all the HCSC components which cannot be imported and their causes are displayed and the message KEOS50239-E indicating an error in validation is output. After that, the command ends successfully.
```
KEOS52322-I cscrepcheck will now start.
Command Edit Time: YYYY/MM/DD hh:mm:ss.SSS
KEOS50237-I Verification of the repository to be imported will now be started.
...
<Display an error message for each HCSC component>
...
KEOS50239-E Verification of the repository to be imported has ended with errors.
KEOS52323-I cscrepcheck ended normally.
```
If any other error occurs, the command ends successfully without showing the error message KEOS50239-E as an output.

To Page Top

(2) Importing a repository using component as a unit (cscrepctl command)

An example of importing a repository with component as a unit by using the cscrepctl command is as follows. In this example, it is a prerequisite that the user ID and password of HCSC-Manager are defined in HCSC-Manager command definition file.

Example 1 of command execution

Only the HCSC component having service ID "1" from repository.zip is imported in the repository of the operating environment.
```
cscrepctl -import repository.zip -compo -name 1
```
Example 2 of command execution

If the -name option is not specified as shown below, all the HCSC components from repository.zip are imported in the repository of the operating environment.
```
cscrepctl -import repository.zip -compo
```
Example 3 of command execution

From among the HCSC components present in repository.zip, the HCSC components specified in HCSC component-specification file "hcsccomponent.txt"^# are imported in a batch in the repository of the operating environment.
```
cscrepctl -import repository.zip -compo -namelist hcsccomponent.txt
```

Note#: For HCSC component-specification file, see "6.5.5 HCSC component-specification file" in "Service Platform Reference Guide".

For the cscrepctl command, see "cscrepctl (Importing/Exporting)" in "Service Platform Reference Guide".

To Page Top