Using the Admin Tool
This section covers the following topics:
Permissions
When you use the Admin Tool, you can perform only those actions that are allowed for the user whose alias and password you specified when you started the tool. Only a user with the role of administrator can perform certain commands (
chown, for example).Displaying Exceptions
The Admin Tool enables you to avoid viewing long stack traces when a command fails.
When a command fails, the Admin Tool prints the first line of the stack trace and the following message:
If you need more information, execute the
show exceptioncommand next to see the full stack trace.The
show exceptioncommand always displays the stack trace of the immediately preceding command.Identifying Registry Objects
The primary way to identify registry objects is by name. This extends to identifying
RegistryPackageobjects by the path from the registry root to theRegistryPackage. For example,/registry/userDatais the path to theuserDataRegistryPackage.Some matches for names support wildcards. Use a question mark (
?) to match a single character, and use an asterisk (*) to match zero or more characters.Some commands (for example,
cdandchown) support identifying objects by their Uniform Resource Name (URN), which must include a leadingurn:. For example,urn:uuid:2702f889-3ced-4d49-82d1-e4cd846cb9e4.The
chowncommand also supports using%numberto refer to aUserlisted by a previoususerscommand.For some commands, you can enter names that contain spaces by enclosing the entire name in double quotes or by preceding each space in the name by a backslash.
The Effect of Locale on Specifying Names
A
RegistryObject(or aRegistryPackage) may have multiple names, each of which is associated with a different locale.The paths and object names that you specify are evaluated with respect to the current locale only. When you attempt to select by name a registry object that has multiple names, the Registry attempts to match the name that you provide against only one alternative for the registry object's name (the choice whose locale most closely matches the current locale), not against all the multiple names for the registry object.
For example, suppose the current
RegistryPackagehas a member object that has two names, each associated with a different locale:redin theen(English) locale androugein thefr(French) locale. When the current locale isen, the commandls rougedoes not display that member object, but when the locale isfr(or one of its variants), then it does.Case Sensitivity
Command names and literal parameters that are recognized by the Admin Tool are not case sensitive. For example,
ls,Ls, andLSare equivalent.Options to which you provide the value are passed literally to the code that uses the option.