Release Notes

This document covers the following topics:


About Natural for Ajax Version 8.3

Natural for Ajax Version 8.3 is available as a runtime version and as a development version. The runtime version is intended for production usage. The development version is intended for Natural for Ajax development with Natural Studio and Natural for Ajax Tools, which is a Natural Studio extension.

Beside this product documentation, additional product information is available at the following places:

License Key

A valid license key file is required during the installation. The license key file is an XML file which is usually supplied along with the product. Alternatively, you can obtain a license key file from Software AG via your local distributor.

For the runtime version, you need a license key for Natural for Ajax Runtime.

For the development version, you need a license key for Natural for Ajax Developer.

Make sure to copy only one license key file to the appropriate location during installation.

Prerequisites

See Prerequisites in the Installation section for detailed information.

Supported Operating Systems

Development Version

Microsoft Windows 7 Professional (x86)
Microsoft Windows 7 Professional (x64)
Microsoft Windows 8 Professional (x64)
Microsoft Windows Server 2008 (x86)
Microsoft Windows Server 2008 (x64)
Microsoft Windows Server 2012 (x64)
Red Hat Enterprise Linux 6 (zSeries 64-bit)
Red Hat Enterprise Linux 6 for AMD64 and Intel EM64T (x86-64)
SUSE Linux Enterprise Server 11 (zSeries 64-bit)
SUSE Linux Enterprise Server 11 for AMD64 and Intel EM64T (x86-64)

Natural for Ajax is always delivered as 32-bit application, even on 64-bit platforms.

Runtime Version

Microsoft Windows 7 Professional (x86)
Microsoft Windows 7 Professional (x64)
Microsoft Windows 8 Professional (x64)
Microsoft Windows Server 2008 (x86)
Microsoft Windows Server 2008 (x64)
Microsoft Windows Server 2012 (x64)
Oracle Solaris 10
Oracle Solaris 11
AIX 7.1 64-bit
HP-UX 11i v3 64-bit (Itanium)
Red Hat Enterprise Linux 6 (zSeries 64-bit)
Red Hat Enterprise Linux 6 for AMD64 and Intel EM64T (x86-64)
SUSE Linux Enterprise Server 11 (zSeries 64-bit)
SUSE Linux Enterprise Server 11 for AMD64 and Intel EM64T (x86-64)
z/OS 1.12
z/OS 1.13

Natural for Ajax is always delivered as 32-bit application, even on 64-bit platforms.

Supported Application Servers and Web Containers

JBoss Application Server 5.1, 6.1 and 7.1
Oracle GlassFish Server 3.1
Apache Tomcat 6 and 7
IBM WebSphere Application Server 7, 8.0 and 8.5

where Oracle GlassFish Server is only supported on

Microsoft Windows
Solaris

Supported Web Browsers

Internet Explorer 8, 9 and 10
Mozilla Firefox Extended Support Release 10 and 17 (1)
Safari 5.1 on Windows and Mac OS X
Google Chrome (2)

Notes:

(1) Only the Extended Support Releases of Mozilla Firefox are explicitly supported.

(2) The Google Chrome support is based on Google Chrome Version 19. Due to frequent version upgrades of Google Chrome, compatibility of Natural for Ajax with future versions of Google Chrome cannot be fully guaranteed. Possible incompatibilities will be removed during the regular maintenance process of Natural for Ajax.

New Features in Version 8.3.1

This section describes new features and enhancements in Natural for Ajax which have been added after the release of Natural or Ajax Version 8.2.7.

New Property for NATPAGE

The NATPAGE control now supports the new property natkcheck. This property helps to avoid ambiguous variable names when a check for keywords is performed with the Natural profile parameter KCHECK.

HTTP Method POST

It is now possible to start applications with the HTTP method POST. With previous versions, it was only possible to use the HTTP method GET. See Starting a Natural Application with a URL in Client Configuration.

Integrated Authentication Framework (IAF)

With Natural for Ajax, it is now possible to authenticate against a Software AG IAF server. See Using Integrated Authentication Framework (IAF) in Client Configuration.

Error Handling Servlet

A default error handling servlet is now available. See Customizing Error Pages in Client Configuration.