Work with Connectors

This example shows how to configure an Application Workspace connector using the LOCAL identity source.

1. In the source Application Workspace zone, create a new user in the LOCAL identity source called Test.
2. Assign a Connector type access policy to the newly created Test user.
3. 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.
4. 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
5. In the connector detailed view that opens, in the Overview screen, click Synchronize.
6. 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

7. 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.

8. 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.

Further reading

CVE, Then and Now: Overview and Practical Integration with Application Workspace