Implementation considerations

---

Review the following items before you begin your installation:

• WebSphere Application Server customization generates RACF® commands.

  These commands must be translated to another security product, like ACF2 or TopSecret, if RACF is not used.

  If ACF2 is used, then apply PTF QO29304 to correct an abend in the WebSphere Application Server bootstrap process.

• DB2 requires both JDBC drivers and Net.Data.

• Net.Data requires CGI.

  Important:  

  Do not use FCGI, because it will not work.

• The WebSphere Application Server load library is a PDSE and requires a minimum of 1000 cylinders of spaces for allocation.

• Workload Manager (WLM) must be in goal mode.

  WebSphere Application Server uses WLM to start spawned address spaces.

• The WebSphere Application Server V4 load library needs to be installed in LPA:

  • It requires approximately 200 MB of ECSA.

• Consider adding an additional page dataset for the installation and initial use.

• There are a number of dependencies on other products in order to complete critical path tasks:

  • DB2

  • TCP/IP

  • WLM

  • Security

  Coordination between systems implementation groups is extremely important.

• Ensure that the JAVA runtime is at the most current level supported by WebSphere Application Server V4.

• Because WSAA requires HTTP Server to be configured with the WebSphere Application Server V4 plug-in, make sure you have PTF UQ79426.

• Verify that the installation user has access to the HTTP server from a Web page.

• Ensure that you have applied the most current PTF levels for WebSphere Application Server V4 and SMP/E.

• WebSphere Application Server and WSAA installation jobs will create large volumes of SYSPRINT output.

Consider using MVS data sets for output in order to conserve JES spool space.

---