Completing the Installation

This document covers the following topics:

Windows User Group

The Natural installation creates a local Windows user group with the name "SAG Natural Users". The user "EVERYONE" is assigned to this user group by default.

When the Windows user group "SAG Natural Users" is created, you have to reboot your machine when the installation finishes. When this user group has already been created (due to a previous installation), this reboot is not required.

The user group "SAG Natural Users" receives full write permissions for all installed objects. Due to the user "EVERYONE", all users have write permissions for all installed objects. You can limit these permissions by removing the user "EVERYONE" from the user group "SAG Natural Users", and then manually adding all required users to this group. To do so, go to Control Panel > System and Security > Administrative Tools > Computer Management; in the resulting window, select Local Users and Groups.

Entries in the Start Menu

Depending on your selection in the product selection tree, some or all of the following entries have been created in the Windows Start menu:

where n.n stands for the current version number. The Start menu group name (by default, this is "Software AG") can be changed during the installation.

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.

The database IDs and file numbers of the new or existing files (FSEC or NCP) that you specify using the SYSPCI utility are entered into the default parameter files for Natural Security (NSCPARM) 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 NATPARM and NSCPARM files.

When you initialize (activate) Natural Security using the SYSPCI utility, 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.

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.

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 command line.

Start of instruction setTo invoke the SYSPCI utility

  1. From the Windows Start menu, choose All Programs > Software AG > Tools > Natural n.n to invoke Natural.

  2. From the View menu, choose Command Line to switch on the display of the command line.

  3. Enter the following command in the command line:

    SYSPCI

    For more information, see SYSPCI Utility - Product Configuration and Initialization in Natural's Tools and Utilities documentation.

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.

  • SPoD-Specific Features
    If have installed the development environment and you want to use plug-ins which make up the Natural development client for SPoD, see the descriptions of the appropriate SPoD-specific features in the Natural Single Point of Development documentation for further information. This documentation is available separately.

  • Entire Systems Management
    Entire Systems Management requires additional software on the server. If you have installed the Entire Systems Management clients, you have to initialize the clients before you can use them. To do so, choose All Programs > Software AG > Administration > ESM Configuration for Natural n.n from the Windows Start menu. In the resulting dialog box, you can select whether to initialize or remove a client. Only initialized clients will be shown in the Entire Systems Management application window. See the following documentation sets for further information - these documentation sets are available separately:

    • Mainframe Navigation documentation

    • Output Management GUI Client documentation

    • Entire Operations GUI Client documentation

  • 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 service), 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.

Setting Up Natural Security

If you have installed the Natural Security runtime version, no further steps are required.

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 the full version of 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.