This is the next blog post in the App Orchestration series. In previous blogs, all the key concepts have been already explained. In this post I will focus on the details on subscriptions.
In the Manage Ads post, he described how advertisements can be created from the available applications that are discovered that the workload of machines are imported from a workload catalog.
as the management of tenants following describes how tenants can be imported using Citrix App Studio.
Once the ads and tenants are in place, the next step is to create subscriptions. This triggers the release of applications in the XenApp farm. For more information please refer to workflows entries in this series. A subscription is really an association between an advertisement and a tenant. As part of this association, users are specified. Note that it is recommended that the group accounts are used instead of adding individual user accounts. The accounts specified for the subscription must be contained in the root organizational unit that was specified when the tenant was imported.
In App Studio, the subscriptions creation task can be launched from the view of the subscription or sight tenants. In the first case, the wizard will prompt you to select the tenant, and in the second case, the first assistant prompts you to select the announcement. multiple advertisements can be selected at once, but only one tenant can be selected when creating subscriptions. In the event that more ads are selected, a batch operation creates several subscriptions at once. So a subscription is still associated with a single ad and a single tenant.
The next step of the wizard will ask you a list of accounts to add to the subscription. The accounts must be validated before moving on to the last page of the wizard. On the same page, the accounts can also be removed if they were incorrectly added. The last page of the wizard is just a confirmation of this action. After clicking on the Finish button, App Studio will create the workflows that create applications published in the farm.
Note that during this process, the selection of the farm or the work load is maintained internally. This is intentional since the Orchestration engine takes care of allocating a farm when needed. For example, if advertising was created to be shared among multiple tenants, shared farm will be selected. Otherwise, a farm available will be allocated to the tenant.
Another detail that the engine maintains internal Orchestration is the controller in the farm to the target for the execution of the workflow. When farms have multiple controllers, each machine will have a Orchestration agent, but only one is elected primary. This will be the target of all configurations of the battery, including the creation of published applications.
Note that the application parameters are obtained from advertising. If any parameter is changed, then the corresponding workflow to update all applications associated with advertising will be created.
After the subscription is created, multiple accounts can be added or existing accounts may be removed. To do this, first find the subscription is the view of the tenant or Advertisements view. When you are in the details view, you should see the tabs for subscriptions. Select the subscription and details see the subscription will be charged. Here you will see the actions to add and remove users. In this view you can also delete the subscription, which will effectively remove also the corresponding farm.
It is important to understand that there can be a subscription by combining ad / tenant. So if you try to create a new subscription and select advertising and tenant for which there is already an established subscription, this operation will simply add new users specified and ignore duplicate users. It will never create a new subscription.
The current version of App Studio, deleting an announcement will also delete all subscriptions that are associated with advertising. Similarly, removing a tenant will all subscriptions to the tenants to remove. The list of subscriptions that will be deleted by either the action is displayed in a dialog so that the operation can be confirmed.
One last topic related to subscriptions has to do with integration with ClooudPortal Services Manager, which provides a self-service interface to create tenants and subscriptions. More details will be available soon. Stay tuned!
- · Concepts
- · architecture
- · Machine Provisioning Part 1 & Part 2
- · Management of tenants
- · Classified Management
- · Management of subscriptions (this blog)
- · Patching workload machines
- · Understanding Workflows Part 1, Part 2, Part 3
- · Troubleshooting (forthcoming)
- · integration with CloudPortal services Manager (forthcoming)
0 Komentar