What Can be Installed With Natural

#### Search Results

Search

# What Can be Installed With Natural

This document covers the following topics:

- Natural

- Natural Development Server

- Natural Web I/O Interface

- ApplinX Interface

- Natural Security

- License Files

- Natural Community Edition

## Natural

This is the local Natural development environment.

## Natural Development Server

Natural Development Server (NDV) enables remote development using Natural Single Point of Development (SPoD). Natural Development Server needs the Natural development environment as a prerequisite.

For further information (including any limitations that may apply for your installation), see the separate Natural Single Point of Development documentation and the separate Natural Development Server documentation.

## Natural Web I/O Interface

The Natural Web I/O Interface is used to execute Natural applications in a web browser and consists of a server and a client. The server part of the Natural Web I/O Interface needs the Natural development environment as a prerequisite. On Linux, the server is implemented as a daemon.

The Natural Web I/O Interface server supports two types of clients: the Natural Web I/O Interface client for displaying character-based applications in the web browser, and Natural for Ajax for displaying rich internet applications in the web browser. For more information, see the Natural Web I/O Interface documentation.

## ApplinX Interface

The ApplinX interface is used to replace the Natural character-based user interface by the ApplinX GUI facilities. It needs the Natural development environment as a prerequisite. See the separate ApplinX documentation for further information.

## Natural Security

Natural Security enables you to protect your Natural environment against unauthorized access and improper use. For further information, see the Natural Security documentation and especially the chapter Natural Security On Different Platforms.

## License Files

During the installation of Natural, the Installer prompts you to enter the path to one or more valid license files. However, if these licenses are not required (see below), these fields can be left empty. If a license file is not specified at installation time, it can be manually installed later (see below). The license file is an XML file which is delivered by e-mail.

Separate license files are required for the following products:

- Natural

  Note
  Starting with version 9.3.3, Natural can be installed without a license. During installation, you will still be prompted for the path to a license file, but you can leave the field empty. Without a license file, Natural runs in Community Edition mode (see below).

- Natural Security

  Note
  Starting with version 9.3.3, Natural Security can be installed and "activated" via `SYSPCI` without a license. However, to run Natural Security, both a valid Natural license file and a valid Natural Security license file are required.

To install or replace a license file manually, you can copy it to the common/conf subdirectory of your corresponding Natural development installation directory, overwriting any existing license file. Note that the name of the license file must be <product-code><version>.xml, where <product-code> is the three-letter product abbreviation in lower case (for example "nat" for Natural, "nsc" for Natural Security, or "one" for NaturalONE), and <version> is the first two digits of the version number. For example, for Natural Security 9.3.3, the name of the license file must be nsc93.xml.

Notes:

1. The Installer does not check all information in the license file. All license checks are done, however, when the product itself is started.
2. Starting with Natural 9.3.3, a license for the Natural Development (NDV) Server is no longer required, neither during installation, nor at run-time.

## Natural Community Edition

Starting with Natural 9.3.3, the Natural Community Edition is no longer a separate product, but a mode of operation that is employed when Natural is started without a license. For simplicity and convenience, however, the term "Natural Community Edition" is sometimes still used, as if it still were a separate product.

In Community Edition mode, Natural runs without an expiration date but with the following limitations:

- User libraries are limited to 200 objects. System libraries do not have this restriction but are read-only.

- No more than two Natural sessions can simultaneously be running on the same buffer pool, even if the buffer pool was started with Maximum Users set to a larger value (see also Buffer Pool Assignments in the Configuration Utility documentation). However, if a valid Natural license is subsequently installed, the full user capacity provided by the buffer pool will immediately be available to newly started Natural sessions, without the buffer pool needing to be restarted.

- Batch mode is not available.

- Natural Security cannot be used.

- The maximum number of database calls between consecutive screen I/O requests (`MADIO`) is 32767. If `MADIO` is set to 0, it is treated as 32767 rather than "unlimited".

- The maximum number of program calls between consecutive screen I/O requests (`MAXCL`) is 50. If `MAXCL` is set to 0, it is treated as 50 rather than "unlimited".

- The `USIZE` parameter value is forced to its default setting of 20 MB internally, regardless of the passed value.

### On this page

- Natural
- Natural Development Server
- Natural Web I/O Interface
- ApplinX Interface
- Natural Security
- License Files
- Natural Community Edition