The ADMINISTRATION > SETTINGS page lets you configure your shared workspace by setting properties and enabling features on the Mobile Center server.
Select a category from the left panel. After you modify the settings in a specific section, click Verify and Save and wait for the server to acknowledge your changes. To erase the changes that you made, click Discard Changes in the top right of the screen.
You can set properties in the following areas:
This section lets you configure general settings, such as compatibility validation, lock duration (for consecutive failed logins on the account and for idle devices), password expiration time, and the collection of anonymous usage data. You can also specify the string for Single Sign-On logins.
The default password expiration is 180 days. Twenty days before the expiration date, Mobile Center issues a warning to the user to change the password. A "0" value indicates no expiration date. To prevent users from being locked out after entering a wrong password three times, set the Lock duration to "0".
If a user's password expires or if a user forgets their password, an administrator can reset it. For details, see Manage user accounts with scripts.
The Single Sign-on Init string is mandatory for integration with the ALM extension for Mobile Center. Paste in the value of the COMMUNICATION_SECURITY_PASSPHRASE flag from the ALM Site Administration. If you leave this field empty, single sign-on will not work. For details, see Open the Mobile Center wizard.
|Proxy setting (web access)||
The Proxy settings let you specify the name, port, and credentials of the proxy server for the extended services.
When using the Early access features for multiple projects, this settings is controlled globally by the operator.
This section lets you set the default reservation duration and extension times.
|Android/ iOS packaging service||
To enable record and replay functionality when testing certain apps, you need to repackage them with Mobile Center libraries. These sections allow you to specify the host machine, port, and protocol for the Android and iOS packagers. For details, see App packaging and signing services.
|Amazon Device Farm integration||
Amazon Device Farm (ADF) integration lets you use devices from the Amazon farm for testing purposes.
In this section, you provide the AWS security credentials. If you created a project that you want to use through the EC2 interface, specify its name here.
For details, see AWS Device Farm integration or follow the links to the AWS documentation in this pane.
|Production Usage (AppPulse Integration)||
In this section, you enable AppPulse Mobile integration. AppPulse Mobile lets you know how your users really experience your app, and identify the problems that influence most users or affect functionality in a critical way.
To prepare your machine for working with AppPulse Mobile, see Configure Mobile Center to work with AppPulse Mobile (for administrator)
For details on using AppPulse, see View AppPulse Mobile analytics.
Tip: You must click Save in each section to which you made changes, to make your selections effective.
|Security Scan (FoD integration)||
FoD (Fortify On Demand) lets you scan and assess the security of your app at all stages of development. In this section, you enable the FoD integration.
All fields in this section are mandatory, except for the Tenant time zone. For details, see Security Scan.
|Crowd Testing (Ubertesters integration)||
Ubertesters integration helps you perform crowd testing, by allowing you to monitor and manage your mobile beta testers and the testing process.
In this section, you enable and configure the Ubertesters integration. For details, see Crowd Testing.
|App X-Ray (SafeDK integration)||
SafeDK offers proprietary technology and an SDK Marketplace to support the mobile app development cycle.
In this section, you can enable the SafeDK integration. For details, see App X-Ray.
|Network Virtualization integration||
This section lets you specify the NV Test Manager machine information, its authentication token, and the protocol to use (HTTP or HTTPS).
For details about these settings, see Set up Network Virtualization integration in Mobile Center.
For information on how to set up your machine and devices, see Network Virtualization integration.
Organizations that use LDAP to manage their user accounts, can let users access Mobile Center with their LDAP credentials.
When using the Early access features for multiple projects, some of these settings are controlled globally by the operator.
Considerations when using LDAP: