When you remove a connector, resources already imported in Application Workspace are not affected.
The Connectors page displays all connectors currently available in the Application Workspace System.
Selecting multiple table rows
- Adjacent rows: Click on the first row, hold down the Shift key, click on the last row in the range
- Non-adjacent rows: Hold the Ctrl or Cmd key and click on each row you want to select
- Adjacent rows, using only the mouse: Click and hold the left mouse button on the first row, then drag the cursor up or down across the rows to highlight the desired ones
Toolbar options
- Create or Edit a connector
- Resources - Displays all the resources available in the remote system.
Select one or multiple resources and click Create package to create new packages within your Application Workspace System.
NOTE: When creating a package, the Package type default is what you've set for the connector in Overview > Default package type.
This option is available for the On-demand synchronization method.
- Updates - Displays a list with all the updates available for the packages created through the connector. This option is available for the On-demand synchronization method.
-
Synchronize - You can choose only to check the newly available updates or download and apply them.
- For On-demand connectors, Download and apply updates updates only the packages created from the connector resources.
- For Synchronize connectors, Download and apply updates updates all existing packages and imports new ones.
- Remove - Remove the connector from Application Workspace.
- Views - Choose how the table displays. The default view contains all your connectors in alphabetic ascending order, and only a few columns: Name, Type, Direction, Method, Enabled and Server.
NOTE: You can create your own personalized view of the table by filtering the connectors or adding/deleting columns and clicking Save as in the Views drop-down.
To create a new connector:
1. On the Connectors page, click the Create button.
NOTE: To edit a connector, double-click its entry or select the connector and click the 
Edit button.
2. Select a Connector Type.
3. Accept the Terms and conditions.
4. Configure settings on the Overview, On-demand, Settings, Releases tabs (settings described below).
Global Settings on the Overview tab
On the Overview tab, give the new connector a name, choose whether it is Enabled, and configure its global settings:
- Direction - Determines in which direction the connector sends information:
- Push - The connector will create packages in the remote system.
- Pull - Packages can be created from resources or imported from the remote system
- Synchronization Method - Determines how the connector should be synchronized.
- On-demand - Synchronizes only the packages you created based on the connector resources.
- Synchronize - This option will automatically synchronize all packages with new available information.
- Stage
- Development
- Test
- Acceptance
- Production
- Package name prefix - The default prefix used for the names of the new packages from the connector, which will help you to easily identify all packages originating from a certain connector.
On-demand settings
On the On-demand tab, set the package type.
- Default package type - This option determines the way a package will be handled after creation:
- Managed - the package is eligible for automatic updates and it has an action set that is locked for editing. You are still able to add new action sets to this package.
- Unmanaged - the package is not eligible for automatic updates and no locked action sets are added.
Connector-specific settings
For options you'll need to configure on the Settings tab, see the articles for each connector type.
- Citrix StoreFront
- Application Workspace Setup Store
- Application Workspace
- Microsoft Azure Virtual Desktop
- Microsoft Print Server
- Microsoft RDS
- Microsoft Store
- Microsoft System Center Configuration Manager
- Nutanix Frame
- Okta
- Omnissa Horizon
Entitlement settings
On the Entitlements tab, manage entitlements on packages created via the connector. This allows you to assign a default set of entitlements for all connectors. Some connectors support importing entitlements from the remote system.
NOTE: This tab is available only when the connector is set to use the synchronized method.
Import entitlements
With the import entitlements functionality enabled, you can add policies to match an identity (user, group, device or device collection) configured in the remote system with an identity known within Liquit.
Overview tab
- Identity Source - The Application Workspace identity source to match users and groups from the remote system.
- Applies To - Which Application Workspace identity types (user, group, context, device, device collection) inside the selected identity source should be matched.
- Property - The property of the Application Workspace identity to use when matching with the remote system.
Value transformation tab
- Compare - What operator needs to be used on the property selected in the Overview tab.
- Match - The regex used to match part or all of the properties from the remote system; use
.\*to match all of the properties. - Result - The value to compare against the regular expression's result. To match against the exact same property, use
${0}. To match against a different property from a Liquit Identity, use one of the predefined identity variables that appear in the drop-down list of the field when you try to edit it. See Variables for a complete list of all predefined variables within Application Workspace.
Settings tab
Keep the default settings for publishing packages on the user's devices or override them. See Packages for more information.
Manual entitlements
With the manual entitlements functionality enabled, you can add entitlements manually by selecting the Add static button in the table toolbar.
In the Overview tab select the Application Workspace identity (user, group, context, device or device collection) you want to entitle.
In the Settings tab keep the default settings for publishing packages on the user's devices or override them. See Packages for more information.
8. On the Synchronization profiles tab, specify whether the Application Workspace System or the remote system is controlling some of the packages' information.
Available Options:
- Synchronize from connector - If the entity exists in Application Workspace, it is updated with the value provided by the remote system. Application Workspace will not attempt to create entities if they don't exist.
- Synchronize from connector, create entity if not exist - Updates the existing entities and creates new entities if they don't exist in Application Workspace yet.
- Set from connector during creation - Updates the existing entities and creates new entities if they don't exist in Application Workspace yet. Uses the value provided by the remote system only initially and it can be modified without it getting changed by the connector afterwards.
- Create entity from connector during creation - Associates entities and creates new ones if they don't exist in Application Workspace yet. The entities can be modified after creation without them getting changed by the connector afterwards.
- Static - If you select this option, an adjacent empty field or check box appears, that lets you configure a permanent value for this package option.
- Ignore - Never retrieve the value/entity from a remote system.
Release settings
This page allows you to define the way releases should be created on packages. For more information about each type of publishing stage see Packages.
NOTE: The Test and Acceptance stages are available only when you have a Release and Patch Management license.
Available Options:
- Publish - Choose the stage to which the packages are published by default.
- Enable release retention - Enables the Remove releases older than and Keep number of releases sections on this screen.
- Remove releases older than section - Set the number of days after which the releases are automatically removed.
- Keep number of releases section- Set the number of releases that should be preserved.
Packages managed by the connector
On the Managed Packages tab, you can view the list of packages that are managed by this connector.
Audit of changes to the connector
On the Auditing tab, you can view a log of changes to this connector, displaying the identity behind each modification.
NOTE: This tab is available only if the auditing is enabled in the Database Event Collector.
For more information, see Auditing.
This example shows how to configure an Application Workspace connector using the LOCAL identity source.
- In the source Application Workspace zone, create a new user in the LOCAL identity source called Test.
- Assign a Connector type access policy to the newly created Test user.
- Entitle the Test user to all the packages that you want to export later. You can do that in Manage > Users > Test user > Packages screen or in Manage > Workspace > Packages > desired package > Entitlements screen.
- In the destination Application Workspace zone, create an Application Workspace type connector with the following parameters:
- In the Overview tab:
Direction Pull
Synchronization method Synchronize
Stage Development
Package name prefix RecastSoftware - In the Settings tab:
URL the URL of the source Application Workspace zone,
Username insert "LOCAL\Test" (the username of the user configured at steps 1-2)
Password insert the password of the Test user (the user configured at steps 1-2) - In the Summary tab, leave the Modify connector after creation selected
- In the Overview tab:
- In the connector detailed view that opens, in the Overview screen, click
Synchronize. - In the Synchronize dialog box that opens, select Check for updates. A log will appear, containing all the packages that will be created in the target Application Workspace zone
Synchronize.
- Close the log, click Synchronize again and this time select Download and apply updates. After it finishes a log will appear listing all the newly created packages.
- Close the log and go to the Managed packages screen to access all the packages you imported.
In this example using MongoDB Community Edition 6.0, we'll create a managed package in Application Workspace via the Application Workspace Setup Store.
To create a managed package:
1. In your Application Workspace Setup Store connector, navigate to Overview > Resources.
2. Search for and select MongoDB Community Edition 6.0.
3. Click Create package.
4. In the Create package window that opens:
On the Overview tab
- Enter a name for your new package or keep the default name.
- As the Package type, select 'Managed'. Managed means that every time MongoDB releases a new version for this product, the Application Workspace Setup Store connector updates the package with the latest version. For more details about package types, see Connectors.
- In Publish, select the stage to which you want to publish the new package. For more details, see Package
- Leave the Update existing packages unchecked. If this option is selected, it will overwrite an existing package.
On the Setup details tab, you can access links to the release notes and product description on the developer's official website, links to Recast knowledge base articles, virus scan scores and CVE reports in case any vulnerabilities and exposures exist for this resource. Also, in the Superseded by products table, you can view all the product versions within Application Workspace Setup Store that supersede the currently selected version.
If you decide that you want to install one of the versions marked as superseded in this table, just double-click on it, and then click Confirm. It will open a new Create package dialog box for this version.
On the Dependencies tab, Application Workspace lists all prerequisite software components and automatically detects if they are installed or not on your local system. You can easily create a package for each uninstalled component right from the dialog box by double-clicking it or by selecting it and pressing 
Create package in the table toolbar. It opens a new Create package dialog box where you configure the new package.
- Select Ignore missing dependencies if you do not want to create managed packages for connected dependencies.
On the Customize tab, you can access the customization wizard that helps you browse through additional settings offered by the developer to choose the ones that suit your needs.
On the Entitlements tab, add the identity (like contexts, device collections, devices, groups, users and user collections) to which you wish to publish the newly created package.
On the Summary tab, leave the Modify package after creation selected if you want to open the newly created package and further configure it.
If you configure the managed package to be published in the user's catalog, the following sections come prefilled: excerpt, description, media, details and website. For more information see Packages.
Further reading
CVE, Then and Now: Overview and Practical Integration with Application Workspace
