Adding a child group:
tacmd addgroupmember
{-g|--group} GROUPNAME
{-m|--member} MEMBERNAME
{-t|--groupType} DEPLOY|BUNDLE|SITUATION|COLLECTION
Adding a bundle group member:
tacmd addgroupmember
{-g|--group} GROUPNAME
{-m|--member} MEMBERNAME
{-t|--groupType} BUNDLE
{-y|--productType} PRODUCT_TYPE
[-i|--platform PLATFORM]
[-v|--version VERSION]
[-p|--property|--properties PROPERTY...]
Adding a deploy group member:
tacmd addgroupmember
{-g|--group} GROUPNAME
{-m|--member} MEMBERNAME
{-t|--groupType} DEPLOY
[-p|--property|--properties PROPERTY...]
Adding a situation or collection group member:
tacmd addgroupmember
{-g|--group} GROUPNAME
{-m|--member} MEMBERNAME
{-t|--groupType} SITUATION|COLLECTION
Adding multiple members by using member file:
tacmd addgroupmember
{-g|--group} GROUPNAME
{-x|--file} FILE
where:
- -g|--group
- Specifies the name of the group that the new group member is
added to.
- -m|--member
- Specifies the name of the group member.
- -t|--groupType
- Specifies the group type name. Acceptable type names are DEPLOY,
BUNDLE, SITUATION, or COLLECTION. When adding a child group with -t
COLLECTION, the collection setting member is distributed and started
on the target system
- -p|--property|--properties
- Specifies one or more name=value pairs
that identify the configuration properties to be persisted for the
group member. See Configuration options and properties for information on these properties.
- -y|--productType
- Specifies the product type code. The product value corresponds
to the value that is displayed in the Product Code field as a result
of running the viewDepot or listBundles command.
- -i|--platform
- Specifies the platform code of the product. The platform value
corresponds to the value that is displayed in the Host Type field
as a result of running the viewDepot or listBundles command.
- -v|--version
- Specifies the version number of the deployment bundle being
added as a bundle group member.
- -x|--file
- Specifies the file containing one or more group members to add.
This example adds the deploy member w099o002.tivlab.raleigh.ibm.com
to the group NewWindowsDeployGroup:
tacmd addGroupMember -g NewWindowsDeployGroup -t DEPLOY
-m w099o002.tivlab.raleigh.ibm.com -p KDYRXA.installDir=c:\\IBM\\ITM KDYRXA.RXAusername=Administrator
KDYRXA.RXApassword=****
Note:
To add a member to a group, you need to create
a group first. In the example above, create a deployment group NewWindowsDeployGroup
by using the createGroup command, and then execute
the addGroupMember command.
This example adds the situation group member NT_Disk_Space_Low
to the group NEW_NT_SITUATION_GROUP:
tacmd addgroupmember -g NEW_NT_SITUATION_GROUP -m NT_Disk_Space_Low
-t SITUATION
Note:
To add a member to a group, you need to create
a group first. In the example above, create a situation group NEW_NT_SITUATION_GROUP
by using the createGroup command, and then execute
the addGroupMember command.
This example adds the bundle member specified in the first column
of the CSV file to the bundle group NewBundleGroup:
tacmd addGroupMember -g NewBundleGroup -x c:\bulk_bundle_list.csv
The CSV file's format includes the following variables: member,type,cmdLine_options,properties
In the example above, the bulk_bundle_list.csv CSV file
contents are in the following format:
| unixBundle |
BUNDLE |
-y UX |
KDYRXA.RXA
protocol=
ssh
KDYRXA.
RXAport=22 |
| db2Bundle |
BUNDLE |
-y UD |
-v 062000000 |
f50pa2d.tivlab.
raleigh.ibm.com |
BUNDLE |
-y UD |
INSTANCE=db2inst1 |
amssol19.tivlab.
raleigh.ibm.com |
BUNDLE |
-y UM |
UA.CONFIG=
'file.mdl' |