Creating user accounts for BMC BladeLogic Client Automation

For the purpose of integration, you must create two types of users in the People form to use the BMC Helix ITSM: Change Management application. The first user is a CMS AR System user. This single, special user is created for the integration. The other type of users are BMC Helix ITSM: Change Management users. In both cases, there must be the same login and password combination in both the BMC BladeLogic Client Automation and BMC Helix ITSM: Change Management systems.

To create the BMC BladeLogic Client Automation AR System User

Although these steps cover creating the BMC BladeLogic Client Automation AR System User, you follow the same basic steps to create Change Management Users. You must make sure the user has the proper permissions to access both the Change Management and BMC BladeLogic Client Automation applications.

1. On the IT Home page, click the Application Administration Console link.
2. Click the Custom Configuration tab.
3. From the Application Settings list, select Foundation > People > People, and then click Open.
4. On the People form, enter the People Information that is useful to you in finding and editing this information in the future.
   This information might include name, client type, profile status, location information, and optionally, an email address.
5. On the Login/Access Details tab, enter the login ID CMSUSER.
6. Create a password.
7. Click Update Permission Groups.

8. In the Permission Group list on the Permission Group dialog box, select each appropriate permission group to add and then click Add/Modify for each one.
   The following table lists all the permissions necessary to configure the users properly, including the BMC BladeLogic Client Automation permissions that you use later.

   User type	Change Management permissions	BMC BladeLogic Client Automation permissions
   Change Management Users	Change > Infrastructure Change User Asset > Asset User Important: When you select the Infrastructure Change User permission, you automatically inherit the Asset Viewer permission as well.	Admin
   CMS AR System User	Change > Infrastructure Change User AR System > Administrator Important: When you select the Infrastructure Change User permission, you automatically inherit the Asset Viewer permission as well.	Primary Admin

9. After you have given the user the necessary permissions, close the Permission Groups Update dialog box.
10. In the Access Restrictions area of the People form, select Unrestricted Access.
11. Click Save.

To edit the Application Registry for the BMC BladeLogic Client Automation AR System User

This registry is provided for the Command Automation Interface (CAI) integration.

1. On the IT Home page, click the Application Administration Console link.
2. Click the Custom Configuration tab.
3. From the Application Settings list, select Foundation > Advanced Options > Command Automation Interface - Application Registry, and then click Open.
4. On the Application Registry form, click the New Search toolbar icon, and then click Search.
5. In the list of application registry records, select the BMC Configuration Management registry.
6. On the Connection tab, edit the Password to be exactly the same as the CMS AR System User created previously, and then click Save. 
   Use the default user name CMSUSER, but change the password for this user. The CMS AR System User name can be changed, but must be changed in the People form, in this registry, and in the CM system.
7. Click Save. 
   A completed Application Registry form is displayed.

CMS integration tasks

The following tasks must be completed on the CMS application for the integration to be complete.

To edit the directory service for correct user credentials

You must edit the Directory Service AR System Integration to include the CMS AR System User with exactly the same login and password that you created when you created the CMS AR System User.

See the BMC Configuration Automation for Clients CMS and Tuner Guide for complete instructions about editing directory services.

To set up user roles for authentication

Ensure that the user has the correct roles to perform configuration management tasks. Verify that the correct roles are available in BMC Configuration Management. For detailed information about user roles, see the BMC BladeLogic Automation for Clients CMS and Tuner Guide.

1. Log on to the BMC Configuration Management console.
2. Select Applications > Console > System Settings.
3. Click the User Authentication tab.
4. On the User Authentication Settings page, click the User Roles link.
5. On the User Roles page, make sure that you have properly set up the group capabilities of users when they log in to use the BMC Configuration Management browser-based applications.
   When users log in to the system, their roles are assigned based on the user name and password they provide.
   • The CMS AR System User must be assigned the Primary Administrator role.
     Primary administrators have access to all product features available in the applications, including the system settings and configuration pages for applications. Among the system settings that primary administrators have access to is managing user access to applications.
   • The Change Management Users must be assigned at least the Administrator role. Administrators can log in to the applications and have access to most product features available, except those reserved for primary administrators.
6. Define any missing groups.
7. Click OK to save your changes.

To communicate with the Action Request System by using the BMC Configuration Management console

The Mid Tier facilitates communication between a browser (in this case, BMC Configuration Management) and the AR System. The Mid Tier lets a browser become a fully functional AR System client.

1. In the BMC Configuration Management console, select Applications > Console > System Settings.
2. Click the AR Settings tab and then click the AR Settings link.
3. In the Mid tier host field, enter the host name of the machine on which the mid tier web server is running. 
   Make sure the mid tier is reachable.
4. In the Mid tier port field, enter the port number of the machine on which the mid tier web server is running. 
   The default is 80.
5. In the AR Server field, enter the name of the AR System being used by the Mid Tier.

6. In the User name field, enter the user name for accessing AR System. 
   The user account must have the correct permissions to access the AR System, Change Management, and the Product Catalog.

   Important

   This should be the user CMSUSER and password.

7. In the Password field, enter the password for accessing AR System.
8. In the HTTP timeout field, enter the timeout for the web services HTTP messages. 
   The default is 50 seconds.
9. In the Company field, enter Global if it is not entered already.
10. To use SSL on the server for communication with AR System, select the Use SSL check box.
11. Click OK.

To communicate with the AR System database and BMC Configuration Management

Every AR System is configured to a database, which stores the definitions and data. This procedure lets you specify a database location and name so that the BMC Configuration Management Report Center can leverage the AR System Product Catalog to generate inventory reports with normalized names and reports based on BMC Helix CMDB queries.

1. Select Applications > Console > System Settings.
2. Click the AR Settings tab, and then click the AR Database link.
3. In the AR database type field, select a database type from the list.
4. In the AR database host name field, enter the name of the machine on which the AR System database is running.
5. In the AR database port field, enter the port number used to remotely connect to the database.
   Port numbers are usually 1521 for Oracle, and 1433 for Microsoft SQL Server.
6. In the AR database service name field, enter the AR System database name.
   The default is ARSystem.
7. In the AR database user name field, enter the user name created by the Action Request System database security script.
8. In the AR database user password field, enter the password created by the Action Request System database security script.
9. Click OK.