Skip to main content
Version: 1.12.6.x LTS

Server handling

The administrative command-line interface

The nevismeta command-line interface integrates the op and sudo command-line tools. It consists of several commands.

Instances
Instances can be managed by adding an instance name as parameter to the nevismeta command, for example:

# nevismeta instance1 start

If no instance is explicitly specified, the nevismeta command manages the default instance.

Setting up servers

The instance commands are used to install new server instances. There is a "default" instance for easy installation. Other or additional instances need to be configured by providing setup parameters.

  • nevismeta inst

    This command lists the names of all configured server instances.

  • nevismeta inst create <instancename>

    A new server instance is set up by entering the following command:

# nevismeta inst create default

The newly created instance will be deployed on port 8996.

Setup parameters may be provided on the command-line or by passing a setup property file:

# nevismeta inst create default /tmp/setup.properties
  • nevismeta inst remove <instancename>

    This command removes all files related to the specified instance.

  • nevismeta inst exists <instancename>

    This command is used by configuration scripts to query for already installed server instances.

  • nevismeta handover

    This command performs the following steps:

# nevismeta inst create default
# nevismeta default start

It offers a quick way of installing and starting a nevisMeta default installation.

Controlling the server

  • nevismeta start

    Before starting the nevisMeta server, the command nevismeta start checks whether the server is not already running. If the server is already running, the command only provides status information.

The startup procedure may look as follows:

nevismeta start
nevismeta [MESSAGE]: Starting nevismeta.
Starting standalone instance 'nevismeta' ..
--------------------------------------------------------------------------------
Status : UP
Instance : nevismeta
Process ID : 51788
Ownership : nvauser / nvbgroup
Filedescriptors : 1024
--------------------------------------------------------------------------------
  • nevismeta stop

    To shut down a running server, the command nevismeta stop terminates all running processes. The display may therefore look as follows:

nevismeta stop
nevismeta [MESSAGE]: Stopping nevismeta.
Stopping standalone instance 'nevismeta' ..
--------------------------------------------------------------------------------
Status : DOWN
Instance : nevismeta
Process ID : 0
Ownership : --- / ---
Network port(s) : ---
Filedescriptors : 1024
--------------------------------------------------------------------------------
  • nevismeta restart

    This command performs a nevismeta**stop followed by a nevismeta**start. It may be used as a convenient way to restart nevisMeta after applying configuration changes.

Retrieving status information

  • nevismeta status

    This command displays basic information on the server's current runtime state.

A server that is running displays the following output:

nevismeta status
--------------------------------------------------------------------------------
Status : UP
Instance : nevismeta
Process ID : 51788
Ownership : nvauser / nvbgroup
Network port(s) : iam.net:8996
Filedescriptors : 1024
--------------------------------------------------------------------------------

Configuration editing

The configuration files are located in the following directory:

/var/opt/nevismeta/<instancename>/conf/

To apply changes to the configuration, a restart of the nevisMeta server is required, see the chapter nevismeta restart.

  • nevismeta config

The command nevismeta config opens the main configuration file nevismeta.properties for editing in a console editor.

Parameter nameDefaultDescription
fileimportsize5242880Maximum size of importable files in bytes.For example, "5242880" means 5 MB.
maxCacheDuration600Maximum cache duration for REST interface responses in seconds.For example, "600" means 10 min.
module.oauthv2.import.regenerate.clientsecretfalseRegenerates client secrets when importing OAuthV2 client entities. {true | false}
expiredDataCleaningInterval3600Interval after which expired data will be cleaned, in seconds. For example, "3600" means 60 minutes or one hour.
  • nevismeta config login

    The command nevismeta config login opens the login configuration file nevismeta.properties for editing in a console editor.

The following aspects are configured here:

Parameter nameDescription
server.auth.ninja.truststoreSpecifies the truststore file to use for Ninja to parse the SecToken.
server.auth.ninja.user-getterDefines how Ninja gets the user ID from the SecToken.
server.auth.ninja.role-gettersDefines how Ninja gets user role from the SecToken.
server.auth.ninja.sec-role-mappingMaps SecToken roles to groups or to role principals.Syntax: group | role. Recommended setting: "group". See also chapter Configuration of the Web Application in the Ninja reference guide.
server.auth.ninja.log-debugEnables the debug mode for Ninja.

For more details, see chapter User ID and Roles in the Ninja reference guide.

  • nevismeta config vmargs

    The command nevismeta config vmargs opens the configuration file vmargs.conf for editing in a console editor.

The file specifies arguments to be passed to the JVM initialization:

  • JVM heap sizing and garbage collection tuning

  • JNDI customizations

  • JCE/JSSE provider and default certificate setup

  • JAAS add-on

  • nevismeta config env

    The command nevismeta config env opens the configuration file env.conf for editing in a console editor. Some plugged components may require additional environment information. This is configured by adding entries to the config file as follows:

VARIABLENAME=VALUE
export VARIABLENAME

The following aspects are configured here:

  • JDK/JRE to use (JAVA_HOME)

Package handling

As a rule, the delivered packages use unversioned links to the latest installed software version to reference required binaries without having to specify an exact version. The following command displays these links:

ls -l /opt/nevismeta

Use the nevismeta version command to display the installed version of nevisMeta.