Once your database has been properly configured and your config profile is set to use that database, you are ready to start your server using the omero admin start command:
$ bin/omero admin start
This command performs the following operations in order:
Most configuration files under etc/grid are generated using the templates under etc/grid/templates and the server configuration stored in etc/grid/config.xml. The rewriting step updates the JVM memory settings (see Memory configuration) and the server ports (see Ports) based on the server configuration.
Display the help for this subcommand.
This option is particularly useful for debugging and maintenance and allows for starting the server up in the foreground, that is without creating a daemon on UNIX-like systems or service on Windows. During the lifetime of the server, the prompt from which it was launched will be blocked.
This option forces the server configuration files under etc/grid to be rewritten before the status of the server is checked.
To stop a running server, you can invoke the omero admin stop subcommand:
$ bin/omero admin stop
This command does the following operations in order:
Display the help for this subcommand.
This option forces the configuration files to be rewritten before the server status is checked.
To stop and start the server in a single command, you can use the omero admin restart command:
$ bin/omero admin restart
The restart subcommand supports the same options as omero admin start.
To debug a server or inspect the configuration, you can use the omero admin diagnostics command:
$ bin/omero admin diagnostics
The output of this command will report information about: