Page: Installing the Platform
Page: Installing the Configuration Database
Page: AppServer Installation
Page: Installing AppServer
Page: IIS 7 Configuration
Page: IIS 6 Configuration
Page: Introduction to Plug-ins
Page: Installing AppStudio
Page: Installation Requirements
Page: Configuring IIS Security
Before you can install the AppStudio enterprise mobility platform, you must download and expand the platform's ZIP file. This file is available on the download page. When you expand this file, it has the following file structure:
During the installation procedures, you will install different parts of this file.
This topic describes the requirements for each part of AppStudio enterprise mobility platform:
The AppServer is an internal Web server that runs AppStudio services, and responds to HTTP requests from mobile devices. System requirements include:
- Server-class computer with a minimum of 2x1 GHz CPUs, 4GB RAM, 10GB available disk space
- Windows Server, one of the following:
- 2003 R2 SP2 32-bit
- 2008 R2 SP1 64-bit
- 2012 Standard 64-bit
- IIS 6.0 or later, including IIS 7.5 and IIS 8
- Microsoft .NET Framework v4.x
- IP connectivity to the AppStudio database server and required enterprise and external data sources
Configuration database requirements
The Microsoft SQL Server DBMS hosting configuration database has the following requirements:
- Server-class computer with a minimum of 2x1 GHz CPUs, 2GB RAM, and 20GB disk space available to SQL Server
- Microsoft SQL Server 2005, 2008, or 2012
The workstation running AppStudio has the following requirements:
- Windows 7 64-bit
- Microsoft .NET Framework v4.0 or higher
- IP connectivity to the AppStudio's database server
Mobile device requirements
The following section describe the requirements for each supported mobile device.
Android device system requirements
Android devices must have OS v2.2 through 5.0.
iOS device system requirements
Devices running iOS must run iOS versions 8.x - 9.0.
BlackBerry device system requirements
BlackBerry devices have the following requirements:
- BlackBerry OS 5.x - 7.1
- HTTP connectivity via BlackBerry Enterprise Server (BES), BlackBerry Internet Service (BIS), or WAP 2.0
- eMMC or SD card
For an SD card, you need a minimum capacity of 1 GB with a minimum of 10 MB free.
This section describes the required network connectivity between the major server components of AppStudio's infrastructure for both typical and more complex customer infrastructures.
The following diagram shows servers and network links that are required to run AppStudio enterprise mobility platform:
Review network connectivity requirements before installing AppStudio enterprise mobility platform. Typical preparation includes:
- Establishing IP connectivity between servers.
- Opening firewall ports as needed.
- Configuring HTTP proxies.
- Establishing domain trusts between required servers.
The following table describes some of the connections:
|MDM to data sources|
AppStudio plug-ins run on the AppServer and in AppStudio. Each AppStudio plug-in requires connectivity to its specific data source.
To configure the connection to the MDM and data sources:
|AppServer to configuration database|
The AppServer executes services that issue online data requests to the configuration database server. These services use ADO.NET to exchange SQL requests and data with the database server.
To configure the AppServer to the configuration database:
|AppServer to domain controller|
The AppServer authenticates each HTTP request against the specified domain controller, active directory, or directory using IIS-based NTLM or basic authentication.
To configure the connection between the AppServer and the domain controller:
The IIS server must be able to access and have sufficient trusts for the domain authority to authenticate inbound user requests.
|MDS to AppServer|
BlackBerry Enterprise Server's Mobile Data Service (MDS) handles HTTP requests made via the AppStudio client app from a BlackBerry device, and directs requests to the appropriate AppStudio Web server. HTTP connectivity between MDS and the AppServer, the latter listens on the configured port, typically port 80. AppStudio supports SSL, enabled on the AppServer to encrypt traffic within this connection.
To configure the connection between MDS and the AppServer:
|BES MDS to app on a device|
Configure BES MDS with outbound-only connectivity to the Internet via port 3101; see RIM’s BES documentation.
To configure the connection between BES MDS and a AppStudio app running on a device:
This BES configuration is the same as required for BES to send/receive standard email traffic. If wireless email works, do nothing here.
|AppStudio to configuration database|
AppStudio connects directly to the database server via ADO.NET, using SQL commands to read and write data.
To configure the connection between AppStudio and the configuration database:
Database connection parameters are configured via AppStudio during login, using server name, user ID and password.
Complex infrastructure requirements
This section shows how to configure server and connectivity requirements for customers who use load balancers, proxy servers, and Windows Server 2003.
Configuring a linked server
If you plan to download large volumes of data and memory resources are limited, you can use AppStudio SQL pass-through capability by configuring a required linked server between the configuration database and enterprise data sources. In order to connect to your data via a linked query, configure the appropriate AppStudio plug-in as follows:
- Enable the AllowLinkedQuery connection parameter.
- Assign the LinkDataSource parameter to your linked server name.
For detailed instructions on configuring AppStudio plug-ins to SQL enterprise sources see Working with Plug-ins.
Configuring the AppServer in a Web farm environment
To set the AppServer to support a Web farm:
- Install the AppServer on all desired Web servers.
- On the load balancer, set session data to stick to user profiles.
AppStudio does not store session data on IIS. Authentication requires stored session data, so if you intend to use authentication on a Web farm you must enable sticky sessions on the load balancer to send users to the server hosting their data.