Completing the Installation

This document covers the following topics:

Registering Daemons and Setting File Permissions
Setting the Environment Variables with sagenv.new
Setting Up Your Products Using the SYSPCI Utility
Invoking the SYSPCI Utility
Re-Linking a Natural Nucleus
Setting Up the Additional Natural Components
Setting Up Natural Security

Registering Daemons and Setting File Permissions

If you installed Natural on a UNIX system and did not use sudo, the installer was not able to register daemons and set file permissions for the affected products. Also the runpath directory /opt/softwareag/Natural/v<version>/lib may not have been created if the user that you are using to install does not have full read and write permissions to the runpath directory. Note that the runpath directory may have been created by a previous Natural installation. 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 daemons for Natural, set file permissions or create the runpath directory, proceed as follows:

Remove the commands to start the setup scripts in the afterInstallAsRoot.sh script before you execute it. The scripts to register daemons are called install_daemon_natbpsrv, install_daemon_natdvsrv and install_daemon_nwosrvd. The scripts to set file permissions are called install_bin_apx and install_bin_nwo. The script to set up the run path library is called install_lib_to_runpath. All these scripts are located in the <install-dir>/Natural/INSTALL directory.

For the daemons, uninstall scripts are available. Therefore, if you do not want to register the daemons, 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 Natural daemons using the uninstall_daemon_natbpsrv, uninstall_daemon_natdvsrv and uninstall_daemon_nwosrvd scripts in the <install-dir>/Natural/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 Software AG 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.

Running the sagenv.new script is also recommended before configuring the installed products with the SYSPCI utility.

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 Your Products Using the SYSPCI Utility

After you have installed your product, you need to set up a number of files, parameters and individual settings depending on your environment. These are described below. To set them up, you use the SYSPCI utility. For detailed information on this utility, see SYSPCI Utility - Product Configuration and Initialization in Natural's Tools and Utilities documentation.

The Natural Command Processor requires an NCP file.

Natural Security requires an Adabas FSEC system file.

Natural Security provides the function Logging of Maintenance Functions. If logging is activated, a Natural Security log file (NSL) is required in Adabas and needs to be set up with the SYSPCI utility. With this version, you can continue to use your existing Natural Security log file. If you want to set up a Natural Security log file, it is recommended that you do this before setting up an FSEC file for Natural Security. In this order, both files can be set up by starting the SYSPCI utility only once.

Natural Development Server requires an Adabas FDIC system file. After the installation of Natural Development Server, the FDIC parameter is not set automatically. If you start Natural without setting the FDIC parameter and then use the Natural editor, the Natural error NAT7399 will occur because the FDIC file is not available for locking.

If you want to use an FDIC file and you use Natural Security, configure the FDIC file first. When an FDIC file is configured, additional FDIC information will be written to the FSEC file when it is initialized. It is thus recommended that you set up the files for Natural Development Server and Natural Security in the following order:

FDIC
NSL
FSEC

The database IDs and file numbers of the new or existing files (FSEC, FDIC or NCP) that you specify using the SYSPCI utility are entered into the default parameter files for Natural Security (NSCPARM), Natural Development Server (NDVPARM) and Natural (NATPARM).

Note:
If Natural Security is already active and you use the SYSPCI utility to create a new FSEC file, database ID and file number are not entered into the current NSCPARM file.

The FSEC definition will also be written to the NDVPARM parameter file.

When you initialize (activate) Natural Security using the SYSPCI utility or when you start Natural Development Server, the default FNAT system file from the installation must be used (that is, <install-dir>/Natural/fnat). Otherwise, a subsequent update installation will not be possible.

Note:
If you want to use the same FDIC file in both Natural Development Server and Predict (which is not the recommended way), it is recommended that you install Natural Development Server without initializing an FDIC file. Then install Predict and do the initialization there. Afterwards, run the SYSPCI utility, process the Predict FDIC file and deactivate the Initialize product option. You can then also use the newly created FDIC file in Natural Development Server. When you set up a Predict FDIC file after setting up a Natural Development Server FDIC file, an inconsistency problem will occur because Predict always delivers the very latest FDIC file.

The required Adabas files can either be local or remote.

Remote Access
If the file is located in a remote database, Entire Net-Work must be active and the database must be accessible.

Note:
For Natural Security, see also Using Natural Security on Multiple Platforms in the Natural Security documentation.
Existing Local File
Before you start the SYSPCI utility, make sure that the Adabas database containing the required files is active. With this version, you can continue to use your existing files. No migration of data from the previous version to the current version is necessary.
New File
Before you start the SYSPCI utility, make sure that the Adabas database which will contain the required files is active. The SYSPCI utility will load and initialize these files. This should be also done if another file is required for your product.

Before you create new files with the SYSPCI utility, make sure that the ASSO and DATA sizes of your Adabas database are appropriate for these files. It is therefore recommended that you check the Adabas .fdu files in the <install-dir>/<product>/INSTALL/<product-code> directory for the used sizes. If required, change your database setup so that the files can be created.

For Natural Security, for example, the ASSO and DATA sizes are not appropriate if you are using the default database. The .fdu files for Natural Security can be found in the <install-dir>/Natural/INSTALL/nsc directory.

In addition, make sure that the Adabas nucleus parameters listed in the following table are set for the database you want to use at database startup. They are not appropriate if you are using the default nucleus parameters.

`LWP`	Must be at least 1,000,000.
`OPTIONS`	The option `TRUNCATION` must be set in the `OPTIONS` parameter.

Notes:

After Natural Security has been initialized (activated) with the SYSPCI utility, you need to use a Natural Security nucleus to start Natural. The Natural Security nucleus delivered with the Natural Security installation is called "natsec" and is located in the <install-dir>/Natural/bin directory. Start Natural Security with natsec parm=NSCPARM. Alternatively, you can back up the nucleus called "natural" and rename "natsec" to "natural".
When you have installed Natural Security, you need to start Natural Development Server with a Natural Security nucleus (for example, natdvsrv –s=natsec).

Invoking the SYSPCI Utility

In order to invoke the SYSPCI utility, you must first invoke Natural. You can then invoke the SYSPCI utility using the Direct Command window.

To invoke the SYSPCI utility

Enter the following command at the UNIX system prompt to invoke Natural:
```
natural
```
Select the Direct menu and press ENTER to invoke the Direct Command window.
Enter the following command in the Direct Command window:
```
SYSPCI
```
For more information, see SYSPCI Utility - Product Configuration and Initialization in Natural's Tools and Utilities documentation.

Re-Linking a Natural Nucleus

The Natural installation delivers two standard Natural nuclei in the <install-dir>/Natural/bin directory. One nucleus is linked with a classic Adabas control block (ACB), but without Natural Security. This nucleus is called "natural". The other nucleus is also linked with a classic Adabas control block (ACB) and with Natural Security. This nucleus is called "natsec".

If you want to link a modified Natural nucleus with the necessary drivers appropriate to your needs, you have to proceed as described below.

Note:
If Natural Security is installed and you link a modified Natural nucleus, the Natural Security interface is automatically linked. The name of the nucleus containing Natural Security is then "natural" (not "natsec").

To link a modified Natural nucleus

Set the environment variables for your Adabas (see also the information in the table below).
Run the natenv script in the <install-dir>/Natural/INSTALL directory to set the environment variables for Natural.

Run the makefile located in the <install-dir>/Natural/bin/build directory with the following command:

make natural {flags}

This make generates a program with the name natural which is placed in the current directory (<install-dir>/Natural/bin/build).

The following flags are available:

Flag	Description
`ada=yes`	Link with classic Adabas control block (ACB). When executing the makefile, the following environment variables must be set: `ADADIR`: Adabas base directory. `ADAVERS`: Adabas version.
`ada2=yes`	Link with extended Adabas control block (ACBX). When executing the makefile, the following environment variables must be set: `ADADIR`: Adabas base directory. `ADAVERS`: Adabas version. `ACLDIR`: Adabas client directory. `ACLVERS`: Adabas client version. The `ACL*` variables are also required during runtime.
`osx=yes`	Link with SQL interface (OSX). When executing the makefile, the SQL interface libraries must be accessible in the `<install-dir>`/Natural/bin/build directory. In addition, the following environment variables must be set: `OSXDIR`: OSX base directory. `OSXVERS`: OSX version.
`ascii=yes`	Link with former ASCII interface of Natural (instead of the new binary interface).
`sax2=yes`	Link with XML SAX parser. Required for the `PARSE XML` statement, for Tamino access, and for the application programming interface `USR6001N` (call external XSLT processor) in the library `SYSEXT`.
`xslt=yes`	Link with XSLT processor. Required for `USR6001N`.
`ins=yes`	Link with Tamino interface. The XML SAX parser is implicitely used. Therefore, do not specify `sax2=yes` in addition to `ins=yes`.
`apx=yes`	Link with ApplinX interface.
`shlib=yes`	Link Natural shared library (libnatural.so or libnatural.sl, depending on the UNIX platform). Required for the Natural Native Interface. Non-Natural applications can load this shared library dynamically and access Natural code through the exported interface functions. Do not use `apx=yes` in combination with `shlib=yes` because interactive I/O is suppressed for shared libraries.

Use the following command to copy the generated natural program from <install-dir>/Natural/bin/build to <install-dir>/Natural/bin:
```
make install
```
The original natural program in <install-dir>/Natural/bin is then renamed to natural.old.
If you have specified shlib=yes, use the following command to copy the generated libnatural.so or libnatural.sl program from <install-dir>/Natural/bin/build to <install-dir>/Natural/bin:
```
make install shlib=yes
```
The original libnatural.so or libnatural.sl program in <install-dir>/Natural/bin is then renamed to libnatural.so.old or libnatural.sl.old.

See the source of the makefile for more information.

Setting Up the Additional Natural Components

After Natural has been installed for the first time, additional configuration steps are required in the following cases:

Natural Development Server
If you have installed Natural Development Server (NDV), see the description of the appropriate NDV server in the Natural Single Point of Development (SPoD) documentation for further information. This documentation is available separately.

If you want to get information about the startup parameters for the Natural Development Server, enter the following command in the Natural/bin directory:
```
natdvsrv -help
```
The possible startup parameters are then shown with explanations.
Natural Web I/O Interface
If you have installed the Natural Web I/O Interface, see the Natural Web I/O Interface documentation for information on how to configure the server part (that is, the daemon), and how to install and configure the Natural Web I/O Interface client. If you want to use Natural for Ajax as the client, see the Natural for Ajax documentation. This documentation is available separately.
ApplinX Interface
If you have installed the ApplinX interface, see the ApplinX documentation for information on how to replace the Natural character-based user interface by the ApplinX GUI facilities. This documentation is available separately.

Setting Up Natural Security

The initial installation of Natural Security results in the creation of the following security profiles and relationships:

A library security profile with library ID SYSSEC. The library is people-protected (People-protected set to "Y" and Terminal-protected set to "N").
A user security profile with user ID "DBA", user type "ADMINISTRATOR", and password set to "DBA".
User "DBA" is linked to library SYSSEC (ordinary link, no special link).

If there is a previously installed version of Natural Security, these two security profiles will not be modified by a subsequent installation, nor will any objects or relationships already defined be affected.

If you have installed Natural Security for the very first time (that is, if the version you have installed is your first version of Natural Security on this FSEC system file), proceed as described in the Natural Security documentation under the heading First Steps After the Installation. Do this immediately after a successful installation of Natural Security.