Sas Intelligence Platform User Manual

Download

SAS® 9.2 Intelligence Platform

System Administration Guide Second Edition

The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2010.

SAS

9.2 Intelligence Platform: System Administration Guide, Second Edition. Cary, NC:

SAS Institute Inc.

SAS

9.2 Intelligence Platform: System Administration Guide, Second Edition

retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, or otherwise, without the prior written permission of the publisher, SAS Institute Inc.

For a Web download or e-book: Your use of this publication shall be governed by the terms established by the vendor at the time you acquire this publication.

U.S. Government Restricted Rights Notice. Use, duplication, or disclosure of this software and related documentation by the U.S. government is subject to the Agreement with SAS Institute and the restrictions set forth in FAR 52.227–19 Commercial Computer Software-Restricted Rights (June 1987).

SAS Institute Inc., SAS Campus Drive, Cary, North Carolina 27513. 1st electronic book, November 2010 SAS Publishing provides a complete selection of books and electronic products to help

customers use SAS software to its fullest potential. For more information about our e-books, e-learning products, CDs, and hard-copy books, visit the SAS Publishing Web site at support.sas.com/publishing or call 1-800-727-3228.

and all other SAS Institute Inc. product or service names are registered trademarks

SAS or trademarks of SAS Institute Inc. in the USA and other countries.

indicates USA

registration. Other brand and product names are registered trademarks or trademarks of their

respective companies.

What’s New ix

Overview ix New Logging Facility for SAS Servers New Server Management and Monitoring Features New SAS Server Components Enhancements and Changes Pertaining to Metadata Server Administration Enhancements and Changes Pertaining to Metadata Administration New Conﬁguration Management Tool New Documentation for Administrators

PART1 Getting Started 1

xii

xiii

Chapter 1

Introduction to the SAS Intelligence Platform: System Administration

Guide 3

About the SAS Intelligence Platform: System Administration Guide Prerequisites for Using the SAS Intelligence Platform: System Administration

Guide

Accessibility Features in the SAS Intelligence Platform Products

Chapter 2

Overview of the State of Your System Overview of SAS Management Console

Understanding the State of Your System 5

Overview of SAS Deployment Manager and SAS Web Administration Console Overview of the SAS Metadata Server and Its Initial Conﬁguration Overview of SAS Application Server Components and Their Initial Conﬁguration Overview of Other SAS Servers and Spawners Overview of Ports

Overview of the Conﬁguration Directory Structure Overview of Conﬁguration Files

Overview of Initial Roles, Groups, and Users

Chapter 3

Who Can Do What: Credential Requirements for SAS Management Console

Tasks 33

About Security for System Administration Tasks Who Can Do What in the Metadata Manager Plug-in Who Can Do What in the Server Manager Plug-in About Adding Users to the SAS Administrators Group Requirements for Accessing a Standard Workspace Server 37 Clearing the Credentials Cache 37

Chapter 4

What to Do Next: Administration Tasks 39

Overview of Administration Tasks 39 First-Priority Setup Tasks 40

Standard Setup Tasks 43 Optional Setup Tasks Ongoing System Administration Tasks Best Practices for Ensuring the Integrity of Your System

PART2 Starting, Stopping, and Checking the Status of Servers 49

PART

Chapter 5

Overview of Server Operation Running Servers as Windows Services Starting and Stopping SAS Servers on z/OS

Operating Your Servers 51

Using the sas.servers Script on UNIX or z/OS to Start or Stop All Servers Running Servers as UNIX Daemons Using Scripts to Operate SAS Servers Individually Using SAS Management Console to Operate SAS Servers Starting and Stopping Web Application Servers

Chapter 6

Checking the Status of Servers 75

About Checking the Status of Servers Use a Server Script to Display the Status of a Server or Spawner Checking the Access State of the SAS Metadata Server

Checking the Access State of Metadata Repositories and the Repository Manager Check the Status of the Object Spawner

Validate the SAS Metadata Server, SAS Workspace Servers, SAS Pooled Workspace Servers, SAS Stored Process Servers, and SAS OLAP Servers

Validate the SAS Content Server

System Monitoring and Logging 85

Chapter 7

About SAS Server Monitoring Using SAS Management Console to Monitor SAS Servers Using the Server Performance Counters and Information Fields Using the SAS OLAP Server Monitor Using Third-Party Products to Monitor SAS Servers

Chapter 8

About Server Logging About Metadata Server Loggers

Monitoring the Activity of SAS Servers 87

100

Administering Logging for SAS Servers 103

103

104

101

Enabling Server Logging 106 Initial Logging Conﬁguration for SAS Servers

107

Modifying Your Server Logging Conﬁgurations 110 Enable More Detailed Logging for Server Troubleshooting 111 Create a Log File for Workspace Server Troubleshooting 112 Enable More Detailed Logging for SAS Object Spawner Troubleshooting 113 Collecting ARM Log Information for SAS Data Integration Studio Jobs 113

Collecting ARM Log Information in SAS OLAP Servers 115 Audit Server Logging Level Changes That Originate in Client Applications Capture Metadata Server Management Events in the System Facility Appender Capture XML Information in the SAS Metadata Server Log

PART4 Backing Up and Restoring Your System 121

116

117

Chapter 9

About Backups and Restores About the Metadata Server Backup and Restore Utilities Using Operating System Commands to Back Up the Metadata Server About Using the Export SAS Package Wizard to Back Up Speciﬁc SAS Folders Best Practices for Backing Up Your SAS System Best Practices for Restoring Your System

Chapter 10

About the Backup Wizard Summary of Procedures for Using the Backup Wizard Ensure Appropriate User Credentials Use the Backup Wizard to Deﬁne a Backup Job and a Corresponding Restore Job Manage Backup and Restore Jobs That Were Created by the Wizard Run a Backup or a Restore Job That Was Created by the Wizard Troubleshooting the Backup Wizard Use Schedule Manager to Schedule a Backup Job That Was Created by the Backup

Wizard

Chapter 11

About %OMABAKUP What %OMABAKUP Does Ensuring Appropriate User Credentials Running the backupServer.sas and restoreServer.sas Programs Error Logging 151 Writing Custom Programs Using %OMABAKUP Warning Messages %OMABAKUP Macro: Reference 156

Best Practices for Backing Up and Restoring Your System 123

123

124

126

127

134

Using the Backup Wizard in SAS Management Console 137

137

138

139

142

143

144

145

Using the %OMABAKUP Macro to Perform Backups and Restores 147

147

148

149

150

151

155

126

140

PART

Chapter 12

Manually Restoring an Unresponsive SAS Metadata Server

Manually Restoring an Unresponsive SAS Metadata Server 161

161

5 Optimizing the Performance of the SAS Metadata Server 165

Chapter 13 Performance 167

Overview of Performance-Related Conﬁguration Settings 167 Conﬁguring the Number of Threads Used by the Metadata Server 167 Conﬁguring Metadata Server Journaling 170

Using Conﬁguration Settings to Optimize Metadata Server

Chapter 14

Managing Metadata Server Performance 173

Setting the Server’s MEMSIZE Parameter 173 Input/Output Balancing Conﬁguring Concurrent Queries/Clients Note to Users of 32–bit Windows Systems

173

174

Using %OMARUNAN (or the RUNANALYSIS Option of %OMABAKUP) to Optimize Memory Usage

%OMARUNAN Autocall Macro: Reference Recovering Memory on the SAS Metadata Server

175

177

PART6 Managing SAS Metadata Repositories 179

Chapter 15

Creating, Registering, Moving, Copying, Renaming, and Deleting SAS

Metadata Repositories 181

About SAS Metadata Repositories About SAS Metadata Repository Access Modes Create a Custom Repository Change the Properties of a Metadata Repository Copying, Promoting, Importing, and Exporting Your Metadata Moving a Metadata Repository to a New Location on the Same Metadata Server Porting a Metadata Repository to a Different Host Environment Registering a Metadata Repository Unregistering a Metadata Repository Deleting a Metadata Repository

181

182

183

184

191

192

193

185

188

189

PART

7 Managing Metadata Content 195

Chapter 16

Working with SAS Folders 197

About the SAS Folder Structure Best Practices for Managing SAS Folders Best Practices for Maintaining Associations Among Objects in SAS Folders Using the BI Lineage Plug-in Customizing Your Folder Structure

Chapter 17

Using the Promotion Tools 213

Overview of Promotion Tools Special Considerations for Promoting Metadata Special Considerations for Promoting Metadata From SAS 9.1.3 to SAS 9.2 Preparing to Use the Promotion Tools How to Access the Promotion Tools Using the Export SAS Package and Import SAS Package Wizards: Example Usage

Scenario

229

Using the Batch Export and Import Tools 238 Troubleshooting the Promotion Tools 253

PART8 Appendixes 257

197

201

202

203

208

214

221

223

226

229

vii

Appendix 1

Overview 259 Default Port Numbers for SAS Servers and Spawners Default Port Numbers for Third-Party Software Port Numbering in a Multiple-Level Environment

Appendix 2

Introduction to the Conﬁguration Directory Reference Contents of the Levn Subdirectory Contents of the Metadata Server Subdirectory (SASMeta) Contents of the Application Server Subdirectory (SASApp or SASMain) Contents of the Web Subdirectory

Appendix 3

Default Locations for Server Logs

Appendix 4

Reference: Conﬁguration Files for SAS Servers Reference Information for omaconﬁg.xml

Appendix 5

Modifying the Metadata Server Invocation Options Recommended Parameters 289 Optional Parameters 292

Default SAS Ports 259

259

260

261

Reference: Conﬁguration Directories 263

263

265

267

Default Locations for Server Logs 269

269

Conﬁguration Files 271

271

280

Options for the Metadata Server Invocation Command 289

289

266

Appendix 6

Using the SAS Deployment Manager to Update Host Name

References 295

Overview of Updating Host Name References Process for Updating Host Name References Troubleshooting the Update Host Name References Tool Example Scenarios for Updating Host Name References

Appendix 7

What’s New

Overview

The SAS Intelligence Platform includes new and enhanced system administration tools, new features for server logging and management, new server components, changes to metadata repositories, and new documentation for administrators. The enhancements and changes include the following:

a new logging facility for SAS servers

new server management and monitoring features

new SAS server components

enhancements and changes pertaining to metadata server administration

enhancements and changes pertaining to metadata administration

a new conﬁguration management tool

new documentation for administrators

New Logging Facility for SAS Servers

A new standard logging facility is provided for SAS servers. The facility supports problem diagnosis and resolution, performance and capacity management, and auditing and regulatory compliance. The logging facility provides the following capabilities for servers:

Log events can be directed to multiple destinations, including ﬁles, operating system facilities, and client applications.

For each log destination, you can conﬁgure the message layout, including the contents, the format, the order of information, and literal text.

For each log destination, you can conﬁgure a ﬁlter to include or exclude events based on levels and message contents.

For the metadata server, security-related events are captured, including authentication events, client connections, changes to user and group information, and permission changes.

You can generate performance-related log events in a format that can be processed by an Application Response Measurement (ARM) 4.0 server.

x What’s New

You can adjust logging levels dynamically by using the Server Management

features of SAS Management Console.

You can use SAS Management Console and third—party monitoring tools to view

the contents of logs.

New Server Management and Monitoring Features

The following new features are provided to help you manage and monitor your SAS

server components, including the SAS Metadata Server, SAS OLAP Server, SAS Stored Process Server, SAS Workspace Server, SAS Pooled Workspace Server, SAS object spawner, and SAS Table Server:

You can use the new Server Manager features of SAS Management Console to

perform the following tasks:

quiesce, stop, pause, resume, and validate servers

test connections to servers

view information about current connections and processes

view performance counters that provide statistics about activity that has occurred since a server was last started

view server logs

change logging levels dynamically

refresh servers, so that metadata changes take effect without the need to restart

Server monitoring can also be performed using third-party enterprise systems

management products.

On UNIX and z/OS systems, you can use the new sas.servers script to start, stop,

or restart all of your SAS servers in the correct order with a single command. You

can also use the script to display the status of servers and to create a UNIX boot

script that is tailored to your platform.

New SAS Server Components

The initial conﬁguration of your system includes these new server components:

a server context for the metadata server called SASMeta. In multiple-machine

installations, this server context includes a workspace server and other servers

that are needed to run metadata utilities such as the Backup and Restore Wizard.

a SAS Pooled Workspace Server, which is conﬁgured to use

this new conﬁguration,the SAS object spawner maintains a collection of workspace

server processes that are available for clients. This server conﬁguration is

intended for use by query and reporting tools such as SAS Information Map

Studio, SAS Web Report Studio, and the SAS Information Delivery Portal.

a SAS Deployment Tester Server, which processes validation tasks that are

requested either by the SAS Deployment Tester plug-in or by a SAS Deployment

Tester batch client.

Depending on which SAS offerings you have installed, your conﬁguration might also

include the following new server components:

a SAS Content Server, which is included with some offerings. This server stores

digital content (such as documents, reports, and images) that is created and used

by SAS Web applications. For example, the SAS Content Server stores report

server-side pooling.In

What’s New xi

deﬁnitions that are created by users of SAS Web Report Studio, as well as images and other elements that are used in reports. In addition, the SAS Content Server stores documents and other ﬁles that are to be displayed in the SAS Information Delivery Portal or in SAS solutions.

To interact with the SAS Content Server, client applications use WebDAV-based protocols for access, versioning, collaboration, security, and searching. Administrative users can use the browser-based SAS Web Management Console to create, delete, and manage permissions for folders on the SAS Content Server.

a SAS Table Server, which is used by the SAS Shared Services component of the middle tier.

a DataFlux Integration Server, which executes DataFlux jobs and real-time services that cleanse data or analyze data quality. The jobs and services are created using DataFlux applications (dfPower Architect and dfPower Proﬁle) and are executed on the server through job ﬂows that are created in SAS Data Integration Studio.

a SAS In-Process Server, which provides the ability to schedule jobs from certain Web-based SAS applications without using a separate scheduling server. The scheduling functions run as a process within the application.

Enhancements and Changes Pertaining to Metadata Server Administration

The following enhancements and changes pertain to administration of the SAS

Metadata Server:

Users can be assigned to administrator roles that enable them to have unrestricted access to metadata, act as metadata server operators, or perform user administration tasks.

The metadata server can be paused to an Administration state, enabling unrestricted users (but not other users) to continue to perform tasks that require access to the server.

The Backup and Restore Wizard in SAS Management Console enables you to create backup and restore jobs and execute them or deploy them for scheduling. In addition, SAS now provides customized backup and restore programs that you can launch from the command line. Metadata server conﬁguration ﬁles are included in backups.

Metadata server journaling is turned on by default.

New options for internal user authentication have been added to the metadata server conﬁguration ﬁle omaconﬁg.xml.

Enhancements and Changes Pertaining to Metadata Administration

The following enhancements pertain to the administration of metadata and metadata

repositories:

Content is stored in a hierarchy of SAS folders that are visible in the

Folders tab

of SAS Management Console and in other client applications, as applicable. The folders segregate system information from business information, provide personal folders for individual users, and provide an area for shared data.

BI Manager import and export wizards have been replaced with the Export SAS Package and Import SAS Package wizards. The wizards have been expanded to handle a larger number of object types. In addition, new batch tools enable you to

xii What’s New

export and import folders, objects, or groups of folders and objects from an operating system command line or from a batch script.

In the second maintenance release for SAS 9.2, the ExportCubes and ImportCubes batch tools are new. These tools provide a simpliﬁed method of promoting OLAP cubes from SAS 9.1.3 to SAS 9.2.

Custom repositories are supported by all applications.

It is not necessary to deﬁne dependencies between repositories. If a repository dependency was deﬁned in SAS 9.1.3, then the dependency relationship is eliminated during the SAS 9.1.3 to SAS 9.2 migration process. However, the existing associations between metadata objects still remain in effect.

The November 2010 release includes these features:

The new BI Lineage plug-in for SAS Management Console identiﬁes

connections between BI objects in the SAS Folders tree. The lineage

information is stored in a repository called the BILineage repository. For

details, see “Using the BI Lineage Plug-in” on page 203.

The Export SAS Package and Import SAS Package wizards can be used to

promote dashboard objects (including dashboards, indicators, indicator data,

ranges, indicator conﬁgurations, and dashboard components). For important

details, see “Promoting SAS BI Dashboard 4.3 Content” in the

SAS

Intelligence Platform: Web Application Administration Guide.

The new content promotion tool for the SAS Information Delivery Portal 4.3

can be used to promote portal pages, page templates, portlet instances, and

the portal’s application and user permissions trees. See “Promoting Portal

Content” in the SAS Intelligence Platform: Web Application Administration

Guide.

The following features have been removed:

The Replication Wizard in SAS Management Console has been deprecated.

This wizard includes the functions of the Replication Wizard and the

Promotion Wizard that were available in SAS 9.1.3. The documentation for

this feature was removed effective with the November 2010 edition of the

SAS Intelligence Platform: System Administration Guide. For more

information, see SAS Note 40834 or contact SAS Technical Support.

The use of third-party database management systems to store the repository

manager and metadata repositories is no longer supported.

The repository auditing feature provided in previous releases has been

removed.

New Conﬁguration Management Tool

The new SAS Software Deployment Manager enables you to remove conﬁguration information (including metadata deﬁnitions, conﬁguration ﬁles, and Windows services) for one or more components of your installation. You can use this feature to remove a component that you will no longer be using, or to move a component from one machine to another. You can also use the SAS Software Deployment Manager to rebuild SAS Web applications and to update a service account password that is included only in metadata.

In the October 2009 release, the SAS Deployment Manager includes a new option to renew software licenses for some SAS solutions that depend on a SAS middle tier.

In the third maintenance release for SAS 9.2, the SAS Deployment Manager includes a new option to change the host names (including the network domains to which they belong) of server machines in your deployment.

New Documentation for Administrators

SAS 9.2 includes these changes to system administration documentation:

All information about scheduling has been moved to Scheduling in SAS.

Detailed information about conﬁguring logging for SAS servers is now available in the SAS Logging: Conﬁguration and Programming Reference.

What’s New xiii

xiv What’s New

PART

Getting Started

Chapter 1..........

Chapter 2..........

Chapter 3..........

Chapter 4..........

Introduction to the SAS Intelligence Platform: System Administration Guide

Understanding the State of Your System

Who Can Do What: Credential Requirements for SAS Management Console Tasks

What to Do Next: Administration Tasks 39

CHAPTER

Introduction to the SAS Intelligence Platform: System Administration Guide

About the SAS Intelligence Platform: System Administration Guide

Prerequisites for Using the SAS Intelligence Platform: System Administration Guide

Accessibility Features in the SAS Intelligence Platform Products

About the SAS Intelligence Platform: System Administration Guide

The SAS Intelligence Platform is a comprehensive, end-to-end infrastructure for creating, managing, and distributing enterprise intelligence. The SAS Intelligence Platform comprises four software offerings:

SAS BI Server

SAS Enterprise BI Server

SAS Data Integration Server

SAS Enterprise Data Integration Server

Solutions for enterprise intelligence, customer intelligence, and ﬁnancial intelligence are built on the SAS Intelligence Platform, as well as turnkey solutions for specialized markets in life sciences, health care, retail, manufacturing, and others. Therefore, if your SAS deployment plan includes a SAS solution, then the SAS Intelligence Platform documentation also pertains to you.

This guide covers administrative tasks that you will need to perform on an ongoing basis after the initial installation and conﬁguration of the SAS Intelligence Platform. The guide covers tasks that apply to the SAS Intelligence Platform as a whole, including the following:

starting and stopping servers

checking the status of servers

monitoring server activity

administering server logging

administering the SAS Metadata Server, including the following tasks:

performing backups and restores

monitoring the server

optimizing the server’s performance

administering SAS Metadata Repositories and metadata content, including the following tasks:

creating repositories

working with SAS Folders

importing, exporting, and copying metadata

4 Prerequisites for Using the SAS Intelligence Platform: System Administration Guide

promoting metadata and related content

modifying your conﬁguration

The appendixes of this guide provide reference information about log ﬁles,

conﬁguration ﬁles, and default ports.

This guide is one of several documents that SAS publishes to support administration

of the SAS Intelligence Platform. Additional guides are available to cover the following administration topics:

SAS Application Server administration

data administration

security administration

Web application administration

desktop application administration

scheduling

logging

Chapter 1

To access these documents, go to

http://support.sas.com/92administration.

Additional information for speciﬁc operating systems is available in the SAS

companion guides.

Prerequisites for Using the SAS Intelligence Platform: System Administration Guide

Before using this guide, you should be familiar with the concepts and terminology

that are introduced in the SAS Intelligence Platform: Overview.

In addition, you should have completed all of the tasks that are described in the SAS

Intelligence Platform: Installation and Conﬁguration Guide.

To access these documents, go to

http://support.sas.com/92administration.

Accessibility Features in the SAS Intelligence Platform Products

For information about accessibility for any of the products mentioned in this book,

see the documentation for that product.

For Windows-based assistive technologies to interoperate with SAS Java-based

desktop applications, you need to download and install the Java Access Bridge (JAB) from Sun Microsystems. For instructions, see “Accessibility Features in the SAS Desktop Clients” in the SAS Intelligence Platform: Desktop Application Administration Guide.

If you have questions or concerns about the accessibility of SAS products, send e-mail

to accessibility@sas.com.

CHAPTER

Understanding the State of Your System

Overview of the State of Your System Overview of SAS Management Console

About SAS Management Console About SAS Management Console Plug-ins Using the SAS Management Console Plug-ins

About the SAS Management Console Folders Tab 9 Overview of SAS Deployment Manager and SAS Web Administration Console Overview of the SAS Metadata Server and Its Initial Conﬁguration

What Is the SAS Metadata Server?

About the Metadata Manager Plug-in

About the SASMeta Server Context

About the SAS Metadata Repositories and the Repository Manager

How the SAS Metadata Server Works 13

The Initial Conﬁguration of the SAS Metadata Server 14 Overview of SAS Application Server Components and Their Initial Conﬁguration 15

About the SAS Application Server Hierarchy 15

About the SAS Application Server Components 16 Overview of Other SAS Servers and Spawners 17 Overview of Ports 19 Overview of the Conﬁguration Directory Structure 19

About the Conﬁguration Directory 19

About the Levn Subdirectory 20

About the Application Server Subdirectory 21

About the SASMeta Subdirectory 21

About the Web Subdirectory 22 Overview of Conﬁguration Files 22

About the SAS Metadata Server Conﬁguration File (omaconﬁg.xml) 22

About Other SAS Server Conﬁguration Files 23

About the Security-Related Conﬁguration Files 23

About Conﬁguration Files for Client Applications 24 Overview of Initial Roles, Groups, and Users 24

About User Roles for System Administration 24

Overview of System Administration User Roles 24 Metadata Server: Unrestricted Role 24 Metadata Server: User Administration Role 25 Metadata Server: Operation Role 25 Management Console: Advanced Role 26 Management Console: Content Management Role 26

About the Initial User Groups 26

User Groups Initially Deﬁned in the Operating System 26 User Groups Initially Deﬁned in Metadata 26

6 Overview of the State of Your System

Chapter 2

About the Initial User Accounts

Overview of the Initial User Accounts SAS Administrator SAS Trusted User SAS Installer SAS Spawned Servers Account SAS First User SAS Anonymous Web User LSF Administrator lsfuser 32

Overview of the State of Your System

Before you begin administering the SAS Intelligence Platform, you should be aware

of the following components that have been put in place during the installation and deployment process:

SAS Management Console, which is a Java application that provides a single point of control for administering the SAS Intelligence Platform.

SAS Deployment Manager and SAS Web Administration Console, which are also used to administer the SAS Intelligence Platform.

the SAS Metadata Server, which serves metadata from one or more SAS Metadata Repositories to all SAS Intelligence Platform client applications.

the SAS Application Server components that have been installed and conﬁgured in your environment to run SAS processes. These components can include SAS Workspace Servers, SAS Pooled Workspace Servers, SAS Stored Process Servers, SAS OLAP Servers, SAS/CONNECT servers, SAS Grid Servers, and SAS batch servers.

Note: In the SAS Intelligence Platform, the term server refers to a program or

programs that wait for and fulﬁll requests from client programs for data or services. The term server does not necessarily refer to a speciﬁc computer, since a single computer can host one or more servers of various types.

other SAS servers that might have been installed in your environment, including a

SAS/SHARE server, a SAS Content Server, a SAS Table Server, and a DataFlux Integration Server.

the ports that are used by each server to listen for incoming requests.

the conﬁguration directory that stores conﬁguration ﬁles, logs, scripts, and special-purpose SAS data sets on each SAS server machine and each middle-tier machine.

the main conﬁguration ﬁles that control the operation of the system.

the initial SAS users, groups, and roles that have been deﬁned, both on your host operating systems and in the SAS Metadata Repository.

Read the following topics to learn about these components and their initial

conﬁguration.

Understanding the State of Your System

Overview of SAS Management Console

About SAS Management Console

As you administer the SAS Intelligence Platform, your primary tool will be SAS Management Console. SAS Management Console is a Java application that provides a single point of control for administering your SAS servers and for managing metadata objects that are used throughout the SAS Intelligence Platform.

Whenever the SAS Metadata Server is running, you can use SAS Management Console to connect to the SAS Metadata Server and view and manage the metadata objects that are stored in the server’s metadata repositories. The SAS Management Console user interface includes a access metadata, as described in the following topics.

About SAS Management Console Plug-ins

SAS Management Console is a framework in which a variety of plug-ins are installed. A plug-in is an application module that is designed to create and maintain metadata for a speciﬁc type of resource. For example, the Server Manager plug-in is used to create and update metadata to deﬁne SAS servers. Some plug-ins include additional functionality. For example, the Server Manager plug-in enables you to stop, pause, and resume servers and to monitor server activity.

Only certain users can view and use plug-ins. A user’s access to plug-ins depends on which roles the user is assigned to and which capabilities are assigned to those roles (see “Overview of Initial Roles, Groups, and Users” on page 24).

If you are authorized to use plug-ins, then the when you open SAS Management Console and connect to a metadata server, as shown in this example:

Plug-ins tab and a

About SAS Management Console Plug-ins 7

Folders tab that you can use to

Plug-ins tab appears in the left pane

The following table provides the name and purpose of each of the most frequently used SAS Management Console plug-ins. References to related documentation are also provided.

8 About SAS Management Console Plug-ins

Table 2.1 SAS Management Console Plug-ins

Plug-in Name Plug-in Description

Chapter 2

Authorization Manager

Deﬁne and maintain access rules to control how users and groups can access metadata deﬁnitions. For details, see the SAS Intelligence Platform: Security Administration Guide.

BI Lineage Identify connections between BI objects in the SAS Folders tree. For

details, see “Using the BI Lineage Plug-in” on page 203 and the SAS Management Console Help. This plug-in is new with the November 2010 release of SAS Management Console.

Conﬁguration Manager

View and modify conﬁguration attributes for SAS applications including SAS Information Delivery Portal, SAS Web Report Studio, SAS Financial Management, and SAS Strategic Performance Management. For details, see the SAS Intelligence Platform: Web Application Administration Guide.

Data Library Manager

Foundation Services Manager

Create and maintain deﬁnitions for SAS libraries and database schemas. For details, see the SAS Intelligence Platform: Data Administration Guide.

View and modify deployment conﬁgurations for infrastructure and extension services that are used by applications such as SAS Information Delivery Portal, SAS Web Report Studio, and SAS Web OLAP Viewer for Java. For details, see the SAS Intelligence Platform: Web Application Administration Guide.

Map Service Manager Create and maintain map service deﬁnitions that link cubes to ESRI

ArcGIS map services so that ESRI Geographic Information System (GIS) spatial map information can be accessed and returned by an OLAP server when the cubes are queried. For details, see the SAS Intelligence Platform: Web Application Administration Guide.

Metadata Manager Perform administration tasks related to the SAS Metadata Server,

including the following:

stop, pause, resume, or reset the metadata server

check the status of the metadata server and the metadata repositories

create and manage metadata repositories

create and execute jobs to back up or restore your metadata repositories

Publishing Framework

Create and maintain deﬁnitions for channels, package subscribers, group subscribers, and event subscribers. For details, see the SAS Intelligence Platform: Web Application Administration Guide.

Schedule Manager Create and maintain schedules for running jobs that are created in SAS

Data Integration Studio and SAS Web Report Studio. For details, see

Scheduling in SAS.

Understanding the State of Your System

Plug-in Name Plug-in Description

Server Manager Perform administration tasks related to SAS servers, including the

following:

check the status of servers and validate them to ensure that they are conﬁgured correctly

stop, pause, quiesce, resume, or refresh the SAS object spawner or the SAS Table Server; and stop, pause, resume, or quiesce a process on a SAS OLAP Server, SAS Workspace Server, or SAS Stored Process Server

connect to the metadata server, to components of SAS Application Servers, to the SAS object spawner, or to a SAS Table Server to perform monitoring activities

Details about the preceding tasks are provided in this guide.

You can also use the Server Manager plug-in to create and maintain deﬁnitions for servers. For details, see the Application Server Administration Guide.

User Manager Create and maintain deﬁnitions for users, groups, and roles. For details,

see the SAS Intelligence Platform: Security Administration Guide.

About the SAS Management Console Folders Tab 9

SAS Intelligence Platform:

Using the SAS Management Console Plug-ins

To use the plug-ins, follow these general steps:

To display the metadata objects and folders that are associated with a plug-in, click the plus sign next to the plug-in icon. The objects and folders are displayed in a navigation tree.

To expand a folder or object in the navigation tree, click the plus sign next to it.

To determine the actions that you can take with an item in the navigation tree (for example, a plug-in, a folder, or an object), right-click the item and select an action from the menu that appears.

To view the metadata deﬁnition for an object in the navigation tree, right-click the object and select

To obtain help for a plug-in, select the plug-in (or any object associated with the plug-in) in the navigation tree, and select

Properties.

HelpIHelp on <plug-in name>.

Some of the plug-ins have wizards that assist you in creating new metadata objects. For example, Data Library Manager has a New Library Wizard that helps you create a new SAS library. To access the wizard, you expand the Data Library Manager node, right-click the

SAS Libraries folder, and select New Library.

For detailed information about using SAS Management Console and its plug-ins, see the product Help and the applicable administration guides.

About the SAS Management Console Folders Tab

The Folders tab in SAS Management Console displays the hierarchy of SAS folders. These folders are used to store metadata for business intelligence content such as libraries, tables, jobs, cubes, information maps, and reports. The folders also store SAS system content that is not directly accessed by business users.

As a system administrator, you will use this view for tasks such as the following:

setting up a folder structure for your users

10 Overview of SAS Deployment Manager and SAS Web Administration Console

setting permissions on folders and objects

importing and exporting metadata and associated ﬁles (for example, when

promoting content to production)

For a newly installed system, the folder organization is similar to the following:

Chapter 2

For details, see “About the SAS Folder Structure” on page 197.

Overview of SAS Deployment Manager and SAS Web Administration Console

In addition to SAS Management Console, the following interfaces are provided to

help you administer the SAS Intelligence Platform:

SAS Deployment Manager, which is a graphical user interface that enables you to

do the following:

remove one or more components of a SAS Intelligence Platform conﬁguration from your environment. For details, see “Removing a SAS Conﬁguration ”in the SAS Intelligence Platform: Installation and Conﬁguration Guide.

update passwords for the service accounts that were conﬁgured when you ran the SAS Deployment Wizard. For details, see “Manage Passwords” in the SAS Intelligence Platform: Security Administration Guide.

rebuild Web applications. For details, see “Rebuilding the SAS Web Applications” in the SAS Intelligence Platform: Web Application Administration Guide.

renew your software license for some SAS solutions that depend on a SAS middle tier. For details, see “Updating the SID File in Metadata for SAS Solutions” in the SAS Intelligence Platform: Installation and Conﬁguration Guide.

change the host names (including the network domains to which they belong) of server machines in your deployment. For details, see Appendix 6, “Using the SAS Deployment Manager to Update Host Name References,” on page

295.

conﬁgure a product after you have applied maintenance or after you have upgraded the product to a new release. For details, see “Conﬁguring SAS

Understanding the State of Your System

About the Metadata Manager Plug-in 11

Products” in the SAS Intelligence Platform: Installation and Conﬁguration Guide.

SAS Web Administration Console, which is a Web-based interface that enables you to monitor which users are logged on to SAS Web applications; manage folders and permissions for content in the SAS Content Server; and view the current conﬁguration of Web applications. For details, see “Using the SAS Web Administration Console” in the SAS Intelligence Platform: Web Application Administration Guide.

Overview of the SAS Metadata Server and Its Initial Conﬁguration

What Is the SAS Metadata Server?

The SAS Metadata Server is the most critical software component in the SAS Intelligence Platform. All of the client applications and the other SAS servers that are part of the platform depend on the SAS Metadata Server and cannot operate without it.

The SAS Metadata Server is a multi-user server that serves metadata from one or more SAS Metadata Repositories to all of the SAS Intelligence Platform client applications in your environment. The SAS Metadata Server enables centralized control so that all users access consistent and accurate data.

The functionality of the SAS Metadata Server is provided through the SAS Open Metadata Architecture, which is a metadata management facility that provides common metadata services to applications. One metadata server supports all of the applications in your environment and can support hundreds of concurrent users. This architecture enables the following:

the exchange of metadata between applications, so that applications can work together more easily.

centralized management of metadata resources. Because there is a common framework for creating, accessing, and updating metadata, it is easier to manage the applications that rely on this metadata.

The SAS Metadata Server stores information about the following:

the enterprise data sources and data structures that are accessed by SAS applications

resources that are created and used by SAS applications, including information maps, OLAP cubes, report deﬁnitions, stored process deﬁnitions, and scheduled jobs

the servers that run SAS processes

the users and groups of users that use the system, and the levels of access that users and groups have to resources

About the Metadata Manager Plug-in

In SAS Management Console, the SAS Metadata Server appears in the Metadata Manager plug-in, as shown here:

12 About the SASMeta Server Context

You can use this plug-in to stop, pause, resume, or reset the metadata server; to

check the status of the metadata server and the metadata repositories; and to create and manage metadata repositories. You can also access metadata utilities such as the Backup and Restore Wizard.

Chapter 2

Note: In the Plug-ins view, the

metadata deﬁnition. However, when you select

Properties action generally displays an object’s

Properties on the

Active Server

node of the Metadata Manager plug-in, the information that is displayed is supplied directly by the metadata server.

About the SASMeta Server Context

So that you can make use of SAS Management Console’s server monitoring features,

the metadata server also appears in the SASMeta application server tree (also referred to as the SASMeta server context) in the Server Manager plug-in, as shown here:

As shown in the preceding display, the SASMeta server context also includes a

workspace server and a DATA step batch server. This workspace server is only visible to and accessible by users who are in the SAS Administrators group. This server is used to execute metadata utilities including the Backup and Restore Wizard and the Import SAS Package and Export SAS Package wizards.

CAUTION:

Use the SASMeta workspace server only for running the metadata utilities. Do not use it for other SAS processing.

The DATA step batch server in the SASMeta context is provided for scheduling backup jobs that are created by using the Backup Wizard.

About the SAS Metadata Repositories and the Repository Manager

The SAS Metadata Server is a SAS process that enables clients to read metadata

from and write metadata to one or more SAS Metadata Repositories. A repository is a physical location in which a collection of related metadata objects is stored.

Metadata repositories are managed by a repository manager, which is a library of

tables that deﬁne the set of repositories that can be accessed by a SAS Metadata

Understanding the State of Your System

How the SAS Metadata Server Works 13

Server. A metadata server cannot be started without a repository manager. Each metadata server can have only one repository manager.

The SAS Metadata Server supports three types of metadata repositories:

foundation repository

the required metadata store for a SAS Metadata Server. Each metadata server has one foundation repository. As a default, the name of the foundation repository is Foundation. (If you performed a custom installation, then you might have assigned a different name.)

project repository

a metadata repository that serves as an isolated work area or playpen. Project repositories are available for SAS Data Integration Studio only. In general, each user who participates in change management has his or her own project repository.

A project repository enables a user to check out and lock metadata from a foundation repository or a custom repository so that the metadata can be modiﬁed and tested in a separate area. When the metadata is ready, it is checked in and unlocked so that it is available to other users.

custom repository

an optional metadata store for a SAS Metadata Server, in addition to the foundation repository. Custom repositories are useful for physically segregating metadata for storage or security purposes.

Custom repositories appear as separate root folders in the

Folders tab of SAS

Management Console.

In SAS Management Console, the repositories are displayed in the Metadata Manager plug-in, as shown in this example:

In SAS 9.2, it is not necessary to deﬁne dependencies between repositories. If a repository dependency was deﬁned in SAS 9.1.3, then the dependency relationship is eliminated during the SAS 9.1.3 to SAS 9.2 migration process. However, the existing associations between metadata objects still remain in effect.

How the SAS Metadata Server Works

SAS Intelligence Platform applications connect to the SAS Metadata Server and issue SAS Open Metadata Interface method calls that access SAS Metadata Repositories.

To enable high-speed access by clients, the SAS Metadata Server is an “in-memory” server. As clients submit queries and updates, the data sets that contain the requested records are read from repository data sets on disk into the server’s memory, where they remain until the server is paused and resumed or until the server is stopped.

In the default conﬁguration, metadata updates that are requested by client applications are recorded immediately in memory and in a journal ﬁle so that client access can be resumed. The more time-consuming updates to the repository data sets on disk are performed later in the background.

14 The Initial Conﬁguration of the SAS Metadata Server

The Initial Conﬁguration of the SAS Metadata Server

The SAS Deployment Wizard provides the following initial conﬁguration for your

metadata server:

Your metadata server contains a foundation metadata repository called

Foundation. (If you performed a custom installation, then you might have

assigned a different name.) This repository contains the following items:

metadata deﬁnitions for initial users, groups, and roles

default authorization settings that give the initial users, groups, and roles access to different levels of functionality

metadata deﬁnitions for your servers

a full set of resource templates that can be used to create additional metadata objects

The data sets that make up the foundation repository are typically located in

the following path:

SAS-conﬁguration-directory

MetadataServer\MetadataRepositories\Foundation

In this path, SAS-conﬁguration-directory refers to the SAS conﬁguration

directory (see “About the Conﬁguration Directory” on page 19).

Journaling has been enabled.

When journaling is not enabled, clients that request metadata updates must wait for updates to be written to the repository data sets on the ﬁle system before client access is resumed. When journaling is enabled, access is returned to clients as soon as the metadata updates are written to the in-memory database and the journal ﬁle. The more time-consuming updates to the repository data sets are performed later in the background.

The default settings for journaling are as follows:

The name of the journal ﬁle is

The journal ﬁle is written to the following path:

SAS-conﬁguration-directory

On 32–bit machines and z/OS systems, 200 megabytes of storage on the metadata server are reserved for the journal ﬁle and cannot be used for other processes. On 64–bit machines, the default setting is 500 megabytes. To modify these settings, see “Conﬁguring Metadata Server Journaling” on page

170.

Chapter 2

\Lev1\SASMeta\

MetadataJournal.dat.

\Lev1\SASMeta\MetadataServer\Journal

Two special users of the metadata server have been set up: the SAS Administrator and the SAS Trusted User.

The metadata server has been conﬁgured to write daily logs. The default location for logs is as follows:

SAS-conﬁguration-directory

\Lev1\SASMeta\MetadataServer\Logs

For details about the default logging conﬁguration, see “Initial Logging Conﬁguration for SAS Servers” on page 107.

Understanding the State of Your System

About the SAS Application Server Hierarchy 15

Overview of SAS Application Server Components and Their Initial Conﬁguration

About the SAS Application Server Hierarchy

The SAS Deployment Wizard creates metadata deﬁnitions and conﬁguration ﬁles for

a set of SAS servers that are referred to collectively as a SAS Application Server. The server hierarchy includes the following levels:

SAS Application Server

a logical framework (or

framework enables you to specify metadata that applies to all of the logical servers

and servers that the SAS Application Server contains. You can also attach

libraries, schemas, directories, and other resources that are available to SAS

servers, regardless of the type of server. As a result, you can deploy applications in

several modes while ensuring that applications will execute properly in each mode.

The default name of the initial SAS Application Server is SAS Deployment Wizard enables you to provide a different name during installation. (In single-machine installations that are migrated from SAS 9.1.3, the SAS Application Server is typically called

Your installation also includes a SAS Application Server called SASMeta, which is used to execute metadata utilities (see “About the SASMeta Server Context” on page 12).

server context) under which SAS applications execute. This

SASApp. However, the

SASMain).

logical servers

a logical framework within SAS Application Server metadata that contains deﬁnitions for one or more similar servers. A logical server is referenced when an application requests a speciﬁc launch mode, such as interactive or batch.

servers

speciﬁc process instances that perform the requested work. A server deﬁnition contains the server metadata that is required to connect to a SAS server on a particular machine. The deﬁnition includes details about where the process is executing and how a client should contact the server, as well as options that describe how the server should behave.

Note: In the SAS Intelligence Platform, the term server refers to a program or programs that wait for and fulﬁll requests from client programs for data or services. The term server does not necessarily refer to a speciﬁc computer, since a single computer can host one or more servers of various types.

The SAS Application Server hierarchy appears in SAS Management Console in the Server Manager plug-in, as in the following example:

16 About the SAS Application Server Components

About the SAS Application Server Components

The most common components of a SAS Application Server are SAS Workspace

Servers, SAS Pooled Workspace Servers, and SAS Stored Process Servers. An application server can also contain SAS/CONNECT servers, SAS OLAP Servers, SAS DATA step batch servers, and SAS Grid Servers. The purpose of each server component is described in the following table.

Chapter 2

Table 2.2 SAS Application Server Components

Server Name Server Description

SAS Workspace Server

SAS Pooled Workspace Server

SAS Stored Process Servers

SAS Workspace Servers fulﬁll client requests for SAS sessions. When these servers are conﬁgured as standard workspace servers (without workspace pooling), each client establishes a connection to a single-user server process, uses the server, and then disconnects. For details, see the SAS Intelligence Platform: Application Server Administration Guide.

SAS Pooled Workspace Servers are workspace servers that use server-side pooling, which is new with SAS 9.2. The SAS object spawner maintains a pool of reusable workspace server processes called a pool, thus avoiding the overhead that is associated with creating a new process for each connection. Workspace server load balancing is built in to server-side pooling.

Pooled workspace servers are intended for use by query and reporting tools such as SAS Web Report Studio and SAS Information Delivery Portal when accessing relational information maps.

For details, see the SAS Intelligence Platform: Application Server Administration Guide.

SAS Stored Process Servers fulﬁll client requests to execute SAS stored processes. A stored process is a SAS program that is stored on a server and can be executed as required by requesting applications.

Stored process servers are conﬁgured to be load balanced. By default, the object spawner balances workloads across three stored process server processes.

For details, see the SAS Intelligence Platform: Application Server Administration Guide.

SAS/CONNECT server

SAS/CONNECT servers enable clients to execute code on a remote host, or to move data between client and server machines. For details, see

SAS/CONNECT User’s Guide.

Understanding the State of Your System

Server Name Server Description

SAS OLAP Server SAS OLAP Servers provide access to multidimensional data. For details,

see the SAS Intelligence Platform: Application Server Administration Guide.

SAS batch server SAS batch servers are part of the conﬁguration for SAS scheduling. They

are metadata objects that store information about an executable that the scheduling server can use to run scheduled tasks. For details, see Scheduling in SAS.

SAS Grid Server A SAS Grid Server is conﬁgured if you have the SAS Grid Manager

software package. SAS Grid Servers are metadata objects that store information about an executable that the scheduling server can use to start SAS/CONNECT on grid nodes. For details, see Grid Computing in SAS.

For additional details, see:

“Initial Logging Conﬁguration for SAS Servers” on page 107

“Reference: Conﬁguration Files for SAS Servers” on page 271

Overview of Other SAS Servers and Spawners

Overview of Other SAS Servers and Spawners 17

The SAS Intelligence Platform includes additional servers and spawners that might appear in the Server Manager tree in SAS Management Console, as shown here:

The servers and spawners include the following:

18 Overview of Other SAS Servers and Spawners

Table 2.3 Other SAS Servers and Spawners

Chapter 2

Server or Spawner Name

SAS Content Server stores digital content (such as documents, reports, and images) that are

DataFlux Integration Server

SAS In-Process Services

Server or Spawner Description

created and used by SAS client applications. To interact with the server, clients use WebDAV-based protocols for access, versioning, collaboration, security, and searching.

The SAS Content Server is used by SAS Information Delivery Portal and SAS Web Report Studio, as well as other SAS products and solutions.

The server’s repositories are stored in the conﬁguration directory. For more information, see the SAS Intelligence Platform: Web Application Administration Guide.

executes DataFlux jobs and real-time services that cleanse data or analyze data quality. The jobs and services are created using DataFlux applications (dfPower Architect and dfPower Proﬁle) and are executed on the server through job ﬂows that are created in SAS Data Integration Studio.

For information about conﬁguring this server, see “Administering SAS Data Integration Studio” in the SAS Intelligence Platform: Desktop Application Administration Guide.

provides the ability to schedule jobs from certain Web-based SAS applications without using a separate scheduling server. The scheduling functions run as a process within the application. For details, see Scheduling in SAS.

AppData subdirectory of your

SAS object spawner runs on the same machine as the SAS Application Server components. The

spawner listens for incoming client requests for workspace servers, pooled workspace servers, and stored process servers, and it launches instances of these servers as needed.

Although the object spawner is not part of the SAS Application Server hierarchy, it is essential to the operation of workspace servers, stored process servers, and pooled workspace servers.

For details, see the SAS Intelligence Platform: Application Server Administration Guide.

SAS Table Server is included in some SAS Intelligence Platform software offerings. It is used

by the SAS Shared Services component of the middle tier.

SAS/CONNECT spawner

SAS/SHARE server SAS/SHARE enables multiple users to update a SAS ﬁle (or several ﬁles)

listens for SAS/CONNECT client requests and invokes SAS sessions on the remote computer. For details, see Communications Access Methods for SAS/CONNECT and SAS/SHARE.

at the same time. It also enables users to access SAS ﬁles on a server without requiring a separate SAS/CONNECT report login for each user. For details, see the SAS/SHARE User’s Guide.

In addition, the following server appears under the Deployment Tester plug-in under

Application Management:

SAS Deployment Tester Server

processes validation tasks that are requested either by the SAS Deployment Tester

plug-in or by a SAS Deployment Tester batch client. For usage instructions, see

the SAS Management Console Help.

Understanding the State of Your System

For additional details, see:

“Initial Logging Conﬁguration for SAS Servers” on page 107

“Reference: Conﬁguration Files for SAS Servers” on page 271

Overview of Ports

The servers in the SAS Intelligence Platform communicate with clients and other servers using TCP/IP. Thus, each server listens on a particular port or ports for incoming requests. For information about the default ports, see Appendix 1, “Default SAS Ports,” on page 259. During installation, the SAS Deployment Wizard enables you to override the default port numbers with different values.

Overview of the Conﬁguration Directory Structure

About the Conﬁguration Directory 19

About the Conﬁguration Directory

Every server-tier and middle-tier host has a conﬁguration directory which is the root of the SAS Intelligence Platform environment. The structure and contents of the directory vary depending on the host operating system, which products are installed, and whether the host machine is a server-tier host or a middle-tier host.

Throughout the SAS Intelligence Platform administration documentation, the variable path. The default paths are as follows:

SAS-conﬁguration-directory is used to designate your conﬁguration directory

on Windows systems:

:\SAS\deployment-plan-name

drive

on UNIX systems:

usr/local/deployment-plan-name or

usr/local/sas

Note:

In these paths, deployment-plan-name is the name that was speciﬁed when the deployment plan was created. If no name was speciﬁed, then the default name

Config is used.

You can specify a different path when you run the SAS Deployment Wizard. In UNIX environments, the installer generally overrides the path with the site’s preferred location (for example,

opt/sas/Config). The installer must

have write permission to this path.

on z/OS systems, the directory that is speciﬁed in the CONFIG_DIR environment variable

In the conﬁguration directory, the SAS Deployment Wizard builds a directory structure that contains important ﬁles for managing your system. Here is an example of the conﬁguration directory structure for a single-machine Windows implementation:

20 About the Levn Subdirectory

Note: Depending on your operating system and which products you have installed,

your site might have different subdirectories.

Chapter 2

About the Levn Subdirectory

The Levn subdirectory contains conﬁguration information and other ﬁles for a

particular installation instance. Additional levels, such as

Lev2 and Lev3, can be used for environments that you install

for purposes such as development and testing. During installation, the SAS Deployment Wizard enables you to specify the level number.

The contents of the

Levn directory depend on which components are installed on the

machine. Its contents might include the following:

on UNIX and z/OS machines, a script called sas.servers that you can use to start,

stop, or restart all of the SAS servers and spawners on the machine in the correct

order by using a single command.

an AppData subdirectory, which contains data sets for the SAS Content Server

repository. It also contains data that is installed for the use of speciﬁc applications

(for example, SAS BI Dashboard).

a subdirectory for the application server (see “About the Application Server

Subdirectory” on page 21).

a subdirectory for the metadata server (see “About the SASMeta Subdirectory” on

page 21).

subdirectories for other SAS servers and spawners, including the SAS object

spawner, the SAS Deployment Tester Server, the SAS Table Server, the SAS/

CONNECT spawner, and the SAS/SHARE server.

Lev1 is generally used for production environments.

a Web subdirectory for ﬁles related to Web applications (see “About the Web

Subdirectory” on page 22) .

logs and documents that were created during the installation and conﬁguration

process

For more details about the

Levn directory, see “Contents of the Levn Subdirectory” on

page 263.

Understanding the State of Your System

About the SASMeta Subdirectory 21

About the Application Server Subdirectory

On machines where components of a SAS Application Server are installed, the Levn directory contains an application server subdirectory. A SAS Application Server is a logical entity that contains speciﬁc servers (for example, a SAS Workspace Server and a SAS Stored Process Server) that execute SAS code. Application server subdirectories are named as follows:

SASApp is the default name that the SAS Deployment Wizard assigns to directory

for the ﬁrst application server. If you assigned a different name when you ran the SAS Deployment Wizard, then the subdirectory is named accordingly.

If you conﬁgure more than one application server, then additional directories are created that correspond to each of the application server names.

If you have a single-machine installation that was migrated from SAS 9.1.3, then the application server subdirectory is typically called

The application server subdirectory contains the following items:

a subdirectory for each component of the application server, including the workspace server, the pooled workspace server, the OLAP server, the stored process server, the SAS/CONNECT server, batch servers, and grid servers (if applicable). Each of these subdirectories contains the server’s start-up scripts, conﬁguration ﬁles, logconﬁg.xml ﬁles to conﬁgure logging, and

a subdirectory for data that is used by the application server.

a SASEnvironment

subdirectory to store deployed jobs, job steps, SAS format and informat catalogs, and user-created SAS autocall macros that are needed to perform processing on the application server

conﬁguration ﬁles that apply to all components of the application server

SASMain.

Logs directories to store log ﬁles.

For more details about this subdirectory, see “Contents of the Application Server Subdirectory (SASApp or SASMain)” on page 266. For information about the server conﬁguration ﬁles that are contained in this subdirectory, see “Conﬁguration Files for Components of SAS Application Servers” on page 274.

About the SASMeta Subdirectory

On the machines where the metadata server is installed, the a subdirectory for the metadata server’s ﬁles.

SASMeta

is the name that the SAS Deployment Wizard assigns to the metadata server context and, in turn, to this directory.

The

SASMeta directory contains the following items:

conﬁguration ﬁles that apply to the SASMeta application server components, which include a workspace server and a DATA step batch server.

a WorkspaceServer subdirectory, which contains ﬁles for the SASMeta workspace server. This server is used to execute metadata utilities. The subdirectory contains start-up scripts, conﬁguration ﬁles, a logconﬁg.xml ﬁle, and a Logs directory for this server.

a BatchServer subdirectory, which contains ﬁles for the SASMeta DATA step batch server. This server is used to schedule backup jobs that are created by the Backup Wizard. The subdirectory contains start-up scripts, conﬁguration ﬁles, a logconﬁg.xml ﬁle, and a

SASEnvironment and Data subdirectories that can be used by the workspace

Logs directory for this server.

server.

Levn directory includes

22 About the Web Subdirectory

a MetadataServer

Chapter 2

subdirectory, which contains the following:

the metadata server’s start-up and management scripts, conﬁguration ﬁles, logconﬁg.xml ﬁles to conﬁgure logging, and

Logs

directories to store log ﬁles.

programs to back up and restore the metadata server (for details, see “About the Metadata Server Backup and Restore Utilities” on page 124).

a subdirectory called

MetadataRepositories, which contains a subdirectory

for each metadata repository. These subdirectories contain the SAS data sets that store your metadata.

a subdirectory call

rposmgr, which contains data sets for the repository

manager.

CAUTION:

The MetadataRepositories and rposmgr directories contain data sets that are critical to the operation of your system.

To safeguard the integrity of your

system:

Never move, delete, modify, or directly read the data sets in these directories. These data sets should be accessed only by metadata server processes.

Do not place other ﬁles in these directories.

Back up the contents of these directories regularly, as described in Chapter 9, “Best Practices for Backing Up and Restoring Your System,” on page 123.

a directory for the metadata server journal.

a SASBackup directory that can be used as a destination for backing up the metadata server.

For more information about the metadata server conﬁguration ﬁles, see “Conﬁguration Files for the Metadata Server” on page 272. For a complete list of the contents of the MetadataServer subdirectory, see “Contents of the Metadata Server Subdirectory (SASMeta)” on page 265.

About the Web Subdirector y

On middle-tier machines (that is, machines with installed Web components), the

Lev1 directory contains a subdirectory called

Subdirectory” on page 267. For information about administering middle-tier applications and components, see the Administration Guide.

Overview of Conﬁguration Files

Web. For details, see “Contents of the Web

SAS Intelligence Platform: Web Application

About the SAS Metadata Server Conﬁguration File (omaconﬁg.xml)

On the machine that hosts the SAS Metadata Server, the SASMeta\MetadataServer

directory contains a ﬁle called omaconﬁg.xml. This ﬁle contains SAS Metadata Server settings such as the following:

Understanding the State of Your System

values for the libref and path of the metadata server’s repository manager

the names and locations of the adminUsers.txt and trustedUsers.txt ﬁles, which

About the Security-Related Conﬁguration Files 23

contain information about special users of the metadata server

journaling options

For details about the omaconﬁg.xml ﬁle, see “Reference Information for

omaconﬁg.xml” on page 280.

About Other SAS Server Conﬁguration Files

Server-tier machines contain conﬁguration ﬁles for each SAS server. These ﬁles specify the SAS system options that are in effect when the server is launched. The following conﬁguration ﬁles are present in each server’s conﬁguration directory:

sasv9.cfg

is the primary conﬁguration ﬁle for a server. You should not edit this conﬁguration ﬁle.

sasv9_usermods.cfg

enables user modiﬁcations to a server conﬁguration. If you need to modify an option or add a new option for a speciﬁc server, then edit this ﬁle.

logconﬁg.xml

speciﬁes the logging conﬁguration for the server. For details, see Chapter 8, “Administering Logging for SAS Servers,” on page 103.

The ﬁles sasv9.cfg and sasv9_usermods.cfg are also present in the conﬁguration directory for the SAS Application Server (for example, the

SASApp directory) and in the

SAS–home directory where SAS Foundation installed. Conﬁguration ﬁles are set up to inherit options from one another.

For details about the server conﬁguration ﬁles, see “Reference: Conﬁguration Files for SAS Servers” on page 271.

About the Security-Related Conﬁguration Files

On the machine that hosts the SAS Metadata Server, three conﬁguration ﬁles that affect security are located in the

Note: Be sure to limit access to these ﬁles to only those users who require access in order to perform their job functions.

adminUsers.txt

deﬁnes your system’s initial unrestricted user. The SAS Deployment Wizard creates this user, which is usually called the SAS Administrator. In the ﬁle, the unrestricted user name is preceded by an asterisk. For information about unrestricted users, see “About User Roles for System Administration” on page 24.

SASMeta\MetadataServer directory:

Note: If you migrated your system from SAS 9.1.3, then you might have additional users in this ﬁle. In SAS 9.2, role memberships are the preferred method for assigning unrestricted user status.

trustedUsers.txt

conveys privileged status to a service account to enable that account to act on behalf of other users. For more information, see “About the Initial User Accounts” on page 27.

trustedPeers.xml

24 About Conﬁguration Files for Client Applications

Chapter 2

can be used to limit the scope of trust for connections from SAS sessions to the metadata server. Initially, the scope is not limited. For details, see the “Trusted Peer” topic in the “Authentication Mechanisms” chapter of the Platform: Security Administration Guide.

About Conﬁguration Files for Client Applications

Conﬁguration ﬁles for client applications are described in the following documents:

SAS Intelligence Platform: Web Application Administration Guide

SAS Intelligence Platform: Desktop Application Administration Guide

Overview of Initial Roles, Groups, and Users

About User Roles for System Administration

SAS Intelligence

Overview of System Administration User Roles

A user role is a set of capabilities. Some SAS applications make certain actions available only to users or groups that have a particular role. To enable a user or group to perform those actions, you add the user or group to the appropriate role.

During installation, the SAS Deployment Wizard creates metadata deﬁnitions for several user roles. The following initial roles are created for performing system administration tasks:

Metadata Server: Unrestricted

Metadata Server: User Administration

Metadata Server: Operation

Management Console: Advanced

Management Console: Content Management

The SAS Deployment Wizard also creates some additional roles for users of speciﬁc client applications, including SAS Enterprise Guide, SAS Web Report Studio, and SAS Add-In for Microsoft Ofﬁce.

Note:

To understand how role assignments affect a user’s ability to perform the system administration tasks that are documented in this guide, see Chapter 3, “Who Can Do What: Credential Requirements for SAS Management Console Tasks,” on page

33.

For information about how to add users to roles or to deﬁne additional roles, see “Managing Users, Groups, and Roles” in the SAS Intelligence Platform: Security Administration Guide.

Metadata Server: Unrestricted Role

Note: The initial name of this role is META: Unrestricted Users Role, and the initial display name for this role is

Metadata Server: Unrestricted.

Understanding the State of Your System

About User Roles for System Administration 25

The Metadata Server: Unrestricted

role has access to all metadata regardless of SAS permissions settings. Users in this role, which are referred to as unrestricted users, can do the following:

perform all of the functions that users in the

Administration

access all metadata except user passwords

continue to access metadata repositories and use features of SAS Management

and

Metadata Server: Operation

Metadata Server: User

roles can perform

Console when the metadata server is paused to the Administration state

Follow these important guidelines when using an account that is in the

Server: Unrestricted

This role is intended only for tasks that require unrestricted access to metadata (for example, adding other users to the

role:

Metadata Server: Unrestricted

Metadata

role, performing tasks when the metadata server is paused to the Administration state, and creating, deleting, formatting, and unregistering foundation repositories).

Use the accounts in this role only to log on to SAS Management Console. You should not use these accounts to log on to other client applications.

The SAS Deployment Wizard places one user in this role. This user, which is generally called the SAS Administrator, is speciﬁed in the ﬁle adminUsers.txt. For details, see “About the Initial User Accounts” on page 27.

Note: The

Metadata Server: Unrestricted

role provides access to the metadata server, not to other SAS servers. Some administration tasks require access to a SAS Application Server, which might require additional credentials. For details, see Chapter 3, “Who Can Do What: Credential Requirements for SAS Management Console Tasks,” on page 33.

Metadata Server: User Administration Role

Note: The initial name of this role is

Role

, and the initial display name for this role is

Administration

to this role.

Users who are assigned to the

. The SAS Deployment Wizard assigns the SAS Administrators group

Metadata Server: User Administration

create and modify users, groups, and roles. Users in this role are authorized to update user passwords. They cannot read existing passwords, except the passwords for their own logins.

For details about the user administration tasks, see the SAS Intelligence Platform:

Security Administration Guide.

META: User and Group Administrators

Metadata Server: User

role can

Metadata Server: Operation Role

Note: The initial name of this role is

display name for this role is

Metadata Server: Operation. The SAS Deployment

Wizard assigns the SAS Administrators group to this role.

Users who are assigned to the

Metadata Server: Operation role can perform the

following tasks:

stop, pause, resume, and reset (or refresh) the metadata server

add, delete, format, and unregister metadata repositories (except the foundation repository)

META: Operators Role, and the initial

Users who perform these tasks must also be assigned to the SAS Management Console Advanced Role, which provides access to the Metadata Manager plug-in.

26 About the Initial User Groups

Management Console: Advanced Role

Chapter 2

The Management Console: Advanced

role is initially conﬁgured to allow access to all of the plug-ins in SAS Management Console. The SAS Deployment Wizard assigns the SAS Administrators group to this role.

You must make the following additional role assignments to enable certain functions:

the

Metadata Server: User Administration

Unrestricted

the Metadata Server: Operation

Unrestricted

role, to access functionality within the User Manager plug-in

role, to access some functions within the Metadata Manager plug-in

role or the

Metadata Server:

Management Console: Content Management Role

The Management Console: Content Management

enable access to the following features of SAS Management Console:

the User Manager, Authorization Manager, and Library Manager plug-ins

the Folders

tab

To have access to certain functionality within User Manager plug-in, the user must

also be assigned to the

Metadata Server: Unrestricted role.

Metadata Server: User Administration

role is initially conﬁgured to

” role or the

About the Initial User Groups

User Groups Initially Deﬁned in the Operating System

On some of the machines in your conﬁguration, the following operating system user

groups might have been deﬁned during installation:

sas (UNIX only)

This group is used to control access to the conﬁguration directories on UNIX machines. The group includes the installer (the sas user). Typically, you will not add any other users to this group.

SAS Server Users (Windows only)

This group might have been created on Windows machines that have stored process servers, pooled workspace servers, or standard workspace servers installed. During the installation process, you should have assigned this group the right to

Log on as a batch job

, which is required in order to start processes for

those servers.

If you are not using Integrated Windows authentication, then you can add users

to this group to enable them to start workspace server processes.

SASGRP (z/OS only)

On z/OS systems, this RACF group is used to control access to the conﬁguration directory. The group is deﬁned with an OMVS segment and is set as the default group for the SAS Installer and SAS Spawned Servers accounts.

User Groups Initially Deﬁned in Metadata

The SAS Deployment Wizard creates the following user groups in metadata. These groups are part of the SAS Intelligence Platform security infrastructure. For information about how they are used to implement security, see the SAS Intelligence

Platform: Security Administration Guide.

Understanding the State of Your System

About the Initial User Accounts 27

PUBLIC

a standard group with implicit membership. This group includes everyone who can access the metadata server, either directly or through a trust relationship. A user who does not have an individual identity uses the PUBLIC group identity.

SASUSERS

a standard group with implicit membership. This group includes all users who have individual identities.

SAS Administrators

a standard group for metadata administrators. By default, this group is granted broad access to the metadata and has all roles other than the

Unrestricted

role.

Metadata Server:

SAS System Services

a standard group for service identities that need to read server deﬁnitions or other system resources.

SAS General Servers

a standard group whose members can be used for launching stored process servers and pooled workspace servers.

Table Server Administrators

a standard group that has permission to administer SAS Table Servers.

LSF Services

a group whose members can schedule jobs in the LSF component of Platform Suite for SAS. Beginning with the second maintenance release for SAS 9.2, this group is part of the standard conﬁguration for sites that use Platform Suite for SAS to schedule SAS Web Report Studio reports.

The LSF Services group is not needed if you use SAS In-Process Services to

schedule reports.

About the Initial User Accounts

Overview of the Initial User Accounts

During installation, the SAS Deployment Wizard creates several initial user accounts. Some of these user accounts are created for all installations, some of the accounts are optional, and some of the accounts are created only if certain software components are installed.

SAS Administrator

SAS Trusted User

SAS Installer

SAS Spawned Servers

SAS First User

SAS Anonymous Web User

LSF Administrator

lsfuser

These user accounts might have been assigned different names at your site. For each account, the following topics provide the default name and user ID, information about

28 About the Initial User Accounts

whether or when the account is required, the account’s purpose and use, and the locations where the account is set up.

SAS Administrator

Chapter 2

Type of Installation

New with default settings

New with external authentication selected

Migrated from

9.1.3

Default User Name Default User ID Required?

SAS Administrator

sasadm@saspw Yes Metadata

sasadm Yes Metadata and OS

Location of Account

The SAS Administrator user account has privileges that are associated with the

Metadata Server: Unrestricted

role (see “Metadata Server: Unrestricted Role” on page 24). In addition, the SAS Administrator account is initially a member of the SAS Administrators group (see “User Groups Initially Deﬁned in Metadata” on page 26) .

This user is deﬁned in the following locations:

in the ﬁle adminUsers.txt, which is typically located in the following path:

SAS-conﬁguration-directory

\Lev1\SASMeta\MetadataServer

This ﬁle ensures that your site will always have at least one user with the privileges of an unrestricted user, regardless of what is speciﬁed in metadata. You cannot override this user’s privileges by modifying the user deﬁnition in SAS Management Console.

in metadata.

in the operating system of the metadata server machine, only in the following situations:

You selected the External authentication option for this user during a custom installation.

You migrated your system from SAS 9.1.3 to SAS 9.2.

In new, default installations of SAS 9.2, the SAS Administrator is an internal user account that is known only to SAS and that is authenticated internally in metadata. When internal authentication is used, it is not necessary for this user to have a local or network account.

Note: We recommend that you establish individual metadata administrators rather than sharing the SAS Administrator account. See “Security Tasks” in the SAS Intelligence Platform: Security Administration Guide.

SAS Trusted User

Understanding the State of Your System

About the Initial User Accounts 29

Type of

Installation

New with default

settings

New with

external

authentication

selected

Migrated from

9.1.3

Default User Name Default User ID Required?

SAS Trusted User

sastrust@saspw Yes Metadata

sastrust Yes Metadata and OS

Location of Account

The SAS Trusted User is a privileged service account that can act on behalf of other

users on a connection to the metadata server. No user should log on directly as a

trusted user, except to perform certain administrative tasks associated with the SAS

Information Delivery Portal. For details about those tasks, see the SAS Intelligence

Platform: Web Application Administration Guide.

The SAS Trusted User is deﬁned in the following locations:

in metadata.

in the ﬁle trustedUsers.txt, which is typically located in the following path:

SAS-conﬁguration-directory

\Lev1\SASMeta\MetadataServer

A user is granted privileges as a trusted user only if the user is speciﬁed in this

ﬁle.

Note: Typically, there is no reason to add more IDs to this ﬁle. In particular, do

not add regular users to this ﬁle.

in the operating system of the metadata server machine, only in the following

situations:

You selected the External authentication option for this user during a custom installation.

You migrated your system from SAS 9.1.3 to SAS 9.2.

In new, default installations of SAS 9.2, the SAS Trusted User is an internal user

account that is known only to SAS and that is authenticated internally in metadata.

When internal authentication is used, it is not necessary for this user to have a local or

network account.

For detailed information about this user, see the SAS Intelligence Platform: Security

Administration Guide.

SAS Installer

Default User Name Default User ID Required? Location of Account

SAS Installer sas Yes OS

30 About the Initial User Accounts

The SAS Installer is a user account that is used to install and conﬁgure SAS software. On UNIX and z/OS systems, this account is the owner of conﬁguration directories and their contents and is the process owner for items such as the metadata server, the OLAP server, and the object spawner. The account should continue to be available after installation so that it can be used to apply maintenance.

The SAS Installer account must be deﬁned in the operating systems of the following machines:

the metadata server machine

machines that host an OLAP server

machines where the object spawner is installed

This user is not deﬁned in metadata.

SAS Spawned Servers Account

Default User Name Default User ID Required? Location of Account

SAS Spawned Servers sassrv Yes OS and metadata (as

Chapter 2

a login for the SAS General Servers group)

The SAS Spawned Servers account is the initially conﬁgured process owner for pooled workspace servers and stored process servers. An account for this user must be deﬁned in the operating system of the following machines:

machines that host a stored process server

machines that host a pooled workspace server

During the installation process on Windows machines, this user should have been assigned the right to

Log on as a batch job

. This right can also be assigned by adding the user to the SAS Server Users group (see “User Groups Initially Deﬁned in the Operating System” on page 26) .

This user does not have an individual metadata identity. However, a login for this

user is deﬁned for the SAS General Servers group.

SAS First User

Default User Name Default User ID Required? Location of Account

SAS Demo User sasdemo No Metadata and OS

The SAS First User is an optional account that can serve as a generic end user when you are testing any of the SAS client applications. During installation, the Software Deployment Wizard enables you to specify whether to create this user.

If you selected the option to create this user, then the user’s account is deﬁned in the following locations:

in metadata

Understanding the State of Your System

in the operating system of the metadata server machine and workspace server

About the Initial User Accounts 31

machine

During the installation process on Windows machines, this user should have been

assigned the right to

Log on as a batch job

. This right can also be assigned by adding the user to the SAS Server Users group (see “User Groups Initially Deﬁned in the Operating System” on page 26) .

SAS Anonymous Web User

Type of Installation

New with default settings

New with external authentication selected

Default User Name Default User ID Required?

SAS Anonymous Web User

webanon@saspw No Metadata

webanon No Metadata and OS

Location of Account

The SAS Anonymous Web User is an optional account that is used to grant clients access to applicable SAS Web Infrastructure Platform components. When Web clients request access to Web services, they are not prompted for credentials but instead are granted access under this user account.

This user is deﬁned in the following locations:

in metadata. In default installations of SAS 9.2, the SAS Anonymous Web User is an internal user account that is known only to SAS and that is authenticated internally in metadata. When internal authentication is used, it is not necessary for this user to have a local or network account.

in the operating system of the metadata server machine, only if you selected the External authentication option for this user during a custom installation.

LSF Administrator

Default User ID Required? Location of Account

none Yes, if Platform Suite for SAS is installed OS

The LSF administrator is the primary administrator for the Platform scheduling server and the owner of the Process Manager server. This user is required only if you have installed Platform Suite for SAS in support of either scheduling or grid computing.

The LSF administrator account must be deﬁned in the operating system of the machine where Platform Suite for SAS is installed. This user must have full control of the LSF and Process Manager directories. On Windows systems, this user must belong to the Administrators Group and must have rights to

system

and Log on as a batch job.

Act as part of the operating

32 About the Initial User Accounts

This user is not deﬁned in metadata.

lsfuser

Default User ID Required? Location of Account

Chapter 2

lsfuser Yes, if Platform Suite for SAS is

installed and is used to schedule WRS reports

OS, metadata (as a login for the LSF Services group), and password ﬁle in LSF

The lsfuser account is used by default when you schedule SAS Web Report Studio

reports using the LSF component of Platform Suite for SAS. The lsfuser account must be deﬁned in the operating system of the machine where Platform Suite for SAS is installed. On Windows machines, the account must also be added to the password ﬁle in the LSF software. For details, see “Enabling Report Scheduling With Platform Suite for SAS” in

Scheduling in SAS.

This user does not have an individual metadata identity. However, a login for this

user is deﬁned for the LSF Services group, effective with the second maintenance release for SAS 9.2.

Note:

If you have not yet installed the second maintenance release for SAS 9.2, follow

the instructions in SAS Installation Note 35283 to set up credentials for

scheduling reports in LSF.

The lsfuser account is not needed if you use SAS In-process Services to schedule

reports.

CHAPTER

Who Can Do What: Credential Requirements for SAS Management Console Tasks

About Security for System Administration Tasks

The system administration tasks that can be performed using SAS Management Console affect the stability of your servers, the integrity of your data and metadata, and the performance of client applications. Therefore, it is important to limit access to system administration tasks to only those users who:

have the necessary skills, background, and knowledge

need to perform system administration tasks in order to fulﬁll their job functions

The security model for the SAS Intelligence Platform model enables you to control access to system administration tasks by adding users to administrative roles, adding users to groups, and granting permissions on metadata. If necessary, you can change the capabilities that are assigned to a role. You can also create new roles.

This chapter describes the group memberships, role memberships, and other criteria that are required for users to perform the system administration tasks that are documented in this guide. Requirements are provided for two different approaches to system administration:

centralized administration, which means that a single administrative user (or a small group of users) performs all administrative functions for your SAS deployment, with no division of responsibility

delegated administration, which means that various types of administrative functions for your SAS deployment are divided among different administrative users or groups of users

For some functions, the requirements are the same regardless of whether you are using centralized or delegated administration.

The requirements in this chapter reﬂect initial settings in a default installation. Role deﬁnitions and group membership might be conﬁgured differently at your site. For an in-depth description of the security model, or for information about modifying the security structure, see the SAS Intelligence Platform: Security Administration Guide.

34 Who Can Do What in the Metadata Manager Plug-in

Chapter 3

Who Can Do What in the Metadata Manager Plug-in

Use the following table to determine the group memberships, role memberships, and

other criteria that enable users to perform tasks in the Metadata Manager plug-in in SAS Management Console:

Table 3.1 Who Can Do What in the Metadata Manager Plug-in

Actions

Check the access state of the metadata server, metadata repositories, and repository manager

Create, register, and delete custom repositories

Change a repository’s properties, including the access mode, the location of users’ folders, and mapping for notes and documents

Stop, pause, or resume the metadata server

Continue to use all functions of SAS Management Console when the metadata server is paused to the Administration state

Requirements

Centralized Administration Approach

Membership in the SAS Administrators group

Membership in the

Unrestricted

Metadata Server:

role

Delegated Administration Approach

Membership in the

Management Console: Advanced

Membership in the

role.

Management Console: Advanced

and Metadata

Server: Operation

roles, and WriteMetadata permission on the Root folder of the SAS Folders tree.

Membership in the

Management Console: Advanced

and Metadata

Server: Operation

roles.

Analyze, repair, or upgrade metadata

Initialize or unregister a custom repository

Add, initialize, register, unregister, and delete a foundation repository.

Use the Backup Wizard Membership in the SAS Administrators group and

Membership in the SAS Administrators group,

speciﬁcation as an unrestricted user in adminUsers.txt, and an external user ID that can be authenticated on the metadata server host machine

credentials to start a workspace server (see “Requirements for Accessing a Standard Workspace Server” on page 37). For additional requirements, see Chapter 10, “Using the Backup Wizard in SAS Management Console,” on page 137.

1 These columns list minimum requirements. The Metadata Server: Unrestricted role

can be substituted for any of the roles and groups that are speciﬁed here.

2 Deleting or unregistering the foundation repository makes the metadata server unusable. These

actions should be taken only in special situations.

Who Can Do What

Who Can Do What in the Server Manager Plug-in 35

As a best practice, users who are members of the SAS Administrators group should be deﬁned as internal users (rather than external users) in metadata. For more information, and to understand what role memberships and permissions are derived from membership in this group, see “About Adding Users to the SAS Administrators Group” on page 36.

Who Can Do What in the Server Manager Plug-in

Use the following table to determine the group memberships, role memberships, and other criteria that enable users to perform tasks in the Server Manager plug-in in SAS Management Console:

Table 3.2 Who Can Do What in the Server Manager Plug-in

Actions

Create or update server metadata (except the SASMeta workspace server and the SASMeta DATA step batch server)

Validate servers (except the SASMeta workspace server)

Connect to servers and spawners and view the following tabs

Metadata server Connections and

Options tabs

Object spawner

OLAP server Connections, and

Options

Connect to servers and spawners (except the metadata server and the SASMeta workspace server) and view all tabs

Adjust the logging level for a server, spawner, or server process (except the metadata server)

Stop, pause, resume, or quiesce a server, spawner, or server process (except the metadata server and the SASMeta workspace server)

Refresh the object spawner

Options tab

Sessions,

tabs

Requirements

Centralized Administration Approach

Membership in the SAS Administrators group

Validation of a standard (non-pooled) workspace server also requires credentials to start a workspace server (see “Requirements for Accessing a Standard Workspace Server” on page 37).

Membership in the SAS Administrators group

Delegated Administration Approach

Membership in the

Management Console: Advanced

Validation of a standard (nonpooled) workspace server also requires credentials to start a workspace server (see “Requirements for Accessing a Standard Workspace Server” on page 37).

Membership in the

role

Management Console: Advanced

Administer permission on server metadata

role, and

36 About Adding Users to the SAS Administrators Group

Chapter 3

Actions

Centralized Administration Approach

Connect to the metadata server and view the

Clients,

Adjust the metadata server’s logging levels

Stop, pause, or resume the metadata server

Validate the SASMeta workspace server

Connect to the SASMeta workspace server and view tabs

Stop, pause, resume, or quiesce a process on the SASMeta workspace server

Loggers, and

Logs tabs

Membership in the SAS Administrators group

1 These columns list minimum requirements. The

Metadata Server: Unrestricted

Requirements

can be substituted for any of the roles and groups that are speciﬁed here.

2 To view tabs, you must right-click on the server or spawner and click

Delegated Administration Approach

Membership in the

Management Console: Advanced

and

Metadata Server: Operation

Membership in the

roles

Management Console: Advanced

ReadMetadata and Administer permission on the SASMeta workspace server

role; and

Connect.

role

As a best practice, users who are members of the SAS Administrators group should

be deﬁned as internal users (rather than external users) in metadata.

For more information, and to understand what role memberships and permissions

are derived from membership in this group, see the next topic.

About Adding Users to the SAS Administrators Group

When you add a user to the SAS Administrators group, the user derives the following

memberships and permissions (if the group’s initial settings have not been changed):

membership in the

membership in the Metadata Server: Operation

membership in the

required in order to perform most actions in the User Manager plug-in.

WriteMetadata permission on the Root folder of the SAS Folders tree

Administer permission on server metadata

ReadMetadata on server metadata in the SASMeta context

If you use a centralized (rather than delegated) approach to system administration, then the SAS Administrators group provides a convenient mechanism for enabling users to perform administrative tasks. Centralized administration means that a single administrative user (or a small group of users) performs all administrative functions for your SAS deployment, with no division of responsibility.

As a best practice, users who are members of the SAS Administrators group should

be deﬁned as internal users (rather than external users) in metadata whenever possible. For details about creating administrative users, see “Add Administrators” in the SAS Intelligence Platform: Security Administration Guide.

Metadata Server: Advanced

role

Metadata Server: User Administration

role. This role is

Who Can Do What

Clearing the Credentials Cache 37

Requirements for Accessing a Standard Workspace Server

Special rights are required for tasks that involve running processes on a standard (non-pooled) workspace server. In SAS Management Console, these tasks include the following:

validating a workspace server

using the Backup Wizard

using the Import SAS Package and Export SAS Package wizards or the batch promotion tools to import or export physical content that is associated with stored processes, tables, jobs, libraries, or external ﬁles

The requirements for performing these tasks depend on which authentication method is used and which server is being accessed:

If you use host (credential-based) authentication, the following requirements must be met:

The user’s account must be known to the workspace server host. On Windows, the account must have rights to host machine. Typically, you would add the user to an operating system group that has this right (for example, the SAS Server Users group).

The user’s account must correspond to a metadata identity that has the ReadMetadata permission for the server deﬁnition.

Log on as a batch job

on the

If you use Integrated Windows authentication (IWA), the following requirements must be met:

The user’s account must be known to the workspace server host. It is not necessary to have rights to

The user’s account must correspond to a metadata identity that has the

Log on as a batch job

ReadMetadata permission for the server deﬁnition.

Integrated Windows authentication must be selected in the connection proﬁle that the user uses to log on to SAS Management Console. In addition, Integrated Windows authentication must be fully conﬁgured on the workspace server.

If the workspace server is conﬁgured to use SAS token authentication, then no credentials on the workspace server host are necessary. The user can log on to SAS Management Console with either an internal account or an external account. The account must correspond to a metadata identity that has the ReadMetadata permission for the server deﬁnition.

If you are using a workspace server that is part of the metadata server context (for example, SASMeta), then the user must also be a member of the SAS Administrators group. The use of this server is limited to metadata server administration tasks such as using the Backup and Restore Wizard and using the Import SAS Package and Export SAS Package wizards.

For detailed information about conﬁguring and using the authentication methods for SAS servers, see the SAS Intelligence Platform: Security Administration Guide.

Clearing the Credentials Cache

If a user is denied access when trying to connect to or validate a server or spawner, and the user’s credentials are then updated to allow access, the credentials cache must

38 Clearing the Credentials Cache

be cleared before the user tries to connect again. To clear the credentials cache, click

File

Clear Credentials Cache

If the object spawner denies access to a server because of the lack of ReadMetadata

permissions, and the user is then granted the needed permission, you must reset the object spawner’s authorization cache before the user tries to connect again. To do so, expand the Server Manager tree in SAS Management Console. Next, expand the object spawner, right-click the host node, and click right-click the host node again, and click

Chapter 3

in SAS Management Console.

Connect. After you have connected,

Refresh Spawner

CHAPTER

What to Do Next: Administration Tasks

Overview of Administration Tasks First-Priority Setup Tasks

Summary of First-Priority Setup Tasks Recommended Operating System Protections for Windows Machines

Default Operating System Protections for UNIX and z/OS Machines Standard Setup Tasks 43 Optional Setup Tasks Ongoing System Administration Tasks Best Practices for Ensuring the Integrity of Your System

Allow Only the Metadata Server to Access Your Metadata Repositories

Use Best Practices for Working with SAS Folders

Overview of Administration Tasks

Before you perform the administration tasks that are outlined in this chapter, you

should have successfully completed the following tasks:

Use the SAS Deployment Wizard to install and conﬁgure your software on each

machine in your environment.

Complete the post-installation tasks that are described in your

Instructions.html ﬁle, which is located in the Documents subdirectory of your

conﬁguration directory. These tasks include performing manual conﬁguration

steps (if applicable), validating your SAS servers, validating your Web

applications, and backing up your system.

After the SAS Intelligence Platform has been installed, conﬁgured, and validated, you will have a functional system. You can now begin performing administration tasks that are necessary to fully implement the SAS Intelligence Platform in your environment. These include the following categories of tasks:

ﬁrst-priority setup tasks that are necessary to protect the integrity of your system.

You should perform these tasks ﬁrst, as soon as possible after you have completed

your installation.

standard setup tasks that enable the users in your organization to begin using

SAS Intelligence Platform client applications to access and analyze your data.

optional setup tasks that you might want to perform to address speciﬁc

requirements in your environment.

ongoing tasks to keep the SAS Intelligence Platform operational.

40 First-Priority Setup Tasks

Chapter 4

First-Priority Setup Tasks

Summary of First-Priority Setup Tasks

The following tasks are necessary to protect the integrity of your system. Complete

these steps as soon as possible after installation, before you complete any of the other tasks that are outlined in this chapter.

Table 4.1 First-Priority Setup Tasks

Task Description

Secure the SAS conﬁguration on each server machine.

Establish a formal, regularly scheduled backup process.

For a secure deployment, the conﬁguration directory on each server machine must be protected by operating system controls. These controls will prevent inappropriate access to repository data sets, server scripts, server logs, and conﬁguration ﬁles.

On Windows systems, all conﬁguration directories, ﬁles, and scripts are owned by the user who performs the installation. You must update the permissions as shown in “Recommended Operating System Protections for Windows Machines” on page 40. These recommendations assume that your SAS servers and spawners run as services under the Local System account.

On UNIX and z/OS systems, the SAS Deployment Wizard automatically applies the appropriate permissions. The default permissions are shown in “Default Operating System Protections for UNIX and z/OS Machines” on page 42.

Establish a formal, regularly scheduled backup process that includes your metadata repositories as well as the associated physical ﬁles.

SAS provides backup and restore utilities that enable you to perform correct backups and restores of your metadata repositories, the repository manager, the metadata journal ﬁle, and the metadata server conﬁguration ﬁles while minimizing disruptions in service. It is important to also back up the physical data that is associated with the metadata so that related information will be synchronized if a restore becomes necessary.

Before you back up your SAS Intelligence Platform, read Chapter 9, “Best Practices for Backing Up and Restoring Your System,” on page 123.

Recommended Operating System Protections for Windows Machines

On Windows server machines, we recommend that you apply the following operating

system protections to your conﬁguration directory. All of these directories are located in

SAS-conﬁguration-directory\Lev1.

What to Do Next: Administration Tasks

Recommended Operating System Protections for Windows Machines 41

Table 4.2 Recommended Operating System Protections on Windows

Directories Users Recommended

Permissions

SYSTEM and

SAS-conﬁguration-directory\Lev1

Lev1 subdirectories: Documents, ReportBatch, SASApp, SASMeta, Utilities, Web

Lev1 subdirectories: ConnectSpawner, Logs, ObjectSpawner, SASApp\OLAPServer, SASMeta\MetadataServer, SASTS, ShareServer

SASApp subdirectories : PooledWorkspaceServer, StoredProcessServer

SASApp subdirectories: ConnectServer\Logs, Data\wrsdist, Data\wrstemp, PooledWorkspaceServer\Logs, PooledWorkspaceServer\sasuser, StoredProcessServer\Logs , StoredProcessServer\sasuser, and WorkspaceServer\Logs

SASMeta\WorkspaceServer\Logs

sasv9_meta.cfg ﬁle SYSTEM and

SASMeta subdirectories: MetadataServer, MetadataServer\rposmgr, MetadataServer\MetadataRepositories

\Foundation

Backup destination (for example, SASMeta\MetadataServer\SASBackup)

Administrators

All other users List Folder Contents,

SYSTEM and Administrators

SYSTEM, Administrators, and SAS Spawned Servers (sassrv)

Administrators

The user who backs up the metadata server. You can add this user to the Administrators group to provide the required access.

Full ControlSAS-conﬁguration-directory

Read

Full Control

Remove all other users and groups

Full Control

Remove all other users and groups

Full Control

Read and Write

Remove all other users and groups

Full Control

Note:

These recommendations assume that your SAS servers and spawners run as

services under the Local System account. If servers and spawners are run under a

different account, then grant that account the permissions that are recommended

for SYSTEM.

You might have selected the custom installation option to place all of your log ﬁles

in a single directory. If you selected this option, then you will need to grant the

SAS Spawned Servers (sassrv) user Full Control of the central log destination (for

example, SAS-conﬁguration-directory

If users will be using SAS Enterprise Guide to create stored processes, then the

\Lev1\Logs).

SAS Spawned Servers (sassrv) account must have Write access to the directory in

which stored processes will be stored.

If you enable logging for a workspace server, then you will need to grant all users

of the workspace server Full Control of the log directory. (See “Create a Log File

for Workspace Server Troubleshooting” on page 112).

42 Default Operating System Protections for UNIX and z/OS Machines

For information about backups, see Chapter 10, “Using the Backup Wizard in SAS

Management Console,” on page 137 and Chapter 11, “Using the %OMABAKUP Macro to Perform Backups and Restores,” on page 147.

For details about the conﬁguration directory structure, see “Overview of the

Conﬁguration Directory Structure” on page 19.

Default Operating System Protections for UNIX and z/OS Machines

The following table shows the default operating system protections that are provided

automatically for conﬁguration directories on UNIX and z/OS machines. All of these directories are located in

Table 4.3 Default Operating System Protections on UNIX and z/OS

Directories Users Default Permissions

SAS-conﬁguration-directory

SAS-conﬁguration-directory/Lev1

Lev1 subdirectories: Documents, ReportBatch, SASApp, SASMeta, Utilities, Web

Lev1 subdirectories: ConnectSpawner, Logs, ObjectSpawner, SASApp/OLAPServer, SASMeta/MetadataServer, SASTS, ShareServer

PooledWorkspaceServer, StoredProcessServer

Data/wrsdist, Data/wrstemp, PooledWorkspaceServer/Logs, PooledWorkspaceServer/sasuser, StoredProcessServer/Logs , StoredProcessServer/sasuser, and WorkspaceServer/Logs

SAS-conﬁguration-directory

Chapter 4

/Lev1.

SAS Installer Read, Write, and Execute

All other users Read and Execute

SAS Installer Read, Write, and Execute

All other users No access

SAS Installer Read, Write, and ExecuteSASApp subdirectories :

sas group Read and Execute

SAS Installer Read, Write, and ExecuteSASApp subdirectories : ConnectServer/Logs,

sas group Read, Write, and Execute

SASMeta/WorkspaceServer/Logs

SAS Installer Read and Writesasv9_meta.cfg ﬁle

All other users no access

Note:

Make sure that the SAS Spawned Servers account (sassrv) is a member of the sas group, which has the necessary permissions to server conﬁguration ﬁles and log directories.

You might have selected the custom installation option to place all of your log ﬁles in a single directory. If you selected this option, then you will need to grant either the sas group or the SAS Spawned Servers (sassrv) user Read, Write, and Execute permission on the central log destination (for example,

SAS-conﬁguration-directory

/Lev1/Logs).

What to Do Next: Administration Tasks

If users will be using SAS Enterprise Guide to create stored processes, then the

Standard Setup Tasks 43

SAS Spawned Servers (sassrv) account must have Write access to the directory in

which stored processes will be stored.

If you enable logging for a workspace server, then you will need to grant all users

of the workspace server Read, Write, and Execute permission on the log directory.

(See “Create a Log File for Workspace Server Troubleshooting” on page 112).

The user who backs up the metadata server must have full access to

SAS-conﬁguration-directory

rposmgr

and

MetadataRepositories/Foundation, and to the backup destination

(for example, SAS-conﬁguration-directory

SASBackup

). The SAS Installer user has the required access.

/Lev1/SASMeta/MetadataServer, to its subdirectories

/Lev1/SASMeta/MetadataServer/

CAUTION:

Do not run a backup or a restore as the Root user. Doing so will change ownership of the metadata server ﬁles.

For more information, see Chapter 10, “Using the Backup Wizard in SAS

Management Console,” on page 137 and Chapter 11, “Using the %OMABAKUP

Macro to Perform Backups and Restores,” on page 147.

For details about the conﬁguration directory structure, see “Overview of the

Conﬁguration Directory Structure” on page 19.

Standard Setup Tasks

The following administration tasks are essential to enable the users in your organization to begin using SAS Intelligence Platform client applications to access and analyze your data.

44 Optional Setup Tasks

Table 4.4 Standard Setup Tasks

Task Description

Chapter 4

Add users and manage access.

Establish connectivity to your data sources.

Set up your metadata folder structure.

Standard security setup activities include the following:

creating SAS administrators and regular SAS users

managing access to metadata, data, and application functionality

For details, see “Security Tasks” in the SAS Intelligence Platform: Security Administration Guide.

To enable the client applications in the SAS Intelligence Platform to access your data sources (including SAS data sets, third-party relational databases, and data from Enterprise Resource Planning systems), you must create metadata objects that represent your data. For example, to enable users to access data in a library of SAS data sets, you must deﬁne metadata objects that represent the SAS library and each of the tables in the library. For details, see “Connecting to Common Data Sources” in the SAS Intelligence Platform: Data Administration Guide.

SAS Intelligence Platform clients use a hierarchy of SAS folders to store metadata for content such as libraries, tables, OLAP schemas, jobs, information maps, and reports. The initial structure provides private folders for individual users and provides a separate area for shared data. Within these folders, you should create a customized folder structure that meets your speciﬁc needs. For details, see Chapter 16, “Working with SAS Folders,” on page 197.

Note: Be sure to secure access to the folders as described in the SAS Intelligence Platform: Security Administration Guide.

Optional Setup Tasks

It might be necessary for you to modify your initial conﬁguration to meet speciﬁc requirements in your environment. Optional administration and conﬁguration tasks include the following.

Table 4.5 Optional Setup Tasks

Task Description

Optimize the

performance and

reliability of the

metadata server.

The following are some steps that you might need to take to optimize the performance and reliability of the metadata server:

Move the metadata server journal ﬁle to another ﬁle system (see “Move the Journal File to Another File System” on page 171).

Adjust the maximum number of threads used by the metadata server (see “Conﬁguring the Number of Threads Used by the Metadata Server” on page 167).

For other performance-related tasks, see Chapter 14, “Managing Metadata Server Performance,” on page 173.

What to Do Next: Administration Tasks

Optional Setup Tasks 45

Modify the

conﬁguration of your

processing servers.

The following are some server conﬁguration changes that you might want to make for performance optimization or other reasons:

Deﬁne a cluster of load-balanced workspace servers in order to balance a load across workspace servers that you have installed on multiple hosts. This type of conﬁguration is most useful when you have a large number of users (such as data integration specialists) using a workspace server for relatively long-running jobs. For details, see “Understanding Server Load Balancing” in the

SAS

Intelligence Platform: Application Server Administration Guide.

Modify load balancing or algorithms for stored process servers and pooled workspace servers. For details, see “Modify Logical Pooled Workspace or Logical Stored Process Server Load-Balancing Properties” in the SAS Intelligence Platform: Application Server Administration Guide.

If your SAS server metadata contains characters other than those typically found in the English language, then you must start your SAS server with an ENCODING= or LOCALE= system option that accommodates those characters. For details, see “Encoding and Locale Information” in the SAS Intelligence Platform: Application Server Administration Guide.

If you will be submitting large jobs (for example, JAVA GRAPH jobs) on z/OS servers, then you might need to specify a larger region size. For details, see “Managing Memory” in the SAS Companion for z/ OS.

Optimize Web

application

performance.

For information about conﬁguring middle-tier components for better efﬁciency and performance, see “Best Practices for Conﬁguring Your Middle Tier” in the SAS Intelligence Platform: Web Application Administration Guide.

Adjust server logging. You can change your server conﬁgurations to obtain additional logging

information for troubleshooting, performance management, or other purposes. For details, see Chapter 8, “Administering Logging for SAS Servers,” on page 103 and SAS Logging: Conﬁguration and Programming Reference.

Enable job and report

scheduling.

To enable SAS scheduling features, you can install and conﬁgure scheduling software, conﬁgure operating system scheduling, or conﬁgure in-process scheduling. For details, see Scheduling in SAS.

46 Ongoing System Administration Tasks

Task Description

Increase Java heap memory allocation for desktop applications.

Chapter 4

To process large amounts of data, you might need to modify the Java heap memory allocation that is conﬁgured for SAS Management Console, SAS Data Integration Studio, SAS OLAP Cube Studio, and SAS Information Map Studio. For details, see “Managing the Java Heap Used By Desktop Applications” in the

Administration Guide.

SAS Intelligence Platform: Desktop Application

Set up change management for SAS Data Integration Studio users.

Collect ARM log information for SAS Data Integration Studio batch jobs.

If you want to implement change management for SAS Data Integration Studio, then you must set up project repositories and at least one change-managed folder. For details, see “Administering Data Integration Studio” in the SAS Intelligence Platform: Desktop Application Administration Guide.

If you want to collect ARM log information for SAS Data Integration Studio jobs that are run on a batch basis, then you must enable logging for the batch server that executes the jobs. For details, see .

Ongoing System Administration Tasks

The following table lists important system administration tasks that you need to perform on an ongoing basis to keep the SAS Intelligence Platform operational.

Table 4.6 Ongoing System Administration Tasks

Task Documentation Reference

Start, stop, pause, resume, and refresh the servers that are used in the system.

Chapter 5, “Operating Your Servers,” on page 51

Check the status of a server of or of a metadata repository.

Monitor the activity of servers.

Perform regular full backups of the metadata server.

Use server logs and conﬁgure logging options.

Create a new metadata repository.

Promote individual metadata objects or groups of objects.

Chapter 6, “Checking the Status of Servers,” on page 75

Chapter 7, “Monitoring the Activity of SAS Servers,” on page 87

Chapter 9, “Best Practices for Backing Up and Restoring Your System,” on page 123

Chapter 8, “Administering Logging for SAS Servers,” on page 103 and SAS

Logging: Conﬁguration and Programming Reference

Chapter 15, “Creating, Registering, Moving, Copying, Renaming, and Deleting SAS Metadata Repositories,” on page 181

Chapter 17, “Using the Promotion Tools,” on page 213

Note: The preceding table includes only the tasks that are documented in this guide. Other important administration tasks are described in the following documents:

What to Do Next: Administration Tasks

SAS Intelligence Platform: Security Administration Guide. In this guide, you can

Use Best Practices for Working with SAS Folders 47

use the “Checklists for a More Secure Deployment” to ensure that your environment remains secure on an ongoing basis.

SAS Intelligence Platform: Data Administration Guide.

SAS Intelligence Platform: Application Server Administration Guide.

SAS Intelligence Platform: Desktop Application Administration Guide.

SAS Intelligence Platform: Web Application Administration Guide.

Scheduling in SAS.

SAS/SHARE User’s Guide.

SAS/CONNECT User’s Guide.

To access these documents, go to

http://support.sas.com/92administration.

Best Practices for Ensuring the Integrity of Your System

Allow Only the Metadata Server to Access Your Metadata Repositories

The MetadataRepositories and SAS conﬁguration directory, are critical to the operation of your system. These data sets contain metadata that deﬁnes your servers, users, access levels, enterprise data sources, and data structures. They also contain metadata for resources that are created and used by SAS applications, including information maps, OLAP cubes, report deﬁnitions, stored process deﬁnitions, and jobs.

To safeguard the integrity of your system:

Never move, delete, modify, or directly read the data sets in the

MetadataRepositories and rpsomgr

accessed only by metadata server processes.

Do not place other ﬁles in these directories.

Back up the contents of these directories regularly, as described in Chapter 9, “Best Practices for Backing Up and Restoring Your System,” on page 123.

rpsomgr subdirectories, which are located in the

directories. These data sets should be

Use Best Practices for Working with SAS Folders

The folders that appear in the client applications to store business intelligence content and system information. Inappropriate renaming, deleting, or moving of these folders or their contents could cause client applications to malfunction.

When interacting with folders in SAS Management Console, be sure to follow the best practices that are provided in Chapter 16, “Working with SAS Folders,” on page

197. If you need to move or copy the contents of these folders, use the procedures that are provided in Chapter 17, “Using the Promotion Tools,” on page 213.

Folders tab of SAS Management console are used by

PART

Starting, Stopping, and Checking the Status of Servers

Chapter 5..........

Chapter 6..........

Operating Your Servers

Checking the Status of Servers

CHAPTER

Operating Your Servers

Overview of Server Operation

About Required Servers Starting Servers in the Correct Order About Server Start-up Parameters About SAS Metadata Server States

Summary of Procedures for Server Operation 54 Running Servers as Windows Services Starting and Stopping SAS Servers on z/OS Using the sas.servers Script on UNIX or z/OS to Start or Stop All Servers

About the sas.servers Script

Use the sas.servers Script to Start, Stop, or Restart All Servers or to Display the Status of

Servers

Using generate_boot_scripts.sh to Regenerate the sas.servers Script 59

Install sas.servers as a Boot Script 60 Running Servers as UNIX Daemons 61 Using Scripts to Operate SAS Servers Individually 61

About Using Scripts to Operate Servers 61

Use Individual Scripts to Operate the SAS Metadata Server, SAS Object Spawner, SAS OLAP

Server, and SAS Table Server Use Individual Scripts to Operate Servers and Spawners 63 Starting or Stopping the SAS Services Application 64

Using SAS Management Console to Operate SAS Servers 65

Obtain the Appropriate User Credentials, and Clear Cached Credentials (If Necessary) 65 Use SAS Management Console to Stop, Pause, Resume, or Reset the SAS Metadata Server 65 Use SAS Management Console to Stop, Pause, Resume, Quiesce, or Refresh the SAS Object

Spawner Use SAS Management Console to Stop, Pause, Resume, Quiesce, or Refresh the SAS OLAP

Server Use SAS Management Console to Control Processes on Servers 68

Starting and Stopping Web Application Servers 69

Starting or Stopping a JBoss Application Server 69 Starting or Stopping an IBM WebSphere Application Server or an IBM WebSphere Application

Server Network Deployment (ND)

Starting or Stopping an Oracle WebLogic Server 72

About generate_boot_scripts.sh 59 About the server-name.srv Files 60 Regenerate the sas.servers Script 60

Starting or Stopping an IBM WebSphere Application Server or an IBM WebSphere

Application Server Network Deployment (ND) on Windows or UNIX

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

z/OS

52 Overview of Server Operation

Chapter 5

Overview of Server Operation

About Required Servers

In order for clients to access the SAS Intelligence Platform, the following components

must be running on network-accessible machines:

a SAS Metadata Server

the SAS object spawner, which acts as a listener for SAS Workspace Servers, SAS Pooled Workspace Servers, and SAS Stored Process Servers

Depending on which SAS products you have installed, one or more instances of the following additional components might also be required to be running on network-accessible machines: SAS OLAP Server, SAS Table Server, SAS Services Application (also referred to as Remote Services), SAS/CONNECT spawner, SAS/ SHARE server, SAS Content Server, and a Web application server.

If you want to use the SAS Deployment Tester utility, then the SAS Deployment Tester server must also be running.

Starting Servers in the Correct Order

Because of dependencies, it is important to start the servers in the correct order. Server dependencies are shown in the following table:

Server Server Dependencies

SAS Metadata Server None

SAS OLAP Server SAS Metadata Server

SAS object spawner SAS Metadata Server

SAS Table Server SAS Metadata Server

SAS Services Application (Remote Services) SAS Metadata Server

Web application server SAS Services Application (Remote Services)

SAS/CONNECT spawner SAS Metadata server

SAS/SHARE server SAS Metadata server

SAS Deployment Tester server None

The following start-up order meets the dependency requirements:

1 Start the SAS Metadata Server.

2 Start the SAS OLAP Server.

3 Start the SAS object spawner.

4 Start the SAS/SHARE server

5 Start the SAS/CONNECT spawner.

6 Start the SAS Table Server.

7 Start the SAS Services Application (Remote Services).

Operating Your Servers

8 Start the SAS Deployment Tester server.

Start the Web application server. (The SAS Content Server starts automatically

About SAS Metadata Server States 53

when the application server is started.)

Servers should be stopped in the inverse order, with the metadata server stopped last.

About Server Start-up Parameters

The start-up parameters for SAS servers are stored in conﬁguration ﬁles. For a list of these conﬁguration ﬁles and their locations, see “Reference: Conﬁguration Files for SAS Servers” on page 271.

For detailed information about start-up parameters for each server, see the documentation references in the table in “Summary of Procedures for Server Operation” on page 54.

About SAS Metadata Server States

A SAS Metadata Server can exist in any of the following states:

Online

The metadata server is available to accept client requests from authenticated users.

External systems such as Windows Services Manager report the Online state as

running or started.

Ofﬂine

The metadata server is paused and is not available to accept client requests. When the metadata server is paused to Ofﬂine status, the server does the following:

retains all active client connections.

temporarily changes the access state of all repositories to Ofﬂine.

temporarily stops receiving client requests to read or write metadata. If a client application submits a new request, the client displays a message indicating that the server is paused.

ﬂushes updated metadata from the server’s memory and writes the updated metadata to the metadata repository.

closes the SAS data sets that serve as repository containers.

Utilities such as the Backup Wizard automatically pause the metadata server to the Ofﬂine state because they require repository containers to be closed. The Ofﬂine state is also useful if you need to disable users’ access while you perform maintenance on the metadata server machine.

External systems such as Windows Services Manager report the Ofﬂine state as

paused.

Administration

The metadata server is paused and will accept requests only from an unrestricted administrative user. When the metadata server is paused to Administration status, the server does the following:

retains all active client connections.

temporarily stops receiving client requests to read or write metadata, except for requests from users in the

Metadata Server: Unrestricted role. (For

information about this role, see “About User Roles for System

54 Summary of Procedures for Server Operation

Administration” on page 24). If the user is not unrestricted, then the client

displays a message indicating that the server is paused.

The Administration state is useful when you need to disable users’ access while

you connect to the metadata server to perform administrative tasks such as the following:

run diagnostic and repair tools

upgrade metadata to a new version

promote metadata and related content

modify metadata for components of a SAS Application Server

External systems such as Windows Services Manager report the Administration state as

paused.

Stopped

The Stopped state terminates the SAS Metadata Server process and breaks all client connections. The metadata server, and all SAS servers that depend on it, must be started before clients can connect again.

Chapter 5

Summary of Procedures for Server Operation

To operate servers in SAS Management Console, you must have the appropriate user credentials. To determine what credentials are required for each task, see Chapter 3, “Who Can Do What: Credential Requirements for SAS Management Console Tasks,” on page 33.

The following table summarizes the server operation methods for each server. For detailed information about startup parameters for each server, see the documentation references that are provided in the last column.

Server Type

SAS Metadata Server, SAS OLAP Server, and SAS object spawner

Available Methods for Server Operation

Windows service

z/OS started task

sas.servers script3(UNIX or z/OS)

Individual server script (or Windows shortcut)

SAS Management Console (except startup)

Documentation Location for Startup Parameters

Appendix 5, “Options for the Metadata Server Invocation Command,” on page 289

“System Options for Application Server Components” in the SAS

Intelligence Platform: Application Server Administration Guide

“Spawner Invocation Options” in the

SAS Intelligence Platform: Application Server Administration Guide

SAS Workspace Server, SAS Pooled Workspace Server, and SAS Stored Process Server

Started by the object spawner

SAS Management Console (except startup)

“System Options for Application Server Components” in the SAS

Intelligence Platform: Application Server Administration Guide

Operating Your Servers

Running Servers as Windows Services 55

Server Type

SAS Table Server

SAS Services

Application

(Remote

Services)

Web application

server

SAS Content

Server

SAS/CONNECT

spawner, SAS/

SHARE server,

and SAS

Deployment

Tester server

Available Methods for Server Operation

Windows service

z/OS started task

sas.servers script

(UNIX or

z/OS)

Individual server script (or Windows shortcut)

SAS Management Console

Windows service

z/OS started task

sas.servers script

(UNIX or

z/OS)

Remote Services script (or Windows shortcut)

Server console or script

Windows service (JBoss and Oracle WebLogic only)

Starts automatically when the Web application server is started

Windows service

z/OS started task

sas.servers script3(UNIX or

z/OS)

Script (or Windows shortcut)

Documentation Location for Startup Parameters

SAS Intelligence Platform: Web Application Administration Guide

Communications Access Methods for SAS/CONNECT and SAS/SHARE

SAS/SHARE User’s Guide

1 On Windows systems, this is the recommended method.

2 On z/OS systems, this is the recommended method.

3 On UNIX systems, this is the recommended method.

For details about the server operation procedures that are summarized in this table,

see the remaining topics in this chapter.

Running Servers as Windows Services

On Windows systems, depending on the options that were selected during the installation process, the following might be installed as services: the SAS/CONNECT spawner, the SAS Metadata Server, the SAS object spawner, the SAS OLAP Server, the SAS Services Application (Remote Services), the SAS Table Server, the SAS/SHARE server, and the SAS Deployment Tester server. This installation option is highly recommended. If these servers have been installed as services, then they start automatically when you restart the machines. To ensure that services are always started in the correct order, the required dependencies are built into the services.

The JBoss Application Server also might be installed as a service. This service is set up to be started manually.

56 Running Servers as Windows Services

The third maintenance release for SAS 9.2 includes scripts for installing the Oracle

WebLogic Managed Server and WebLogic Administration Server as Windows services. You can install these services by following instructions that are provided in the Instructions.html ﬁle, which is located in

Documents

. After you install the services, they will start up automatically when you

restart the machine.

For each service, the following table shows the built-in dependencies and the actions

that you can take from within Windows Services Manager:

Server Dependencies Available Net Commands

SAS Metadata Server None Start, stop, pause, and continue

SAS OLAP Server Metadata server Start, stop, pause, and continue

SAS object spawner Metadata server Start, stop, pause, and continue

Chapter 5

SAS-conﬁguration-directory

/Levn/

SAS Services Application (Remote Services)

SAS Table Server Metadata server Start, stop, pause, and continue

SAS/CONNECT spawner Metadata server Start and stop

SAS/SHARE server Metadata server Start and stop

SAS Deployment Tester server None Start and stop

JBoss Application Server SAS Services Application

Oracle WebLogic Administration Server

Oracle WebLogic Managed Server

Metadata server Start and stop

Start and stop

(Remote Services)

None Start and stop

Oracle WebLogic Administration Server

Start and stop

The service names have the following format:

SAS [deployment-name-and-level] <server-context -> server-name

For example, your services might be displayed in Windows Services Manager as

follows:

SAS [Config-Lev1] Deployment Tester Server SAS [Config-Lev1] Object Spawner SAS [Config-Lev1] Remote Services SAS [Config-Lev1] SASApp - OLAP Server SAS [Config-Lev1] SASMeta - Metadata Server SAS [Config-Lev1] SASTS - Table Server

If you installed the JBoss Application Server as a service, the service is displayed as

JBoss - SASServer1. If you installed the WebLogic Administration Server and

WebLogic Managed Server as services, the service names consist of the domain name, the server name, and the conﬁguration directory path, as in the following examples:

SASDomain AdminServer (sas.Config.Lev1) and SASDomain SASServer1 (sas.Config.Lev1)

SAS provides batch scripts that you can use to manage these services from the

command line (see “Using Scripts to Operate SAS Servers Individually” on page 61). You can also use the Windows Net command, which has the following syntax:

net start|stop|pause|continue "service-name"

Operating Your Servers

For example, if the service name for the object spawner is SAS [Config-Lev1]

Object Spawner

You would use the following command to stop the service:

net stop "SAS [Config-Lev1] Object Spawner"

You would use the following command to start the service:

net start "SAS [Config-Lev1] Object Spawner"

Starting and Stopping SAS Servers on z/OS

On z/OS systems, the SAS Deployment Wizard initially starts the SAS servers under UNIX System Services (USS) by using scripts that are provided for each server. After the initial installation and conﬁguration has been completed and validated, SAS recommends that you stop the servers and restart them as started tasks.

The SAS Deployment Wizard creates started task deﬁnitions for each server. The deﬁnitions are stored in tasks, see the instructions.html document that is created by the SAS Deployment Wizard.

After the started tasks are deployed, you can operate your servers as follows:

1 Log on as the SAS Installer user (for example, sas).

To start a server, use the following console command:

SAS-installation-location.W0.SRVPROC. To deploy the started

Starting and Stopping SAS Servers on z/OS 57

START started-task-name

To stop a server, use the following console command.

STOP started-task-name

Note:

You can perform the equivalent of a restart by stopping and then starting a server.

Stopping the metadata server stops other components, including object spawners, OLAP servers, table servers, SAS/CONNECT spawners, and SAS/ SHARE servers.

Messages are written to the system log when the SAS Metadata Server, the SAS OLAP Server, or the SAS/SHARE server is started or stopped. Automated tools can scan the system log to determine the current operational state of these servers. The log messages are displayed with the preﬁx

SAH, as shown in the

following examples:

SAH011001I SAS (9.2) Metadata Server <(port-number)>, State, starting SAH011999I SAS (9.2) Metadata Server <(port-number)>, State, running SAH019001I SAS (9.2) Metadata Server <(port-number)>, State, stopping SAH019999I SAS (9.2) Metadata Server <(port-number)>, State, stopped

When servers are running under USS, you can start and stop the servers as follows:

by using individual scripts that are provided for each server. See “Using Scripts to Operate SAS Servers Individually” on page 61.

by using the sas.servers script. See “Using the sas.servers Script on UNIX or z/OS to Start or Stop All Servers” on page 58.

These methods are not recommended for production environments.

For more information about using SAS on z/OS, see the SAS Companion for z/OS.

58 Using the sas.servers Script on UNIX or z/OS to Start or Stop All Servers

Chapter 5

Using the sas.servers Script on UNIX or z/OS to Start or Stop All Servers

About the sas.servers Script

During installation, the SAS Deployment Wizard creates a sas.servers script on each

UNIX and z/OS server tier machine. You can perform the following tasks with this script:

start, stop, or restart all of the SAS servers and spawners on the machine in the

correct order by using a single command

display the status of all the SAS servers and spawners on the machine by using a

single command

Note: To use the script on z/OS systems, you must run the servers under UNIX

System Services (USS). On z/OS systems, SAS recommends operating servers as started tasks. See “Starting and Stopping SAS Servers on z/OS” on page 57.

The script performs the preceding tasks for all instances of the following servers,

spawners, and services that are installed on the machine:

SAS Metadata Server

SAS object spawner

SAS OLAP Server

SAS/CONNECT spawner

SAS/SHARE server

SAS Table Server

SAS Services Application (Remote Services)

SAS Deployment Tester server

The sas.servers script is located in the top level of your conﬁguration directory. For example, in a Level 1 deployment, the script is located in the following path:

SAS-conﬁguration-directory

/Lev1/.

CAUTION:

You should not directly update the sas.servers script.

If the script needs to be updated (for example, to add new servers or remove servers), then regenerate the script by using generate_boot_scripts.sh.

Use the sas.servers Script to Start, Stop, or Restart All Servers or to Display the Status of Servers

To use the sas.servers script to start, stop, or restart all servers on a UNIX or z/OS

machine or to display the status of all servers on the machine, follow these steps:

1 Log on as the SAS Installer user (for example, sas). 2 Go to the directory SAS-conﬁguration-directory/Lev1/. 3 Type ./sas.servers followed by one of the following arguments:

start

starts the servers and spawners in the following order: SAS Metadata Server, SAS OLAP Server, SAS object spawner, SAS/SHARE server, SAS/CONNECT spawner, SAS Table Server, SAS Remote Services, SAS Deployment Tester server.

Operating Your Servers

Using generate_boot_scripts.sh to Regenerate the sas.servers Script 59

Note: The OLAP server, object spawner, SAS/SHARE server, SAS/CONNECT spawner, and table server require that the metadata server be running. If the metadata server is conﬁgured on a different host machine, make sure that the server is running before you use this script.

stop

stops the servers and spawners in the following order: SAS Deployment Tester server, SAS Remote Services, SAS Table Server, SAS/CONNECT spawner, SAS/ SHARE server, SAS object spawner, SAS OLAP Server, SAS Metadata Server.

Note:

When you stop the metadata server, any dependent servers and spawners (whether they are on the same host machine or a different machine) will stop running.

Before you stop an OLAP server, you should ﬁrst stop the active sessions, as follows:

In SAS Management Console, expand the

OLAP Server Monitor

2 Right-click the name of the logical SAS OLAP Server, and select

Connect.

3 In the dialog box that appears, enter your user name and password and

click

OK.

Right-click the name of each session that you want to close, and select

Close Session.

node.

Monitoring

node and the

SAS

restart

stops and then starts the servers and spawners in the following order: SAS Metadata Server, SAS OLAP Server, SAS object spawner, SAS/SHARE server, SAS/CONNECT spawner, SAS Table Server, SAS Remote Services.

status

displays the current status of the servers and spawners in the following format:

server-name server-instance

(process-ID) is running|is stopped

For example, the following messages mean that two instances of the SAS OLAP Server are conﬁgured on the machine. The ﬁrst instance is running, and the second instance is stopped:

SAS OLAP Server 1 (pid 29529) is running

SAS OLAP Server 2 (pid 29530) is stopped

Note: To use the script on z/OS systems, you must run the servers under UNIX System Services (USS). On z/OS systems, SAS recommends operating servers as started tasks. See “Starting and Stopping SAS Servers on z/OS” on page 57.

Using generate_boot_scripts.sh to Regenerate the sas.servers Script

About generate_boot_scripts.sh

The generate_boot_scripts.sh script enables you to automatically regenerate the sas.servers script for a particular UNIX or z/OS host machine. This feature is useful in the following types of situations:

60 Install sas.servers as a Boot Script

You have conﬁgured a new server or spawner on the machine. In this situation,

the script generation process detects the new server or spawner and adds it to the

sas.servers script.

You have removed a server or spawner conﬁguration from the machine. In this

situation, the script generation process detects the absence of the server or

spawner and removes it from the sas.servers script.

You want to remove a server or spawner from the script so that you can operate it

separately, or you want to add a server or spawner that you previously removed.

You have changed the location of the server’s log.

About the server-name.srv Files

On UNIX and z/OS systems, each server’s conﬁguration directory contains a ﬁle

called server-name.srv. For example, the metadata server’s conﬁguration directory contains a ﬁle called MetadataServer.srv, and the workspace server’s conﬁguration directory contains a ﬁle called WorkspaceServer.srv.

The generate_boot_scripts.sh script accesses each of the server-name.srv ﬁles to

determine which servers and spawners are to be included in the sas.servers script. If a server’s server-name.srv ﬁle contains the keyword ENABLE, then the server is included in the script. If the ﬁle contains the keyword DISABLE, then the server is excluded from the script.

In the initial conﬁguration, all server-name.srv ﬁles contain the keyword ENABLE. The server-name.srv ﬁles also contain the path to the server’s startup script and the

path to the server’s log ﬁles.

Chapter 5

Regenerate the sas.servers Script

To regenerate the sas.servers script, follow these steps:

1 Log on as the SAS Installer user (for example, sas).

If you want to remove a server or spawner from the script, or if you want to add a

server or spawner that you previously removed, follow these steps:

a Navigate to the server’s conﬁguration directory and open the ﬁle

server-name.srv in an editor.

For example, if you want to remove the SAS/SHARE server from the script, you would go to SAS-conﬁguration-directory open the ﬁle ShareServer.srv.

b Locate the line that contains the keyword ENABLE or DISABLE. If you want

to exclude the server from the sas.servers script, change the keyword to ENABLE. If you want to include the server in the sas.servers script, change the keyword to DISABLE. Save the ﬁle.

Go to the directory SAS-conﬁguration-directory/Lev1/.

4 Enter the following command:

./generate_boot_scripts.sh

A new sas.servers script is created to reﬂect the servers that are currently conﬁgured on the machine. If any of the server-name.srv ﬁles contain the keyword DISABLE, the following message appears:

<number-of-disabled-servers>

their .srv files

SAS servers were explicitly disabled in

/Lev1/ShareServer and

Install sas.servers as a Boot Script

On UNIX machines, you can choose to install the sas.servers script as a boot script so

that the servers will start automatically when you start the machine. The comments in

Operating Your Servers

the sas.servers script contain installation instructions that are tailored to your operating environment.

Use Individual Scripts to Operate Servers 61

Running Servers as UNIX Daemons

On UNIX systems, as an alternative to using the sas.servers script, you can conﬁgure

your system so that certain servers or spawners run as daemons. For example, to make the metadata server run as a daemon, you can copy the MetadataServer.sh script to the boot directory of your machine. Then add the needed information and links to the host’s start and stop commands so that the metadata server is started at boot time and stopped at shutdown time. For more information, see your UNIX system administrator or the system administration guide for your platform.

Using Scripts to Operate SAS Servers Individually

About Using Scripts to Operate Servers

The conﬁguration directory for each SAS server and spawner contains a script that

enables you to operate the server or spawner individually from a command line.

On Windows machines, depending on the options that were selected during

installation, the SAS Deployment Wizard might have also added shortcuts to your

Start menu to enable you to start, stop, pause and resume servers and spawners.

On UNIX and z/OS systems, you can use the sas.servers script to start and stop

servers with a single command (see “Using the sas.servers Script on UNIX or z/OS to Start or Stop All Servers” on page 58). On z/OS systems, SAS recommends operating servers as started tasks (see “Starting and Stopping SAS Servers on z/OS” on page 57).

For information about the startup parameters for each server, see the documentation

references that are provided in “Summary of Procedures for Server Operation” on page

54.

Use Individual Scripts to Operate the SAS Metadata Server, SAS Object Spawner, SAS OLAP Server, and SAS Table Server

You can use scripts to start, stop, pause, or resume the metadata server, an object

spawner, an OLAP server, or a table server from the DOS command line, the UNIX console, or the z/OS console. The scripts also enable you to install or remove a server or spawner as a Windows service and to display the server or spawner’s current status.

Note:

The metadata server must be running before you can start an object spawner, an

OLAP server, or a table server.

Before using scripts to operate the metadata server, see “About SAS Metadata

Server States” on page 53.

Follow these steps:

62 Use Individual Scripts to Operate Servers

1 On Windows, log on as a user who is a member of the host operating system’s

Administrators group. On UNIX or z/OS, log on as the SAS Installer user (for example, sas).

2 Use one of the following scripts, which are located in the path

SAS-conﬁguration-directory

Table 5.1 Scripts for Operating Servers and Spawners

Chapter 5

/Lev1:

Server or Spawner

SAS Metadata Server

SAS object spawner Windows: ObjectSpawner\ObjectSpawner.bat

SAS OLAP Server Windows: SASApp\OLAPServer\OLAPServer.bat

SAS Table Server Windows: SASTS\TableServer\TableServer.bat

1 Your installation might have different names for the

Script Name and Location

Windows: SASMeta\MetadataServer\MetadataServer.bat

UNIX and z/OS: SASMeta/MetadataServer/MetadataServer.sh

UNIX and z/OS: ObjectSpawner/ObjectSpawner.sh

1,2

UNIX and z/OS: SASApp/OLAPServer/OLAPServer.sh

1,2

UNIX and z/OS: SASTS/TableServer/TableServer.sh

1,2

SASApp directory.

2 In single-machine installations that were migrated from SAS 9.1.3, the default location

for the OLAP server script is

OLAPServer

on UNIX or z/OS.

SASMain\OLAPServer

on Windows and

SASMain/

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 or spawner as a Windows service.

-remove

removes the server or spawner service from Windows.

-start

starts the server or spawner.

Note: Before you start the object spawner, the OLAP server, or the table

server, make sure that the metadata server is running.

-stop

completely stops the server or spawner.

Note:

Stopping the metadata server stops other components, including object spawners, OLAP servers, table servers, SAS/CONNECT spawners, and SAS/SHARE servers.

Before you stop an OLAP server, you should ﬁrst stop the active sessions, as follows:

a In SAS Management Console, expand the Monitoring node and

the

SAS OLAP Server Monitor node.

b Right-click the name of the logical SAS OLAP Server, and select

Connect.

c In the dialog box that appears, enter your user name and password

and click

OK.

-restart

Operating Your Servers

d Right-click the name of each session that you want to close, and

Close Session

select

Use Individual Scripts to Operate Servers and Spawners 63

stops and then starts a running server or spawner.

-pause

causes the server or spawner to ﬁnish processing all active client sessions and to stop accepting new requests.

When this option is used with the metadata server, the server is placed in

the Ofﬂine state.

-resume

resumes the server or spawner process when it is in the paused state.

When this option is used with the metadata server, the server is returned

to the Online state if the current state is Ofﬂine or Administration.

-status

displays the current status of the server or spawner.

The metadata server script has two additional options:

-backup

executes the program backupServer.sas, which is located in your metadata server

startup directory. This program pauses the metadata server and copies your

metadata repositories, the repository manager, the metadata journal ﬁle, and the

metadata server’s conﬁguration ﬁles to a subdirectory called

SASBackup in the

metadata server’s conﬁguration directory. For details about this and other

methods of performing backups, see “About the Metadata Server Backup and

Restore Utilities” on page 124.

CAUTION:

For production backups and restores, it is highly recommended that you follow the best practices that are provided in Chapter 9, “Best Practices for Backing Up and Restoring Your System,” on page 123.

-restore

executes the program restoreServer.sas, which is located in your metadata server

startup directory. This program pauses the metadata server and copies your

metadata repositories, the repository manager, the metadata journal ﬁle, and the

metadata server’s conﬁguration ﬁles from the backup directory to the metadata

server conﬁguration directory. For details about this and other methods of

performing restores, see “About the Metadata Server Backup and Restore

Utilities” on page 124.

Use Individual Scripts to Operate Servers and Spawners

To use an individual script to operate the SAS/CONNECT spawner, SAS/SHARE

server, and SAS Deployment Tester server, follow these steps:

1 On Windows, log on as a user who is a member of the host operating system’s

Administrators group. On UNIX and z/OS, log on as the SAS Installer user (for

example, sas).

2 Use one of the following scripts, which are located in the path

SAS-conﬁguration-directory

for

SASApp subdirectory):

/Lev1 (your installation might have a different name

64 Starting or Stopping the SAS Services Application

Table 5.2 Scripts for Operating Servers and Spawners

Chapter 5

Server or Spawner

SAS/CONNECT spawner

SAS/SHARE server Windows: SASApp\ShareServer.bat

SAS Deployment Tester server

Script Name and Location

Windows: SASApp\ConnectServer.bat

UNIX and z/OS: SASApp/ConnectServer.sh

UNIX and z/OS: SASApp/ShareServer.sh

Windows:

DeploymentTesterServer\DeploymentTesterServer.bat

UNIX and z/OS:

DeploymentTesterServerDeploymentTesterServer.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 or spawner as a Windows service.

-remove

removes the server or spawner service from Windows.

-start

starts the server or spawner.

-stop

stops the server or spawner.

-restart

restarts the server or spawner.

-status

displays the current status of the server or spawner.

For more information, see Communications Access Methods for SAS/CONNECT and

SAS/SHARE and SAS/SHARE User’s Guide.

Starting or Stopping the SAS Services Application

The SAS Services Application deploys a set of services called Remote Services that are used by the SAS Information Delivery Portal, the SAS Stored Process Web application, and other Web applications. This application must be started before you start your Web application server. To start the SAS Services Application:

1 Make sure that the metadata server is running.

On Windows, log on as a user who is a member of the host operating system’s Administrators group. On UNIX and z/OS, Log on as the SAS Installer user (for example, sas).

3 Use one of the following scripts:

On Windows: SAS-conﬁguration-directory\Lev1\Web\

Applications\RemoteServices\RemoteServices.bat

On UNIX or z/OS: SAS-conﬁguration-directory/Lev1/Web/

Applications/RemoteServices/RemoteServices.sh

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

Operating Your Servers

Use SAS Management Console to Stop, Pause, Resume, or Reset the SAS Metadata Server 65

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

-install

installs the SAS Services Application as a Windows service.

-remove

removes the SAS Services Application service from Windows.

-start

starts the SAS Services Application.

-stop

stops the SAS Services Application.

-restart

restarts the SAS Services Application.

-status

displays the current status of the SAS Services Application.

Using SAS Management Console to Operate SAS Servers

Obtain the Appropriate User Credentials, and Clear Cached

Credentials (If Necessary)

To connect to a server or spawner in SAS Management Console, you must have the appropriate user credentials. Membership in the SAS Administrators group typically provides sufﬁcient rights and permissions. For details, see “Who Can Do What in the Server Manager Plug-in” on page 35.

If you attempt to connect to a server or spawner and you are denied access, make sure you have the appropriate credentials. After your credentials are updated, be sure to clear the credentials cache before you try to connect again. To clear the credentials cache, click

FileIClear Credentials Cache

in SAS Management Console.

Use SAS Management Console to Stop, Pause, Resume, or Reset the SAS Metadata Server

You can use SAS Management Console to stop, pause, or resume the SAS Metadata Server. You can also use SAS Management Console to reset the metadata server in order to recover memory on the host machine.

Note: Before using these features to operate the metadata server, see “About SAS Metadata Server States” on page 53.

Follow these steps:

1 Log on to SAS Management Console as a user with the appropriate credentials.

2 On the Plug-ins tab, expand the Metadata Manager node, and right-click the

Active Server node.

3 Select one of the following actions:

Stop

66 Use SAS Management Console to Stop, Pause, Resume, Quiesce, or Refresh the SAS Object Spawner

completely stops the metadata server.

Note:

Stopping the metadata server stops other components, including object spawners, OLAP servers, table servers, SAS/CONNECT spawners, and SAS/SHARE servers.

To start the metadata server after stopping it, you must use a script. If you want to be able to resume processing without using a script, use

Pause

Ofﬂine instead.

Chapter 5

Pause

Ofﬂine

pauses the metadata server to the Ofﬂine state. In the Pause Comment dialog box, you can enter a comment that provides information about the pause action. When a client attempts to read or write metadata, the comment is appended to the appropriate message and displayed as follows:

Error accessing metadata: The GetMetadataObjects request failed because the server is paused for OFFLINE use. The reason for the server pause is

Pause

Administration

comment.

pauses the metadata server to the Administration state. In the Pause Comment dialog box, you can enter a comment that provides information about the pause action. When a user who is not in the

Unrestricted

role attempts to read or write metadata, the comment is

appended to the appropriate message and displayed as follows:

accessing metadata: The GetMetadataObjects request failed because the server is paused for ADMINISTRATION use. The reason for the server pause is

Resume

comment.

Metadata Server:

Error

returns the metadata server to the Online state (if the current state is Ofﬂine or Administration). The metadata server resumes accepting client requests to read and write metadata and re-opens repository containers as clients request metadata from them.

Reset

unloads from memory and closes the containers of all registered repositories in order to recover memory on the metadata server host. The metadata server then re-opens repository containers as clients request metadata from them. This option is useful if the host computer experiences an out-of-memory condition.

To start the metadata server, see “Running Servers as Windows Services” on page 55 and “Using Scripts to Operate SAS Servers Individually” on page 61. For information about metadata server startup parameters, see Appendix 5, “Options for the Metadata Server Invocation Command,” on page 289.

Use SAS Management Console to Stop, Pause, Resume, Quiesce, or Refresh the SAS Object Spawner

You can use SAS Management Console to stop, pause, resume, quiesce, or refresh the object spawner. Follow these steps:

1 Log on to SAS Management Console as a user with the appropriate credentials.

2 On the Plug-ins tab, expand the Server Manager node and the Object Spawner

node.

Operating Your Servers

3 Right-click the object spawner instance that you want to administer, and click

Connect.

4 After you are connected, you can select any of the following actions:

Use SAS Management Console to Stop, Pause, Resume, Quiesce, or Refresh the SAS OLAP Ser ver 67

Refresh

updates the SAS Management Console display with current information about the spawner.

Disconnect

discontinues your current connection to the spawner.

Stop

stops the spawner process, including any active client requests.

Note: If you want active requests to be completed ﬁrst, use

Pause

Quiesce.

causes the spawner to ﬁnish processing all active client requests and to stop accepting new requests.

Resume

resumes the spawner process when it is in the paused state.

Quiesce

stops the spawner process after the spawner has ﬁnished processing all active client requests.

Refresh Spawner

re-initializes the spawner. During re-initialization, the spawner stops any spawned servers that are currently running, rereads the metadata in the spawner deﬁnition, and applies any new options that have been set.

Note: If the spawner is in a paused state when the Refresh Spawner

action occurs, the spawner remains paused after it is re-initialized.

To start the object spawner, see “Running Servers as Windows Services” on page 55 and “Using Scripts to Operate SAS Servers Individually” on page 61. For information about startup options for the object spawner, see “Spawner Invocation Options” in the SAS Intelligence Platform: Application Server Administration Guide.

Use SAS Management Console to Stop, Pause, Resume, Quiesce, or Refresh the SAS OLAP Server

You can use SAS Management Console to stop, pause, resume, quiesce, or refresh the SAS OLAP Server. Follow these steps:

Log on to SAS Management Console as a user with the appropriate credentials.

On the Plug-ins tab, expand the node (for example,

3 Right-click the OLAP server instance that you want to administer, and click

Connect.

4 After you are connected, you can select any of the following actions:

Refresh

SASApp), and the node for the logical OLAP server.

updates the SAS Management Console display with current information about the OLAP server.

Disconnect

Server Manager node, the application server

68 Use SAS Management Console to Control Processes on Servers

discontinues your current connection to the OLAP server.

Stop

stops the OLAP server process, including any active client requests.

Chapter 5

Note: If you want active sessions to be completed ﬁrst, use

Pause

Quiesce.

causes the OLAP server to ﬁnish processing all active sessions and to stop accepting new client requests.

Resume

resumes the OLAP server process when it is in the paused state.

Quiesce

stops the OLAP server process after the server has ﬁnished processing all active sessions.

Note: To start the OLAP server after quiescing it, you must use a script. If you want to be able resume processing without using a script, use instead.

Pause

To start the OLAP server, see “Running Servers as Windows Services” on page 55 and “Using Scripts to Operate SAS Servers Individually” on page 61. For information about OLAP server startup parameters, see “System Options for Application Server Components” in the SAS Intelligence Platform: Application Server Administration Guide.

Use SAS Management Console to Control Processes on Servers

You can use SAS Management Console to stop, pause, resume, or quiesce a process on a workspace server, pooled workspace server, or stored process server. Follow these steps:

1 Log on to SAS Management Console as a user with the appropriate credentials.

2 On the

server node (for example,

Expand the node for the logical server that is running the process, and then expand the node for the server instance that is running the process. The server’s available connections are displayed in the server tree and in the right pane.

4 Highlight the appropriate host machine name, as shown in this example.

Plug-ins tab, expand the

SASApp).

Server Manager

node and the application

Right-click the mouse, and click Connect. For each process that is active for that connection, the right pane displays the process ID, the process owner, and the port, as shown in this example:

Operating Your Servers

5 In the Server Manager tree, expand the node for the connection that you are

Starting or Stopping a JBoss Application Server 69

working with. The active processes for the connection are displayed in the tree.

Highlight the process that you want to stop, pause, resume, or quiesce, as shown

in this example:

In the right pane, the following tabs become active: Clients, Options, and

Loggers. For pooled workspace servers and stored process servers, the

and Log

tabs also become active.

Sessions

Note: If some tabs are disabled, then you need additional user credentials. See “Who Can Do What in the Server Manager Plug-in” on page 35. For details about the tabs, see “Use the Server Manager Tabs to Obtain Monitoring Information and to Adjust Logging Levels (If Needed)” on page 91.

7 Right-click the mouse and select one of the following actions:

Stop

stops the server process, including any active client requests.

Note:

If you want active requests to be completed ﬁrst, use

Pause

causes the server process to ﬁnish processing all active client requests and to stop accepting new requests.

Resume

resumes the server process when it is in the paused state.

Quiesce

stops the server process after the server has ﬁnished processing all active client requests.

Starting and Stopping Web Application Servers

Quiesce.

Starting or Stopping a JBoss Application Server

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” on page 64).

2 Use one of the following scripts:

On Windows:

70 Starting or Stopping an IBM WebSphere Application Server or an IBM WebSphere Application Server Network Deployment

(ND)

Chapter 5

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” on page 55.

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:

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

"SASDmgr01"

On UNIX:

WAS_INSTALL_ROOT

"SASDmgr01"

\bin\startManager.bat -profileName

/bin/startManager.sh -profileName

SASDmgr01 is the default proﬁle 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.

Operating Your Servers

Use one of the following commands, where WAS_INSTALL_ROOT is the

Starting or Stopping an IBM WebSphere Application Server or Network Deployment 71

home directory of the application node:

On Windows:

WAS_INSTALL_ROOT

"SAS

host-name01"

On UNIX:

WAS_INSTALL_ROOT

host-name01"

"SAS

\bin\startNode.bat -profileName

/bin/startNode.sh -profileName

SAShost-name01 is the default proﬁle name for the managed node, which contains the node agent and the application server that is used to run SAS. The proﬁle 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

-profileName "SAS

On UNIX:

WAS_INSTALL_ROOT

-profileName "SAS

\bin\startServer.bat "server-name"

host-name01"

/bin/startServer.sh "server-name"

host-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 proﬁle name on Windows and UNIX. If multiple servers are installed, then the default names for the additional proﬁles 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 ﬁrst 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:

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:

Run the following script, where WAS_INSTALL_ROOT is the home directory of the deployment manager:

72 Starting or Stopping an Oracle WebLogic Server

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

Issue the MVS START command to start the node agent. Specify the 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

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

Issue the MVS STOP command against the application server control region.

Chapter 5

/bin/startNode.sh

/bin/startServer.sh "

/bin/stopServer.sh "server-name"

server-name"

Note: When you use the SAS Deployment Wizard to deploy or migrate a SAS

system that uses WebSphere, you must ﬁrst stop all WebSphere application servers. For instructions, see the IBM documentation for WebSphere Application Server.

Starting or Stopping an Oracle WebLogic Server

By default, the SAS Deployment Wizard conﬁgures the WebLogic domain in the

following path: SAS-conﬁguration-directory have been conﬁgured 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.

2 If the WebLogic Administration Server is not running, start it by using the

following command:

domain-home-directory

3 Start the WebLogic Managed Server by using

\startWebLogic.cmd

is located in domain-home-directory

startManagedWebLogic.cmd server-name administration-server-URL

For example:

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

Note: The third maintenance release for SAS 9.2 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” on page 55.

/Lev1/Web/SASDomain. Your domain might

startManagedWebLogic.cmd, which

\bin\. The syntax is as follows:

Operating Your Servers

Starting or Stopping an Oracle WebLogic Server 73

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.

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

is located in domain-home-directory

startManagedWebLogic.sh

server-name administration-server-URL

/bin/. The syntax is as follows:

startManagedWebLogic.sh, which

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.

CHAPTER

Checking the Status of Servers

About Checking the Status of Servers Use a Server Script to Display the Status of a Server or Spawner Checking the Access State of the SAS Metadata Server

Use SAS Management Console to Check the Access State of the SAS Metadata Server Use PROC METAOPERATE to Check the Access State of the SAS Metadata Server

Checking the Access State of Metadata Repositories and the Repository Manager 77

About Metadata Repository Access States and Access Modes How the Access State of the Metadata Server Affects the Access States of Metadata Repositories About Repository Manager Access States Use SAS Management Console to Check the Access State of a SAS Metadata Repository Use PROC METADATA to Check the Status of Metadata Repositories and the Repository

Manager

Create and Run a PROC METADATA Program 80

Example: PROC METADATA Output 81 Check the Status of the Object Spawner 82 Validate the SAS Metadata Server, SAS Workspace Servers, SAS Pooled Workspace Servers, SAS Stored

Process Servers, and SAS OLAP Servers

Validate the SAS Content Server 83

About Checking the Status of Servers

SAS provides a number of tools that you can use to determine the status of your SAS server components. SAS Management Console includes features that enable you to do the following:

use a server script to display the status of a server from the command line

check the access state of the SAS Metadata Server to determine whether it is online, paused for administration, or paused to an Ofﬂine state

check a SAS Metadata Repository to determine whether it is in an Online, Administration, Administration (ReadOnly), ReadOnly, or Ofﬂine access state

check an instance of the SAS object spawner to ensure that you can make a connection

submit SAS code to validate that instances of a SAS Metadata Server, SAS Workspace Server, SAS Pooled Workspace Server, SAS Stored Process Server, or SAS OLAP Server are set up correctly

determine whether the SAS Content Server is listening on the speciﬁed host and port, and that the ﬁrst conﬁgured base path exists on the server

You can also use SAS programming features to check the status of the metadata server, metadata repositories, and the repository manager.

76 Use a Server Script to Display the Status of a Server or Spawner

Note: To check the status of a SAS/SHARE server, see the SAS/SHARE User’s

Guide.

Chapter 6

Use a Server Script to Display the Status of a Server or Spawner

To display the status of a server or spawner from a command line, you can use the

-status

to Operate SAS Servers Individually” on page 61.

On UNIX and z/OS, you can use the

display the status of all servers and spawners on a machine. For details, see “Use the sas.servers Script to Start, Stop, or Restart All Servers or to Display the Status of Servers” on page 58.

option of the script for that server or spawner. For details, see “Using Scripts

-status

option of the sas.servers script to

Checking the Access State of the SAS Metadata Server

Use SAS Management Console to Check the Access State of the SAS Metadata Server

To use SAS Management Console to determine the access state of the SAS Metadata

Server:

1 In the SAS Management Console

node.

2 Right-click the

The current state is displayed in the Active Server Properties dialog box. If the state is Administration or Ofﬂine, then the

Comment ﬁeld displays any comments that were entered by the administrator

who paused the server.

For a description of the Ofﬂine, Administration, and Online states, see “About SAS Metadata Server States” on page 53. To change the state of the metadata server, see “Use SAS Management Console to Stop, Pause, Resume, or Reset the SAS Metadata Server” on page 65.

Active Server node and select

Plug-ins tab, expand the

Properties.

State

ﬁeld on the

Metadata Manager

General tab of the

Use PROC METAOPERATE to Check the Access State of the SAS Metadata Server

To check the access state of the SAS Metadata Server, you can use PROC

METAOPERATE to issue a STATUS action. The syntax is as follows:

PROC METAOPERATE

SERVER=’host-name’ PORT=port-number USERID=’user-ID’ PASSWORD=’password’ PROTOCOL=BRIDGE ACTION=STATUS;

RUN;

Checking the Status of Servers

About Metadata Repository Access States and Access Modes 77

Any user who can log on to the SAS Metadata Server can issue a STATUS action.

If the SAS Metadata Server is running normally, information similar to the following

is written to the SAS Output window:

NOTE: Server dXXXX.us.company.com SAS Version is 9.02.02B0P082107 NOTE: Server dXXXX.us.company.com SAS Long Version is 9.02.02B0P08212007 . NOTE: Server dXXXX.us.company.com Operating System is XP_PRO. NOTE: Server dXXXX.us.company.com Operating System Family is WIN. NOTE: Server dXXXX.us.company.com Client is userid@DOMAIN. NOTE: Server dXXXX.us.company.com Metadata Model is Version 11,01. NOTE: Server dXXXX.us.company.com is RUNNING on 10Sep07:14:47:57.

If the SAS Metadata Server is paused, information similar to the following is written

to the SAS Output window:

A SAS Metadata Server that is stopped will not respond to a PROC METAOPERATE

request.

For more information about PROC METAOPERATE, see

SAS Language Interfaces to

Metadata.

Checking the Access State of Metadata Repositories and the Repository Manager

About Metadata Repository Access States and Access Modes

The access state of a metadata repository indicates its current state with regard to

client access. A metadata repository can exist in any of the following access states:

Online

Clients can read, write, and update metadata.

ReadOnly

Clients can read metadata but cannot write, update, or delete metadata.

Administration

Only users who are in the

write metadata. (For information about this role, see “Overview of Initial Roles,

Groups, and Users” on page 24.)

Metadata Server: Unrestricted role can read or

Administration (ReadOnly)

Only users who are in the

Metadata Server: Unrestricted role can read

metadata. Users cannot write, update, or delete metadata.

Ofﬂine

Clients can neither read nor write metadata to the repository.

78 How the Access State of the Metadata Server Affects the Access States of Metadata Repositories

The access state of a repository depends on both the current state of the metadata server and the repository’s registered access mode. The access mode of a SAS metadata repository is the repository’s intended access state (see “About SAS Metadata Repository Access Modes” on page 182). When the metadata server is Online, the access state of a repository is equal to its access mode. When the metadata server is paused to the Ofﬂine state or the Administration state, the access state of a repository can change temporarily. When the metadata server is resumed, the repository’s access state returns to its registered access mode.

How the Access State of the Metadata Server Affects the Access States of Metadata Repositories

Generally, the access state of a repository is the same as the access mode that is recorded in the repository’s metadata. However, a repository’s access state can change temporarily when the metadata server is paused to an Ofﬂine state (for example, while a backup process is executing) or when the metadata server is paused for administration. When the metadata server is resumed, the repository’s access state returns to its registered access mode.

The following table shows how the access state of the metadata server affects the access state of a repository, based on the repository’s access mode:

Chapter 6

Table 6.1 The Effect of Metadata Server States on Metadata Repository Access States

Metadata Server Access State

Online Online Online

Online Administration Administration

Online ReadOnly ReadOnly

Online Ofﬂine Ofﬂine

Administration Online Administration

Administration Administration Administration

Administration ReadOnly Administration (ReadOnly)

Administration Ofﬂine Ofﬂine

Ofﬂine Online Ofﬂine

Ofﬂine Administration Ofﬂine

Ofﬂine ReadOnly Ofﬂine

Ofﬂine Ofﬂine Ofﬂine

Metadata Repository Registered Access Mode

Metadata Repository Access State

About Repository Manager Access States

The repository manager is a library of tables that deﬁne the set of repositories that can be accessed by a SAS Metadata Server. An access state of ReadOnly or Ofﬂine for the repository manager is typically reﬂected in the following behavior:

ReadOnly

Checking the Status of Servers

Clients can read and write metadata in repositories, but they cannot create or delete repositories or change their registrations.

Ofﬂine

The behavior can vary depending on whether a repository is available in memory. Assume that repositories are unavailable for reading or writing to all users.

Use SAS Management Console to Check the Access State of a SAS

Metadata Repository

If the metadata server is online or is paused for administration, then you can use SAS Management Console to determine the current access state of a metadata repository, as follows:

In the SAS Management Console node.

To view the access state of the foundation repository and any custom repositories that you have created, select the project repositories, expand the

Repositories

For each repository, the access mode and the current access state are displayed

in the table view, as shown in the following example:

Use SAS Management Console to Check the Access State of a SAS Metadata Repository 79

Plug-ins

Active Server

tab, expand the

Metadata Manager

node. To view the access state of

node and select the

Project

folder.

The table lists the following information for each registered repository:

Access

indicates the access mode of the repository as it is recorded in the Access attribute of the repository’s metadata deﬁnition

State

indicates the current access state of the repository. Generally, the access state of a repository is equal to its access mode. However, if the metadata server is paused to an Ofﬂine state or is paused for administration, then the repository’s access state might be changed temporarily (see “How the Access State of the Metadata Server Affects the Access States of Metadata Repositories” on page 78).

The

Access and State ﬁelds are also displayed in the metadata repository

properties. To see these properties, right-click the repository name in the Active Server tree, select

Properties, and select the Registration tab.

80 Use PROC METADATA to Check the Status of Metadata Repositories and the Repository Manager

Note:

If the metadata server is paused to the Administration state, then you must be in

Metadata Server: Unrestricted

the

role to view the server’s status in SAS

Management Console.

If the metadata server is paused to the Ofﬂine state, then the access state of

repositories cannot be displayed in SAS Management Console.

Use PROC METADATA to Check the Status of Metadata Repositories and the Repository Manager

Create and Run a PROC METADATA Program

If the metadata server is online, then you can use PROC METADATA to check the

status of metadata repositories. To do so, use PROC METADATA to issue a GetRepositories method call that sets the OMI_ALL ﬂag to method is part of the SAS Open Metadata Interface.

The syntax is as follows:

Chapter 6

1. The GetRepositories

PROC METADATA

SERVER="host-name" PORT=port-number USERID="your-user-ID" PASSWORD="your-password" IN="<GetRepositories>

<Repositories/> <Flags>1</Flags> <Options/> </GetRepositories>";

RUN;

Note:

To run this program, you must have ReadMetadata permission to all repositories

on the SAS Metadata Server.

If the metadata server is paused to an Ofﬂine state, then you cannot use PROC

METADATA to issue a GetRepositories method call.

If the metadata server is paused to an Administration state, then special user

credentials are required to use PROC METADATA to issue a GetRepositories

method call. The user must either (1) be a member of the

Unrestricted

role or (2) be listed in adminUsers.txt, either with or without an

Metadata Server:

asterisk.

For each repository that is registered to the metadata server, the GetRepositories

method returns the values of the following attributes:

speciﬁes the repository’s unique object identiﬁer.

Name

speciﬁes the name assigned to the repository.

Desc

Checking the Status of Servers

contains a description of the repository.

Access

indicates the repository’s intended access mode, which is speciﬁed in the Access attribute of the repository’s metadata deﬁnition. This ﬁeld corresponds to the repository’s

OMS_FULL OMS_READONLY,

CurrentAccess

contains information that is used by metadata server processes. This ﬁeld is displayed because it is sometimes used by SAS Technical Support in the resolution of metadata repository issues.

PauseState

indicates the current access state of the repository. This ﬁeld corresponds to the repository’s both the current state of the metadata server and the repository’s registered access mode (see “How the Access State of the Metadata Server Affects the Access States of Metadata Repositories” on page 78). An empty string means that the repository is online.

Path

indicates the path where the repository’s data sets are located.

Use PROC METADATA to Check the Status of Metadata Repositories and the Repository Manager 81

Access ﬁeld in SAS Management Console. The possible values are

(which is displayed as

OMS_ADMIN, and

State

ﬁeld in SAS Management Console. The access state depends on

Online in SAS Management Console),

OMS_OFFLINE.

RepositoryFormat

contains the revision level of the metadata model that is used by the repository. A RepositoryFormat level that is less than the level of the server can cause the repository to have a

PauseState

(access state) of ReadOnly.

For more information about the METADATA procedure and the GetRepositories method, see SAS Language Interfaces to Metadata.

Example: PROC METADATA Output

The following is an example of output from PROC METADATA when the metadata server is online:

<Repository Id="A00000001.A00000001"

Name="REPOSMGR" Desc="The Repository Manager" DefaultNS="REPOS" RepositoryType="" RepositoryFormat="11" Access="OMS_FULL" CurrentAccess="OMS_FULL" PauseState="" Path=’’C:\SAS\EBIserver\Lev1\SASMeta\MetadataServer\rposmgr’’/>

<Repository Id="A00000001.A50Q21KN"

Name="Foundation" Desc="" DefaultNS="SAS" RepositoryType="FOUNDATION" RepositoryFormat="11" Access="OMS_FULL" CurrentAccess="OMS_FULL"

82 Check the Status of the Object Spawner

PauseState="" Path=’’C:\SAS\EBIserver\Lev1\SASMeta\MetadataServer\Foundation’’/>

<Repository Id="A00000001.A5IPLNM1"

Name="Test Repository" Desc="" DefaultNS="SAS" RepositoryType="CUSTOM" RepositoryFormat="11" Access="OMS_READONLY" CurrentAccess="OMS_READONLY" PauseState="READONLY" Path=’’C:\SAS\EBIserver\Lev1\SASMeta\MetadataServer\TestRepository’’/>

This output in this example provides the following information:

For the repository manager (

available.

For the Foundation repository:

mode of Online, and

Online.

For the Test Repository:

mode of ReadOnly, and

state is ReadOnly.

Chapter 6

REPOSMGR):

Access="OMS_FULL"

PauseState="" indicates that the current access state is

Access="OMS_READONLY"

PauseState="READONLY"

PauseState="" indicates that it is

indicates a registered access

indicates that the current access

Check the Status of the Object Spawner

The SAS object spawner is a program that listens for incoming client requests for

SAS Workspace Servers, SAS Pooled Workspace Servers, and SAS Stored Process Servers and then launches instances of these servers to fulﬁll the request. The object spawner needs to be running in order for these server instances to be launched.

To make sure that the spawner is working, follow these steps:

1 Log on to SAS Management Console as a user with the appropriate credentials

(see “Who Can Do What in the Server Manager Plug-in” on page 35).

2 On the

Plug-ins tab, expand the

Server Manager

node and the Object Spawner

node.

Right-click the object spawner instance that you want to check, and click

Connect.

Validate the SAS Metadata Server, SAS Workspace Servers, SAS Pooled Workspace Servers, SAS Stored Process Servers, and SAS OLAP Servers

To determine whether your metadata server, workspace servers, pooled workspace

servers, stored process servers, and OLAP servers are set up correctly, you can use the Validate feature. This feature submits a small SAS program to the server to determine whether it can process the code. You can validate either a logical server or a particular instance of a server.

Note: You cannot validate a workspace server that is conﬁgured to use client-side

(rather than server-side) pooling. To determine whether a workspace server uses client-side pooling, right-click the server’s logical server node and click the properties dialog box contains a server uses client-side pooling.

Pooling tab that lists at least one puddle, then the

Properties.If

Checking the Status of Servers

Validate the SAS Content Server 83

To validate a server, follow these steps:

Log on to SAS Management Console as a user with the appropriate credentials (see “Who Can Do What in the Server Manager Plug-in” on page 35).

In SAS Management Console, expand the the application server (for example,

3 To validate a logical server:

Right-click the logical workspace server, logical pooled workspace server,

Server Manager

SASApp).

node and the node for

logical stored process server, or logical OLAP server that you want to validate.

b Select

To validate a particular server instance:

Expand the appropriate logical server node.

In the tree that appears under the logical server deﬁnition, expand the server

Validate.

deﬁnition node.

In the tree that appears under the server deﬁnition, select the server instance that you want to validate, as shown in this example:

d Right-click the server instance and select Validate.

5 SAS Management Console sends a small SAS program to the server for execution.

If the program executes correctly, the following message is displayed:

Validation Successful!

If the program does not execute correctly, an error message is displayed. For assistance in resolving the problem, see “Troubleshooting the SAS Server Tier” in the SAS Intelligence Platform: Installation and Conﬁguration Guide.

If you are denied access, make sure you have the appropriate credentials. After your credentials are updated, click Management Console before you try to validate again.

Note: To run more extensive validation tests, you can use the SAS Deployment Tester plug-in in SAS Management Console or the SAS Deployment Tester batch clients. These tools enable you to validate components on both the middle tier and the SAS server tier. For more information, see the SAS Management Console Help. The SAS Deployment Tester Server must be installed on the same machine as the components that you are validating.

Validate the SAS Content Server

If your installation includes a SAS Content Server, you can use the Validate feature to determine whether the server is set up correctly, as follows:

FileIClear Credentials Cache in SAS

1 Log on to SAS Management Console, and expand the Server Manager node.

2 Right-click the SAS Content Server node.

84 Validate the SAS Content Server

3 SAS Management Console attempts to make a WebDAV connection to the server.

If the connection is successful, the following message is displayed:

Validation Successful!

This message indicates that a WebDAV server is listening on the speciﬁed host

and port, and that the ﬁrst conﬁgured base path exists on the server.

If the connection is not successful, an error message is displayed.

Chapter 6

PART

System Monitoring and Logging

Chapter 7..........

Chapter 8..........

Monitoring the Activity of SAS Servers

Administering Logging for SAS Servers

103

Sas Intelligence Platform User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

What’s New

Overview

New Logging Facility for SAS Servers

New Server Management and Monitoring Features

New SAS Server Components

Enhancements and Changes Pertaining to Metadata Server Administration

Enhancements and Changes Pertaining to Metadata Administration

New Documentation for Administrators

Getting Started

Introduction to the SAS Intelligence Platform: System Administration Guide

About the SAS Intelligence Platform: System Administration Guide

Prerequisites for Using the SAS Intelligence Platform: System Administration Guide

Accessibility Features in the SAS Intelligence Platform Products

Understanding the State of Your System

Overview of the State of Your System

Overview of SAS Management Console

About SAS Management Console

About SAS Management Console Plug-ins

Using the SAS Management Console Plug-ins

About the SAS Management Console Folders Tab

Overview of SAS Deployment Manager and SAS Web Administration Console

What Is the SAS Metadata Server?

About the Metadata Manager Plug-in

About the SASMeta Server Context

About the SAS Metadata Repositories and the Repository Manager

How the SAS Metadata Server Works

About the SAS Application Server Hierarchy

About the SAS Application Server Components

Overview of Other SAS Servers and Spawners

Overview of Ports

About the Levn Subdirectory

About the Application Server Subdirectory

About the SASMeta Subdirectory

About the Web Subdirector y

Overview of Initial Roles, Groups, and Users

About User Roles for System Administration

About the Initial User Groups

About the Initial User Accounts

Who Can Do What: Credential Requirements for SAS Management Console Tasks

About Security for System Administration Tasks

Who Can Do What in the Metadata Manager Plug-in

Who Can Do What in the Server Manager Plug-in

About Adding Users to the SAS Administrators Group

Requirements for Accessing a Standard Workspace Server

Clearing the Credentials Cache

What to Do Next: Administration Tasks

Overview of Administration Tasks

First-Priority Setup Tasks

Summary of First-Priority Setup Tasks

Recommended Operating System Protections for Windows Machines

Default Operating System Protections for UNIX and z/OS Machines

Standard Setup Tasks

Optional Setup Tasks

Ongoing System Administration Tasks

Best Practices for Ensuring the Integrity of Your System

Allow Only the Metadata Server to Access Your Metadata Repositories

Use Best Practices for Working with SAS Folders

Starting, Stopping, and Checking the Status of Servers

Operating Your Servers

Overview of Server Operation

About Required Servers

Starting Servers in the Correct Order

About Server Start-up Parameters

About SAS Metadata Server States

Summary of Procedures for Server Operation

Running Servers as Windows Services

Starting and Stopping SAS Servers on z/OS

Using the sas.servers Script on UNIX or z/OS to Start or Stop All Servers

About the sas.servers Script

Use the sas.servers Script to Start, Stop, or Restart All Servers or to Display the Status of Servers

Using generate_boot_scripts.sh to Regenerate the sas.servers Script

Install sas.servers as a Boot Script

Running Servers as UNIX Daemons

Using Scripts to Operate SAS Servers Individually

About Using Scripts to Operate Servers