The WebSphere Deployment Manager, the node agent, and any other WebSphere servers that are managed in the same cell should be stopped prior to running the SAS Deployment Wizard. While numerous ports are used when you run SAS Web applications on the WebSphere Application Server, the SAS Deployment Wizard prompts for some, but not all, of the ports. Typically it prompts for the HTTP, HTTPS, RMI, and SOAP ports. The wizard uses defaults values for those ports for which it does not prompt.

If the WebSphere Deployment Manager is already running, the automatic configuration in the SAS Deployment Wizard might fail with the following error:

**ERROR** Update of JVM Options for server "SASServer1" failed during createServerOnWAS. Check WebSphere logs
at "/opt/IBM/WebSphere/AppServer/profiles/SASDmgr01/logs/dmgr" for analysis.   

WebSphere's startServer.log file might contain messages similar to the following:

ADMU3028I: Conflict detected on port 8879.  Likely causes: a) An instance of the server dmgr is already running  b) some other process is using port 8879  
ADMU3027E: An instance of the server may already be running: dmgr            
ADMU3002E: Exception attempting to process server dmgr                      
ADMU3007E: Exception   
com.ibm.websphere.management.exception.AdminException: ADMU3027E: An instance of the server may already be running: dmgr

If you encounter a configuration failure while automatically configuring SAS Web applications in WebSphere, make sure that no other processes are running the deployment manager, the node agent, or another WebSphere server before you rerun the SAS Deployment Wizard.

Operating System and Release Information