|
Getting Started
Initial Servers and Services Setup
After you run the SAS Configuration Wizard, you will have an initial server configuration. To understand the locations of your configuration information, see
Understanding the State of Your System in the
SAS Intelligence Platform: System Administration Guide.
Your initial server setup includes a SAS Metadata Server and might include one or more additional server configurations.
Initial SAS Metadata Server Configuration
After you run the SAS Configuration Wizard, the initial SAS Metadata Server configuration includes the following:
SAS Metadata Repository on the SAS Metadata Server's host machine, located in the
MetadataServer\MetadataRepositories\<RespositoryName> directory of the installation.
SAS Metadata Server startup script or service configuration,
located in the MetadataServer directory of the installation.
For more information about the initial metadata server configuration and how to modify it, see the SAS Intelligence Platform: System Administration Guide.
Initial IOM Server Configuration
After you run the SAS Configuration Wizard, you will have one or more servers configured.
The following table details the server configurations that might be set up.
Initial IOM Server Configurations |
Server |
Location and Type of Server Startup |
Credentials Used for Server Startup and SAS Metadata Server Connection |
Metadata |
Credentials Used in Metadata Configuration |
Modifying the Configuration |
SAS Workspace Server |
Spawner startup script, located in the ObjectSpawner subdirectory
of your installation. See
Spawner Overview and
Invoking the Spawner.
|
To connect to the SAS Metadata Server, the ObjectSpawner subdirectory also contains the spawner's metadata configuration file, OMRConfig.xml , which specifies the SAS Trusted User's user ID*.
To start the server, the spawner uses the client's credentials to launch the SAS Workspace Server.
|
Standard logical server definition called "Main - Logical Workspace Server"
|
N/A |
Pooling. See
Overview of Pooling.
Adding a new server and spawner. See
Standard Server Metadata.
Adding a new server with a COM connection. See
Standard Server Metadata.
|
Server definition called "Main - Workspace Server" |
N/A |
Spawner definition |
N/A |
SAS Stored Process Server |
Spawner startup script, located in the ObjectSpawner subdirectory of your installation.
Modifying the startup script. See
Spawner Overview and
Invoking the Spawner.
|
To connect to the SAS Metadata Server, the ObjectSpawner subdirectory also contains the spawner's metadata configuration file, OMRConfig.xml , which specifies the SAS Trusted User's user ID*.
To start the server, the spawner uses the login credentials that are owned by the SAS General Servers group to launch the SAS Stored Process Server.**
|
Load-balanced logical server definition called "Main - Logical Stored Process Server"
|
Logical server credentials, which are specified as the group login of the SAS General Servers group |
Load balancing. See
Load Balancing Overview
Adding a new server and spawner. See
Standard Server Metadata.
|
Load-balanced server definition called "Main - Stored Process Server" |
Multi-user login, which is specified as the group login of the SAS General Servers group. This login
is the user ID under which the SAS Stored Process Server runs. |
Spawner definition |
N/A |
SAS OLAP Server |
Startup script or service startup, located in the OLAPServer subdirectory of your installation
Modifying the startup script or service configuration. See
Starting, Stopping, and Pausing Servers
in the SAS Intelligence Platform: System Administration Guide.
|
To connect to the SAS Metadata Server, the SAS OLAP server uses the SAS Trusted User's user ID.*
To start the server (if not started as a service), the SAS user credentials are used.
|
Standard logical server definition called "Main - Logical OLAP Server""
|
N/A |
Adding a COM connection to the server.
See Adding a COM Connection.
Adding a New Server Definition. See
Standard OLAP Server Metadata (IOM Bridge)
and Standard Server Metadata (COM)
. Also see the Server Manager Help in SAS Management Console.
|
Server definition called "Main - OLAP Server" |
N/A |
*The SAS Trusted User is a member of the SAS System Services group, which has permission to read the metadata (ReadMetadata permission) for the server definitions.
**The SAS General Servers group owns the login that the spawner uses to start the SAS Stored Process Server. The spawner (which connects to the SAS Metadata Server as the SAS Trusted User) can see the SAS General Servers group login because SAS Trusted User is a member of the SAS General Servers group.
To move servers to a different machine, depending on whether
you have both the SAS Workspace Server and SAS Stored Process Server installed (either on the same machine or on separate machines),
see the following:
Initial WebDAV Server Configuration
If you use the SAS Configuration Wizard to configure the Apache HTTP server as a WebDAV server, it creates a server definition, "HTTP DAV Server." To modify the WebDAV server definition, see the
Server Manager Help in SAS Management Console. To add a new WebDAV server definition, see HTTP Servers and WebDAV.
If you are using the Xythos WFS WebDAV server, you can implement
authentication using the SAS Metadata Server's authentication provider,
and implement authorization using the Xythos WFS WebDAV Administration GUI to specify
access controls for the SAS users and groups that are defined on the SAS Metadata Server.
For details, see Implementing Authentication
and Authorization for the Xythos WFS WebDAV Server.
Initial SAS Foundation Services Configuration
The installation process places an XML service deployment file into the Deployments directory of the project installation. The service deployment file contains the local and remote service deployment configurations. For details about working with service deployments, see the Foundation Services section of the SAS Integration Technologies: Administrator's Guide and Foundation Services and WebDAV Server Deployment in the
SAS Intelligence Platform: Web Application Administration Guide.
|