Project

General

Profile

Wiki » Documentation » Installation Configuration and Administration Guide » Directory Configuration Reference »

Session Management

Introduction

These are the configuration values which can be set in the directory to affect session creation or sesssion behavior for execution of converted 4GL code.

For details on the configuration for session initialization and termination hooks, see Server and Context Hooks.

Search Algorithm

The session related parameters are located inside the runtime container. If given with a relative path the order in which the parameter will be looked up will be:

  1. /server/<serverID>/runtime/<account_or_group>/<id>
  2. /server/<serverID>/runtime/default/<id>
  3. /server/default/runtime/<account_or_group>/<id>
  4. /server/default/runtime/default/<id>

or

  1. /server/<serverID>/<id>
  2. /server/default/<id>

or a combined lookup, when the per-account nodes are checked first and the per-server nodes last.

Configuration Parameters

helpapp

This setting is used to locate and execute a preconfigured HELP program (the program to be accessed in ChUI mode when F2 is pressed). The value of this setting should be the execute method of the main help Java class.

The path in which helpapp parameter resides is:

/server/<server_id>/runtime/<account_or_group>/helpapp

Example:

<node class="string" name="helpapp">
   <node-attribute name="value" value="com.acme.bogus.MyHelp.execute"/>
</node>

In ChUI applications, this was often a program named applhelp.p.

maxusers

The maxusers setting sets the maximum number of interactive users allowed to create a session. It is an integer value that defaults to -1. -1 means there is no limit.

The path in which the parameter resides is /security/config/.

Example:

     <node class="integer" name="maxusers">
        <node-attribute name="value" value="5"/>
     </node>

maxusersessions

The maxusersessions setting sets the maximum number of active interactive user sessions allowed per user account. It is an integer value that defaults to -1. -1 means there is no limit.

The path in which the parameter resides is /security/config/.

Example:

     <node class="integer" name="maxusersessions">
        <node-attribute name="value" value="3"/>
     </node>

p2j-entry

The p2j-entry setting is used to set the default "entry point" program for FWD clients when they connect to the server. If you have converted multiple files, you still must know which one is the main entry point for the application.The value of this setting will be the execute method of the entry point Java class.

The path in which p2j-entry parameter resides is:

/server/<server_id>/runtime/<account_or_group>/p2j_entry

Example:

<node class="string" name="p2j-entry">
   <node-attribute name="value" value="com.acme.bogus.MyApp.execute"/>
</node>

See also Specifying the Startup Program.

stop_disposition

This setting is used to define how FWD will respond when the business logic encounters STOP condition.

The stop_disposition parameter can have the following values:

   0 - retry without logging off
   1 - force logoff and then re-logon (not recommended in practice, but mimic's procedure editor)
   2 - force logoff (best practice)

The path in which stop_disposition parameter resides is:

/server/<server_id>/runtime/<account_or_group>/stop_disposition

<node class="integer" name="stop_disposition">
   <node-attribute name="value" value="2"/>
</node>

Larger Example

Full configuration example:

...
<node class="container" name="security">
  <node class="container" name="config">
...
     <node class="integer" name="maxusersessions">
        <node-attribute name="value" value="3"/>
     </node>
     <node class="integer" name="maxusers">
        <node-attribute name="value" value="5"/>
     </node>
  </node>
</node>
...
<node class="container" name="runtime">
  <node class="container" name="account_or_group_name">
    <node class="string" name="p2j-entry">
       <node-attribute name="value" value="com.acme.bogus.MyApp.execute"/>
    </node>
    <node class="string" name="helpapp">
       <node-attribute name="value" value="com.acme.bogus.MyHelp.execute"/>
    </node>
    <node class="integer" name="stop_disposition">
       <node-attribute name="value" value="2"/>
    </node>
  </node>
</node>
...

Reference

The following options can be specified for any of the /server/<server_id>/runtime/<account_or_group>:

Option ID Data Type Default Value Required Details
p2j_entry String N/a Yes This node is used to set the default "entry point" program for FWD clients when they connect to the server. If you have converted multiple files, you still must know which one is the main entry point for the application. The value of this setting will be the method execute of the entry point Java class.
helpapp String N/a No This node is used to locate and execute a preconfigured HELP application. The value of this setting will be the execute method of the main help Java class.
stop_disposition Integer 0,
1,
2		 Yes This setting is used to define how FWD will respond when the business logic encounters STOP condition.
Values:
   0 - retry without logging off
   1 - force logoff and then re-logon
   2 - force logoff

The following options can be specified for any of the /security/config/:

Option ID Data Type Default Value Required Details
maxusers Integer -1 No Maximum number of interactive users allowed to create a session. -1 means there is no limit.
maxusersessions Integer -1 No Maximum number of active interactive user sessions allowed per user account. -1 means there is no limit.

© 2004-2025 Golden Code Development Corporation. ALL RIGHTS RESERVED.