Natural Client Configuration Tool

The number of seconds that the client waits for the next user activity. When the defined number of seconds has been reached without user activity, the session is closed. The default is 3600 seconds.

Optional. Location of a different trace directory.

When a different trace directory is not defined, the trace files are written to the default trace directory. By default, the trace files are written to the directory which has been set by the Java property java.io.tmpdir. On Windows, this is normally the environment variable TMP for the user who started the application server. On UNIX, this is normally /tmp or /var/tmp.

You can also set this property in the start script for the application server. The following examples apply to JBoss.

• Example for Windows (run.bat):

  set JAVA_OPTS=%JAVA_OPTS% -Djava.io.tmpdir=C:\temp

• Example for UNIX (run.sh):

  set JAVA_OPTS="$JAVA_OPTS -Djava.io.tmpdir=/tmp

Tracing can be enabled individually for each session (see Overview of Session Options below). However, it should only be enabled when requested by Software AG support.

Optional. The path to your trust file. See Configuring SSL for further information.

If your trust file is password-protected, you have to specify the appropriate password.

When you do not specify the password for a password-protected trust file, the trust file cannot be opened and it is thus not possible to open an SSL session.

When your trust file is not password-protected, you should not specify a password.

If selected, users are authenticated before they access the Natural for Ajax logon page. See also Configuring Application-Managed Authentication.

If Use SAML for JAAS-based authentication is also selected, the secure logon page is only shown in the case of an error in the SAML artifact validation.

If selected, Natural for Ajax expects the use of the SAMLArtifactLoginModule which does not prompt the end user for a user name and password.

If you want to use other login modules which expect the user to enter a valid user name and password (such as the SSXLoginModule), make sure that this check box is not selected.

See also Using Software AG Security Infrastructure.

Optional. An application name of your choice. This name is used to provide more individual disconnect messages. The name entered here will replace the term "Application" in the standard disconnect message of Natural for Ajax applications.

For example, if the field Application name contains the word "Calculator" the disconnect message "Application finished successfully" would instead be "Calculator finished successfully".

Similar custom messages will be displayed if the application ends with an error.

• Undefined
  Default. User ID and password can have a maximum of 32 characters. See also the description for Natural for Windows, UNIX or OpenVMS below.

• Natural for Mainframes
  User ID and password can have a maximum of 8 characters.

• Natural for Mainframes with Natural Security
  User ID and password can have a maximum of 8 characters. The user ID must comply with the Natural naming conventions for library names.

• Natural for Windows, UNIX or OpenVMS
  User ID and password can have a maximum of 32 characters. When a domain is required, you have to specify it together with the user ID (in the form "domain\user-ID").

With Natural for Ajax, the users can switch to another style sheet during a running session. If set to No, the users are no longer able to select another style sheet.

The name of the style sheet which determines the colors, fonts and PF key button style of the current session. See Using Style Sheets. When this element is specified, a fixed style sheet is used. In this case, the corresponding field does not appear on the logon page and the user is thus not able to select a different style sheet.

Important:
If you want to use SSL with Natural for Mainframes, one of the corresponding mainframe types must be selected; the type must not be Undefined or Natural for Windows, UNIX or OpenVMS. The other way around, if you want to use SSL with Natural for Windows, UNIX or OpenVMS, you must not select one of the mainframe types; the type may also be Undefined in this case.

If selected, application-managed authentication is used. This setting implies that Forward credentials is also selected. See also Configuring Application Managed Authentication.

If Use SAML for JAAS-based authentication is also selected in the global settings, the user name and password are not visible in the Natural for Ajax logon page. See also Using Software AG Security Infrastructure.

If selected, the security credentials from the application server are forwarded to the Natural Web I/O Interface server, thus sparing the user a second logon. See also Forwarding the User Credentials to Natural.

Optional. A valid password for the above user ID.

Under Windows, UNIX and OpenVMS, this is always the operating system password of the user, even if Natural Security is active.

On the mainframe, this is different: When Natural Security is not active, this is the operating system password of the user. When Natural Security is active, this is the Natural Security password.

When a password is specified, the corresponding field does not appear on the logon page. The configuration tool saves the password in encrypted form.

Applies only to applications that are designed as Application Designer workplaces.

If set to Yes (default), the default behavior of the option Share session user applies.

If set to No, the user credentials (user ID and password) are not saved in the Application Designer session and are therefore not available for an Application Designer subsession.

An example for a workplace application is available under the following URL:

http://<host>:<port>/cisnatural/servlet/StartCISPage?PAGEURL=/njxdemos/wpworkplace.html

where <host> and <port> are the host name and port number of your application server.

Applies only to applications that are designed as Application Designer workplaces.

If set to No (default), the user credentials of the main Application Designer session are automatically used in an Application Designer subsession if the server and port of the subsession is the same as in the main session. If the server and port are not the same, the user has to specify the user ID and password in a logon dialog.

If set to Yes, the user credentials of the Application Designer main session are always used for all Application Designer subsessions on all involved servers - even if the server and port are different.

• Natural for Mainframes
  The name of the Natural program or a command sequence that starts your application as you would enter it on the NEXT prompt. Example:

  TEST01 data1,data2

• Natural for UNIX
  The name of the UNIX shell script for starting the Natural application (a file similar to nwo.sh).

• Natural for OpenVMS
  The name of the Natural image file (for example, natural<version> or natural<version>.exe).

• Natural for Windows
  The name of the Windows command file (.bat) for starting the Natural application.

When this is specified, the corresponding field does not appear on the logon page.

Optional. Parameters for starting the Natural application. This can be stack parameters, a parameter file/module or other Natural-specific information.

• Natural for Mainframes
  Used to pass dynamic Natural profile parameters to the session, for example:

  SYSPARM=(MYPARMS) STACK=(LOGON MYAPPL)

  Note:
  It is recommended to specify the Natural program that starts the application with the option Application instead of passing it with the profile parameter STACK.

• Natural for UNIX and Natural for Windows
  Used when the above shell script (UNIX) or command file (Windows) uses the parameter $5 after "natural", for example:

  PARM=MYPARM STACK=(LOGON MYLIB;MENU)

• Natural for OpenVMS
  Used for starting a Natural application, for example:

  BP=BPnode-name NLDCHK WEBIO=ON "STACK=(LOGON SYSEXT;MENU)"

Defines whether the default disconnect page is to be shown when a Natural program ends, or whether the current browser tab is to be closed. You can select the required setting from the drop-down list box.

• Display disconnect page
  Default. The disconnect page is always displayed.

• Always close browser
  The current browser tab is closed. When the last tab in the browser is closed, the entire browser is closed.

• Close browser, but display disconnect page on error
  The current browser tab is closed. When the last tab in the browser is closed, the entire browser is closed. However, in the case of an unexpected error, the disconnect page is shown.

Internet Explorer allows closing the browser with JavaScript by default. For Firefox, however, this has to activated as follows:

1. In the Firefox address bar, type the following:

   about:config

   A warning message appears, saying that changing the advanced settings can be harmful and that you should only continue if you are sure of what you are doing.

2. Choose the I'll be careful, I promise! button.

3. In the Filter text box, type the following:

   dom.allow_scripts_to_close_windows

4. Set this value to "true" by double-clicking on the entry (default: "false").

You can select the required language from the drop-down list box.

It is also possible to select Set in workplace from the the drop-down list box. When selected, the language that is currently used in the workplace will also be used for the next start of Natural.

See also Multi Language Management. Default: English.

Applies only to Natural maps, not to rich GUI pages.

The key that is to be simulated when double-clicking an output field. By default, this is the ENTER key.

It is possible to disable the double-click behavior, or to define a function key (PF1 through PF12).

You can select the required setting from the drop-down list box.

Tip:
When context-sensitive help has been defined for the output fields, it may be useful to define PF1. The help function will then be invoked when the user double-clicks an output field.

Applies only to Natural maps, not to rich GUI pages.

By default, only the named function keys are shown as buttons.

It is also possible to show buttons for all function keys, including those which do not have names. You can specify whether to display buttons for 12, 24, 36 or 48 function keys. Each line always contains 12 function key buttons. The first line also contains a button for the ENTER key. Each function key button is always displayed at the same position.

You can select the required setting from the drop-down list box.

Applies only to Natural maps, not to rich GUI pages.

The number of rows in the output window. Possible values: minimum 24, no upper limit. Default: 24.

Not used by Natural for Mainframes which uses the profile parameter TMODEL instead.

Applies only to Natural maps, not to rich GUI pages.

The number of columns in the output window. Possible values: minimum 80, no upper limit. Default: 80.

Not used by Natural for Mainframes which uses the profile parameter TMODEL instead.

Applies only to Natural maps, not to rich GUI pages.

If set to Yes, the PF key numbers are shown next to the PF keys.

If set to Yes (default), numeric input fields are validated. In this case, only the following characters are allowed in numeric input fields (in addition to the numbers "0" through "9"):

blank
+ (plus)
- (minus)
_ (underscore)
, (comma
. (period)
? (question mark)

If set to No, numeric input fields are not validated.

Applies only to Natural maps, not to rich GUI pages.

If set to Yes, the cursor is automatically placed in the next input field when the last possible character has been entered in the current input field.

If set to No (default), the cursor remains in the current input field.

Applies only to Natural maps, not to rich GUI pages.

Optional. Used to translate characters that are sent from the host or entered by the user into different characters to be shown on the screen.

You enter the characters to be translated in the Translate characters from text box and the characters to be used instead in the Translate characters to text box (in the same order as in the first text box). Both text boxes must contain the same amount of characters.

The following example shows how to translate all lower-case characters to upper-case characters:

The following example shows how to translate the so-called "European numerals" to "Arabic-Indic numerals":

Applies only to Natural maps, not to rich GUI pages.

Optional. The filler character that is to be removed from the input fields. An application can define, for example, an underscore (_) as the filler character. Trailing filler characters will be removed from the input fields, and leading filler characters will be replaced with blanks.