The command line tool "inoadmin" offers functionality for performing low-level administrative operations on the CentraSite Registry Repository. The functionality provided by inoadmin includes:
Starting and stopping the CentraSite Registry Repository.
Maintaining the internal database that houses the CentraSite Registry Repository.
Configuring port numbers used by the CentraSite Registry Repository.
Configuring Secure Communication between the CentraSite Registry Repository and the CentraSite Application Server Tier.
The practical use of the tool is described in the scenarios documented in the preceding sections.
The tool is located in the directory <CentraSiteInstallDir>\bin. If you call inoadmin without parameters, you receive a summary of the command syntax and the available functions.
You can use environment variables to configure the inoadmin behavior:
| Environment variable | Purpose |
|---|---|
| INOADMIN_OUTPUT_TXT |
Determines whether the inoadmin output is displayed as an XML document or as a formatted table. If the value is null (i.e. if the value is not defined), the inoadmin output is displayed as an XML document. If any non-null value is specified, a formatted table is displayed. |
| INOADMIN_NO_MESSAGE_OUTPUT |
Determines whether progress status messages are output while inoadmin calls are running. If this variable is null (i.e. if the value is not defined), all progress status messages are output. If any other value is set for this variable, the progress status messages are suppressed and only the result is displayed. |
| INOADMIN_RUN_AS_JOB |
Creates a job log that contains status information generated while inoadmin is running. |
If you use inoadmin within a command script, you can use the return status to verify the successful completion of the command. A zero return status means that the command executed successfully, whereas a non-zero return status means that the command did not execute successfully.
webMethods Command Central is a tool that release managers, infrastructure engineers, system administrators and operators can use to perform administrative tasks from a single location. Command Central can assist with the following configuration, management and monitoring tasks:
Infrastructure engineers can see at a glance which products and fixes are installed where, and can easily compare installations to find discrepancies.
System administrators can configure environments using a single web UI, command-line tool or API, so maintenance can be performed with a minimum of effort and risk.
Release managers can prepare and deploy changes to multiple servers using command-line scripting for simpler, safer lifecycle management.
Operators can monitor server status and health, as well as start and stop servers from a single location. They can also configure alerts to be sent to them in case of unplanned outages
For more information, see the Command Central documentation.
The following table describes the return codes you might encounter when using the command line tool "inoadmin".
| Return Code | Description |
|---|---|
| 0 | Execution of the command was successful. |
| 1 | A required parameter was not specified. |
| 2 | The command includes an invalid parameter. |
| 3 | The command includes an invalid number of parameters. |
| 4 | The output that a command returned does not match the expected values specified with the version option.
|
| 5 | The server was not registered. |
| 6 | The server already exists. |
| 7 | The state of the server is active. |
| 8 | The state of the server is inactive. |
| 9 | The server startup failed. |
| 10 | The specified file cannot be located. Make sure you have entered the correct path and file name. |
| 11 | A parameter specified an invalid name. |
| 12 | A parameter specified an invalid value. |
| 13 | An error occurred during command execution. |
| 14 | Access to the operating system file is denied. |
| 15 | The backup deletion failed. |
| 16 | The specified service cannot be found. |
| 17 | First time startup of the service failed. |
| 18 | First time startup of the service failed. |
| 19 | The directory name is not valid. |
| 20 | Indicates that the dbspace name is invalid. |
| 21 | An autorepair is pending. |
| 22 | An operating system file is locked by the server. |
| 23 | No space left on the database. |
| 24 | There is not enough memory to run the script. |
| 25 | The function called is not implemented. |
