Modifying Groups in Bulk

Modifying Groups Using an XML File

An XML file is created exclusively for modifying multiple groups. The main purpose of modifying the groups is to associate and disassociate elements available in a group. In order to associate the elements in the Group, entries in this file should be of the following format:

<?xml version="1.0" encoding="UTF-8"?>

</Element>

</Group>

Note that the elements should be specified in the format: <Component Type>:<component name>:<Port>

For instance:

<?xml version="1.0" encoding="UTF-8"?>

<associateelements>2x client gateway:client4:80,2x client gateway:client5:80</associateelements>

<groupname>Group1</groupname>

</Element>

</Group>

If you wish to disassociate the elements in the Group, entries in this file should be of the following format:

<?xml version="1.0" encoding="UTF-8"?>

</Element>

</Group>

Note that the elements should be specified in the format:<Component Type>:<component name>:<Port>

For instance:

<?xml version="1.0" encoding="UTF-8"?>

<disassociateelements>2x client gateway:client3:80,2x Publishing Agent:agent1:20002</disassociateelements>

<groupname>group2</groupname>

</Element>

</Group>

Note that the XML tags are the same as the input parameters of the ‘ModifyGroup’ command supported by eG CLI (see Modifying a Group)

Once the XML file is created on the orchestrator’s host, invoke the following command from the orchestrator to update the eG manager with all the modifications contained in the XML file:

egcli modifyGroup -managerid <ManagerID> -file <Fullpath_to_the_XML_file>

For example:

egcli modifyGroup -managerid mgr153 -file E:\bulkmodifygroup.xml

Note:

Each modification should be included within the main <Group></Group> block only.
A single XML file should not contain more than one <Group></Group> block.
An XML file that is created for modifying group details should not include sections pertaining to any other operation.
A single XML file can be used for modifying the details of groups of different types.

Modifying Groups Using a CSV File

As already mentioned, an exclusive CSV file will have to be created to handle bulk modifications to group details.

In order to associate the elements in the Group, entries in this file should be of the following format:

Element,action

Group,modify

groupname,associateelements

groupname,“<comma-separated list of elements>”

Note that the elements should be specified in the format:<Component Type>:<component name>:<Port>

For instance:

Element,action

Group,modify

groupname,associateelements

group1,"2x client gateway:client1:80,2x client gateway:client2:80"

group2,2x Publishing Agent:agent1:20002

group3,"Microsoft Windows:wincli1,Microsoft Windows:wincli2"

If you wish to disassociate the elements in the Group, entries in this file should be of the following format:

Element,action

Group,modify

groupname,disassociateelements

groupname,“<comma-separated list of elements>”

Note that the elements should be specified in the format:<Component Type>:<component name>:<Port>

For instance:

Element,action

Group,modify

groupname,disassociateelements

group1,"2x client gateway:client1:80,2x client gateway:client2:80"

group2,2x Publishing Agent:agent1:20002

group3,"Microsoft Windows:wincli1,Microsoft Windows:wincli2"

Once the CSV file is created on the orchestrator’s host, invoke the following command from the orchestrator to update the eG manager with all the modifications contained in the CSV file:

egcli modifyGroup -managerid <ManagerID> -file <Fullpath_to_the_CSV_file>

For example:

egcli modifyGroup -managerid mgr153 -file E:\bulkgroupmodify.csv