IceGrid provides two administrative clients: a command-line tool and a graphical application.
On this page:
The icegridadmin utility is a command-line tool for administering an IceGrid domain. Deploying an application with this utility requires an XML file that defines the descriptors.
The IceGrid administration tool supports the following command-line options:
{zcode}
Usage: icegridadmin [options]
Options:
-h, --help Show this message.
-v, --version Display the Ice version.
-e COMMANDS Execute COMMANDS.
-d, --debug Print debug messages.
-s, --server Start icegridadmin as a server (to parse XML
files).
-u, --username Login with the given username.
-p, --password Login with the given password.
-S, --ssl Authenticate through SSL.
-r, --replica NAME Connect to the replica NAME.
{zcode} |
The -e option causes the tool to execute the given commands and then exit without entering an interactive mode. The -s option starts icegridadmin in a server mode that supports the IceGrid::FileParser interface; a proxy for the object is printed to standard output. If neither -e nor -s is specified, the tool enters an interactive mode in which you issue commands at a prompt.
To communicate with the IceGrid registry, icegridadmin establishes an administrative session. The tool uses SSL authentication if you specify the -S option or define its equivalent property IceGridAdmin.AuthenticateUsingSSL. Otherwise, icegridadmin uses password authentication and prompts you for the username and password if you do not specify them via command-line options or properties. If you want icegridadmin to establish its session using a Glacier2 router, define Ice.Default.Router appropriately. See IceGrid Administrative Client Properties for more information on the tool's configuration properties.
Once the session is successfully established, icegridadmin displays its command prompt. The help command displays the following usage information:
helpexit, quitCATEGORY helpCATEGORYCOMMAND helpCOMMAND. The tool's commands are organized by category. The supported command categories are shown below:
applicationnoderegistryserverserviceadapterobjectserver templateservice templateYou can obtain more information about each category using the help command:
{zcode}
>>> application help
{zcode} |
application add [-n | --no-patch] DESC [TARGET ... ] [NAME=VALUE ... ]DESC. If specified the optional targets are deployed. Variables are defined using the NAME=VALUE syntax. The application is automatically patched unless the -n or --no-patch option is used to disable it. application remove NAMENAME. application describe NAMENAME.application diff DESC [TARGET ...] [NAME=VALUE ...]DESC and the current deployment. Variables are defined using the NAME=VALUE syntax. application update DESC [TARGET ...] [NAME=VALUE ...]DESC. Variables are defined using the NAME=VALUE syntax. application patch [-f | --force] NAMENAME. If -f or --force is specified, IceGrid will first shut down any servers that depend on the data to be patched.application listnode listnode describe NAMENAME.node ping NAMENAME.node load NAMENAME.node processors [NAME]NAME. If NAME is omitted, print the number of processor sockets for each node. (The IceGrid.Node.ProcessorSocketCount property allows you to explicitly set this value for systems where the number of sockets cannot be obtained programatically.) node show [OPTIONS] NAME [stderr | stdout]-f, --follow-t, --tail NN lines of text. -h, --head NN lines of textnode shutdown NAMENAME.
registry listregistry describe NAMENAME.registry ping NAMENAME.registry show [OPTIONS] NAME [stderr | stdout]-f, --follow-t, --tail NN lines of text.-h, --head NN lines of text.registry shutdown NAMENAME.
server listserver remove IDID.server describe IDID.server properties IDID.server property ID NAMENAME of server ID.server state IDID.server pid IDID.server start IDID.server stop IDID.server patch IDID.server signal ID SIGNALSIGNAL (such as SIGTERM or 15) to server ID.server stdout ID MESSAGEMESSAGE on server ID's standard output.server stderr ID MESSAGEMESSAGE on server ID's standard error.server show [OPTIONS] ID [stderr | stdout | LOGFILE]LOGFILE. The supported options are shown below:
-f, --follow-t, --tail NN lines of text.-h, --head NN lines of text.server enable IDID.server disable IDID (a disabled server can't be started on demand or administratively).
service start ID NAMENAME in IceBox server ID.service stop ID NAMENAME in IceBox server ID.service describe ID NAMENAME in IceBox server ID.service properties ID NAMENAME from IceBox server ID.service property ID NAME PROPERTYPROPERTY of service NAME from IceBox server ID.service list IDID.
adapter listadapter endpoints IDID.adapter remove IDID.
The object command operates on well-known objects.
object add PROXY [TYPE]object remove IDENTITYobject find TYPETYPE.object describe EXPREXPR. A trailing wildcard is supported in EXPR, for example "object describe Ice*".object list EXPREXPR. A trailing wildcard is supported in EXPR, for example "object list Ice*".
server template instantiate APPLICATION NODE TEMPLATE [NAME=VALUE ...]NAME=VALUE syntax.server template describe APPLICATION TEMPLATETEMPLATE from the given application.
service template describe APPLICATION TEMPLATETEMPLATE from the given application.
icegridadmin requires that the locator proxy be defined in the configuration property Ice.Default.Locator. If a configuration file already exists that defines this property, you can start icegridadmin using the configuration file as shown below:
{zcode}
$ icegridadmin --Ice.Config=<file>
{zcode} |
Otherwise, you can define the property on the command line:
{zcode}
$ icegridadmin --Ice.Default.Locator=<proxy>
{zcode} |
Refer to the discussion of our ripper client for more information on configuring the Ice.Default.Locator property for an IceGrid client.
The graphical administration tool, IceGrid Admin, allows you to perform anything that you can do from the command line via a GUI. Please refer to the instructions included with your Ice distribution for details on how to start the administration tool.