SAS Real-Time Decision Manager is available for both distributed and non-distributed SAS LASR Analytic Server deployments. These system requirements apply to both LASR deployments. The headings below indicate whether components apply to a specific LASR deployment.
The Design Server is used with the SAS Real-Time Decision Manager Run-Time Server, which deploys decisions. For more information, see the separate System Requirements document for the Run-Time Server.
SAS Real-Time Decision Manager (Distributed LASR) includes the distributed version of SAS Visual Analytics Administration and Reporting. 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.
To keep pace with changes to third-party technologies, SAS has adopted a general policy of supporting one or more baseline major versions and subsequent minor updates for each officially supported operating system. For example, if the baseline for SAS x is Red Hat Enterprise Linux 6.1, SAS x will also support Red Hat Enterprise Linux 6.7 under this policy.
The full SAS Support policy that applies to third-party software can be found at https://support.sas.com/en/documentation/third-party-software-reference/baseline-and-higher.html. As part of this policy, SAS strongly encourages customers to install the latest operating-system service packs.
With SUSE Linux Enterprise Server 12, SP2 is required.
SAS Real-Time Decision Manager Design Server includes two SAS/ACCESS engines of choice from the following list:
SAS Real-Time Decision Manager Design Server also includes three SAS Metadata Bridges of choice, plus General Industry Standards, which is included automatically.
For information about the requirements for SAS Data Integration Server, refer to the system requirements document for that offering.
With SUSE Linux Enterprise Server 12, SP2 is required.
SAS Federation Server includes a SAS Federation Server Driver of choice, either Greenplum, Netezza, or Teradata.
DB2 and PostgreSQL are Federation Server drivers that are automatically included in Real-Time Decision Manager, along with the Oracle driver.
With SUSE Linux Enterprise Server 12, SP2 is required.
With SUSE Linux Enterprise Server 12, SP2 is required.
SAS Visual Analytics Administration and Reporting Server, Distributed or Non-Distributed LASR includes a standard SAS/ACCESS engine of choice. This must be the same as the SAS Real-Time Decision Manager Design ACCESS engine; others are licensed separately.
With SUSE Linux Enterprise Server 12, SP2 is required.
SAS Solution LASR Analytic Server, Non-Distributed LASR includes a standard SAS/ACCESS engine of choice (for transactional data purposes) as available per platform. This must be the same as the SAS Visual Analytics Administration and Reporting ACCESS engine; others are licensed separately.
With SUSE Linux Enterprise Server 12, SP2 is required.
If you want to colocate SAS software with Hadoop File System (HDFS), the maintenance release number of your SAS 9.4 software determines the requirements for your colocated Hadoop deployment:
For information about supported Hadoop distributions, refer to https://support.sas.com/en/documentation/third-party-software-reference/9-4/support-for-hadoop.html. The plug-ins require additional configuration. For more information, see SAS High-Performance Analytics Infrastructure 3.5: Installation and Configuration Guide at http://support.sas.com/documentation/onlinedoc/hp-analytics-infrastructure/index.html.
With SUSE Linux Enterprise Server 12, SP2 is required.
SAS Business Rules Manager Server includes a standard SAS/ACCESS engine of choice, either Oracle or PostgreSQL.
With SUSE Linux Enterprise Server 12, SP2 is required.
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.
SAS Data Management Studio Clients server includes a Quality Knowledge Base Locale of choice.
SAS Decision Services Toolkit is provided via customer download for Windows 32-bit workstations and Windows for x64 workstations.
SAS Visual Analytics Mobile Clients (SAS Mobile BI) are available for the Apple iPad and Android tablets via free downloads from app stores.
SAS Real-Time Decision Manager 6.4 can connect to various databases using SAS/ACCESS. The following is the list of database versions with which SAS Real-Time Decision Manager 6.4 is compatible:
Note: Microsoft software Server Failover Cluster is not
supported.
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 utilized, HBase version 0.94.11 or higher is required.
Note: Teradata, Netezza, and Greenplum are massively parallel processing data storage technologies often deployed as enterprise data warehouses. Databases deployed in this manner may not have the performance necessary for certain high-throughput SAS Real-Time Decision Manager usage scenarios. Consult with SAS Customer Intelligence Professional Services before deploying SAS Real-Time Decision Manager with these databases. The SAS Real-Time Decision Manager Administrator's Guide provides further guidance on this matter.
For more information, visit SAS Install Center at 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.
This figure represents 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 setup directories may require is listed 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 for the relevant operating system: http://support.sas.com/resources/sysreq/index.html.
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.