This document covers the following topics:
NaturalONE is part of the Software AG Designer. It is an Eclipse-based development environment for developing and maintaining Natural applications with web-based user interfaces and Natural services. NaturalONE combines the functionality of several tools into a single development framework, and covers functionality across the entire product development lifecycle, including application development, testing, automated documentation of the sources in Predict, versioning, and deployment of the application into the production environment.
NaturalONE uses the standard Eclipse functionality and adds its own perspective, views, editors and commands to the Eclipse workbench. NaturalONE is integrated seamlessly into the Eclipse workbench. This means that you do not see where the standard Eclipse workbench ends and where the NaturalONE-specific user interface starts.
NaturalONE addresses developers who are used to work natively on mainframe, UNIX, Linux, OpenVMS or Windows platforms. Owing to the graphical user interface and many features for fast Natural source development (such as code assist), developers gain productivity using this environment. Developers who are already familiar with Eclipse can comfortably edit Natural sources in an environment to which they are already used; the environment always behaves in the same way, no matter whether Natural or Java applications are developed.
If you are not yet familiar with Eclipse, see the Eclipse online help at http://www.eclipse.org/documentation/, or start the Software AG Designer and then choose . General information on Eclipse can then be found under Workbench User Guide. When working with the Software AG Designer, the online help also provides help for the currently installed Software AG products; this can be found under Software AG Designer Guides.
The basic functionality of NaturalONE is described in Using NaturalONE.
In the Eclipse workspace, all files are organized in projects. A direct connection to a Natural server is not required for editing the Natural sources. However, for executing and debugging a Natural application, NaturalONE establishes a connection to the appropriate Natural runtime.
The following topics are covered below:
Applications can be developed or maintained in the Eclipse environment.
To support developers and gain productivity during the development life-cycle, specific Natural editors are available:
The source editor uses a real incremental Natural parser. It supports the developer with syntax coloring of the Natural source and content assist for fast code writing. Both Natural programming modes (reporting mode and structured mode) are supported. For the development of international applications, bidirectional language support is enabled.
NaturalONE makes use of the Natural source editor for data
area editing. Data areas are defined with the
statement. With the assistance of the Natural parser, syntactically correct
data areas can be developed quickly and easily.
With the map editor, Natural maps can be defined graphically. This also includes bidirectional language support. It is possible to navigate through the parts of a map on a graphical basis using the Outline view. Inline rules or Predict rules can also be edited.
DDMs which have been generated by Predict can be adopted for your application. It is also possible to create DDMs from scratch. This can be done for all types supported by Natural: Adabas, SQL, Tamino, VSAM and more. In the Outline view, the DDM structure is visualized in a hierarchical manner.
Debugging and execution of applications is possible. Watchpoints, breakpoints, etc. make bug fixing less complex.
With the XML toolkit, it is possible to generate functionality for the processing of XML documents. DTDs or schemas can be used for generating Natural data areas, parser implementations and serializers for XML documents, and vice versa.
The data browser provides fast access to Adabas or SQL databases. With just a few mouse clicks, it is possible to write a database retrieval and to display the retrieved data in the Report Data view. It is easy to check the content of the database and to test whether the application works correctly.
Offloading the application into the Eclipse workspace gives you several advantages. The Natural builder keeps the dependencies of the application. This is visualized in the Dependencies view. The builder keeps track of the source changes. Owing to the label decorations, you can easily see which Natural objects have not yet been saved locally, not yet been compiled on the Natural server or not yet been versioned in your version control system. When the preferences are set properly, the builder recatalogs the appropriate objects on the Natural server using the Natural parameters that are defined in the Eclipse environment.
Basically, the builder supports two different workspace structures: one which is very Natural-related (that is, the application is based on the conventional Natural library structure), and another which allows you to define folders which follow the naming conventions of the underlying file system (Windows or Linux). With the latter workspace structure, the folders are mapped to "real" Natural libraries. Thus, you can structure your Natural applications in the workspace in a more logical way than with the conventional library structure. Folders can be nested.
Besides using folders in the workspace, it is also possible to use alternative (long) file names for the objects. These file names also have to follow the rules of the underlying file system. There is a mapping between the alternative file name and the Natural object name, where the Natural object name always follows the Natural naming conventions.
Where useful, wizards (for example, for creating new projects or new objects) are used.
Error messages are edited with the error message editor. They are also stored in the Eclipse workspace.
To gain productivity, features which support often repeated actions are available. For example, you can externalize code fragments into separate Natural objects. Or you can rename Natural objects using the refactoring feature. When you create a Natural source from scratch, a skeleton according to the Natural object type is automatically generated.
You can customize the NaturalONE environment to your specific needs. In the Natural preferences, you can change the behavior of the Natural builder, you can define the platform for which the Natural parser is to check the Natural syntax, or you can create your own code templates.
You can version your applications in a version control system. A Natural application consists of the Natural objects, configuration parameters, error messages, etc. A version control system enables you to merge the application pieces from several developers. After merging the sources in the repository of the version control system, the application is ready for deployment onto the designated platform. The deployment wizard ensures that the appropriate parts of the application are deployed onto the Natural server. See also Using a Version Control System.
Out of the box, it is possible, for example, to execute, debug or test Natural applications or parts of them. The local Natural runtime is already configured for usage with NaturalONE. By default, no additional configuration is required. With the local Natural runtime, an EntireX broker environment is available and an RPC server is started. This allows you to develop RPC-based applications or to make use of web services.
If you are used to work with Natural Studio and Natural's Single
Point of Development (SPoD) concept, you will find comparable functionality in
NaturalONE. The Natural Server view makes visible the
information from the Natural servers which may be located on different
platforms (on a mainframe, UNIX, Linux, OpenVMS or Windows platform). Using
this view, you can edit your Natural sources directly on a Natural server, and
catalog or even execute them directly on the server. Information about the
server configuration is available; this is similar to the output of the Natural
Ajax Developer includes a number of tools for creating and maintaining complex graphical user interfaces. Its central tool is the Layout Painter which is used to define layouts for HTML pages.
In addition to the above-mentioned application development functionality which is always installed with NaturalONE, you can also install optional components for NaturalONE. Some of these optional components require that additional software is installed on a server.
The headings below correspond to the names that are used in the product selection tree of the Software AG Installer. See also Installing NaturalONE.
The Application Testing component is used to directly test or create unit tests for various Natural objects, including subprograms, maps, subroutines and business services. It requires that EntireX is installed.
When you select Application Testing in the installer, the context menu will be available in the Navigator view. For detailed information, see the Application Testing documentation.
The Mainframe Tools component includes Mainframe Navigation which allows you to access and manipulate objects stored on a mainframe from Eclipse. These objects include datasets and members, as well as system objects such as active jobs or the console under the z/OS operating system. With Mainframe Navigation, the objects are displayed in a tree structure and can be browsed and edited in Eclipse. On the mainframe server, Mainframe Navigation is supported by Natural ISPF.
Mainframe Navigation requires that additional software is installed on a server. See Installation and Configuration in the Mainframe Navigation documentation.
When you select Mainframe Tools in the installer, the Mainframe Navigation view will be available. For detailed information, see the Mainframe Navigation documentation.
The Natural Construct component allows you to use your existing Natural Construct models in NaturalONE, and to create new Natural Construct models or code frames. It requires that additional software is installed on a server. See Requirements in the Using Natural Construct section of the Code Generation documentation.
When you select Natural Construct in the installer, the context menu will be available in the Navigator view. For detailed information, see Using Natural Construct in the Code Generation documentation.
The Predict component is used to document Natural sources in Predict via NaturalONE, manipulate and retrieve data stored by Predict on the server, and manage external objects (generation and administration). It requires that additional software is installed on a server. See Setting Up a Predict Environment in the Predict Description and Generation documentation.
When you select Predict in the installer, the context menu will be available in the Natural Server view. For detailed information, see the Predict Description and Generation documentation.
When you select Service Development in the installer, the following context menus will be available in the Navigator view:
Used to create and maintain business services. For detailed information, see the Business Services documentation.
This optional component requires that EntireX is installed. It also requires that additional software is installed on a server. See Prerequisites in the Business Services documentation.
Used to generate Natural subprograms and data areas. For detailed information, see the Code Generation documentation.