eBooks

6 ABX ac ons and ac on flows (a way of chaining ac ons together like a workflow) are certainly learnable; however, compared to vRO, there are not yet as many samples to help ease the learning curve. The implica ons that this change could have on your migra ons as a customer could be quite staggering. If you have wri en a ton of complex extensibility code that centered upon using the vRA plug-in for vRO, you're going to significant rework. vRealize Orchestrator 8 has removed the Java client en rely and has migrated en rely to a web interface like what was available in vRA7.6. You can now view and organize workflows and other content based on folder structure (as in vRA7) or by tags. En tlements and Policy Defini ons The en tlement constructs of past versions of vRA7 are now gone, and they have been replaced by policies in Service Broker in vRA8. These policies are in many ways more flexible, but also remove some of the granular permissioning that was present in vRA7 en tlements. Organiza on-Level Policies: In vRA 6.x/7.x, some customers have spent a considerable amount of me wri ng custom workflows to copy en tlements from a "template" business group out to all the other (numerous) business groups. We'll cover one of these implementa ons now to illustrate the differences in the en tlement/permissions. This par cular customer used template business groups, which have separate en tlements, each one pertaining to a different func on (administra ve, service account oriented, or end-user). These en tlements can easily number in the hundreds given there were also over a hundred business groups, and would need to match the corresponding en tlement ed to the template business group. In this case, if you wanted to add a single ac on that is en tled to all business groups, you would have to first en tle that ac on in the template business group, and then run a workflow that copied the en tlements out to the other business groups. In vRA8, it appears that this process has been addressed with the ability to add a policy at the organiza on (rather than project) level. With the policy in the following screenshot you can specify that all project administrators have access to all 2nd-day ac ons in the system within their respec ve projects. You probably wouldn't want to do this in a produc on environment, but it showcases some of the added flexibility inherent in vRA8 policies. M I G R AT I O N G U I D E

• Cover