SAS Real-Time Decision Manager (Non-distributed) includes the non-distributed version of SAS Visual Analytics Administration and Reporting (single-machine environment). This component is required to enable the ‘Reporting Workspace’ in the CI Studio user interface. If SAS Visual Analytics Administration and Reporting is not installed, the Reporting Workspace will not be available in your system. Refer to deployment instructions for more information.
This version of SAS Visual Analytics Administration and Reporting must be installed on a separate machine from SAS Real-Time Decision Manager. Refer to the SAS Visual Analytics 6.4 system requirements for more information.
SAS Real-Time Decision Manager Server includes two SAS/ACCESS engines of choice from the following list:
SAS Visual Analytics Administration and Reporting Server (Non-distributed Mode) includes a standard SAS/ACCESS engine of choice and a SAS LASR Analytic Server (Non-distributed LASR).
The SAS Federation Server Manager requires that a minimum of Java 7 be installed on the host before doing the SAS deployment. Not doing so will cause SAS Federation Server Manager to not install. Please make sure that Java is installed prior to starting the SAS deployment process.
The following data sources can be accessed by the SAS Federation Server:
When using the SAP (R3) driver, the SAP Kernel Release 4.6C or higher is required. The Driver for SAP for Windows and UNIX requires the 64-bit SAP Unicode RFC library, Release 7.20, which is provided by SAP AG.
When using the SAPHANA driver, it requires the ODBC driver (64-bit) for SAP HANA from SAP. The ODBC driver version 1.00 is part of the SAP HANA Client.
The SAS Federation Server Manager requires that a minimum of Java 7 be installed on the host before doing the SAS deployment. Not doing so will cause SAS Federation Server Manager to not install. Please make sure that Java is installed prior to starting the SAS deployment process.
The following data sources can be accessed by the SAS Federation Server:
When using the SAP (R3) driver, the SAP Kernel Release 4.6C or higher is required. The Driver for SAP for Windows and UNIX requires the 64-bit SAP Unicode RFC library, Release 7.20, which is provided by SAP AG.
When using the SAPHANA driver, it requires the ODBC driver (64-bit) for SAP HANA from SAP. The ODBC driver version 1.00 is part of the SAP HANA Client.
The SAS Federation Server Manager requires that a minimum of Java 7 be installed on the host before doing the SAS deployment. Not doing so will cause SAS Federation Server Manager to not install. Please make sure that Java is installed prior to starting the SAS deployment process.
The following data sources can be accessed by the SAS Federation Server:
When using the SAP (R3) driver, the SAP Kernel Release 4.6C or higher is required. The Driver for SAP for Windows and UNIX requires the 64-bit SAP Unicode RFC library, Release 7.20, which is provided by SAP AG.
When using the SAPHANA driver, it requires the ODBC driver (64-bit) for SAP HANA from SAP. The ODBC driver version 1.00 is part of the SAP HANA Client.
The SAS Federation Server Manager requires that a minimum of Java 7 be installed on the host before doing the SAS deployment. Not doing so will cause SAS Federation Server Manager to not install. Please make sure that Java is installed prior to starting the SAS deployment process.
The following data sources can be accessed by the SAS Federation Server:
When using the SAP (R3) driver, the SAP Kernel Release 4.6C or higher is required. The Driver for SAP for Windows and UNIX requires the 64-bit SAP Unicode RFC library, Release 7.20, which is provided by SAP AG.
When using the SAPHANA driver, it requires the ODBC driver (64-bit) for SAP HANA from SAP. The ODBC driver version 1.00 is part of the SAP HANA Client.
The SAS Federation Server Manager requires that a minimum of Java 7 be installed on the host before doing the SAS deployment. Not doing so will cause SAS Federation Server Manager to not install. Please make sure that Java is installed prior to starting the SAS deployment process.
The following data sources can be accessed by the SAS Federation Server:
When using the SAP (R3) driver, the SAP Kernel Release 4.6C or higher is required. The Driver for SAP for Windows and UNIX requires the 64-bit SAP Unicode RFC library, Release 7.20, which is provided by SAP AG.
When using the SAPHANA driver, it requires the ODBC driver (64-bit) for SAP HANA from SAP. The ODBC driver version 1.00 is part of the SAP HANA Client.
The SAS Federation Server Manager requires that a minimum of Java 7 be installed on the host before doing the SAS deployment. Not doing so will cause SAS Federation Server Manager to not install. Please make sure that Java is installed prior to starting the SAS deployment process.
The following data sources can be accessed by the SAS Federation Server:
When using the SAP (R3) driver, the SAP Kernel Release 4.6C or higher is required. The Driver for SAP for Windows and UNIX requires the 64-bit SAP Unicode RFC library, Release 7.20, which is provided by SAP AG.
When using the SAPHANA driver, it requires the ODBC driver (64-bit) for SAP HANA from SAP. The ODBC driver version 1.00 is part of the SAP HANA Client.
A DataFlux driver for Teradata is optional.
SAS makes the following recommendations for SAS Metadata Server deployments:
The disk I/O performance of any server-class system should be sufficient. Memory requirements are highly dependent on the product mix and usage, but 8 GB of RAM are sufficient for most large deployments. For many deployments, 4 GB of RAM are sufficient and should be considered a minimum, unless the specific deployment is tested and verified to require less memory.
SAS Real-time Decision Manager has two types of middle tiers, the Operational Mid-Tier (for executing campaigns) and the Design Mid-Tier (for designing campaigns). Both middle tiers are J2EE applications that run within a J2EE application server.
The SAS Federation Server Manager requires that a minimum of Java 7 be installed on the host before doing the SAS deployment. Not doing so will cause SAS Federation Server Manager to not install. Please make sure that Java is installed prior to starting the SAS deployment process.
The SAS Federation Server Manager requires that a minimum of Java 7 be installed on the host before doing the SAS deployment. Not doing so will cause SAS Federation Server Manager to not install. Please make sure that Java is installed prior to starting the SAS deployment process.
The SAS Federation Server Manager requires that a minimum of Java 7 be installed on the host before doing the SAS deployment. Not doing so will cause SAS Federation Server Manager to not install. Please make sure that Java is installed prior to starting the SAS deployment process.
The SAS Federation Server Manager requires that a minimum of Java 7 be installed on the host before doing the SAS deployment. Not doing so will cause SAS Federation Server Manager to not install. Please make sure that Java is installed prior to starting the SAS deployment process.
The SAS Federation Server Manager requires that a minimum of Java 7 be installed on the host before doing the SAS deployment. Not doing so will cause SAS Federation Server Manager to not install. Please make sure that Java is installed prior to starting the SAS deployment process.
The SAS Federation Server Manager requires that a minimum of Java 7 be installed on the host before doing the SAS deployment. Not doing so will cause SAS Federation Server Manager to not install. Please make sure that Java is installed prior to starting the SAS deployment process.
For information about the application server that is required for SAS Real-Time Decision Manager, select the link for Web Application Servers and HTTP Servers at http://support.sas.com/resources/thirdpartysupport/index.html.
The middle tier of the SAS® 9.4 Intelligence Platform includes a SAS Web Application Server and a SAS Web Server for use as an HTTP server. For more information, see
http://support.sas.com/resources/thirdpartysupport/v94/appservers/index.html.
The SAS Web Application Server is a lightweight server that provides enterprise-class features for running SAS web applications. For more information see
http://support.sas.com/resources/thirdpartysupport/v94/appservers/index.html.
DataFlux Data Management Studio Clients for SAS Decision Services Clients includes a DataFlux Data Management Quality Knowledge Base Locale of choice.
SAS Decision Services Toolkit clients are available for download from the Demos and Downloads website at http://support.sas.com/demosdownloads/setupcat.jsp?cat=SAS+Decision+Services.
Support for presentation virtualization environments (for example, Citrix) for clients included with Real-Time Decision Manager is consistent with the SAS corporate support policy, which can be found at http://support.sas.com/techsup/pcn/virtualization.html.
The list of Web browsers that SAS supports is updated as new products are tested and approved. For the latest information, visit the SAS 9.4 Support for Web Browsers and Plug-Ins page at http://support.sas.com/resources/thirdpartysupport/v94/browsers.html.
Some SAS Web applications use Adobe Flash Player to provide interactive functionality. For support information, see http://support.sas.com/resources/thirdpartysupport/v94/browsers.html#flash.
SAS Real-Time Decision Manager 6.3 can connect to various databases using SAS/ACCESS. The following is the list of database versions with which SAS Real-Time Decision Manager 6.3 is compatible:
Connectivity to Oracle RAC is supported via connection strings containing one Oracle Single Client Access Name (SCAN) listener address. Support has the following limitations:
If staging capabilities are used, HBase version 0.94.11 or higher is required.
For more information, visit SAS Install Center http://support.sas.com/installcenter/.
Memory requirements for optimal performance may vary, and should be determined based on consultation with SAS Enterprise Excellence Center.
Requirements for the Operational Mid-Tier will vary based on the number of requests from other systems and the number of processes that are running concurrently.
Requirements for the Design Mid-Tier will vary based on the requirements of other Web applications, number of total and concurrent users accessing server, and the amount of content accessed by the user.
These values represent the amount of disk space that the SAS Real-Time Decision Manager Server setup directories may require. Additional space may also be required for new content and customization.
Additional disk space will be required for third-party software. The following are examples of third-party software that may be required based on your configuration:
Memory requirements for optimal performance may vary, and should be determined based on consultation with SAS.
Requirements for the Server Tier will vary based on the number of requests from other systems and the number of processes that are running concurrently.
The amount of disk space that the SAS Real-Time Decision Manager Server, SAS Federation Server, and DataFlux Authentication Server set up directories may require is indicated below:
Additional space may also be required for new content and customization.
Additional disk space will be required for third-party software, such as a Database Client.
For memory and disk space requirements, see the SAS 9.4 system requirements at http://support.sas.com/resources/sysreq/index.html under the relevant operating system.
SAS software may be provided with certain third-party software, including but not limited to open-source software, which is licensed under its applicable third-party software license agreement. For license information about third-party software distributed with SAS software, refer to http://support.sas.com/thirdpartylicenses.