There are
a few simple steps required to confirm that the various SAS servers
you have deployed are running properly. The following table summarizes
server validation information:
Validation Summary for the SAS Server Tier
|
|
|
Successful login using
the SAS Management Console.
|
Metadata utility (SASMeta)
workspace server
|
The metadata utility
workspace server can be used only by those members of the SAS Administrators
group who have an external account that is known to the server's host
and is associated with their SAS identity. If the server is on Windows
and uses credential-based host authentication, the account must have
the Log on as a batch job user right.
Right-click the validate
command in SAS Management Console using external account credentials
that meet the criteria described above. Default path:
Server
ManagerSASMetaLogical
Workspace Server.
|
|
If either the stored
process server or one of the workspace servers validates (see below),
then the object spawner is running.
|
|
Right-click the validate
command in SAS Management Console. Default path:
Server
ManagerSASMainLogical
OLAP Server. 1 install: CALS-TBL id="TMIG31"
|
|
Right-click the validate
command in SAS Management Console. Default path:
Server
ManagerSASMainLogical
Pooled Workspace Server. 1
|
|
Right-click the validate
command in SAS Management Console. Default path:
Server
ManagerSASMainLogical
Stored Process Server. 1
|
|
Right-click the validate
command in SAS Management Console using external account credentials.
Default path:
Server
ManagerSASMainLogical
Workspace Server. 1
|
|
Successful launch of
SAS when running the sasbatch script.
On z/OS, use the Schedule
Manager's Deploy SAS DATA Step Program to browse the appserver_autoexec_usermods.sas
file created in the AppServer context.
|
|
|
1Use the value you entered
during the deployment for the server context name. The default is
SASApp or SASMain, for single-machine installations.
|
This procedure is meant
to provide basic validation. For more complex server configurations,
please refer to the appropriate SAS documentation for the server in
question.
To validate the SAS
server tier that has been deployed using the SAS Deployment Wizard,
follow these steps:
-
Log on to the machine
hosting one or more SAS servers.
-
Start SAS Management
Console, using the following command for the appropriate operating
system:
-
Start menuPrograms SASSAS Management Console 9.3
-
Enter the following
command:
SAS-installation-directory/sasmc
/opt/sas/SASManagementConsole/9.3/sasmc
-
Use a Windows or UNIX
machine on which SAS Management Console is installed and connect to
the
z/OS machine(s) where the SAS 9.3 server tier is running.
-
Log on to the metadata
server using a set of valid credentials, such as for the SAS Administrator.
-
In SAS Management Console,
on the
Plug-ins tab, expand the
Server
Manager node.
-
Expand the SAS Application
Server node. (The default name is
SASMain.)
-
Highlight the server
you want to validate, such as the
SASMain - Logical OLAP
Server.
-
Right-click the highlighted
server, and select
Validate.
You should see the following
message:
-
Repeat steps 6 and 7
for the other SAS servers:
-
-
-
standard workspace server
-
When validating the
workspace server, if you are prompted for credentials, we suggest
that you enter the credentials for the Server Invoker (sassrv). Alternatively,
you can enter a user ID and password that meet all of these requirements:
-
The account is known to the host
of the standard workspace server.
(An ID that ends in
@saspw does not meet this requirement.)
-
The account has the Windows right
Log
on as a batch job
(if the server is on Windows).
-
The account has a corresponding
metadata identity.
-
To validate the DATA
step batch server on Windows and UNIX, SAS should successfully launch
when you run the following command, appropriate for the server host
operating system:
-
To validate the DATA
step batch server on
z/OS, use the Schedule Manager's Deploy SAS DATA
Step Program to browse appserver_autoexec_usermods.sas file created
in the AppServer context. When the JCL pane comes up and contains
JCL, then the deployment of the batch server is successful.
-
From SAS Management
Console, right-click on the Schedule Manager plug-in (
Plug-ins tab)
and choose
Deploy SAS DATA Step Program.
-
Click
Browse and
navigate to the appserver_autoexec_usermods.sas file under a server
context such as SASMain (for example,
SAS-configuration-directory/Lev
n/SASMain
).
-
You should see JCL in
the bottom list box.
-
-
Repeat these steps on
each machine in your deployment plan on which you have deployed one
or more SAS servers.