Free 30 Day Trial
Find the root-cause of your cloud, hybrid-cloud
or on-prem performance issues
|
||
|
Unmanaging Components Using an XML File
Entries of the following format should be included in the XML file that is created exclusively for unmanaging multiple components of different types from the eG Enterprise system:
<?xml version="1.0" encoding="UTF-8"?>
<Component action="unmanage">
<Agent>
<Component1 to be unmanaged>
</Agent>
<Agent>
<Component2 to be unmanaged>
</Agent>
.
.
.
.
</Component>
For example:
<?xml version="1.0" encoding="UTF-8"?>
<Component action="unmanage">
<Agent>
<componenttype>Generic</componenttype>
<componentname>gen1</componentname>
</Agent>
<Agent>
<componenttype>AGate</componenttype>
<componentname>agte10</componentname>
<port>3900</port>
</Agent>
<Agent>
<componenttype>Oracle Database</componenttype>
<componentname>ora8</componentname>
<port>1521</port>
<sid>egora</sid>
</Agent>
</Component>
Note that the XML tags are the same as the input parameters of the ‘UnmanageComponent’ command supported by eG CLI (see Unmanaging Components).
Note:
If an Oracle database server with multiple SIDs is be unmanaged, then do not provide a comma-separated list of SIDs within your <sid></sid> tag; instead, make sure that your XML file includes a separate <Agent></Agent> block for each SID to be unmanaged.
Note:
Once the XML file is ready, execute the following command to extract the component information from the file, connect to the required eG manager, and unmanage the specified components:
eGCLI UnmanageComponent -managerID <ManagerID> -file <Full_path_to_the_XML_file>
For example:
eGCLI UnmanageComponent -managerID mgr153 -file c:\unmancomp.xml
Unmanaging Components Using a CSV File
The components to be unmanaged should be included in a CSV file that is created exclusively for this purpose.
Such a CSV file should contain entries of the following format:
Element,action
Component,unmanage
componenttype,componentname,port,sid
<Component1 to be unmanaged>
<Component2 to be unmanaged>
.
.
.
For example:
Element,action
Component,unmanage
componenttype,componentname,port,sid
Generic,gen1,,
AGate,agte10,3900,
Oracle Database,ora55,1521,multi
Note:
Components included in a zone, segment, or service cannot be unmanaged.
Note:
Once the CSV file is ready, execute the following command to extract the component information from the file, connect to the required eG manager, and unmanage the specified components:
eGCLI UnmanageComponent -managerID <ManagerID> -file <Full_path_to_the_CSV_file>
For example:
eGCLI UnmanageComponent -managerID mgr153 -file c:\unmancomp.csv