Before you start developing and executing Natural for Ajax applications, you have to make specific definitions in your environment.
This document covers the following topics:
Currently, there is nothing to configure for Natural pages.
If you are practising remote development with Natural's Single Point of Development (SPoD), a Natural Development Server must be installed and activated on the remote machine.
Mainframe
When your Natural Development Server is located on a mainframe, see
the Natural Development Server documentation.
UNIX
When your Natural Development Server is located on UNIX, see
Activating the Natural
Development Server on UNIX in the
Installation documentation which is provided with Natural
for UNIX.
Windows
When your Natural Development Server is located on Windows, the
Web I/O Interface service option, which can be set with
the
setup type Custom, must
be selected when installing Natural. See the
Installation
documentation which is provided with Natural for Windows.
To set up Natural Studio
Ask your administrator for the host name and the port number of the Natural Development Server.
Connect to the Natural Development Server. See Accessing a Remote Development Environment in the Remote Development Using SPoD documentation which is provided with Natural for Windows.
It is recommended that you create a new Natural library for each Application Designer project.
To set up Natural for Eclipse
Ask your administrator for the host name and the port number of the Natural Development Server.
Map a Natural server in Natural for Eclipse, using this host name and port number. For further information, see the Natural for Eclipse documentation.
When creating a Natural project, assign this server in the project properties.
The following must be installed on the remote machine where you are going to test and execute the Natural code:
Mainframe
When your Natural Development Server is located on a mainframe, the
Natural Web I/O Interface server must be installed and started. For detailed
information, see Installing and Configuring the Natural Web I/O Interface
Server in the Natural Web I/O
Interface documentation which is provided for Natural for
Mainframes.
UNIX
On UNIX, the Natural Web I/O Interface server is implemented as a
daemon.
When your Natural Development Server is located on UNIX, the Natural Web I/O Interface daemon must be installed and activated. For detailed information, see Installing and Configuring the Natural Web I/O Interface Server in the Natural Web I/O Interface documentation which is provided for Natural for UNIX.
Windows
On Windows, the Natural Web I/O Interface server is implemented as a
service.
When your Natural Development Server is located on Windows, the Web I/O Interface service option, which can be set with the setup type Custom, must be selected when installing Natural Runtime. See the Installation documentation which is provided with Natural for Windows.
See also Installing and Configuring the Natural Web I/O Interface Server in the Natural Web I/O Interface documentation which is provided for Natural for Windows.
To set up the runtime environment for Natural for Mainframes
Ask your administrator for the host name and the port number of the Natural Web I/O Interface server.
Invoke the configuration tool which is used for managing the session configurations in the file sessions.xml. See Using the Configuration Tool in the Configuring the Client part of the Natural Web I/O Interface documentation.
Add a new session with the following settings:
| Option | Description |
|---|---|
| Session ID | Enter the name that is to be available for selection in the logon page. |
| Host name | The host name of the Natural Web I/O Interface server. Enter the value that you have received from your administrator. |
| Port number | The port number of the Natural Web I/O Interface server. Enter the value that you have received from your administrator. |
In the configuration file, there is a preconfigured session with the
name "Natural for Ajax Examples". It contains dummy
settings for the host name, port number and application. This session is
intended to start the Natural for Ajax examples that are delivered with Natural
in the library SYSEXNJX.
Enter the settings (host name and port number) that match your environment. Remove the dummy setting for the application (which is "script-name").
Then you will be able to execute the examples from the logon page.
Restart the application server.
To set up the runtime environment for Natural for UNIX
Ask your administrator for the host name and the port number of the Natural Web I/O Interface server and the name of the script that is used to start up Natural sessions. A sample shell script for starting up Natural (nwo.sh) is delivered with Natural for UNIX; see also nwo.sh - Shell Script for Starting Natural in the Natural Web I/O Interface documentation.
Invoke the configuration tool which is used for managing the session configurations in the file sessions.xml. See Using the Configuration Tool in the Configuring the Client part of the Natural Web I/O Interface documentation.
Add a new session with the following settings:
| Option | Description |
|---|---|
| Session ID | Enter the name that is to be available for selection in the logon page. |
| Host name | The host name of the Natural Web I/O Interface server. Enter the value that you have received from your administrator. |
| Port number | The port number of the Natural Web I/O Interface server. Enter the value that you have received from your administrator. |
| Application | The name of the script that is used to start up Natural sessions. Enter the value that you have received from your administrator. |
In the configuration file, there is a preconfigured session with the
name "Natural for Ajax Examples". It contains dummy
settings for the host name, port number and application. This session is
intended to start the Natural for Ajax examples that are delivered with Natural
in the library SYSEXNJX.
Edit this session and enter the settings (host name, port number and the name of the Natural startup script) that match your environment. Then you will be able to execute the examples from the logon page.
Restart the application server.
To set up the runtime environment for Natural for Windows
Ask your administrator for the host name and the port number of the Natural Web I/O Interface server and the name of the batch file that is used to start up Natural sessions. A sample batch file for starting up Natural (nwo.bat) is delivered with Natural for Windows; see also Batch File for Starting Natural in the Natural Web I/O Interface documentation.
Invoke the configuration tool which is used for managing the session configurations in the file sessions.xml. See Using the Configuration Tool in the Configuring the Client part of the Natural Web I/O Interface documentation.
Add a new session with the following settings:
| Option | Description |
|---|---|
| Session ID | Enter the name that is to be available for selection in the logon page. |
| Host name | The host name of the Natural Web I/O Interface server. Enter the value that you have received from your administrator. |
| Port number | The port number of the Natural Web I/O Interface server. Enter the value that you have received from your administrator. |
| Application | The name of the batch file that is used to start up Natural sessions. Enter the value that you have received from your administrator. |
In the configuration file, there is a preconfigured session with the
name "Natural for Ajax Examples". It contains dummy
settings for the host name, port number and application. This session is
intended to start the Natural for Ajax examples that are delivered with Natural
in the library SYSEXNJX.
Enter the settings (host name, port number and the name of the Natural startup batch file) that match your environment. Then you will be able to execute the examples from the logon page.
Restart the application server.
