Interacting with the Server Tier |
About the Data Sources Used by the Middle Tier |
Several services in the middle tier, including SAS Shared Services as well as some solutions, provide a set of features that rely on a relational database to store service data. These relational tables differ from the data that is analyzed, modeled, or otherwise processed by SAS applications, which typically is derived from a site's enterprise or legacy sources. Instead, the shared platform relational tables are intrinsic to or used primarily for the operations of a particular application, product, or a specific service.
Applications and services access data from the database server via a JDBC data source that is defined for the Web application server. In a deployment that includes SAS Shared Services, a data source is created exclusively for use by the Shared Services. Other SAS applications and solutions might specify additional data sources.
Using the SAS Table Server with the SAS Middle Tier |
SAS Table Server stores audit records for enhanced auditing functionality supported by SAS Shared Services.
During an Enterprise BI Server installation, a database and a data source name (DSN) definition are created automatically on the SAS Table Server for the exclusive use of SAS Shared Services. Both the database and the DSN are named SharedServices.
When using SAS Table Server, use the following configuration information for the SharedServices DSN:
These settings are configured during initial deployment. However, you need to know the configuration information if you later make changes, such as moving the SAS Table Server to another host system.
Note: You must specify the user name and password values as required to access the data source.
The following JAR files must reside on the Web application server:
sas.core.jar
sas.core.nls.jar
sas.icons.jar
sas.icons.nls.jar
sas.intrnet.javatools.jar
sas.intrnet.javatools.nls.jar
sas.nls.collator.jar
sas.oda.tkts.jar
sas.oda.tkts.nls.jar
sas.rutil.jar
sas.rutil.nls.jar
sas.security.sspi.jar
sas.svc.connection.jar
sas.svc.connection.nls.jar
To modify the settings for a data source, see the documentation for your Web application server.
The SharedServices.fdb database is located in the following directories:
On Windows:
SAS-configuration-directory\Lev1\SASTS\Content directory.
On UNIX and z/OS:
SAS-configuration-directory/Lev1/SASTS/Content directory.
The Web application server points to this database. The DSN definition is a metadata object that contains connection information that allows SAS Shared Services to connect to the Shared Services database. The connection information is configured by default to be optimum for SAS Shared Services.
Doing so prevents SAS Shared Services from functioning.
To back up the database, use the following command:
sastback -b SharedServices.fdb -mo read_only [-verbose] SharedServices.fbk
To restore the database, use the following command:
sastback -r SharedServices.fbk [-verbose] SharedServices.fdb
On Windows, UNIX, and z/OS, the SASTBACK executable is in the SAS-installation-directory/SASFoundation/9.2/vulcan/bin directory.
Using Other Relational Databases with the SAS Middle Tier |
SAS Shared Services can be configured to use a relational database other than SAS Table Server to handle its storage requirements. In addition, some SAS solutions and applications might require a database other than SAS Table Server (such as MySQL). The other relational databases that can be used vary depending on the set of SAS applications that your site has installed. Contact your on-site SAS support personnel for more information.
Copyright © 2010 by SAS Institute Inc., Cary, NC, USA. All rights reserved.