Completing the Installation

#### Search Results

Search

# Completing the Installation

This document covers the following topics:

- Registering a Daemon and Setting File Permissions

- Setting the Environment Variables with sagenv.new

- Setting up Entire System Server Components

## Registering a Daemon and Setting File Permissions

If you installed Entire System Server (NPR) on a Linux system and did not use sudo, the installer was not able to register daemons and set file permissions for the affected products. Perform these tasks now by executing the script afterInstallAsRoot.sh as the root user. You can find this script in the bin directory of your main installation directory. It contains actions for all installed Software AG products.

Important
If you did not use sudo during the installation, you must run the script afterInstallAsRoot.sh or some products might not work correctly.

If you do not want to register a daemon for Entire System Server (NPR) or set file permissions, proceed as follows:

- Remove the command to start the setup script in the afterInstallAsRoot.sh script before you execute it. The script to register the daemon is called install_daemon_npr. The script to set file permissions is called install_bin_npr. All these scripts are located in the <install-dir>/EntireSystemServer/INSTALL directory.

For the daemon, an uninstall script is available. Therefore, if you do not want to register the daemon, you can also proceed as follows:

- Install all daemons (either automatically with the installation when sudo is used, or manually by executing the afterInstallAsRoot.sh script when sudo is not used) and then uninstall the Entire System Server daemon using the uninstall_daemon_npr script in the <install-dir>/EntireSystemServer/INSTALL directory.

## Setting the Environment Variables with sagenv.new

Before you start your product, it is recommended that you run (source) the sagenv.new script in the <install-dir>/bin directory. This sets the environment variables needed to run your product and other products.

Important
The sagenv.new file is replaced with every new installation. If you have set up your own environment settings file (for example, with the name sagenv), replace only the modified product-specific part in your existing sagenv file.

Important
It is recommended that you start a new shell before switching to a different installation directory and running the sagenv.new script (for example, when switching from the directory for a test environment to the directory for a production environment).

## Setting up Entire System Server Components

Entire System Server on Linux is set up with the following steps

- Step 1: Customize EntireX Broker

- Step 2: Establish Environment Variables

- Step 3: Set Environment Variable ETB_TIMEOUT

- Step 4: Customize the NPR Server

- Step 5: Start Work with Entire System Server

### Step 1: Customize EntireX Broker

The following definitions must be included in the EntireX Broker attribute file:

    DEFAULTS=SERVICE
    TRANSLATION=SAGTCHA
    SERVER=<nodename>
    CLASS=NPR
    SERVICE=<npr_identifier>

where

<nodename> | is the identification of the node where the server is active.
<npr identifier> | is the identification of the service name provided for the NPR server.

Repeat these definitions for every NPR server specified in the npr.ini file. For instance, if an NPR server is available in the `HP001` node with the service name `nprdemo`, the following definitions must be created:

    DEFAULTS=SERVICE
    TRANSLATION=SAGTCHA
    SERVER=HP001
    CLASS=NPR
    SERVICE=nprdemo

For installing EntireX Broker, see the latest documentation.

### Step 2: Establish Environment Variables

Some environment variables are set by the `sagenv.new` (`nprenv`) script if it is invoked during session startup:

- `NPR_HOME` points to the Entire System Server directory;

- `EOR_WORK` points to the Entire Operations work directory. If this variable is already set, it will not be modified by this script.

- `PATH` is set to include ``NPR_HOME`/bin`:

      PATH=$PATH:$NPR_HOME/bin

### Step 3: Set Environment Variable ETB_TIMEOUT

To enable an Entire System Server (NPR) service to stop while the TCP/IP connection to the Broker is down, the environment variable `ETB_TIMEOUT` is automatically set to 60 seconds by `NPRETB` and `NPRMGR`.This avoids a hang of the broker stub during a disconnected TCP/IP connection, and allows the stopping of `npretb` in such a situation. Note that `ETB_TIMEOUT` remains unchanged if it was set before the execution of `npretb` resp. `nprmgr`.

### Step 4: Customize the NPR Server

The npr.ini file is used to define the behavior of the server processes. It is structured in one `[DEFAULTS]` section and one or more `[<npr identifier>]` sections.

You can define settings either in the `[DEFAULTS]` section or in an `[<npr identifier>]` section:

- Define Settings in a Section
- Settings in a [<npr identifier>] Section

#### Define Settings in a Section

The `[DEFAULTS]` section contains default values that apply to all servers. For a particular server such a default can be overwritten by providing an `[<npr identifier>]` section with an alternative setting.

#### Settings in a [<npr identifier>] Section

The [<npr identifier>] sections are optional, and can be created or modified later. They are used to define items specific to a certain server when these are different from default.

Any item defined in the [DEFAULTS] section can also be defined for each [<npr identifier>] section.

Any item defined in the [DEFAULTS] section can also be defined for each [<npr identifier>] section. If an item is not defined in this section, it is taken from the [DEFAULTS] section.

### Step 5: Start Work with Entire System Server

This section covers the following topics:

- Starting a Server
- Stopping a Server

You can omit this step, if Entire System Server is to be used in "local mode" by Entire Operations or Entire Output Management. In this case, no separate NPR server is necessary.

You can omit this step if the application using Entire System Server is running on the same machine as the NPR server. In this case, you must setup the application using Entire System Server (for example: Entire Operations) in a way that it will access the NPR server in the so called "local mode".

For details, see the System Administrator's Documentation of the application that uses Entire System Server.

The npretb module is the Operating System Server for Entire Operations. It can receive remote requests from clients using the EntireX Broker mechanism. The server executes the system functions by calling the adequate function in the dynamic library nprlib.sl. The characteristics of the client/server communication established through the EntireX Broker mechanism are as follows:

- Connection-less oriented mode;

- Broker class always equal to NPR; User identifier always equal to NPR_ETBS;

- Service name always equal to <npr identifier>;

- Default internal timeout value equal to 30 seconds;

- Default internal replica value equal to "YES". This characteristic relative to replica servers is not implemented in the current version.

The npr.ini file defines the attributes related to an NPR server.

#### Starting a Server

To start a server

1. Use the NPRMGR utility:

       $ nprmgr
       NPRMGR> start service <service name>

2. You can check that the server has been successfully initiated with the NPRMGR utility:

       $ nprmgr
       NPRMGR> display service <service name>

#### Stopping a Server

To stop a server

1. Use the NPRMGR utility in this way:

       $ nprmgr
       NPRMGR> stop service <service name>

   Note
   See the subsection The NPRMGR Utility for more information about these commands.

2. Invoke the `startnpr` script directly, followed by the service name:

       startnpr <service-name>

### On this page

- Registering a Daemon and Setting File Permissions
- Setting the Environment Variables with sagenv.new
- Setting up Entire System Server Components