Home
Configuring Mobile
Use the HCL Connections mobile app to perform common tasks from a mobile device.
Configuring security for Mobile
You can secure devices that access Connections content using the Connections mobile app.
Mobile Device Management (MDM)
You can use a Mobile Device Management (MDM) solution to manage devices where the HCL Connections mobile app is installed.
AppConfig for iOS
This help topic describes the steps required for an Enterprise Mobility Management (EMM) administrator to deploy the HCL Connections Mobile app for iOS. The app deployed in this scenario is the base HCL Connections for iOS mobile app that is distributed from the Apple app store. This article applies to Connections for iOS version 6.0.5 and higher. This procedure requires a Mobile Device Management (MDM) profile to be provisioned to the device by your EMM. Any EMM can be used that has the capability of managing an Apple iOS device, though this help topic will provide examples based on HCL’s MaaS360 EMM.
Distributing Connection for iOS to devices
Connections for iOS must be placed into your EMM provider’s enterprise app catalog for it to properly managed on an Apple device. Once the app is available in the app catalog, users can easily install it from your EMM provider’s app catalog on the device. Or, if you have enabled a setting to enforce management of all apps listed in the app catalog, then even if a user were to install Connections for iOS directly from Apple iTunes (or even Apple TestFlight), then the app will still become a managed app and behave like a managed app.

Configuring Mobile
Use the HCL Connections mobile app to perform common tasks from a mobile device.
- Accessibility features for HCL Connections™ iOS mobile app
  Accessibility features help users who have a disability, such as restricted mobility or limited vision, to use information technology products successfully.
- Configuring security for Mobile
  You can secure devices that access Connections content using the Connections mobile app.
  - Administering mobile access to Connections servers
    Register devices, deny access to Connections, and wipe data from lost or stolen devices.
  - Configuring access with client certificates
    Configure an extra layer of authentication using client certificates.
  - Mobile Device Management (MDM)
    You can use a Mobile Device Management (MDM) solution to manage devices where the HCL Connections mobile app is installed.
    - Android Enterprise
      Organizations that use Android Enterprise to manage their Mobile Server applications can deploy Android Enterprise application management capabilities with HCL Connections for Android. This includes the ability to provision application configuration settings, and enforce Android Enterprise security policies. The Android Enterprise capability is built directly into the base version of HCL Connections for Android that is delivered to mobile devices by using Google Play. Make sure that your organization is ready to deploy Android Enterprise by reviewing the following information.
    - AppConfig for iOS
      This help topic describes the steps required for an Enterprise Mobility Management (EMM) administrator to deploy the HCL Connections Mobile app for iOS. The app deployed in this scenario is the base HCL Connections for iOS mobile app that is distributed from the Apple app store. This article applies to Connections for iOS version 6.0.5 and higher. This procedure requires a Mobile Device Management (MDM) profile to be provisioned to the device by your EMM. Any EMM can be used that has the capability of managing an Apple iOS device, though this help topic will provide examples based on HCL’s MaaS360 EMM.
      - Managing Connections for iOS on managed devices
        The first step in managing the Connections for iOS app is to define your EMM device policies that are important for your organization. A device policy is required to manage any native iOS app. When a user provisions their device with the device policy, any applications that are installed using the EMM enterprise app catalog or listed in the EMM enterprise app catalog will be installed as managed apps. Managed apps get access to resources such as per app custom configuration and per app VPN tunnels which can only be accessed by your enterprise apps.
      - Distributing Connection for iOS to devices
        Connections for iOS must be placed into your EMM provider’s enterprise app catalog for it to properly managed on an Apple device. Once the app is available in the app catalog, users can easily install it from your EMM provider’s app catalog on the device. Or, if you have enabled a setting to enforce management of all apps listed in the app catalog, then even if a user were to install Connections for iOS directly from Apple iTunes (or even Apple TestFlight), then the app will still become a managed app and behave like a managed app.
      - Creating a custom app configuration profile
        Connections for iOS supports custom managed configurations that allow the EMM administrator to configure many Connections for iOS settings. Any setting defined using the EMM takes precedence over a similar setting or policy defined at the Connections server. Setting custom app configurations will vary by EMM. All EMM providers support the concept of Apple-managed configuration using custom keys and values. However, some EMM providers now support definition of these parameters using an app’s AppConfig XML definition file as defined by the AppConfig Community.
      - Creating app configuration using Citrix XenMobile
        The following steps are based on Citrix XenMobile documentation for defining an App Configuration Device Policy for an iOS app. It is recommended that you consult the XenMobile documentation for your specific version of XenMobile to ensure that these steps have not changed.
      - Restricting file sharing
        Restrict file sharing by setting up a Restrictions Device Policy using your EMM administration portal. The exact label wording may vary from one EMM to another, but typically there will be two specific settings for restricting if files can be shared between managed apps and unmanaged apps. One setting will prohibit sharing of files from managed apps to unmanaged apps. This is the most common setting and is recommended if you are looking to prevent file data from being shared from the Connections for iOS app to other, unmanaged apps that are on the same device. The other setting will prohibit sharing of files from unmanaged apps to managed apps. This is more uncommon to set, but if you have a use case where you want to prevent files, originating from an unmanaged apps, from being imported using Connections for iOS, then prohibit this file sharing.
      - Removing Connections and wiping app data
        Because Connections for iOS is deployed as a managed app, removing the device profile will remove Connections and all Connections data from the device (this is true for all managed apps). A user could do this themselves if the policy allows for this, or the profile could be removed remotely by the EMM administrator. Most EMM providers also allow the administrator to configure automated actions, which can monitor various compliance scenarios. If one of the monitors is triggered, various actions can be automatically executed, ranging from wiping the enterprise apps and data from the device to notifying the user via an email. See your EMM documentation for more information.
      - Connecting to an on-premises Connections server
        Connections for iOS communicates with its Connection server over a secured TLS channel using the HTTPS protocol. Depending on your network topology and the placement of your Connections server (or a reverse proxy in front of it), the server may or may not be directly accessible from the Mobile Server application without deploying a network tunnel.
      - Connections iOS configuration reference
        Use the table that follows as a reference for the custom app configuration XML. This table can be used if your EMM provider does not yet support the AppConfig schema as defined by the AppConfig Community. If your EMM does support an AppConfig.xml file, then download the .zip file containing the Connections_AppConfig.xml file. Note that Connections iOS does not support configuration of multiple accounts using AppConfig.
    - MDM app configuration
      Configuration settings for Mobile Device Management (MDM) apps.
    - Configuring MaaS360 for Workplace Integration
      Configure Fiberlink MaaS360 integration with the HCL® Connections mobile app.
    - Configuring MobileIron for AppConnect Integration
      Configure MobileIron integration with the Connections Mobile app.
    - HCL Connections for AirWatch
      The HCL Connections for AirWatch app builds in support for AirWatch security policies, custom settings, and administrator actions by using an AirWatch provided toolkit. This app provides all of the same features you know from the regular Connections mobile app, but with more security and management capabilities.
    - Configuring Microsoft Intune for Connections Mobile (iOS)
      This help topic details the steps included in configuring the Microsoft Intune endpoint manager for Connections Mobile, specifically for iOS devices.
    - Configuring Microsoft Intune for Connections Mobile (Android)
      This help topic details the steps included in configuring the Microsoft Intune endpoint manager for Connections Mobile, specifically for Android devices.
    - Configuring File Sync for mobile
      Enable File Sync and configure file synchronization properties.
    - Push Notifications
      Users will receive push notifications on their mobile device if it is enabled for the Connections mobile app.
    - Using links to launch or configure Connections Mobile
      Help users to log in to the HCL Connections™ mobile app by using links to launch or configure the server and user information.
    - Customizing Mobile
      Change the appearance of the Connections mobile app.
- HCL Connections™ Social Cloud
  If your users log in to a HCL Connections™ Social Cloud server, there are mobile configuration properties that you can customize for the cloud environment.
- Administering HCL Connections™ 8 mobile
  Depending on the version of HCL Connections™ that your organization is using, there are specific configuration properties that you can customize for the mobile environment.
- Administering HCL Connections™ 7 mobile
  Depending on the version of HCL Connections™ that your organization is using, there are specific configuration properties that you can customize for the mobile environment.
- Administering HCL Connections™ 6.5 mobile
  Depending on the version of HCL Connections™ that your organization is using, there are specific configuration properties that you can customize for the mobile environment.
- Administering HCL Connections™ 6.0 mobile
  Depending on the version of HCL Connections™ that your organization is using, there are specific configuration properties that you can customize for the mobile environment.
- Administering HCL Connections™ 5.5 mobile
  Depending on the version of HCL Connections™ that your organization is using, there are specific configuration properties that you can customize for the mobile environment.

Distributing Connection for iOS to devices

Connections for iOS must be placed into your EMM provider’s enterprise app catalog for it to properly managed on an Apple device. Once the app is available in the app catalog, users can easily install it from your EMM provider’s app catalog on the device. Or, if you have enabled a setting to enforce management of all apps listed in the app catalog, then even if a user were to install Connections for iOS directly from Apple iTunes (or even Apple TestFlight), then the app will still become a managed app and behave like a managed app.

About this task

The steps will vary from one EMM to another on how the app is loaded into the enterprise app catalog, so consult your EMM provider’s documentation. For HCL’s MaaS360, follow these steps:

Procedure

Enable the option that converts apps in the app catalog to managed on devices where the app is installed from another source. This setting is found under Settings > Deployment Settings.. Note that while this is a global setting for MaaS360, some EMM providers ask that you make this decision for each app as you add it to the enterprise app catalog.
Navigate to Apps > Catalog.
Select Add > iTunes App Store App..
For the App Name, enter HCL Connections and select HCL Connections from the list when it is found.
Select the Policies and Distribution tab and enable desired policies and define the users or devices to receive this app.
The configuration tab could be completed at this point or can be done later. Review the section on custom app configuration in this document. Select Add and this app will appear in your enterprise app catalog for iOS devices.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.