|
|
|
|
Updates a container.
container.update <"serviceName=<regexp>" | "serialNumber=<value>">
[, "newServiceName=<value>"]
[, "serviceType=<device|test>"]
[, "memberListMethod=<auto|manual>"]
[, "memberList=[+,]<regexp_1,regexp_2,...>"]
[, "memberlistAppend=<true | false>"]
[, "ruleDeviceName=<value>"]
[, "ruleDeviceType=<value>"]
[, "ruleDeviceModel=<value>"]
[, "ruleDeviceVendor=<value>"]
[, "ruleDeviceTag1=<value>"]
[, "ruleDeviceTag2=<value>"]
[, "ruleDeviceTag3=<value>"]
[, "ruleDeviceTag4=<value>"]
[, "ruleDeviceTag5=<value>"]
[, "testListMethod=<auto|manual>"]
[, "testName=<regexp_1,regexp_2,...>"]
[, "testType=<type_subtype_pair_1,type_subtype_pair_2,...>"]
[, "severityMethod=<auto|manual>"]
[, "ratioN=<value>"]
[, "memberSeverityN=<ok|unknown|warning|critical>"]
[, "serviceSeverityN=<ok|unknown|warning|critical>"]
[, "parentNames=none|<value1,value2,...>"]
[, "actionName=none|<value>"]
[, "comment=<value>"]
[, "displayComment=<true|false>"]
[, "departmentName=<value>"]
In the above parameters:
serviceType is a required parameter when you use the memberList parameter.
memberListMethod is a required parameter when you use the serviceType=device parameter.
You can use the newServiceName parameter to rename an existing service container. Container names must be unique within the end user department or admin-group, and cannot be case sensitive.
Depending on the value of the serviceType, memberListMethod, and testListMethod parameters, different membership_parameters are available, same as the container.create command.
The default value of memberListAppend is true to prevent accidental deletion of members from a container. If this value is set to false, all previous members of the container will be removed and only the specified members in this command will be part of the container.
If you are changing a device container to a test container (serviceType=test) and there are nested containers below it, move those containers to the immediate parent of the container you are modifying.
Example:
DC1
+-DC2
+-DC3
+-TC1
container.update "serviceName=DC3", "newServiceName=TC2", "serviceType=test"
This results in a new hierarchy:
DC1
+-DC2
+-TC1
+-TC2
Example of adding a new member to an existing container:
container.update "serviceName=All Devices", "serviceType=device", "memberListMethod=manual", "memberList=#All RTT Tests"
Example of adding a JDBC test to a container:
telnet localhost 7661
login <user> <pass>
container.update "serviceName=JMX Stats","servicetype=test","memberlistmethod=manual","testlistmethod=manual","testName=JDBC Pool (path=/server, name=jdbc/DataSource) Active
Connections","memberlist=host.FQDN","memberlistappend=true"