SAS Anti-Money Laundering Alert Generation Server includes three Metadata Bridges of choice, and a SAS Quality Knowledge Base Locale of choice.
SAS Anti-Money Laundering Alert Generation Server also includes a SAS/ACCESS engine of choice for SAS Anti-Money Laundering, and a SAS/ACCESS engine of choice for SAS Enterprise Case Management, selected from the following lists, respectively:
One SAS/ACCESS engine of choice for SAS Anti-Money Laundering:
One SAS/ACCESS engine of choice for SAS Enterprise Case Management:
Note: SAS/ACCESS Interface to Microsoft SQL Server runs on all supported SAS platforms except Microsoft Windows. For Microsoft Windows platforms, please use SAS/ACCESS Interface to ODBC.
SAS recommends that you deploy SAS Metadata Server on a 64-bit host system. The SAS Metadata Server is multi-threaded and multi-core server hardware (typically quad core or higher) is recommended. A dedicated machine for the SAS Metadata Server is recommended to simplify tuning, management, and diagnostics, but is not required. 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 8GB of RAM is sufficient for most large deployments. 4GB of RAM is sufficient for many deployments and should be considered a minimum unless the specific deployment is tested and verified to require less memory.
SAS Data Management Standard DataFlux Server includes a DataFlux Data Management Quality Knowledge Base Locale of choice (which should be the same as was selected for SAS Data Management Standard SAS Server) and a DataFlux Data Management Contextual Extraction Language Pack of choice.
The following list describes the application servers supported by SAS 9.3 and the operating systems on which they are supported:
For information about the Application Servers supported by SAS 9.3, please visit the SAS 9.3 Web Application Servers and HTTP Servers page at http://support.sas.com/resources/thirdpartysupport/v93/appservers/index.html
SAS Anti-Money Laundering supports the following databases:
Note: To leverage advanced tuning features such as bitmap indexing and data partitioning, SAS recommends that you deploy SAS Anti-Money Laundering on Oracle Enterprise Edition instead of Oracle Standard Edition. Oracle Enterprise Edition offers features required for tuning high volume databases. Please consult with your Oracle licensing representative for a complete list of features available.
*The Investigation UI functionality is supported only on DB2, Oracle, and SQL Server. When necessary, it is possible to use separate databases for the Server Tier for Teradata or MySQL.
SAS Anti-Money Laundering 5.1 depends on SAS Shared Services for various components. For example, SAS Workflow is delivered with the SAS Intelligence Platform as a component of SAS Shared Services. In addition, SAS Anti-Money Laundering uses SAS Content Server for storing files in the WebDAV repository.
CAUTION: Do not use the SAS Framework Data Server as a database for SAS Shared Services.
Do not use the SAS Framework Data Server as a database for SAS Shared Services. When feasible, configure the SAS Shared Services database on the same RDBMS that you configure for SAS Anti-Money Laundering. Since Shared Services does not support the use of Teradata as the RDBMS, customers using Teradata as their RDBMS for SAS Anti-Money Laundering will need to configure an alternate RDBMS for the SAS Shared Services database. Please note other RDBMS restrictions stated above.
SAS Data Management Standard DataFlux Studio includes a DataFlux Data Management Quality Knowledge Base Locale of choice and a DataFlux Data Management Contextual Extraction Language Pack of choice.
Please see the SAS AppDev Studio system requirements for the latest information about its requirements.
JMP Pro is included with SAS Anti-Money Laundering 5.1.