If you have 3.0 following along with Richard Hayton recent posts on the publication of storefront, you have probably noticed that we allow storefront with a set of APIs to configure and use it in the way that best match your environment.
, the blog post series is great, and I recommend to check out, as this article is based on them. You can Richards posts here, but be sure to read X1 DIY approvals and Citrix Recipe Box. Storefront approvals, as they are based on what we are talking about today
Because this article contains several sub-parts, we will make this a series of articles, we can down detail in so break each of the steps. With that said, let on Octoblu receive so that your users to access applications to process request, via the storefront API
Overview and Setup .:
This is be more of a general overview of the process and a high level how-to technical articles, and we show you how the storefront / Octoblu up and running integration.
The scenario is that we. A number of applications that we want to display to all users, but only to provide access when the user requests the application A typical approval workflow, handle the workflow engines.
There are a few steps that we need to perform to enable storefront to understand that an application needs to ask for permission. I have the below. Enable to set
- applications showcase sketched state in a holding pattern.
- Set to enable the approval process
- Build a monitoring application subscription database for "pending" application to search the published application.
- Build a Octoblu workflow that handles the process flow for the request, approval. or an application under Deny
- Build / Deploy intermediate page that allows a manager to approve the request
First step :. Activate showcase for workflow
There is an adjustment DLL that we make available that you must fall 3.0 directory in your storefront. Richards Blog (X1 DIY approvals) are the instructions, but I have copied here, as well.
- Visit to allow the directory to the store for the workflow. For example, C: inetpub wwwroot Purple
- Edit web.config in this directory and add the following to the end of
section
- Download the DLL from here and there into the bin directory store (for example, C: inetpub wwroot purple bin)
step Two: Setup to enable a published application (s) workflows
Now that we have configured storefront, we need to modify the published application (s) so that storefront, knows that it is a workflow-enabled application. have to ask in the description of each requested published application that you want the user to access: This is achieved by adding "WFS keywords". Below is an example of the Properties screen of a published application that did the Description field with the appropriate keywords
Step Three :. Setup application storefront monitoring for the application to see requests.
Now that we our storefront and XenApp / XenDesktop configured application, the next step is to create an application that monitor the facade database and searching for applications that are in a "PENDING" and then trigger the Octoblu workflow and wait for a response. The basic sequence is below.
- Monitor storefront subscription database for all subscriptions to the "Pending" state.
- register with the Octoblu service to receive messages.
- For each "Pending" application, call the Octoblu workflow defined.
- process received messages from Octoblu and based on the response, either change to subscribe to the pending status of the application or remove the subscription.
Because this application is the reduction on its own an entire blog, we will build a follow-up blog on the drill-down to such use. Meanwhile, we have the application open source and our GitHub account. You can download it here https://github.com/citrix/Citrix-Storefront-ApprovalMonitoring
* If you can download it, it will run on your storefront server to start pending monitoring applications.
, it is a brief screenshot of the monitoring application and download after you find need to change a few pieces. The code for the specific check-out where to add the following items.
- Add the workflow endpoint in the code.
- Add your device UUID / token into the code. (Check out our Visual Studio from extension to enable you to use as a device in Octoblu)
- Add the e-mail you want to obtain the consent of emails. We built it in this way for you to check the operation quickly
Fourth step: .. Build / provision of intermediate side to process the workflow needs
to enable fast managers to approve or deny requests on we should ask a simple web interface available that you can deploy on a web server to allow managers to approve or deny the user request. We have a skeleton page provided to the GitHub you download from this website you will https://github.com/citrix/Citrix-Storefront-ManagerApprovalSite
* If you need this software to update the code , Add your workflow endpoint. Look at the html for further instructions.
under the screenshot of the interim approval site. As you can see, there are buttons for approving or denying the application
Fifth Step: .. Align the Octoblu workflow for requesting application access
the final step in this post when the create the Octoblu workflow that the request and approval / denial process will handle. We have a plan made available to start download. You can access
https://app.octoblu.com/bluprints/942daf81-6d50-4fc3-ab66-e7ab415fee69
The workflow design here as a general overview - the workflow for some looks data that has been posted to the workflow. It will then determine whether the request is a "use requirement" is or if it is an approval / denial of request. Based on the type of request, the workflow route at different paths. One interested note is that this workflow communicates back to the monitoring application (step 2) to inform them of what it needs to do.
to this workflow to import into your instance of Octoblu own and start your node work through and see how we built the request process
Following is a brief screenshot of the existing workflow .:
as a final note, this article is meant to provide a better overview of the process and some technical information on how it was implemented. We work additional sites on delivering on each of the steps to drill down to have a better understanding of the whole process, but in the meantime, download the code and workflow and let us know what you think.
As always, feel free to reach me on twitter (@johnmcbride) or leave a comment on the post with questions or comments.
John McBride / Developer Advocate
0 Komentar