Perform preliminary tasks
You must perform the following preliminary configuration tasks in both BMC AR System Server and BMC Remedy ITSM for a fully operational BMC Cloud Lifecycle Management environment:
To configure CMDB inline normalization for the Enterprise AR System server
By default, CIs are normalized any time that they are created or modified in BMC Atrium CMDB. Typically you would use inline normalization for datasets where the number of changes is relatively small over time. In this case, when you finish upgrading, you must disable this functionality. Perform these steps on the primary and secondary Enterprise-AR servers.
- From the <AR System server installation directory>/Conf folder, open the ar.conf configuration file.
- Set the
CMDB-Inline-Normalizationparameter to F (instead of
- Save the ar.conf configuration file and restart the BMC Remedy Action Request System Server service.
To create a provider company and a new cloud administrator user account
After installing BMC Cloud Lifecycle Management, you must create the provider company and the cloud administrator account (in that order) in the Application Administration Console. The provider company is the company that manages the cloud and uses the BMC Cloud Lifecycle Management Console. You can create any number of cloud administrator accounts, but you should create only one provider company.
To grant cloud administrator permissions to an existing user, see Updating an existing user account with cloud administrator permissions.
To create a new cloud administrator user account and a provider company, complete the following steps:
- Log on to the Application Administration Console as appadmin (no password) or as a user in the AR administrator group.
You can access the Application Administration Console from the BMC Remedy Mid Tier:
- Log on to the BMC Remedy Mid Tier: midTierHost:midTierPort/arsys
- Select Administrator Console > Application Administration Console from the vertical menu on the left side.
The Application Administration Console is displayed.
- Create the provider company for the cloud administrator, as described in Configuring companies.
Select Operating Company as the company type to indicate that it is the provider company.
- Create the organization, as described in Creating organizations.
- Create the location, as described in Creating locations.
- Create the cloud administrator user, as described in Adding people records from a template, and select the Cloud Admin template.
- When creating the cloud administrator user, ensure that the Unrestricted Access box is checked on the People form.
- Cloud users of all types require a fixed license. Select Fixed License as the License Type on the People form.
- (Optional) On the People form, consider adding permission groups to the cloud administrator user, if needed, by clicking Update Permission Groups.
- Define at least one cloud administrator account with the following additional permission groups to manage companies, organizations, and people who need to access cloud services:
Foundations > Contact Organization Admin
Required if this cloud administrator user needs to create companies or organizations.
Foundations > Contact Location Admin
Required if this cloud administrator user needs to create locations.
Foundations > Licensing
Required if this cloud administrator needs to create People records with a Fixed license type or the Cloud Admin template. This permission group is unnecessary if you have already have BMC Remedy AR Administrator permission.
- Using the new cloud administrator account, log onto the BMC Cloud Lifecycle Management Administration Console.
If you have not yet configured the BMC Cloud Lifecycle Management Administration Console, continue with Setting Configuration workspace options.
To apply AR User Fixed licenses
When the BMC AR System Server & IT Service Mgt. Suite - primary and the BMC AR System Server - Cloud Database primary Control Tier products have finished their installation, manually apply at least fifteen AR User Fixed licenses to the Cloud Database primary host (so that it matches the number of licenses on the BMC AR System Server & IT Service Mgt. Suite - primary host).
You must apply these licenses to correctly configure the Distributed Server Option (DSO) Mappings. You can use either of the methods described in the following sections.
To apply the licenses using the BMC Remedy Mid Tier client
- Log on to the Cloud Portal by using Cloud Admin Credentials.
- Go to Applications > AR System Administration > Enterpriser Host >AR system Administration Console > System >General > Add or Remove license.
- From AR Licensing Server, generate an AR license and update key for the license type AR Server.
- Go to Applications > AR System Administration > Cloud AR Host >AR System Administration Console > System > General > Add or Remove license.
- From AR Licensing Server, generate the AR license and update key for the license type AR Server.
To apply the licenses using a web browser
Use the following procedure to add the Cloud AR server to the existing mid-tier and access the Add or Remove license page through a web browser:
- Using a browser, connect to the BMC Remedy Mid Tier Configuration Tool for the mid-tier where you want to add the Cloud Database primary host.
- In the navigation pane, select AR Server Settings.
- On the AR Server Settings page, select Add Server.
- On the AR Server Settings > Add New Server page, select Add Server.
- On the General Settings page, change the authentication server for the mid-tier (this is a temporary change).
- Connect to the BMC Remedy AR System Administation Console, and use the newly added server name in the previous step to connect to another server.
- In the navigation pane, select Add or Remove license.
- Set the licensing information.
- Once the licenses are set correctly, connect to the BMC Remedy Mid Tier Configuration Tool and revert the authentication of the mid-tier to its original value.
For additional information, see the following topics in the BMC Remedy Action Request System online technical documentation: