Overview

Beginning with the third maintenance release for SAS^® 9.4, SAS^® Integration Technologies includes the SAS LASR Analytic Server Access Tools. The SAS LASR Analytic Server Access Tools include two engines: the SASIOLA engine and the SASHDAT engine. These engines make it possible to copy data from an environment without a SAS LASR Analytic Server to a remote SAS LASR Analytic Server or Hadoop Distributed File System (HDFS).

Key considerations

Here are some key considerations for using the tools:

• The SAS LASR Analytic Server must be installed on a Linux environment. The server can be distributed or non-distributed.
• SSH keys for the LASR administrator must be installed on both the source environment and the target environment that has the SAS LASR Analytic Server.
• The source environment must have the private key.
• The SAS LASR Analytic Server environment must have the public key stored in authorized keys.
• The source environment and the SAS LASR Analytic Server environment do not have to share a common metadata server. However, if the SAS LASR Analytic Server and the library are registered in metadata and they are started with the signer option, then the user who tries to read and write data to the SAS LASR Analytic Server must connect to metadata. Therefore, the user must have the correct metadata permissions on the SAS LASR Analytic Server and the library.
• Throughput is limited to the network connection between environments.
• The SAS LASR Analytic Server Access Tools do not register data in metadata. This task must be done manually.
• The SAS LASR Analytic Server cannot be managed using these tools.
• The SAS LASR Analytic Server Access Tools cannot replace or overwrite tables in memory.

Example: Loading data to SAS LASR Analytic Server

Here is an example of loading data to the SAS LASR Analytic Server from Windows. The user ID is sasdemo.

/* options to specify username and ssh key file */

option set=TKSSH_USER='sasdemo';
option set=TKSSH_IDENTITY='C:\sshkeys\sasdemo\id_rsa';
  
/* Options to specify the metadata server connection and credentials.         */
/* Not necessary on a client, such as SAS Enterprise Guide, logged into the same metadata server.*/

options metaserver='server.mycompany.com' metaport=8561
metauser='sasdemo' metapass='{SAS002}1D57933958C580064BD3DCA81A33DFB2';

/* libname to the running SAS LASR Analytic Server using the signer option */

libname lsrlib sasiola host='server.mycompany.com' port=10090
tag=smp1tag signer='http://server.mycompany.com:7980/SASLASRAuthorization';

/* load sashelp.zipcode to LASR */
data lsrlib.zipcode;
set sashelp.zipcode;
run;

Example: Loading data to HDFS

Here is an example of loading data to HDFS from Windows. The user ID is sasdemo.

/* options to specify username and ssh key file */

option set=TKSSH_USER='sasdemo';
option set=TKSSH_IDENTITY='C:\sshkeys\sasdemo\id_rsa';

/* libname to /tmp in Hadoop using the SASHDAT engine */

libname hdat sashdat server='server.mycompany.com' install='/opt/TKGrid' path='/tmp';

/* load sashelp.zipcode to SASHDAT */

data hdat.zipcode;
set sashelp.zipcode;
run;

Verifying installation

To verify that the SAS LASR Analytic Server Access Tools are installed, follow the instructions in SAS Note: 35968 to generate a Deployment Registry report. Search the report for the following entries:

• lasreng
• tksecuressh
• tklasreng

For new deployments, generate a Deployment Registry report and verify that the report includes inttech, and that the Display Version is 9.4_M3.

Additional resources

For more information about the tools, see the video tutorial "Understanding and Using SAS LASR Analytic Server Access Tools" on the SAS YouTube channel.

For more information about the engines, see "Using the SAS LASR Analytic Server Engine" and "Using the SASHDAT Engine" in the SAS^® LASR™ Analytic Server: Reference Guide.

Operating System and Release Information