|
Getting Started
Getting Started without the SAS Configuration Wizard
If you did not use the SAS Configuration Wizard as part of a planned (Advanced or Personal) installation, then follow these steps:
Plan your implementation:
Determine how your organization intends to use these features of SAS Integration Technologies:
- distributed applications
- SAS Stored Processes
- publish/subscribe
- SAS Foundation Services
In addition, you might want to set up tables and libraries.
Determine the hardware and software elements that will be involved in your SAS Integration Technologies implementation.
For example, if you are administering a distributed application implementation, you will need to know the
communication requirements for connecting your client and server platforms.
The IOM servers are as follows:
- SAS Workspace Server
- SAS Stored Process Server
- SAS OLAP Server
- SAS Metadata Server
For some features, a WebDAV server might be required. The following table details the servers that are required to implement each SAS Integration Technologies feature:
Metadata on the SAS Metadata Server |
Feature |
Required Server Definition |
Metadata Storage (provides central, shared location) |
SAS Metadata Server
|
Submit and Generate SAS Code |
SAS Workspace Server and Spawner
|
Tables and Libraries |
SAS Workspace Server and Spawner
|
Packages |
- if published to an archive on a SAS Workspace Server, a SAS Workspace Server and Spawner
- if published to WebDAV, a WebDAV server
- if published to a file, no server definition is needed for the package
|
Publication Channels |
- if publishing to an archive on a SAS Workspace Server, a SAS Workspace Server and Spawner
- if publishing to an archive on a WebDAV server, a WebDAV server
- if publishing to an archive in the file system, no server definition is needed for the publication channel
|
SAS Stored Processes - Package Results |
if stored in an archive on a SAS Workspace Server, a SAS Workspace Server and Spawner
if outputting a package to DAV, a WebDAV server |
SAS Stored Processes - Streaming Results |
SAS Stored Process Server and Login |
In addition, you might also require certain servers for
Business Intelligence content.
The following table details the servers that are required to implement
SAS Information Maps and SAS Reports:
Metadata on the SAS Metadata Server |
Feature |
Required Server Definition |
SAS Information Maps |
- for relational data, a SAS Workspace Server and Spawner
- for multi-dimensional data, a SAS OLAP Server
|
SAS Reports |
- for relational data, SAS Workspace Server and Spawner
- for multi-dimensional data, a SAS OLAP Server
if storing reports in DAV, a WebDAV server |
Finally, certain SAS clients rely on the servers.
-
Set up the SAS Metadata Server. SAS Integration
Technologies uses the SAS Metadata Server which provides
a central, shared location for storing metadata. The metadata
server provides a common repository from which user, resource,
and security-policy information can be centrally managed.
Because all of the SAS Integration Technologies administration
tasks involve working with metadata information, the first
administration task is to install and set up a metadata
server. For reference material, see Support for SAS
Open Metadata Architecture in the SAS Integration
Technologies: Technical Overview.
Understand, plan, and implement security features.
For details about security, refer to
the
SAS Intelligence Platform: Security Administration Guide.
Set up SAS Stored Process, SAS Workspace, and SAS OLAP Servers. To set up, start, and administer an IOM server, you must complete each of the following tasks:
Choose the appropriate connection(s) for your server configuration:
a COM/DCOM connection, which enables client access using COM/DCOM
an IOM Bridge connection, which enables client access using the SAS Integration Technologies IOM Bridge for COM or IOM Bridge for Java
For details, see Choosing a Server Configuration.
Plan your configuration metadata, which you will define on the SAS Metadata Server using SAS Management Console. For details, see
Planning for Metadata Definitions.
For IOM Bridge connections, determine the
SAS users, groups, and login definitions that are specified in the server connection configuration:
Set up a server using either a COM/DCOM connection or an
IOM Bridge connection. For details about setting up a server that uses a COM/DCOM connection, see the COM section. For details about setting up a server that uses an IOM Bridge connection, see the IOM Bridge section.
These sections provide detailed instructions for creating the metadata to define your server configuration, and for performing server administration and troubleshooting tasks.
Note: Servers that use a COM/DCOM connection do not use a spawner to launch the server.
For SAS Workspace and SAS Stored Process Servers that use an IOM Bridge connection, you must
set up a spawner to launch the server.
In addition, for SAS Workspace Servers, you can choose to set up pooling or load balancing. For SAS Stored Process Servers, you must set up load balancing. For details, see Pooling and Load Balancing.
Configure the startup commands for the spawners and servers as specified in Starting Servers. Instructions are provided for
enabling and launching the spawners and servers on the host machine.
Set up WebDAV Servers. To set up WebDAV server definitions, 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
-
Set up metadata definitions for additional features.
For details about setting up libraries, see Setting
Up Libraries. For details about setting up SAS Foundation
Services deployments, SAS Publishing Framework, and SAS
Stored Processes, see the SAS
Integration Technologies: Administrator's Guide.
Implement security for resource authorization. Set up access controls for
your resources as specified by your security plan (from Step 3).
Start your servers and services in the appropriate order.
For details, see Server and Service Startup Order.
|