Installing Natural

You can install Natural in one of the following two ways:

  1. Using the GUI to Install Natural for an easy user-based installation.

  2. Via a command line interface that is available for automated installation. It is described in Using Software Distribution Tools to Install Natural.

Using the GUI to Install Natural

This installation documentation provides just a brief description on how to install Natural directly on the target machine using the Software AG Installer GUI. For detailed information on the Software AG Installer, see Using the Software AG Installer.

Important:
Make sure all ports you specify on panels or in response to prompts are not already being used by other products on your machine. The installer cannot detect whether ports are in use when products are shut down, and the shutting down of products is a requirement for running the installer. For a list of default ports used by Software AG products, see "List of Used TCP/IP Ports" in Empower (go to Products > Download Components > TCP/IP Ports).

Start of instruction setTo install Natural

Software AG provides one or more license files for Natural; the installer requires them during a first-time installation. Copy the license files to the machine on which you want to install Natural. You can copy the license files to any temporary location. The installer will ask for the location of your license files and will then copy them to the common/conf directory of your installation directory.

  1. Start the Software AG Installer GUI as described in Using the Software AG Installer.

  2. When the first page of the Software AG Installer GUI (the so-called Welcome panel) is shown, choose the Next button repeatedly (and specify all required information on the shown panels as described in Using the Software AG Installer) until the panel containing the product selection tree appears. This tree lists the products you have licensed and which can be installed on the operating system of the machine on which you are installing.

  3. To install Natural with all of its product components, expand the Natural Products node and select Natural.

    Or:
    Expand Natural Products > Natural and select the product components that you want to install.

    Product selection tree

    Note:
    Products or product versions which are already installed in the selected installation directory are shown as disabled.

    The following product components are available:

    • Base Environment
      Installs the local development environment for Natural.

    • Runtime Environment
      You will be prompted to provide the license file later during the installation (first-time installation only).

      Note:
      Runtime Environment or Development Environment must be selected.

    • Development Environment
      You will be prompted to provide the license file later during the installation (first-time installation only).

      Note:
      Runtime Environment or Development Environment must be selected.

    • Development Server
      Installs Natural Development Server (NDV) which enables remote development using Natural Single Point of Development (SPoD). This component requires an additional license file. You will be prompted to provide the license file later during the installation (first-time installation only).

    • ApplinX Interface
      Installs the Natural runtime environment for ApplinX. ApplinX enables you to modernize your Natural applications so that they run in a browser. To set the s-bit for the ApplinX executables, sudoers privileges are required.

    • Web I/O Interface
      Installs the server part of the Natural Web I/O Interface. This enables you to use a browser as the I/O device for Natural applications. To set the s-bit for the Natural Web I/O Interface executables, sudoers privileges are required.

  4. If you want to install Natural Security, select Natural Products > Natural Security 9.1 SPn in the product selection tree. Natural Security can only be installed together with Natural (either with the development environment or the runtime environment) or after the Natural installation is complete.

    Note:
    If user authentication via an LDAP server is to be used, it is required that the SSX security libraries (Infrastructure > Libraries > Security Libraries) are installed as part of the Natural Security installation procedure. By default, if you select Natural Security in the installation tree, the SSX security libraries are automatically selected also. Refer to Authentication Options in the section Administrator Services of the Natural Security documentation for further details.

  5. Choose the Next button.

  6. Read the license agreement, select the check box to agree to the terms of the license agreement, and choose the Next button.

  7. Specify whether to use sudo or not.

    You must either have the installer execute the <install-dir>/bin/afterInstallAsRoot.sh script, or you must run the script manually after installation as explained later in Registering Daemons and Setting File Permissions. If you want to have the installer to execute the script, the user under which you are running the installer must be in the sudoers configuration.

    For security reasons, the installer does not store the sudo password in installation scripts. If you are creating or installing from an installation script, therefore, the option to use sudo is not available. You must execute the afterInstallAsRoot.sh script manually after the installation.

    Sudo

  8. Choose the Next button.

  9. First-time installation only.

    Enter the full path to the Natural license file (or use the Browse button to select it from a dialog box).

    Natural license file

    It is only possible to reuse or copy configuration data from a Natural installation which has been installed with the Software AG Installer.

    Create default configuration data

    Default. All required configuration files are created. These files contain default values.

    Reuse configuration data from the current installation directory

    This option is helpful, if you want to reuse the configuration files from a previous uninstallation in the same directory.

    Copy configuration data from another installation directory

    This option is helpful if you have side-by-side installations. In this case, you can copy the configuration files from an existing Natural installation directory into the current directory. The existing Natural installation remains unchanged. Enter the full path to the existing root directory (or use the Browse button to select the root directory from a dialog box). At least the NATURAL.INI file is expected in this case.

    The following configuration files are reused or copied:

    <install-dir>/Natural/etc/NATURAL.INI 1
    <install-dir>/Natural/etc/NATCONV.INI
    <install-dir>/Natural/etc/NATCONF.CFG 2
    <install-dir>/Natural/etc/SAGtermcap
    <install-dir>/Natural/prof/ 3
    <install-dir>/Natural/<host-name> 4
    <install-dir>/Natural/nwo/<host-name> 5
    All Natural text members INST-<productcode> within the library SYSPCI

    Notes:

    1 For the default buffer pool NATBP, new semaphore and shared memory keys are generated, and the buffer pool parameter READONLY is set to NO.

    2 The paths of the default system files (22,10 and 22,20) are adapted to the current installation directory.

    3 All files except NDVSERVER.PRU.

    4 If available and independent from the selection of the ApplinX Interface: All files except log files.

    5 If available and independent from the selection of the Web I/O Interface: All files except log files.

  10. Choose the Next button.

  11. First-time installation only: When Development Server was selected in the product selection tree, enter the full path to the Natural Development Server license file (or use the Browse button to select it from a dialog box). You can enter a different value for the Natural Development Server port. Values between 1023 and 65536 are valid. The default value is 2700. If this port is already used, the number of the next free port will be shown.

    Natural Development Server

  12. Choose the Next button.

  13. First-time installation only: When Web I/O Interface was selected in the product selection tree, you can enter a different value for the port. This port is used by the Natural Web I/O Interface daemon. Values between 1023 and 65536 are valid. The default value is 2900. If this port is already used, the number of the next free port will be shown.

    Natural Web I/O Interface

  14. Choose the Next button.

  15. First-time installation only: When Natural Security was selected in the product selection tree, enter the full path to the Natural Security license file (or use the Browse button to select it from a dialog box).

    Natural Security license file

  16. Choose the Next button.

  17. On the last panel, review the list of products and items you have selected for installation. If the list is correct, choose the Next button to start the installation process.

    When the Software AG Installer has completed the first-time installation, additional configuration steps are required. See Completing the Installation for further details.

Using Software Distribution Tools to Install Natural

You can use the Software AG Installer to create an installation package which can then be distributed automatically to any number of computers in your environment. You can use third-party distribution tools for this purpose.

To distribute Natural, the following items are required:

  • Software AG Installer.

  • Installer image containing the products to be installed.

  • Script file which defines the location of the image file, the products to be installed, and the locations of all required license files.

  • License files for the products to be installed.

The description below just provides a brief overview on how to create the required files. For more detailed information, see Using the Software AG Installer.

Start of instruction setTo create the image and script

  1. Start the Software AG Installer GUI as described in Using the Software AG Installer.

  2. On the Welcome panel, choose the Advanced Options button.

  3. Go to the Images tab and proceed as follows:

    1. Select the Use installation image check box.

    2. Select the Create image option button.

    3. Specify a location and name for the image. The installer will automatically add the extension .zip.

    4. Specify the platform for which you want to create the image. You can create an image for any platform from any platform.

    5. Choose the OK button to return to the Welcome panel.

  4. Choose the Next button repeatedly in order to:

    1. Select the products to be installed.

    2. Agree to the terms of the license agreement.

    3. Start the installation to create the image.

    Note:
    When creating an image, the panels on which you usually specify the license files and ports do not appear.

  5. Start the Software AG Installer GUI once more, and choose the Advanced Options button again.

  6. Go to the Images tab again and proceed as follows:

    1. Select the Use installation image check box.

    2. Select the Install from image option button.

    3. Specify the name of the image that you have previously created.

  7. Go to the Scripts tab and proceed as follows:

    1. Select the Use installation script check box.

    2. Select the Create script option button.

    3. Select the Do not install products on local machine option button, unless you also want to install on the local machine in the same step.

    4. Specify a location and name for the script.

    5. Choose the OK button to return to the Welcome panel.

  8. Choose the Next button repeatedly in order to:

    1. Specify the installation directory.

    2. Select the products to be installed.

    3. Agree to the terms of the license agreement.

    4. First-time installation only: Specify the paths to all required license files and, if required, specify the ports for the selected products.

    5. Start the installation to create the script.

      Note:
      It is recommended that you create separate scripts for first-time installations and update installations.

Start of instruction setTo adapt the script

  1. Edit the script that you have previously created and adjust the references to the image and license files. For example: 

    guiNscLicense=__VERSION1__,C%3A%5CUsers%5Cxyz%5CDocuments%5CLics%5Cnsc84.WinDesk.2017.xml
guiNatLicense=__VERSION1__,C%3A%5CUsers%5Cxyt%5CDocuments%5CLics%5Crun84WinDesk.2017.xml
imageFile=C\:\\Users\\xyz\\Documents\\NaturalSec84.zip

    For an automated installation, the references to the image and license files need to be adjusted to the actual installation location. You can specify either the full path or a relative path such as file-name, .\\file-name or .\\folder-name\file-name. You can also specify the full path to a file server such as \\\\file-server\\folder-name\file-name. The following examples show the different ways in which a path can be specified: 

    guiNscLicense=__VERSION1__,nsc84.WinDesk.2017.xml
guiNscLicense=__VERSION1__,.\\Lics\\nsc84.WinDesk.2017.xml
guiNscLicense=__VERSION1__,\\\\Server1\\Lics\\nsc84.WinDesk.2017.xml

    You also can use environment variables as part of the path specification. For example: 

    imageFile=$IMAGEDIR$\\NaturalSec84.zip

  2. If necessary, adjust the parameter values in the script (for example, port numbers).

    Note:
    You can delete the port specification lines for Natural Development Server (guiNdvPort=..) and the Natural Web I/O Interface (guiWebioPort=..) from the script if you want to make sure that the installation does not stop if the specified port number is in use. In this case, the next free port number will be used.

Start of instruction setTo start the installation

  1. Start the installation from the command line. Start the installer jar file as follows: 

    java -jar SoftwareAGInstaller.jar -readScript script-file-name -scriptErrorInteract no

    Note:
    An appropriate Java version must be installed on the machine.

  2. For security reasons, the installer does not store the sudo password in installation scripts. Execute the afterInstallAsRoot.sh script manually after the installation (see also Registering Daemons and Setting File Permissions).