Configuring the Natural Web Interface

#### Search Results

Search

# Configuring the Natural Web Interface

This section provides information on how to configure the Natural Web Interface. If you are not familiar with a specific product, refer to the corresponding product documentation for more information.

This section covers the following topics:

- Supported HTTP Servers

- Configuring RPC and RPC Server

- Configuring the Web Interface

- Configuring the Web Interface for Apache 2.4.x (64bit)

- Configuring an HTTP Server

- Communication with Natural Security

The latest documentation updates are published at https://documentation.softwareag.com/.

## Supported HTTP Servers

Operating System | HTTP Server
--- | ---
Windows (Intel) | Microsoft Internet Information Server Version 6.0/7.5 Apache Version 2.0.x Apache Version 2.2.x Apache Version 2.4.x (64bit)
(*) | Apache Version 2.0.x Apache Version 2.2.x Apache Version 2.4.x (64bit)

## Configuring RPC and RPC Server

In the following configuration description, ETB255 is the name of a Broker and NATWEB1 the name of an RPC Server used for the examples.

For the installation and configuration, refer to the Natural RPC, Entire Net-Work, and EntireX Communicator documentation.

The following topics are documented below:

- Current Version of Natural for z/OS, Linux, or Windows

- EntireX Communicator / EntireX Developer's Kit

### Current Version of Natural for z/OS, Linux, or Windows

#### On Windows and Linux Systems using SYSWEB3

To change your NATPARM file so that two additional steplibs can be accessed in the RPC environment, in the Natural Execution Configuration parameter group, add the two steplibs SYSWEB3 and SYSEXT to the steplib parameter subsection.

#### In a z/OS Environment using SYSWEB

If Natural Security is installed, define the steplibs SYSWEB and SYSEXT for your library.

If Natural Security is not installed:

- Modify the Natural program WEB-STLB in library SYSWEB by entering the DBID and file number of the associated FNAT system file of the libraries SYSWEB and SYSEXT. If required, you can add additional steplibs.

- STOW the program.

- The STACK parameter for your RPC server should have the following value: `STACK=(LOGON SYSWEB;WEB-STLB)`

### EntireX Communicator / EntireX Developer's Kit

#### On Windows Systems

Setting the environment variables is not required.

#### On Linux (All Platforms)

All EntireX-relevant environment variables must be passed by the HTTP server.

## Configuring the Web Interface

The following topics are covered below:

- Natural Web Interface

- Natural Web Server Extensions for RPC

- Natural Web Server Extensions for DCOM

### Natural Web Interface

For z/OS, Windows, and Linux environments no configuration is required.

### Natural Web Server Extensions for RPC

Adjust the configuration file using an external editor:

    RPC_ETB_ID_NAME=ETB255
    RPC_SERVER_NAME=NATWEB1

#### With a Natural RPC Server Running in a non-ASCII Environment

The parameter `NWW_OUT_CSS_TRANSLATE` must be set in the Configuration File. Its value depends on the code page used.

### Natural Web Server Extensions for DCOM

#### Local DCOM (All Platforms)

No adjustments are required for local communication.

External DCOM (All Platforms)

For external communication, see the NaturalX documentation for registry changes, or adjust the configuration file using an external editor:

    DCOM_SERVER_NAME=NATWEBEXT

On Windows (Internet Information Server)

If you use the Internet Information Server, the username for anonymous logon, e.g. NATWEB, is used. NATWEB must belong to the group USER, or the GUEST account must be enabled.

#### On Windows (Apache)

If you use the Apache Server, the default settings for User/Group specified at httpd.conf can be used:

# User/Group: The name (or # number) of the user/group to run httpd as User nobody Group #-1

## Configuring the Web Interface for Apache 2.4.x (64bit)

This functionality is currently only applicable in conjunction with RPC (see also Configuring RPC and RPC Server).

In order to use the SYSWEB3 functionality, the MOD approach or the CGI approach can be chosen. MOD means that the module provided by the product is linked to the Apache Web Server libraries in order to speed up performance. The following sections show what modifications are necessary in the configuration file httpd.conf to allow the MOD and the CGI approach.

## Configuring an HTTP Server

#### Windows (Internet Information Server 6.0 and 7.5)

If you use the Internet Information Server, the username for anonymous logon, e.g. |USR_NATWEB, is used. |USR_NATWEB must belong to the group USER, or the GUEST account must be enabled.

## Communication with Natural Security

The new version of the EntireX Developer's Kit supports the usage of two passwords and user IDs.

The first user ID is used to get access through EntireX Security and the second for Natural Security.

The HTTP Server Security is involved as a third security system.

### HTTP Server Security

Restrict the access of the NWW interface at your HTTP Server. For details, refer to your HTTP server documentation.

### EntireX Security

In the configuration file the `NWW_USER_ID` and `NWW_PASSWORD` have to be specified.

### Natural Security

A second User ID/Password (`RPC_USER_ID`, `RPC_PASSWORD`) has to be set.

If the parameter `USE_REMOTE_USER` is activated, the `RPC_USER_ID` will be set/overwritten. The `RPC_PASSWORD` remains unchanged.

It is necessary to set up Natural Security with `"AUTO=ON"` to pass security without password. If no `RPC_USER_ID`/`RPC_PASSWORD` pair is set, the `NWW_USER_ID`/`NWW_PASSWORD` will be used to ensure compatibility with the existing implementation.

### On this page

- Supported HTTP Servers
- Configuring RPC and RPC Server
- Configuring the Web Interface
- Configuring the Web Interface for Apache 2.4.x (64bit)
- Configuring an HTTP Server
- Communication with Natural Security