When deploying in a multiple server setup


A deployment scenario in which multiple BMC ProactiveNet Child Servers communicate with a BMC ProactiveNet Central Server, BMC recommends that all the roles and role user groups be replicated across all the BMC ProactiveNet Servers participating in the deployment. This facilitates clear permission management.

In a brand new deployment, you can create users, user groups and roles, and export or import these to the other servers using the BMC ProactiveNet Command Line Interface (CLI) or the BMC ProactiveNet Operations Console. However, these interfaces replicate all the entities that you export or import and you need to manually remove the entities that are not required, from the other servers. This might lead to ramifications in an existing deployment, in which some of the user management entities with identical names already exist in the system. In such cases, BMC recommends that you closely scrutinize the configuration of these entities and manually adjust them to suit your requirements. For more information, see Importing-and-exporting-users.

In a multiple server deployment, some users may have access rights across multiple servers. In such a scenario, BMC recommends that you integrate with BMC Atrium Single Sign-On, thus allowing for seamless access experience across the deployment.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC ProactiveNet 9.6