Starting and Stopping Web Application Servers

On Windows systems, follow these steps to start a JBoss Application Server:

1. Make sure that the SAS Services Application (Remote Services) has been started (see Starting or Stopping the SAS Services Application).

2. Use one of the following scripts:

   • On Windows:

     JBoss-home-directory\bin\SASServer1.bat

   • On UNIX:

     JBoss-home-directory/bin/SASServer1.sh

   You can use any of the following arguments with these scripts:

   Note:   The hyphen in front of each argument is optional.  

   -install

   installs the server as a Windows service.

   -remove

   removes the service from Windows.

   -start

   starts the server.

   -stop

   stops the server.

If you selected the option to install the JBoss Application Server as a service, see Running Servers as Windows Services.

If you are using an IBM WebSphere Application Server Network Deployment, follow these steps to start the server:

1. Make sure that the SAS Services Application (Remote Services) has been started.

2. If the WebSphere deployment manager is not already running, start it by using one of the following methods:

   • If the deployment manager is installed as a Windows service, start the appropriate service.

   • Use one of the following commands, where WAS_INSTALL_ROOT is the home directory of the deployment manager:

     • On Windows:

       WAS_INSTALL_ROOT\bin\startManager.bat -profileName "SASDmgr01"

     • On UNIX:

       WAS_INSTALL_ROOT/bin/startManager.sh -profileName "SASDmgr01"

     SASDmgr01 is the default profile name for the deployment manager. The name in your installation might be different.

3. If the WebSphere node agent is not already running, start it by using one of the following methods:

   • If the node agent is installed as a Windows service, start the appropriate service.

   • Use the WebSphere administrative console to start the node agent.

   • Use one of the following commands, where WAS_INSTALL_ROOT is the home directory of the application node:

     • On Windows:

       WAS_INSTALL_ROOT\bin\startNode.bat -profileName "SAShost-name01"

     • On UNIX:

       WAS_INSTALL_ROOT/bin/startNode.sh -profileName "SAShost-name01"

     SAShost-name01 is the default profile name for the managed node, which contains the node agent and the application server that is used to run SAS. If multiple servers are installed, then the default names for the additional profiles are SAShost-name02, SAShost-name03, and so on.

4. Start the WebSphere Application Server by using one of the following methods:

   • Use the WebSphere administrative console to start the application server. The default server name on Windows and UNIX is SASServer1. If additional servers are installed, the default server names are SASServer2, SASServer3, and so on.

   • Use one of the following commands, where WAS_INSTALL_ROOT is the home directory of the application node:

     • On Windows:

       WAS_INSTALL_ROOT\bin\startServer.bat "server-name" -profileName "SAShost-name01"

     • On UNIX:

       WAS_INSTALL_ROOT/bin/startServer.sh "server-name" -profileName "SAShost-name01"

     The default server name on Windows and UNIX is SASServer1. If additional servers are installed, the default server names are SASServer2, SASServer3, and so on.

     SAShost-name01 is the default profile name on Windows and UNIX. If multiple servers are installed, then the default names for the additional profiles are SAShost-name02, SAShost-name03, and so on.

To stop the server, use the WebSphere administrative console or the appropriate script (stopServer.bat or stopServer.sh). The scripts are located in the same directory as the startup script.

Note:   When you use the SAS Deployment Wizard to deploy or migrate a SAS system that uses WebSphere, you must first stop all WebSphere servers including deployment management servers, node agent servers, and application servers. For instructions, see the IBM documentation for WebSphere Application Server.  

By default, the SAS Deployment Wizard configures the WebLogic domain in the following path: SAS-configuration-directory/Lev1/Web/SASDomain. Your domain might have been configured in a different location.

If you are using an Oracle WebLogic Server on a Windows system, follow these steps to start the server:

1. Make sure that the SAS Services Application (Remote Services) has been started.

2. If the WebLogic Administration Server is not running, start it by using the following command:

   domain-home-directory\startWebLogic.cmd

3. Start the WebLogic Managed Server by using startManagedWebLogic.cmd, which is located in domain-home-directory\bin\. The syntax is as follows:

   startManagedWebLogic.cmd server-name administration-server-URL

   For example:

   startManagedWebLogic.cmd SASServer1 http://mycompany.com:7501

If you are using a WebLogic Server on a UNIX system, follow these steps to start the server:

1. Make sure that the SAS Services Application (Remote Services) has been started.

2. If the WebLogic Administration Server is not running, start it by using the following command:

   domain-home-directory/startWebLogic.sh

3. Start the WebLogic Managed Server by using startManagedWebLogic.sh, which is located in domain-home-directory/bin/. The syntax is as follows:

   startManagedWebLogic.sh server-name administration-server-URL

   For example:

   startManagedWebLogic.sh SASServer1 http://mycompany.com:7501

You can also use other methods, including the administrative console or the WebLogic Scripting Tool (WLST), to start these servers. For details, see the WebLogic documentation at http://edocs.beasys.com.

To stop the server, use stopManagedWebLogic.cmd (on Windows); or stopManagedWebLogic.sh (on UNIX). These scripts are located in the same directories as the startup scripts.

Copyright © 2009 by SAS Institute Inc., Cary, NC, USA. All rights reserved.