Deployed Components for In-Database Processing :: SAS® 9.4 In-Database Products: User's Guide, Seventh Edition

Deployed Components for Aster

Components that are deployed to Aster for in-database processing are contained in a self-extracting archive file (tkindbsrv-9.4_M3-n_lax.sh). n is a number that indicates the latest version of the file. If this is the initial installation, n has a value of 1. Each time you reinstall or upgrade, n is incremented by 1.

The archive file is located in the SAS-installation-directory/SASTKInDatabaseServer/9.4/AsternClusteronLinuxx64/ directory.

The SAS Embedded Process is the component that is deployed in Aster. The SAS Embedded Process contains run-time libraries, and other software that is installed on your Aster system. The SAS scoring files created in Aster access the routines within the run-time libraries.

In particular, the SAS System libraries, the SAS_SCORE( ) SQL/MR function, and the SAS_PUT( ) SQL/MR function are installed. The SAS Scoring Accelerator for Aster uses these libraries and the SAS_SCORE( ) SQL/MR function to run scoring models inside the database. The SAS_PUT( ) function executes the format files in Aster. The SAS_PUT( ) function is deployed and stored in the NC_INSTALLED_FILES table under either the PUBLIC schema (4.5) or the specified schema (4.6).

For more information about these components, see the installation and configuration instructions in the SAS In-Database Products: Administrator’s Guide.

Deployed Components for DB2

Components that are deployed to DB2 for in-database processing are contained in two self-extracting archive files (acceldb2fmt-3.1-n_*.sh and tkindbsrv-9.4_M3-n_*.sh). n is a number that indicates the latest version of the file. If this is the initial installation, n has a value of 1. Each time you reinstall or upgrade, n is incremented by 1.

The first self-extracting archive file is located in the

SAS-installation-directory/SASFormatsLibraryForDB2/3.1/DB2on<AIX
                     | Linux64>/

directory. The second self-extracting archive file is located in the

SAS-installation-directory/SASTKInDatabaseServer/9.4/DB2on<AIX
                     | Linuxx64>/

directory.

The following components are deployed in the acceldb2fmt-3.1-n_*.sh file:
- The SAS formats library. The library contains many formats that are available in Base SAS.
  
  After you install the SAS formats library, the SAS scoring model functions and the SAS_PUT( ) function created in DB2 can access the routines within its run-time library.
- The binary files for the SAS_COMPILEUDF function.
  
  The%INDB2_PUBLISH_COMPILEUDF macro registers the SAS_COMPILEUDF function in the SASLIB schema of the DB2 database. The SAS_COMPILEUDF function compiles the scoring model source files in the DB2 database, links to the SAS formats library, and then copies the new object files to a specified location.
- The binary files for the SAS_DELETEUDF function.
  
  The %INDB2_PUBLISH_DELETEUDF macro registers the SAS_DELETEUDF function in the SASLIB schema of the DB2 database. The SAS_DELETEUDF function removes existing object files.
The SAS Embedded Process is deployed in the tkindbsrv-9.4_M3-n_*.sh file. The SAS Embedded Process contains run-time libraries and other software that is installed on your DB2 system. The SAS scoring files created in DB2 access the routines within the run-time libraries.

For more information about these components, see the installation and configuration instructions in the SAS In-Database Products: Administrator’s Guide.

Deployed Components for Greenplum

Components that are deployed to Greenplum for in-database processing are contained in two self-extracting archive files (accelgplmfmt-3.1-n_lax.sh and tkindbsrv-9.4_M3-n_lax.sh). n is a number that indicates the latest version of the file. If this is the initial installation, n has a value of 1. Each time you reinstall or upgrade, n is incremented by 1.

The first self-extracting archive file is located in the SAS-installation-directory/SASFormatsLibraryforGreenplum/3.1/GreenplumonLinux64/ directory. The second self-extracting archive file is located in the SAS-installation-directory/SASTKInDatabaseServer/9.4/GreenplumonLinux64/ directory.

The following components are deployed in the accelgplmfmt-3.1-n_lax.sh file:
- The SAS formats library. The library contains many formats that are available in Base SAS.
  
  After you install the SAS formats library, the SAS scoring model functions and the SAS_PUT( ) function created in Greenplum can access the routines within its run-time library.
- The binary files for the SAS_COMPILEUDF function and other utility functions.
  
  The %INDGP_PUBLISH_COMPILEUDF macro registers the SAS_COMPILEUDF function and other utility functions in the database. The utility functions are called by the %INDGP_PUBLISH_MODEL scoring publishing macro.
The SAS Embedded Process is deployed in the tkindbsrv-9.4_M3-n_lax.sh file. The SAS Embedded Process contains run-time libraries and other software that is installed on your Greenplum system. The SAS Embedded Process accesses the scoring files when a scoring operation is performed. The SAS Embedded Process also executes the DS2 thread program when using the SAS In-Database Code Accelerator.

For more information about these components, see the installation and configuration instructions in the SAS In-Database Products: Administrator’s Guide.

Deployed Components for Hadoop

Components that are deployed to Hadoop for in-database processing are contained in a self-extracting archive file, sepcorehadp-9.43000-n.sh). n is a number that indicates the latest version of the file.

The archive file is included in a ZIP file (en_sasep.zip) that is located in the

YourSASDepot/standalone_installs/SAS_Core_Embedded_Process_Package_for_Hadoop/9_43/Hadoop_on_Linux_x64/

directory.

The SAS Embedded Process and SAS Hadoop MapReduce JAR files are the components that are deployed in Hadoop. The SAS Embedded Process contains run-time libraries, and other software that is installed on your Hadoop system.

For more information, see the SAS In-Database Products: Administrator’s Guide.

Deployed Components for Netezza

Components that are deployed to Netezza for in-database processing are contained in two self-extracting archive files (accelnetzfmt-3.1-n_lax.sh and tkindbsrv-9.4_M3-n_lax.sh). n is a number that indicates the latest version of the file. If this is the initial installation, n has a value of 1. Each time you reinstall or upgrade, n is incremented by 1.

The first archive file is located in the SAS-installation-directory/SASFormatsLibraryforNetezza/3.1/Netezza32bitTwinFin/ directory. The second archive file is located in the SAS-installation-directory/SASTKInDatabaseServer/9.4/Netezza64bitTwinFin directory.

The following components are deployed in the accelnetzfmt-3.1-n_lax.sh file:

The SAS formats library. The library contains many formats that are available in Base SAS.

The SAS formats library is published to the database as an object.

After the %INDNZ_PUBLISH_JAZLIB macro publishes and registers the SAS formats library, the SAS scoring model functions and the SAS_PUT( ) function created in Netezza can access the routines within its run-time library.
The binary files for SAS_COMPILEUDF and other utility functions.

The %INDNZ_PUBLISH_COMPILEUDFmacro creates the SAS_COMPILEUDF, SAS_DictionaryUDF, and SAS_HextToText functions that are needed to facilitate the publishing of the scoring models, the SAS_PUT( ) function, and user-defined formats.
The SAS Embedded Process is deployed in the tkindbsrv-9.4_M3-n_lax.sh file. The SAS Embedded Process contains run-time libraries, and other software that is installed on your Netezza system. The SAS Embedded Process accesses the scoring files when a scoring operation is performed.

The %INDNZ_PUBLISH_JAZLIB and %INDNZ_PUBLISH_COMPILEUDF macros are typically run by your system or database administrator.

For more information, see the SAS In-Database Products: Administrator’s Guide.

Deployed Components for Oracle

Components that are deployed to Oracle for in-database processing are contained in a self-extracting archive file (tkindbsrv-9.4_M3-n_lax.sh). n is a number that indicates the latest version of the file. If this is the initial installation, n has a value of 1. Each time you reinstall or upgrade, n is incremented by 1.

The archive file is located in the SAS-installation-directory/SASTKInDatabaseServer/9.4/OracleDatabaseonLinuxx64/ directory.

The SAS Embedded Process is the component that is deployed in Oracle. The SAS Embedded Process contains run-time libraries and other software that is installed on your Oracle system. The SAS scoring files created in Oracle access the routines within the run-time libraries.

For more information about these components, see the installation and configuration instructions in the SAS In-Database Products: Administrator’s Guide.

Deployed Components for SAP HANA

Components that are deployed to SAP HANA for in-database processing are contained in a self-extracting archive file, tkindbsrv-9.4_M3-n_lax.sh). n is a number that indicates the latest version of the file. If this is the initial installation, n has a value of 1. Each time you reinstall or upgrade, n is incremented by 1.

The archive file is located in the SAS-installation-directory/SASTKInDatabaseServer/9.4/SAPHANAonLinux64 directory.

The SAS Embedded Process is the component that is deployed in SAP HANA. The SAS Embedded Process contains run-time libraries and other software that is installed on your SAP HANA system. The SAS scoring files created in SAP HANA access the routines within the run-time libraries.

For more information about these components, see the installation and configuration instructions in the SAS In-Database Products: Administrator’s Guide.

Deployed Components for SPD Server

The SAS Scoring Accelerator for SPD Server requires SAS 9.4 and a specific version of the SAS Scalable Performance Data Server. For more information, see the SAS Foundation system requirements documentation for your operating environment.

If you have a model that was produced by SAS Enterprise Miner, an active SPD Server, and a license for the SAS Scoring Accelerator for SPD Server, you have everything that is needed to run scoring models in the SPD Server. Installation of an in-database deployment package is not required.

Deployed Components for Teradata

Components that are deployed to Teradata for in-database processing are contained in two RPM files (accelterfmt-3.1-n.x86_64.rpm and sepcoretera-9.43000-n.x86_64.rpm). n is a number that indicates the latest version of the file.

The first RPM file is located in the SAS-installation-directory/SASFormatsLibraryforTeradata/3.1/TeradataonLinux/ directory. The second RPM file is included in a ZIP file (en_sasex.zip) that is located in the YourSASDepot/standalone_installs/SAS_Core_Embedded_Process_Package_for_Teradata/9_43/Teradata_on_Linux/ directory.

The components that are deployed are the SAS formats library and the SAS Embedded Process.

The SAS formats library contains many of the formats that are available in Base SAS. After you install the SAS formats library, the SAS scoring model functions and the SAS_PUT( ) function can access the routines within its run-time library.

The SAS Embedded Process contains run-time libraries, and other software that is installed on your Teradata system. The SAS scoring files created in Teradata access the routines within the run-time libraries. The SAS Embedded Process also executes the DS2 thread program when using the SAS In-Database Code Accelerator.

For more information about installing and configuring these components, see the SAS In-Database Products: Administrator’s Guide.