| Decision
| Description
| Status
|
| File systems
| Where to store the runtime environment, logs, and so on.
|
|
| Single install or multiple installations
| Standard installation is to install WAS once on a machine and create multiple runtime environments using profiles. Each profile has its own configuration data but shares WAS binaries. In some instances (test environments, for example), and depending on the chosen topology, we might want to install multiple instances.
|
|
| Installation method
| Choice is influenced by several factors, including the size of the installation (how many systems), the operating systems involved, how many times we anticipate performing the same installation (should we use Installation factory or perform a silent installation?), and if we are performing remote installations with unskilled personnel.
|
|
| Install updates
| To apply maintenance to WAS we need the IBM Update Installer 7.0.
|
|
| Slip install
| Custom installation packages (CIPs) are used to update and manage installed packages.
|
|
| Profile creation
| The environment is defined by creating profiles. we need to determine the types of profiles we will need and on which systems we will need to install them.
|
|
| Naming convention
| Have a consistent naming convention
|
|
| TCP/IP port assignments
| Each type of server (dmgr, node agent, app server, and so on) uses a series of TCP/IP ports. These ports must be unique on a system and must be managed properly. This is essential to avoid port conflicts if we are planning for multiple installations and profiles.
|
|
| Administrative security
| During the installation, we will have the option to enable admin security. Plan a scheme for identifying admin users, their roles, and the user registry we will use to hold this information.
|
|
| Application security
|
|
|
| Install IBM Support Assistant Agent
| Allows remote troubleshooting (such as remote system file transfer, data collections, and inventory report generation).
|
|