| Planning item
| Comments
|
| Create a strategy for admin security. Identify the possible administrators and their roles. Determine the type of user registry that we will use for WebSphere security. If we do not want to use a federated repository, delay enabling admin security until after installation.
|
|
| Review the administration facilities available (scripting, Integrated Solutions Console, and so on) and create an overall strategy for configuration and management of WebSphere resources.
|
|
| Determine where the profile directories (including the configuration repositories) will be located.
|
|
| Define a strategy for automation.
|
|
| Consider whether to use automatic or manual synchronization to nodes.
|
|
| Plan for appserver startup
|
|
| Create app server templates for existing servers if we plan to create multiple servers with the same customized characteristics.
|
|
| Create a strategy for scoping resources.
|
|
| Create a strategy for change management. This includes maintaining and updating apps. It also includes strategies for changes in cell topology and updates to WAS binaries.
|
|
| Create a strategy for problem management. Identify a location and naming convention for storing WAS logs. Set the processes to use those locations.
|
|
| Create a strategy for backup and recovery of the installation and configuration files.
|
|