
	Version 6.3.3	SEARCH INDEX CONTENTS \| PDF BOOKS \| HOME UP PREV NEXT

— Natural for Ajax —

Setting Up Your Environment

Before you start developing and executing Natural for Ajax applications, you have to make specific definitions in your development environment.

This document covers the following topics:

Setting Up Application Designer
Setting Up Your Development Environment for Natural
Setting Up Your Runtime Environment for Natural

Setting Up Application Designer

Currently, there is nothing to configure for Natural pages.

Setting Up Your Development Environment for Natural

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.

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.
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.
Mainframe
When your Natural Development Server is located on a mainframe, see the Natural Development Server documentation.

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.
Create a new target 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 target in the project properties.

Setting Up Your Runtime Environment for Natural

The following must be installed on the remote machine where you are going to test and execute the Natural code:

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 Runtime. See the Installation documentation which is provided with Natural for Windows.
UNIX
A Web I/O Interface daemon must be installed and activated. For detailed information, see the Installation documentation which is provided for Natural for UNIX, especially the following sections:
- Installing and Setting Up Natural on UNIX
- Installing the Web I/O Interface Daemon on UNIX
- Activating the Web I/O Interface Daemon on UNIX
Mainframe
The Web I/O Interface Server must be installed and started. See Natural Web I/O Interface Server in the Natural for Mainframes documentation.

To set up the runtime environment for Natural for Windows

Ask your administrator for the host name and the port number of the Web I/O Interface service 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 Operations documentation.
Edit the configuration file <installdir>/WEB-INF/sessions.xml (the location of <installdir> depends on your application server environment) and add the following entry:
```
<session id="session-name" trace="false">
    <natural_server>host-name</natural_server>
    <natural_port>port-number</natural_port>
    <natural_program>batch-file-name</natural_program>
</session>
```
where:
- session-name is to be replaced with the entry that should be available for selection in the logon page, and
- host-name, port-number and batch-file-name are to be replaced with the values you received from your administrator.
In the configuration file, there is a preconfigured session that is intended to start the Natural for Ajax examples that are delivered with Natural in the library SYSEXNJX. It contains the following settings:
```
<session id="Natural for Ajax Examples" trace="false">
    <natural_server>host-name</natural_server>
    <natural_port>port-number</natural_port>
    <natural_program>batch-file-name</natural_program>
</session>
```
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.

To set up the runtime environment for Natural for UNIX

Ask your administrator for the host name and the port number of the Web I/O Interface daemon 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 Installation documentation.
Edit the configuration file <installdir>/WEB-INF/sessions.xml (the location of <installdir> depends on your application server environment) and add the following entry:
```
<session id="session-name" trace="false">
    <natural_server>host-name</natural_server>
    <natural_port>port-number</natural_port>
    <natural_program>script-name</natural_program>
</session>
```
where:
- session-name is to be replaced with the entry that should be available for selection in the logon page, and
- host-name, port-number and script-name are to be replaced with the values you received from your administrator.
In the configuration file, there is a preconfigured session that is intended to start the Natural for Ajax examples that are delivered with Natural in the library SYSEXNJX. It contains the following settings:
```
<session id="Natural for Ajax Examples" trace="false">
    <natural_server>host-name</natural_server>
    <natural_port>port-number</natural_port>
    <natural_program>script-name</natural_program>
</session>
```
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 Mainframes

Ask your administrator for the host name and the port number of the Web I/O Interface Server.
Edit the configuration file <installdir>/WEB-INF/sessions.xml (the location of <installdir> depends on your application server environment) and add the following entry:
```
<session id="session-name" trace="false">
    <natural_server>host-name</natural_server>
    <natural_port>port-number</natural_port>
</session>
```
where:
- session-name is to be replaced with the entry that should be available for selection in the logon page, and
- host-name and port-number are to be replaced with the values you received from your administrator.
In the configuration file, there is a preconfigured session that is intended to start the Natural for Ajax examples that are delivered with Natural in the library SYSEXNJX. It contains the following settings:
```
<session id="Natural for Ajax Examples" trace="false">
    <natural_server>host-name</natural_server>
    <natural_port>port-number</natural_port>
    <natural_program>script-name</natural_program>
</session>
```
Enter the settings (host name and port number) that match your environment. Remove the following line:
```
<natural_program>script-name</natural_program>
```
Then you will be able to execute the examples from the logon page.
Restart the application server.

SEARCH INDEX CONTENTS | PDF BOOKS | HOME UP PREV NEXT