Client Checklist¶
This section documents the requirements for interactive clients AND all batch (or other dedicated programs) processes. Run through this checklist for every system on which these clients execute.
| # | Description | Reference Chapter | Complete |
|---|---|---|---|
| 1 | JDK 6 (32 bit or 64 bit) installed and operational. | Client Installation | |
| 2 | JDK 6 set as default Java installation for the system or any usage of the binary executables from the JDK must have a fully qualified path so that the correct version is found. | Client Installation | |
| 3 | All support tools used (e.g. jconsole, jstack, jmap, jstat...) are those which are included in the same JDK as used to run the application server. |
Client Installation | |
| 4 | Application binaries (charva.jar, libTerminal.so, libp2j.so and p2j.jar) are copied from the FWD production build and .so files match the “bitness” of the JVM choice. |
Client Installation | |
| 5 | If the interactive or batch client that is using secure sockets, the client configuration files (client bootstrap configuration file(s), client key store(s) and server trust store) can be found into a directory on the client system. | Bootstrap Configuration OR Keystores and Truststores |
|
| 6 | If the interactive client that uses insecure sockets, the client bootstrap configuration file(s) can be found into a directory on the client system. | Bootstrap Configuration | |
| 7 | There are the proper user accounts on the client system under which context the FWD client will run. If there are batch processes, they are started in the context of some appropriate user account. | Client Installation | |
| 8 | The FWD client user account (see item №7 above) has the permissions to: • launch a java process with the necessary amount of RAM • read all of the jar files copied from the FWD build • read access in the directory in which the bootstrap configuration file(s) are stored • create, delete and write its log files to the log file destination • establish outbound TCP socket connection to the FWD Application Server host and port |
Client Installation | |
| 9 | The firewall is configured to allow an outbound TCP socket connection (with subsequent 2-way communication) to the FWD Application Server host and port. | Client Installation | |
| 10 | The client:driver:type is set to 'charva' or 'swing_chui_frame' in bootstrap configuration file or passed as command line parameter. If only swing driver will be used, skip to step №18. |
Client Installation | |
| 11 | NCURSES v5.5 or higher is installed and patched for use with CHARVA. | Client Installation | |
| 12 | TERMINFO definitions for vt320 are fixed. | Client Installation | |
| 13 | TERMINFO definitions for vt220 are fixed. | Client Installation | |
| 14 | TERMINFO definitions for xterm are fixed. | Client Installation | |
| 15 | Terminal emulator used is officially supported or compatibility problems fixed in TERMINFO definitions or in the emulator software itself. | Client Installation | |
| 16 | Any hardware terminals have been tested for compatibility with one of the supported types: vt320, vt220 or xterm. Compatibility problems fixed in TERMINFO definitions or in the terminal hardware's configuration. | Client Installation | |
| 17 | The directory that holds libTerminal.so and libp2j.so files is set in -Djava.library.path= option OR added to the operating system specific shared library loading path. |
Running the Client | |
| 18 | The jar archives copied at №7 (full or relative path) are listed in CLASSPATH environment variable OR in -classpath java command line parameter. |
Running the Client | |
| 19 | The JVM heap size is specified on the java command line. |
Running the Client | |
| 20 | The -server option should be specified on the java command line if a Sun Hotspot JDK is used. |
Running the Client | |
| 21 | Optionally, the -XX:+HeapDumpOnOutOfMemoryError option is added to the java command line. |
Running the Client | |
| 22 | The client's proper bootstrap configuration file name is passed as the first application argument on the java command line. | Running the Client | |
| 23 | The client's bootstrap file specifies the server's hostname, port number and whether secure or insecure sockets are to be used. Alternatively, these options are set as arguments at the end of the java command lineOn systems where multiple application server instances will be started, port calculations are added to startup script. |
Running the Client | |
| 24 | Optionally, FWD_LOG_DIR environment variable is set to the directory where client log files will be located. |
Running the Client | |
| 25 | Bash shell job-control signals are properly handled. | Running the Client | |
| 26 | Any application-specific environment values required for the operation of the converted application are setup in user-specific scripts or profiles. | Client Installation OR Running the Client | |
| 27 | Application-specific configuration files required for the operation of the converted application code are installed. Necessary permissions/ownership are set into operating system. | Client Installation | |
| 28 | Application-specific program files or libraries required for the operation of the converted application code are installed. Necessary permissions/ownership are set into operating system. | Client Installation | |
| 29 | Environment variables that are read directly from the converted application code are encoded as JVM properties in the client command line | Running the Client | |
| 30 | All necessary directories upon which the converted application are created and the necessary permissions/ownership are assigned. | Client Installation | |
| 31 | Printers are installed/configured in the operating system. Queues and connectivity for all the printers are setup and the printers are turned on, attached to the system/network and ready to accept jobs. | Client Installation | |
© 2004-2017 Golden Code Development Corporation. ALL RIGHTS RESERVED.