Resources
System Requirements
SAS® Financial Crimes Monitor 3.1

Server Tier Requirements

SAS Financial Crimes Monitor SAS Server

Please select a target environment:

SAS Financial Crimes Monitor SAS Server includes a SAS Quality Knowledge Base locale of choice.

SAS/ACCESS Engines

SAS Financial Crimes Monitor SAS Server includes a SAS/ACCESS engine of choice for the customer's transaction data. It also includes a second SAS/ACCESS engine of choice, for solution application data, selected from the following list:

  • SAS/ACCESS Interface to DB2
  • SAS/ACCESS Interface to Microsoft SQL Server
  • SAS/ACCESS Interface to MySQL
  • SAS/ACCESS Interface to Oracle

Databases

The following are the database system requirements for SAS Financial Crimes Monitor SAS Server:

  • DB2 Enterprise 9.7
  • MySQL Community 5.1 and 5.5
  • Oracle Enterprise 10g and 11g2
  • SQL Server 2008

SAS Financial Crimes Monitor Data Management Standard and BI Server

Please select a target environment:

SAS Financial Crimes Monitor Data Management Standard and BI Server includes the same two SAS/ACCESS engines that were included with the SAS Financial Crimes Monitor SAS Server.

SAS Financial Crimes Monitor Data Management Standard and BI Server also includes a SAS Quality Knowledge Base locale of choice. Unless otherwise specified, SAS Quality Knowledge Base Locale for English (USA) will be included by default.

SAS Metadata Server

Please select a target environment:
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

Please select a target environment:

SAS Data Management Standard DataFlux Server includes a DataFlux Data Management Quality Knowledge Database locale of choice. It must be the same locale that was selected for the SAS Financial Crimes Monitor Data Management Standard, and BI Server.

SAS Data Management Standard DataFlux Server also includes a DataFlux Data Management Contextual Extraction Language Pack of choice.

DataFlux Authentication Server

Please select a target environment:

Middle Tier Requirements

SAS Financial Crimes Monitor Mid-Tier

Please select a target environment:

SAS BI Server Mid-Tier

Please select a target environment:

Application Servers

The following list describes the application servers supported by SAS 9.3 and the operating systems on which they are supported.

  • JBoss 4.3 (JBoss Community 4.2.3): AIX 6.1 and 7.1, HP-UX 11iv3 (11.31) for the Itanium Processor Family, Red Hat Enterprise Linux 5 and 6, SuSE Linux Enterprise 10 and 11, Solaris 10, Solaris 10 for x64, Windows Server 2003 x64, Windows Server 2008 x64
  • JBoss 5.1.1 (JBoss Community 5.1.0): AIX 6.1 and 7.1, HP-UX 11iv3 (11.31) for the Itanium Processor Family, Red Hat Enterprise Linux 5 and 6, SuSE Linux Enterprise 10 and 11, Solaris 10, Solaris 10 for x64, Windows Server 2003 x64, Windows Server 2008 x64
  • BEA WebLogic 10.3 (10gr3): AIX 6.1 and 7.1, HP-UX 11iv3 (11.31) for the Itanium Processor Family, Red Hat Enterprise Linux 5 and 6, SuSE Linux Enterprise 10 and 11, Solaris 10, Solaris 10 for x64, Windows Server 2003 x64, Windows Server 2008 x64
  • IBM WebSphere ND 7.0.0.13: AIX 6.1 and 7.1, Red Hat Enterprise Linux 5 and 6, SuSE Linux Enterprise 10 and 11, Solaris 10, Solaris 10 for x64, Windows Server 2008 x64 R2
  • IBM WebSphere ND 8.0.0.2: AIX 6.1 and 7.1, Red Hat Enterprise Linux 5 and 6, SuSE Linux Enterprise 10 and 11, Solaris 10, Solaris 10 for x64, Windows Server 2008 x64 R2

Note that if you use JBoss as your application server, JBoss 5.1 is recommended. Use of JBoss AS (Community) 4.2.3 and JBoss EAP 4.3.0 through 4.3.0 CP07 results in a deployment error and requires a manual workaround.


Client Tier Requirements

SAS Data Management Standard, and BI Server Clients

Please select a target environment:

SAS Data Management Standard DataFlux Studio on Windows

SAS Products installed to this machine:
  • DataFlux Data Management Studio 2.4
  • DataFlux Data Management Studio Platform 2.4
  • SAS Data Quality Desktop 2.4
Disk Space Consumed by Installed Products: 210 MB
Supported Environments:
  • Windows 7 Enterprise (32-bit version) on the x64 chip family
  • Windows 7 Enterprise (64-bit version) on the x64 chip family
  • Windows 7 Professional (32-bit version) on the x64 chip family
  • Windows 7 Professional (64-bit version) on the x64 chip family
  • Windows 7 Ultimate (32-bit version) on the x64 chip family
  • Windows 7 Ultimate (64-bit version) on the x64 chip family
  • Windows 8 (32-bit version) on the x64 chip family
  • Windows 8 (64-bit version) on the x64 chip family
  • Windows 8 Enterprise (32-bit version) on the x64 chip family
  • Windows 8 Enterprise (64-bit version) on the x64 chip family
  • Windows 8 Pro (32-bit version) on the x64 chip family
  • Windows 8 Pro (64-bit version) on the x64 chip family
  • Windows HPC Server 2008 Edition (32-bit version) on the x64 chip family
  • Windows HPC Server 2008 Edition (64-bit version) on the x64 chip family
  • Windows HPC Server 2008 R2 Edition (64-bit version) on the x64 chip family
  • Windows Server 2003 SP1 Enterprise Edition (32-bit version) on the x64 chip family
  • Windows Server 2003 SP1 Enterprise Edition (64-bit version) on the x64 chip family
  • Windows Server 2003 SP1 Datacenter Edition (32-bit version) on the x64 chip family
  • Windows Server 2003 SP1 Datacenter Edition (64-bit version) on the x64 chip family
  • Windows Server 2003 SP1 Standard Edition (32-bit version) on the x64 chip family
  • Windows Server 2003 SP1 Standard Edition (64-bit version) on the x64 chip family
  • Windows Server 2003 SP1 Small Business Server (32-bit version) on the x64 chip family
  • Windows Server 2008 Datacenter Edition (32-bit version) on the x64 chip family
  • Windows Server 2008 Datacenter Edition (64-bit version) on the x64 chip family
  • Windows Server 2008 Datacenter without Hyper-V Edition (32-bit version) on the x64 chip family
  • Windows Server 2008 Datacenter without Hyper-V Edition (64-bit version) on the x64 chip family
  • Windows Server 2008 Enterprise Edition (32-bit version) on the x64 chip family
  • Windows Server 2008 Enterprise Edition (64-bit version) on the x64 chip family
  • Windows Server 2008 Enterprise without Hyper-V Edition (32-bit version) on the x64 chip family
  • Windows Server 2008 Enterprise without Hyper-V Edition (64-bit version) on the x64 chip family
  • Windows Server 2008 Foundation Edition (32-bit version) on the x64 chip family
  • Windows Server 2008 Foundation Edition (64-bit version) on the x64 chip family
  • Windows Server 2008 R2 Datacenter Edition (64-bit version) on the x64 chip family
  • Windows Server 2008 R2 Enterprise Edition (64-bit version) on the x64 chip family
  • Windows Server 2008 R2 Foundation Edition (64-bit version) on the x64 chip family
  • Windows Server 2008 R2 Standard Edition (64-bit version) on the x64 chip family
  • Windows Server 2008 Small Business Server (32-bit version) on the x64 chip family
  • Windows Server 2008 Small Business Server (64-bit version) on the x64 chip family
  • Windows Server 2008 Standard Edition (32-bit version) on the x64 chip family
  • Windows Server 2008 Standard Edition (64-bit version) on the x64 chip family
  • Windows Server 2008 Standard without Hyper-V Edition (32-bit version) on the x64 chip family
  • Windows Server 2008 Standard without Hyper-V Edition (64-bit version) on the x64 chip family
  • Windows Server 2008 Storage Server (32-bit version) on the x64 chip family
  • Windows Server 2008 Storage Server (64-bit version) on the x64 chip family
  • Windows Server 2012 Datacenter Edition (64-bit version) on the x64 chip family
  • Windows Server 2012 Essentials Edition (64-bit version) on the x64 chip family
  • Windows Server 2012 Foundation Edition (64-bit version) on the x64 chip family
  • Windows Server 2012 Standard Edition (64-bit version) on the x64 chip family
  • Windows Vista Business (32-bit version) on the x64 chip family
  • Windows Vista Business (64-bit version) on the x64 chip family
  • Windows Vista Enterprise (32-bit version) on the x64 chip family
  • Windows Vista Enterprise (64-bit version) on the x64 chip family
  • Windows Vista Ultimate (32-bit version) on the x64 chip family
  • Windows Vista Ultimate (64-bit version) on the x64 chip family
  • Windows XP Professional SP2 (32-bit version) on the x64 chip family
  • Windows XP Professional SP2 (64-bit version) on the x64 chip family

The SAS Data Management Standard DataFlux Studio Client includes a DataFlux Data Management Contextual Extraction Language Pack of choice and a DataFlux Data Management Quality Knowledge Base Locale of choice. The same choices must be made as were selected for SAS Data Management Standard DataFlux Server.

Web Browsers

SAS Financial Crimes Monitor 3.1 supports the following web browsers:

  • Internet Explorer 7, 8, and 9
  • Firefox 3 and higher

SAS and all other SAS Institute product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. Other brand and product names are registered trademarks or trademarks of their respective companies.
© indicates USA registration.
Copyright © 2013 SAS Institute Inc., Cary, NC, USA. All rights reserved.