This topic explains how to configure a SAS/SHARE data repository as an external data source
Configure SAS/SHARE Data Source
1. Add a line to the file named "services" (For Windows, check in c:\windows\system32\drivers\etc; for Linux and OSX, check in /etc/services) for SAS/SHARE; for example:
sasshare 5010/tcp #SAS/SHARE server
2. Run SAS
3. Execute a script that specifies one or more libnames and starts the SAS/SHARE server. For example:
libname airline 'C:\Program Files\SAS\SAS 9.1\reporter\demodata\airline';
proc server authenticate=optional id=sasshare; run;
4. Add a new SAS DataSource element to your labkey.xml file, for example:
Note that if you will be connecting to more than one external data source, be sure that all have unique name
parameters, i.e. sasDataSource1, sasDataSource2, or similar. This value will be used whenever you connect an external schema
to this datasource so it must be unambiguous.
5. Copy the JDBC driver jars sas.core.jar and sas.intrnet.javatools.jar to your tomcat/lib directory.
Note: We recommend using the latest version of the SAS Driver 9.2 for JDBC; this driver works against both SAS 9.1 and 9.2. At this time, the most recent 9.2 version is called 9.22-m2; the driver lists a version number of 9.2.902126.96.36.19990722190000_v920m2. Earlier versions of the 9.2 driver are not recommended because they had major problems with column data types.
6. Start LabKey Server.
7. Visit the Query Schema Browser
in the folder where you wish to expose your SAS library.
8. Define a new External Schema. Choose your SAS data source, pick a library, and specify a schema name to use within this folder (this name can be different from the SAS library name).
The data sets in the library are now available as queries in this folder. You can browse them via the Schema Browser, configure them in a query web part, create custom queries using them, etc.
For more information on configuring the SAS JDBC Driver, see Introduction to the SAS Drivers 9.2 for JDBC
Note: This procedure will run SAS/SHARE in a completely open, unsecured manner. It is intended for development purposes only. Production installations should put appropriate authentication in place.