Skip to main content
Version: 1.5.x.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, e.g.,:

# 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.
adnglassfish [MESSAGE]: nevismeta>> Starting server 'java'...
Waiting for nevismeta to start .........................
Successfully started the domain : nevismeta
domain  Location: /var/opt/adnglassfish/nevismeta/nevismeta
Log File: /var/opt/adnglassfish/nevismeta/nevismeta/logs/server.log
Admin Port: 8993
Command start-domain executed successfully.
--------------------------------------------------------------------------------
Status          : UP
Component       : adnglassfish/ 3.1.2.8
Instance        : nevismeta
Process         : java
Ownership       : nvbuser / nvbgroup
Network port(s) : https://host:8996
Filedescriptors : 4096
Process ID      : 23086
JRE/JDK         : /opt/adnjdk17
Logfile(s)      : /var/opt/adnglassfish/nevismeta/nevismeta/logs/server.log
--------------------------------------------------------------------------------

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.
Waiting for the domain to stop ..
Command stop-domain executed successfully.
--------------------------------------------------------------------------------
Status          : DOWN
Component       : adnglassfish/ 3.1.2.8
Instance        : nevismeta
Process         : java
Ownership       : nvbuser / nvbgroup
Network port(s) : https://host:8996
Filedescriptors : 4096
JRE/JDK         : /opt/adnjdk17
Logfile(s)      : /var/opt/adnglassfish/nevismeta/nevismeta/logs/server.log
--------------------------------------------------------------------------------

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
Component : nevismeta/ 1.0.4.0
Instance : nevismeta
Process : java
Ownership : nvbuser / nvbgroup
Network port(s) : https://host:8996/nevismeta
Filedescriptors : 1024
Process ID : 23086
JRE/JDK : /opt/adnjdk17
Logfile(s) : /var/opt/adnglassfish/nevismeta/nevismeta/logs/server.log
/var/opt/adnglassfish/nevismeta/nevismeta/logs/nevismeta.log
--------------------------------------------------------------------------------

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 nameDescription
fileimportsize, Default: 5242880Maximum size of importable files in bytes. For example, "5242880" means 5 MB.
maxCacheDuration, Default: 600Maximum cache duration for REST interface responses in seconds. For example, "600" means 10 min.
module.oauthv2.import.regenerate.clientsecret, Default: falseRegenerates client secrets when importing OAuthV2 client entities. `{true
expiredDataCleaningInterval, Default: 3600Interval 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 login.conf for editing in a console editor.

The following aspects are configured here:

  • JAAS module and its configuration parameters (see the Reference Guide Ninja, chapter "Ninja LoginModule for GlassFish")

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.