FAQs and additional information

 Users of BMC Server Automation can continue to organize content in the same way they do currently.

Access to content is based on roles in BMC Server Automation.  Each security group in the portal maps to a role in BMC Server Automation and grants the permissions assigned to that role. Thus, security groups in the portal should be set up to reflect role assignments in BMC Server Automation rather than the other way around. 

Yes, you can create operations in the portal that use those existing jobs.

Users in the portal are organized into security groups. Each portal security group maps to a role in BMC Server Automation. If you set up a security group, all users assigned to its corresponding role in BMC Server Automation are members of the same security group. Those users can share operations. Users in different security groups can also share operations if the underlying RBAC roles in BMC Server Automation have permissions to access the same types of objects. 

Operations that have been created by an operator can also be edited by that operator. From the operations home page, select an operation and then click the Edit icon. Then you can edit the list of targets and rerun the operation.

When creating objects in BMC Server Automation, you have access to all of the underlying data, but in the portal, all you have is a name. For example, you can see component template rules only when viewing results, not when you create them. A best practice is to use a thoughtful approach to naming underlying content so the name conveys some idea of the content.

If the other user belongs to the same portal security group as you, that user can see the output of your work. In addition, if the other user belongs to a role in BMC Server Automation and that role has the same permissions as your role, the other user can see the output of your work.

Customers should map out their use cases for BMC Server Automation (for example, patch, compliance, and so forth) along with the types of users that are involved in each use case. This list of users and roles should then be mapped to the functionality enabled through BladeLogic Portal. Using this list, a subset of users can be identified who might want to adopt the BladeLogic Portal to perform their day-to-day tasks. Broadly speaking, BMC Server Automation administrators will continue to use the BMC Server Automation Console to set up and configure the product. Another set of users will then also use the BMC Server Automation Console to create or manage the underlying content required to enable core use cases. Once that content is created, consumers of that content can use the BladeLogic Portal to execute use cases and review results.