As long as the data source supports LDAP (Lightweight Active Directory Protocol) or ODBC (Open Database Connectivity), then SAFE may receive data from the data source.
If the data source does not support LDAP or ODBC, there may be some minimal effort to provide another connection. The Data Source Agent also supports other integration connectors to outside systems such as: JDBC (Java Database Connectivity), Web Services, Email/POP, etc. (Additional fees may apply.)
Received data records are imported into corresponding records and fields within a XML format for processing by the SAFE rules engine.
The SAFE solution runs on a Microsoft SQL Server or Oracle database platforms.
Typically IT is needed to ensure the server is setup properly per IT organization standards as it relates to the server location(s), approval of software installed, server maintenance and backups, firewall settings, etc.
SAFE Platform components are divided into three tiers (logical nodes): Web Tier, Application Tier, Database Tier. Each tier may be implemented on one server or many depending on the scope of the install.
It runs on a Microsoft SQL Server or Oracle database platforms which are highly secure, scalable, and support high availability. Communication with the database is based on industry standard ODBC (Open Database Connectivity) architecture and SQL (Structured Query Language).

Hardware requirements are dependent on the scope of the implementation. The minimal hardware requirements include:
1. 2 x Dual Core Intel® Xeon® 2.8 GHz+
Processor
2. 8 GB RAM
3. 2 x 120GB SATA Hard Drive
4. 2 x GigE (Gigabit Ethernet) Network
Interfaces
5. ON BOARD SATA RAID
6. 2 x USB port
7. 24x IDE DVD-ROM (Universal Media Bay)
8. VGA plus graphics interface

Typically, the server is deployed in your organizations IT datacenter. In some cases, though, it is deployed within your organization’s security operations center.
SAFE’s architecture is modular and services based thus supporting easy distribution of components on standard, commercial enterprise, computing platforms designed to support high availability and load balancing.
Database Redundancy and Backups: The purpose of SAFE’s System Backup is to preserve the deployed state of the system including necessary configuration in the event of disaster recovery.

The following components are recommended to be backed up:

• Important Configurations
• Business Data
• Databases

The frequency of its System Backup is context specific and varies depending on each customer’s needs.
It is recommended to backup the Database, Biztalk Database, SQL Server Jobs and SQL Linked Server Configurations
nightly. Database redundancies may also be setup.

It is strongly recommended that the SAFE System is backed up on a regular basis so it may be restored quickly and easily in the event of a disaster. The disaster recovery plan typically involves also deploying a remote failover architecture which allows a secondary datacenter to take over mission-critical operations in the event that a disaster strikes the primary datacenter.
Requirements from the customer typically involve ensuring the organization’s high availability, backup procedures and disaster recovery policies are met.
The SAFE solution supports standards-based authentication through LDAP to corporate directory servers or Windows Active Directory. Authorization and access to data and applications is defined using role-based groups and profiles as consistent with industry best practices.
SAFE supports Simple Mail Transfer Protocol (SMTP) for email support and may be configured to communicate with email systems such as: Microsoft Exchange.
In addition to supporting highly secure database platforms, SAFE leverages communication protocols such as Transmission Control Protocol (TCP) between the logical components and the SAFE solution. Protocol configurations are controlled by the organization’s IT standards within their secure environment. Access is role based to limit user viewing. Message queuing is encrypted.