Special Considerations

If you are rebuilding or reconfiguring a Web application server, then make sure that all the Web application servers are stopped. For deployments that use WebLogic Server, also stop the administrative server and the nodemanager server. For deployments that use WebSphere Application Server, stop all the applications in the cell. This includes the deployment manager and the nodeagent server.

For reconfiguration tasks and adding servers, make sure that you avoid port number conflicts.

The configuration scripting tools do have the ability to perform administration like starting and stopping servers. However, the tools are not intended to replace the administration utilities provided by the Web application server vendor or the start and stop scripts provided by SAS.

If you encounter errors while configuring resources such as a JDBC data source, it is possible to use the administrative console for WebSphere Application Server or WebLogic Server to delete the resource, check the settings in your properties files, and try the configuration again.

If you encounter errors while configuring a WebSphere Application Server cell or profile, or while configuring a WebLogic Server domain, consider removing the configuration. For WebSphere Application Server, this might involve removing profiles with the manageprofiles command.

If you encounter errors while configuring JBoss, review the properties that are being used by the tool and rerun the tool. The tool can be run many times without deleting the configuration between runs, so long as JBoss is not running. If JBoss starts in between runs, there can be locks on files that prevent subsequent runs from succeeding.