Application Server Checklist¶
This section documents the requirements for installing the FWD application server.
| # | Description | Reference | Complete |
|---|---|---|---|
| 1 | JDK 6 (32 bit or 64 bit) installed and operational. | Server Installation | |
| 2 | JDK 6 set as default Java installation and Java Path set to point to the correct version. | Server Installation | |
| 3 | Support tools (e.g. jconsole, jstack, jmap, jstat...) included in the same JDK the server uses. | Server Installation | |
| 4 | Build the p2j project in case you have the p2j project in source code form | Server Installation | |
| 5 | Copy necessary files from the FWD production build to be used. These files must all be copied to the same target directory on the application server system. |
Server Installation | |
| 6 | Text collator (for H2 database sorting ) copied into the installed JDK directory. | Server Installation | |
| 7 | Converted application jar files copied into the application server system. | Server Installation | |
| 8 | Customer-specific application jar files copied into the application server system. | Server Installation | |
| 9 | The server configuration files: • fully configured directory file(s) • server bootstrap configuration file(s) • server key store(s) • server trust store are copied into the application server system. |
Bootstrap Configuration OR Keystores and Truststores |
|
| 10 | Application server system user, under which context the FWD application server will run is created. | Server Installation | |
| 11 | The FWD application server's user account has the necessary permissions | Server Installation | |
| 12 | The firewall support is set to allow the necessary inbound/outbound TCP connections. | Server Installation | |
| 13 | Ensure CLASSPATH environment variable ot java command line parameter -classpath contains the list of paths to the necessary jar files. | Running the Server | |
| 14 | JVM heap size specified on the Java command line according to server needs. | Running the Server | |
| 15 | JVM permanent generation size specified in the Java command according to server needs | Running the Server | |
| 16 | Additional options specified in the java command in case a JMX management console is used to monitor or control the JVM of the FWD application server. | Running the Server | |
| 17 | -server option specified inside the java command in case a Sun Hotspot JDK is in use. If a Sun Hotspot JDK is in use. |
Running the Server | |
| 18 | Server bootstrap configuration file passed as the first application argument inside the java command. | Running the Server | |
| 19 | Secure and insecure port numbers must be added inside the bootstrap configuration file or set as arguments in the java command line. For multiple application server instances it is useful to hide port calculations inside a script. |
Running the Server | |
© 2004-2017 Golden Code Development Corporation. ALL RIGHTS RESERVED.