Installation Note 52100: Service dependencies are not set up by the SAS® Deployment Wizard for the SAS® Web Application Server
Applications that run inside SAS Web Application Server instances have dependencies on other SAS services. However, the automated configuration with the SAS Deployment Wizard does not create service dependencies for these SAS services in Microsoft Windows operating environments. When a machine is restarted, not having these dependencies defined can lead to application initialization issues if the prerequisite servers are not started before the SAS Web Application Server instances.
If you want to add dependencies, you can do that after you complete a SAS configuration. However, adding dependencies is not recommended generally as a best practice. When you define a Windows service dependency on a prerequisite server, you cannot restart that server without first stopping each dependent SAS Web Application Server instance and then restarting it. It takes a significantly longer period of time to restart SAS Web Application Server instances than it does for SAS® Metadata Server or the Web Infrastructure Platform Data Server. Therefore, you need to be aware that if you anticipate the need to restart these services occasionally, you will have more overall downtime if you have defined dependencies.
If you do want to define these dependencies, follow the steps below for each SAS Web Application Server instance:
- Locate and edit the wrapper.conf file that resides in the
SAS-configuration-directory\LevN\Web\WebAppServer\server-nameN_N\conf\.
Notes:
- LevN specifies your configuration level (for example, Lev1, Lev2, and so on),
- server-nameN_N specifies the name of the server instance (for example, SASServer1_1)
- Locate the following lines in this file:
# Service dependencies. Add dependencies as needed starting from 1
wrapper.ntservice.dependency.1=
- Replace the lines above with these lines:
wrapper.ntservice.dependency.1=SAS [Config-Lev1] Cache Locator on port 41415
wrapper.ntservice.dependency.2=SAS[Config-Lev1]httpd-WebServer
wrapper.ntservice.dependency.3=SAS [Config-Lev1] JMS Broker on port 61616
wrapper.ntservice.dependency.4=SAS [Config-Lev1] Web Infrastructure Platform Data Server
wrapper.ntservice.dependency.5=SAS [Config-Lev1] SASMeta - Metadata Server
Note: Your service names might be different than those shown above. In particular, the information in the square brackets should reflect the configuration-directory name and level that you have chosen for your configuration. Be sure to use the Microsoft Windows Services tool to verify the correct names of your services.
- Save the file.
- At a Windows command prompt enter these commands to shut down your server (if it is not already down):.
cd SAS-configuration-directory\LevNX\Web\WebAppServer\server-nameN_N\bin
tcruntime-ctl.bat reinstall
tcruntime-ctl.bat start
Operating System and Release Information
SAS System | SAS Enterprise BI Server | z/OS | 9.4 | | 9.4 TS1M0 | |
Microsoft® Windows® for x64 | 9.4 | | 9.4 TS1M0 | |
Microsoft Windows 8 Enterprise x64 | 9.4 | | 9.4 TS1M0 | |
Microsoft Windows 8 Pro x64 | 9.4 | | 9.4 TS1M0 | |
Microsoft Windows 8.1 Enterprise 32-bit | 9.4 | | 9.4 TS1M0 | |
Microsoft Windows 8.1 Enterprise x64 | 9.4 | | 9.4 TS1M0 | |
Microsoft Windows 8.1 Pro | 9.4 | | 9.4 TS1M0 | |
Microsoft Windows 8.1 Pro 32-bit | 9.4 | | 9.4 TS1M0 | |
Microsoft Windows Server 2008 R2 | 9.4 | | 9.4 TS1M0 | |
Microsoft Windows Server 2008 for x64 | 9.4 | | 9.4 TS1M0 | |
Microsoft Windows Server 2012 Datacenter | 9.4 | | 9.4 TS1M0 | |
Microsoft Windows Server 2012 R2 Datacenter | 9.4 | | 9.4 TS1M0 | |
Microsoft Windows Server 2012 R2 Std | 9.4 | | 9.4 TS1M0 | |
Microsoft Windows Server 2012 Std | 9.4 | | 9.4 TS1M0 | |
Windows 7 Enterprise x64 | 9.4 | | 9.4 TS1M0 | |
Windows 7 Professional x64 | 9.4 | | 9.4 TS1M0 | |
64-bit Enabled AIX | 9.4 | | 9.4 TS1M0 | |
64-bit Enabled Solaris | 9.4 | | 9.4 TS1M0 | |
HP-UX IPF | 9.4 | | 9.4 TS1M0 | |
Linux for x64 | 9.4 | | 9.4 TS1M0 | |
Solaris for x64 | 9.4 | | 9.4 TS1M0 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Installation Note |
Priority: | medium |
Date Modified: | 2014-02-12 08:45:37 |
Date Created: | 2014-01-16 09:19:25 |