A while back we published documentation Orchestration Self-Service App SDK. This SDK allows third parties to integrate panels and gates self-service control with the App Orchestration engine.
The self-service SDK was designed for REST-like, so it can be used from any computer, any programming language, any operating system, and can easily firewalls -Fire crosses. However, if you write code on Windows using a .NET language, we can offer a better developer experience raw HTTP messages.
To this end, I am pleased to present the customer Self-Service Orchestration App SDK for .NET.
I would also like to explain a little about how a third party can integrate App Orchestration using this SDK.
If you have a control panel, gate, onboarding page, or even a simple script that helps the task of bringing users tenants in your organization and the establishment XenApp to deliver applications and workstations to these users, you can use this SDK with App Orchestration to simplify the process.
General workflows
Bringing a new tenant on board
When a new tenant wishes to use applications and positions hosted work supported by App Orchestration and XenApp, they must be imported into App Orchestration. See API: Tenants.Import ()
offer applications and desktops to a tenant they can subscribe to using a self-service portal
You can query all the ads available in the App Orchestration and offer them through your own user interface. See API: Advertisements.Get ()
Naturally, users love the images as well, and most people associate more with icons of their favorite applications with the names of these applications. You can query the icon in PNG format for display in your user interface using Icons.Get ()
user subscriptions management in an application or office offering
once your tenant or end user decides on the applications they want, they can choose to join. This is as easy as calling: Subscriptions.Create ()
If the tenant already has a subscription to this application for some users, you can add more users by calling: Subscriptions.AddUser ()
Sometimes the user needs change, or they move on to other organizations. You can remove the access of users to applications and desktops using: Subscriptions.RemoveUser ()
Put together: value in automation
Imagine you want to remove a user from each application, it may have subscribed. While this can be a tedious task to look through all subscriptions by hand and remove it from everyone, it becomes 7 lines of code using the SDK:
context var = new RESTContext ( "https: //server.fqdn/cam/v1", null);
var = context.Tenants.GetByName tenant ( "Joe tenant");
var = subscriptions context.Subscriptions.GetByTenantId (tenant id.);
subscriptions
.SelectMany (sub => sub.Users)
.When (user => user.Name == @ "DOMAIN user")
.ToList ()
.foreach (user => context.Subscriptions.RemoveUser (user.Id));
I have only touched on a small subset of APIs available through the SDK Self-service. See the documentation provided for the full set of APIs. Have fun!
0 Komentar