6.5.5 HCSC component-specification file

(1) Format

[change-type.]{service-ID|reception-ID}
 ... 
[change-type.]{service-ID|reception-ID}

To Page Top

(2) Function

Specifies the add, change, and delete operations of HCSC components in a text file format. To specify multiple HCSC components, specify one component on each line. By specifying the created HCSC component-specification file in a command, you can process multiple HCSC components in a batch.

You can enter the HCSC component-specification file in a text file format as well, but with the following commands you can also output to a file and create the information for HCSC components:

• The -listfile option of the cscrepdiff command (outputs the differences in HCSC components)

• The -listfile option of the cscrepls command (outputs the list of HCSC components)

To Page Top

(3) File storage location

You can store the HCSC component-specification file at any location and assign any name to the file.

To Page Top

(4) Specifiable parameters

[change-type.]{service-ID|reception-ID}

Specifies the service ID or reception ID for the HCSC component to be added, changed, or deleted.

Specify one of the following as the change type of HCSC components:

• add

  Adds the specified HCSC component to the processing target.

• change

  Re-deploys the HCSC component when there is a change in the deployed HCSC component.

• delete

  Deletes the deployed HCSC component from the processing target.

• No specification

  The specified HCSC components are subject to processing by all the commands irrespective of the deployment status.

The following table lists the combination of commands for which you can specify the HCSC component-specification file in the -namelist option, and the specifiable change types:

Command name	Change type
	add	change	delete	No specification
csccompostart	Y	Y	N	Y
csccompostop	N	Y	Y	Y
csccompodeploy	Y	Y	N	Y
csccompoundeploy	N	Y	Y	Y
cscrepctl -import -compo	Y	Y	N	Y
cscrepctl -delete	N	N	Y	Y

To Page Top

(5) Example of coding

The following is an example of coding of the HCSC component-specification file:

#[BusinessProcess]
change.BP2
delete.BP3
add.BP4
 
#[ServiceAdapter]
change.adp2
delete.adp3
add.adp4
 
#[UserDefinedReception]
change.rcp2
delete.rcp3
add.rcp4

To Page Top

(6) Usage

Specify the created HCSC component-specification file in the argument of the -namelist option of the following commands. For details on how to execute the commands, see the description for each command in 5. Commands (Operating and Execution Environments).

• csccompostart command

• csccompostop command

• csccompodeploy command

• csccompoundeploy command

• cscrepctl -import -compo command

• cscrepctl -delete command

To Page Top

(7) Notes

• If you specify multiple HCSC components, the order of executing the HCSC components differs depending on the commands. For details on the execution order, see the description for each command.

• If the service ID or reception ID is repeated, an error occurs even if the change types are different.

• The HCSC components that are not subject to processing are skipped in the cases such as when the HCSC components you want to deploy are already deployed.

• A line beginning with a hash mark (#) is a comment.

• The one-byte spaces at the beginning and at the end of each line are trimmed.

• A blank line is skipped and is not referenced.

To Page Top