Integrate App Volumes Manager and Workspace ONE Intelligent Hub with Omnissa Access

This integration allows App Volumes applications to be available in the Intelligent Hub catalog and delivered to entities when launched based on the entitlements within App Volumes Manager.

This integration synchronizes only the CURRENT package of an application and the associated Active App Links of that application between App Volumes Manager and Workspace ONE Intelligent Hub. After synchronization, the application is listed in the Intelligent Hub catalog. Based on the application assignment in App Volumes Manager, the application is delivered to an end user when the user launches the application from the Intelligent Hub catalog.

Prerequisites

• Ensure that App Volumes and Omnissa Access are configured with the same identity provider.

  Only Active Directory can be used as the identity provider.

• Ensure that you assign the entity with an application which has a CURRENT package. Only users delivered with the CURRENT packages can access applications from the Intelligent Hub catalog.

• Ensure that the App Volumes agent is installed on the target endpoint so that the end user can see the application at launch.

• Only assigned applications are available for end users in the Intelligent Hub catalog, as a result ensure that you assign the applications to entities in App Volumes Manager.

• Ensure that you have the Omnissa Access Tenant URL.

  Important: In anticipation of the upcoming URL migration changes described in KB article 6001062, if your Omnissa Access tenant URL falls in the list of environments under Category 2 - Certificate Branding and URL Change, use the corresponding new URL listed in the New URL column. The new URL has been made available for this use case ahead of the migration for your convenience. Do not use it for any other use cases. The migration timeline will be communicated to all customers through the KB article.

• Ensure that you have completed all the prerequisites in Omnissa Access.
  Keep the Client ID and Shared Secret information handy because this is required when adding this integration.

  For more information about these prerequisites, see Providing Access to App Volumes Packaged Applications in the Setting up Resources in Omnissa Access documentation at Omnissa Product Documentation.

Events that trigger synchronization between App Volumes Manager and Omnissa Access

When the following events occur, synchronization between App Volumes Manager and Omnissa Access is automatically triggered and the list of applications get updated in the Intelligent Hub catalog:

• Change (set or unset) the CURRENT status of a package.
• Activate or deactivate an App Link.
• Update (add or remove) the assignments of an application.
• Edit the integration between App Volumes Manager and Omnissa Access such as change the name of the integration.
• Delete an application.

Procedure

1. Go to INFRASTRUCTURE > Integrations.

2. In the Add App Volumes Integration page, fill up the following information:

   Option	Description
   Type	Select Workspace ONE Intelligent Hub with Omnissa Access.
   Name	Enter a name for this integration.
   Client ID	Enter the Client ID specified when adding a Client in the Oauth 2.0 Management settings within Omnissa Access.
   Client Secret	Enter the Shared Secret generated when the Client is created.
   Tenant	Enter the Omnissa Access tenant URL.

3. Click Add; again, in the Add Integration window, click Add.

   App Volumes Manager is integrated with Omnissa Access.

Results

App Volumes applications with CURRENT packages and those associated with Active App Links are automatically synchronized with Omnissa Access and available in the Intelligent Hub catalog for the end user.

What To Do Next

You can perform any of these tasks:

• In the App Volumes Integration page, to edit the integration, select the integration you want, and click Edit.

  Note:

  • Any change in the integration configuration results in an automatic synchronization between App Volumes Manager and Omnissa Access.
  • If the Client Configuration in the OAuth 2.0 Management settings changes, then the synchronization fails.

• Instead of waiting for the scheduled background job to run, for example: if a package fails to synchronize, you can Manually Synchronize App Volumes Manager and Third Party Services.

• Delete App Volumes Manager Integration with Third Party Services