Starting and Stopping Web Application Servers

Starting or Stopping a JBoss Application Server

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

Make sure that the SAS Services Application (Remote Services) has been started. See Starting or Stopping the SAS Services Application (Remote Services).
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.

Starting or Stopping an IBM WebSphere Application Server or an IBM WebSphere Application Server Network Deployment (ND)

Starting or Stopping an IBM WebSphere Application Server or an IBM WebSphere Application Server Network Deployment (ND) on Windows or UNIX

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

Make sure that the SAS Services Application (Remote Services) has been started.
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.
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 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. The profile name for the managed node in your installation might be different.
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 start-up 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 application servers. For instructions, see the IBM documentation for WebSphere Application Server.

Starting or Stopping an IBM WebSphere Application Server Network Deployment (ND) on z/OS

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

Make sure that the SAS Services Application (Remote Services) has been started.
If the WebSphere deployment manager is not already running, start it by using one of the following methods:
- Run the following script, where WAS_INSTALL_ROOT is the home directory of the deployment manager:
  
  WAS_INSTALL_ROOT/bin/startManager.sh
- Issue the MVS START command to start the deployment manager. Specify the appropriate deployment manager procedure and related parameters.
If the WebSphere node agent is not already started, start it by using one of the following methods:
- Run the following script, where WAS_INSTALL_ROOT is the home directory of the application node:
  
  WAS_INSTALL_ROOT/bin/startNode.sh
- Issue the MVS START command to start the node agent. Specify the appropriate node agent procedure and related parameters.
Start the WebSphere Application Server by using one of the following methods:
- Use the WebSphere administrative console to start each application server.
- Run the following script for each application server, where WAS_INSTALL_ROOT is the home directory of the application node:
  
  WAS_INSTALL_ROOT/bin/startServer.sh "server-name"
- Issue the MVS START command for each server. Specify the appropriate application server procedure and related parameters.

To stop the application server, use one of the following methods:

Use the WebSphere administrative console to stop the application server.
Run the following script for the application server, where WAS_INSTALL_ROOT is the home directory of the application node:

WAS_INSTALL_ROOT/bin/stopServer.sh "server-name"
Issue the MVS STOP command against the application server control region.

Starting or Stopping an Oracle WebLogic 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:

Make sure that the SAS Services Application (Remote Services) has been started.
If the WebLogic Administration Server is not running, start it by using the following command:

domain-home-directory\startWebLogic.cmd
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

Note: SAS includes scripts that you can use to install the WebLogic Managed Server and WebLogic Administration Server as Windows services. If you used these scripts to install the services, see Running Servers as Windows Services.

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

Make sure that the SAS Services Application (Remote Services) has been started.
If the WebLogic Administration Server is not running, start it by using the following command:

domain-home-directory/startWebLogic.sh
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 start-up scripts.