JDBC Data Sources

About the Data Sources Used by the Middle Tier

The SAS Web Infrastructure Platform, and 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 relational tables in the SAS Web Infrastructure Platform database are intrinsic to or used primarily for the operations of a particular application, product, or service.
SAS Web applications and services access data from the SAS Web Infrastructure Platform database through JDBC. SAS Web Infrastructure Platform provides support for the following third-party vendor databases:
  • Oracle Database
  • IBM DB2
  • Microsoft SQL Server
  • MySQL
  • PostgreSQL
Your site can choose to use the database that you are familiar with. However, some SAS solutions have requirements for specific databases. Consider these requirements when you select a database to use as the data source for the SAS Web Infrastructure Platform. As a default option, the SAS Framework Data Server can be configured as the data source for SAS Web Infrastructure Platform.

Connection Information for the JDBC Data Source

The database used by the SAS Web Infrastructure Platform must be configured in the Web application server as a JDBC data source. The JDBC data source is configured with the JDBC driver and connection information for the selected database. These settings are provided to the SAS Deployment Wizard during installation and configuration. You need to know the JDBC connection parameters if you make changes later, such as changing the connection to access a database on another machine. JDBC connection settings typically require a user ID and password for access to the data source.
The default database for SAS Web Infrastructure Platform is the SAS Framework Data Server. The JDBC connection parameters for the SAS Framework Data Server are provided in the following table:
JDBC Connection Parameters for SAS Framework Data Server
Connection Parameter
Setting
JNDI name:
sas/jdbc/SharedServices
JDBC URL:
jdbc:sastkts://serverName:port?stmtpooling=0&constring=(DSN=SharedServices;encoding=UNICODE_FSS)
In the URL, substitute the server name and port number of the SAS Framework Data Server at your site. The default port is 22031.
JDBC driver class:
com.sas.tkts.TKTSDriver
These settings are configured during initial deployment. However, you need to know the connection information if you make changes later, such as moving the SAS Framework Data Server to another host system.
Note: You must specify the user name and password values as required to access the data source.
The SAS Drivers for JDBC are used to connect to the SAS Framework Data Server. The JAR files in the following list must be in the same directory as the JDBC driver to connect with the SAS Framework Data 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.security.sspi.jar
  • sas.svc.connection.jar
  • sas.svc.connection.nls.jar
To modify the settings for a JDBC data source, see the documentation for your Web application server.

The Shared Services Database on SAS Framework Data Server

The database file is located in the following directories:
On Windows:
SAS-config-dir\Lev1\FrameworkServer\Content\SHAREDSERVICES.FDB
On UNIX and z/OS:
SAS-config-dir/Lev1/FrameworkServer/Content/SHAREDSERVICES.FDB
CAUTION:
Do not change the name or contents of the DSN.
Doing so prevents SAS Web Infrastructure Platform from functioning.

Using Other Relational Databases with the SAS Middle Tier

SAS Web Infrastructure Platform can be configured to use a third-party vendor relational database for storage. In addition, some SAS solutions and applications might require a database other than SAS Framework Data Server. 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.