MobileAccess Server Deployment

Depending on the size and complexity of your business and your MSCRM deployment, MobileAccess can be configured to support a number of architectures from a single-server Small Business deployment to very complex multiple server enterprise deployments.

The following sections outline three basic deployment concepts, a small business deployment, such as utilizing Microsoft Small Business Server 2003, a standard business deployment installed over 3 or more standalone servers, and a complex Enterprise deployment where multiple servers may be used to support each component of the solution stack.

In all cases, it is recommended that careful consideration be given to the physical hardware characteristics of the servers and infrastructure to ensure that user performance objectives are met.

Small Business Deployment (Single Server)
In this scenario, all software pre-requisites and the MobileAccess server are running simultaneously on a single, physical server.

The single server can either consist of the traditional Microsoft CRM stack on top of Microsoft Windows Server 2003, or on top of Microsoft Small Business Server 2003 (which includes: SQL, Exchange, Active Directory and IIS), with Microsoft CRM and BlackBerry Enterprise Server running.

Standard Business Deployment
This is the most common deployment scenario where MobileAccess is implemented amongst 3 or more servers.

Typically this scenario has one server for Active Directory, Exchange and BES; another server for SQL; and another running Microsoft CRM. MobileAccess must be installed on the Microsoft CRM server.

Enterprise Deployment
In this deployment scenario, the MobileAccess Server is installed on the Microsoft CRM server and participates with numerous application and platform servers within the enterprise domain. There may be multiple BlackBerry Enterprise Servers, SQL and MSCRM servers with each running various versions of operating system and service packs that may require additional configuration.

In this circumstance, we strongly recommend that you contact TenDigits, or your Certified MobileAccess implementation partner to request an expert opinion and/or advice on an optimal, supported configuration.

Test Deployment
To assist in the testing and deployment process, an internal environment can also be developed that includes a BlackBerry simulator environment.

This configuration allows our Implementation Partners or your IT team to test the various functionality, customizations and configurations of the MobileAccess solution prior to deploying it to the field.