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:
The recommended development Environment for Natural and Natural for Ajax is NaturalONE.
NaturalONE supports the development of both:
Natural programs and Natural for Ajax user interface layouts.
Java programs if you want to use the Natural for Ajax Java support for
extensions or layout pages.
For information on how to start with Natural and Natural for Ajax development in NaturalONE see the NaturalONE documentation, particularly the chapters Using NaturalONE and Ajax Developer.
With NaturalONE, the development of the user interface layouts, does not require anything to be installed or configured. However ...
The development of Natural programs in Natural Server Mode requires
corresponding Natural Development Servers on your remote machines.
The development of Natural programs in Local Mode requires no additional
Natural systems to be installed or configured.
For more information, see the NaturalONE and Natural documentation.
Tip:
Install the Natural for Ajax demos from the Welcome Page of NaturalONE. After installation, run the program MENU.NSP. Each sample shows a documentation page on which you see the names of the layout file and the Natural program. You can open the sample layouts in the Layout Painter editor and edit and debug the Natural code.
For practicing remote development with Natural's Single Point of Development (SPoD), a Natural Development Server must be installed and activated on the remote machine.
When the Natural Development Server runs on a mainframe, see the Natural Development Server documentation.
When the Natural Development Server runs on Linux, see Activating the Natural Development Server on Linux in the Installation documentation provided for Natural on Linux and Cloud.
When the Natural Development Server runs on Windows, the Web I/O Interface service option, with setup type Custom, must be selected when installing Natural. See the Installation documentation provided for Natural for Windows.
To set up Natural Studio
Ask your administrator for the hostname and 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 provided for Natural for Windows.
Creating a new Natural library for each Application Designer project is recommended.
Running Natural for Ajax applications outside of NaturalONE in production and/or test environments requires installation of a Natural server.
Prerequisites:
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 provided for Natural for Mainframes.
On Linux, the Natural Web I/O Interface server runs as a daemon. This 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 provided for Natural on Linux and Cloud.
On Windows, the Natural Web I/O Interface server runs as a service. The Web I/O Interface service must be installed. See the Installation documentation provided for Natural for Windows.
See also Installing and Configuring the Natural Web I/O Interface Server in the Natural Web I/O Interface documentation provided for Natural for Windows.
The Natural for Ajax Runtime package is a web application archived in a .war file. The basic cisnatural.war file contains tools for configuration and monitoring and login pages connecting to remotely running Natural servers.
The cisnatural.war file provides everything for applications based exclusively on Natural Web I/O.
For customized rich internet pages, NaturalONE generates an extended .war file, containing the Natural for Ajax runtime and the customized rich internet pages. To get started, the basic cisnatural.war file includes a rich internet sample application – the NaturalAjaxDemos.
The setup of the basic cisnatural.war file requires an application server or web container - see the chapter System Requirements.
Deploy the cisnatural.war file into your application server or web container using the deployment tools of these servers/containers. See also the chapter Installation.
After the deployment of the cisnatural.war file, you can immediately run the NaturalAjaxDemos and Natural Web I/O applications. Depending on your Natural environment, you may have to adapt the default session configuration. To do so, invoke the configuration tool. See Natural Client Configuration Tool in the Configuration and Administration documentation. Ask your administrator for the host name and port number of the Natural Web I/O Interface server.
To set up the NaturalAjaxDemos for Natural for Mainframes
In the configuration tool, duplicate the Natural for Ajax Example (Windows).
This session starts the Natural for Ajax examples delivered with Natural in the library SYSEXNJX. Adapt the settings as follows:
|
Option |
Description |
|---|---|
|
Session ID |
Enter the name 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 |
Remove the script-name (nwo.bat/nwo.sh). |
Press Ok and then Save Configuration.
Click Natural for Ajax Login and select your newly created Session ID.
To set up the NaturalAjaxDemos for Natural on Linux and Cloud
In the configuration tool, open the Natural for Ajax Example (UNIX). This session starts the Natural for Ajax examples delivered with Natural in the library SYSEXNJX. Adapt the settings as follows:
|
Option |
Description |
|---|---|
|
Session ID |
Enter the name 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. With Natural on Linux and Cloud a default shell script for starting Natural (nwo.sh) is delivered. See also nwo.sh - Shell Script for Starting Natural in the Natural Web I/O Interface documentation. |
Press Ok and then Save Configuration.
Click Natural for Ajax Login and select your newly created Session ID.
To set up the NaturalAjaxDemos for Natural for Windows
In the configuration tool, open the Natural for Ajax Example (Windows). This session starts the Natural for Ajax examples delivered with Natural in the library SYSEXNJX. Adapt the settings as follows:
|
Option |
Description |
|---|---|
|
Session ID |
Enter the name 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. With Natural for Windows a default batch file for starting Natural (nwo.bat) is delivered. See also Batch File for Starting Natural in the Natural Web I/O Interface documentation. |
Press Ok and then Save Configuration.
Click Natural for Ajax Login and select your newly created Session ID.