FWD

Session Management¶

• Session Management
  • Search Algorithm
  • Configuration parameters
    • p2j-entry
    • helpapp
    • stop_disposition
  • Reference

External applications access the FWD server through the remote object protocol. Before that can be used, the external application must establish a session with the FWD server. This involves writing custom Java code to connect to the FWD server and then authenticate using a known account.

Inside the directory there are several parameters that are used to set up a session. Once complete, the session can be used to obtain access to the exported APIs of the FWD server.

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>

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

Configuration parameters¶

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>

helpapp¶

This setting 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.

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>

stop_disposition¶

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

The disposition parameter can have the following values:

   0 - retry without logging off
   1 - force logoff and then re-logon (not recommended in practice)
   2 - force logoff

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="1"/>
</node>

Full configuration example:

...
<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="1"/>
    </node>
  </node>
</node>
...

Inside the directory, session initialization and termination hooks configurations can be found, for more info about Session initialization and termination hooks please see the “Hooks” section of the directory chapter.

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

---

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