Manually installing or upgrading the Azure Provider

The following topics describes the steps to be followed for installing or upgrading the Azure Provider manually:

• • Before you begin
  • Deploying OSGi files on the Cloud Platform Manager
  • Deploying .def and .arx files on the BMC AR System Server
  • Clearing the Mid Tier and browser caches
  • Verifying the Azure installation

Before you begin

Ensure that you have completed the following tasks prior to installing or upgrading the Azure Provider manually:

• Prerequisites-for-installing-the-Azure-Provider.
• If you have failed to install the Azure Provider correctly using the installer, BMC recommends you to cleanup your incomplete Azure Provider installation prior to installing it manually.

• Downloaded and extracted the following Azure Provider installer files and stored it in your local computer:

Deploying OSGi files on the Cloud Platform Manager

1. On the Platform Manager host, navigate to the <Platform_Manager_installation_directory> folder:
   
   • (Windows) C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Platform_Manager
   • (Linux) /gfs/bmc/BMCCloudLifeCycleManagement/Platform_Manager
2. (Applicable only when replacing the existing jars) Make a backup copy of the following files in the <Platform_Manager_installation_directory> folder:
   • <Platform_Manager_installation_directory>/configuration/config.ini
   • <Platform_Manager_installation_directory>/configuration/providers.json
   • <Platform_Manager_installation_directory>/configuration/cloudservices.json
   • <Platform_Manager_installation_directory>/configuration/lib/azure-1.0.0.jar
   • <Platform_Manager_installation_directory>/configuration/lib/azureconnect-1.0.0.jar
     
     
3. Stop the Platform Manager service.
4. Copy the following .jar files to the <Platform_Manager_installation_directory>/configuration/lib folder:
   • azure-1.0.0.jar 
   • azureconnect-1.0.0.jar
5. Edit the media.properties file as per your BMC Cloud Lifecycle Management environment.
6. Copy the media.properties file to the <Platform_Manager_installation_directory>/configuration folder:
7. Open the config.ini file and set the osgi.bundles parameter value as follows:
   osgi.bundles=lib/azure-1.0.0.jar@start
   osgi.bundles=lib/azureconnect-1.0.0.jar@start
8. (Applicable only when replacing the existing jars) Delete the following folder contents and folder:
   • <Platform_Manager_installation_directory>/cache folder contents
   • <Platform_Manager_installation_directory>/configuration/org.eclipse.osgi folder
9. Start the Platform Manager service and monitor the csm log files at the following location:
   <Platform_Manager_installation_directory>\Logs

Deploying .def and .arx files on the BMC AR System Server

You must import the .def and .arx files and configure the forms on the BMC AR System Server computer by using the procedures in the following sections.

Before you begin

Ensure that you have completed the following tasks before you deploy the files:

• Log on to the BMC Remedy Developer Studio as Administrator.
• Switch the mode to Base Development, as shown in the following figure:
  
  

To import the AzureNew_Forms.def file

1. Click File > Import.
2. Select ObjectDefinitions and click Next.
   The Import Objects window is displayed.
3. In the Import File field, browse to the .def file and select it.
4. Click Next.
   The selected object details are displayed in the Object Selection.
5. Select the Replace Objects on the Destination Server checkbox.
6. Click Finish.
   The .def file is imported.
7. Click Save.

To import AzureProvider_Workflows.def file

1. Click File > Import.
2. Select ObjectDefinitions and click Next.
   The Import Objects window is displayed.
3. In the Import File field, browse to the .def file and select it.
4. Click Open.
5. Select the Replace Objects on the Destination Server checkbox.
6. Select the Delete Excess fields checkbox.
7. In Handle Conflicting Types, select Display Conflict Error.
8. Click Finish to import the .def file.

To configure BMC Remedy AR forms

1. Click All Objects > Applications.

2. Navigate to the Application's List and double click to open the BMC Cloud Management Administrator and BMC Cloud Management Foundation applications, as shown in the figure below:

   

   Note

    You must configure the following forms as Primary Form in the respective applications by performing steps 3-5 listed below:

   Application name	Form name
   BMC Cloud Management Foundation	CMF:ProviderAzure_v
   BMC Cloud Management Administrator	CMA:ManageAzureUserAccounts

3. In the Form Selector window, as shown below in the figure below, enter the form name in the Filtering options (CMF:ProviderAzure_v  or CMA:ManageAzureUserAccounts)

   

4. Click OK.
   This adds the selected form in the application.
5. Click Save.

To re-import the .def files

1. To re-import the AzureNew_Forms.def, perform steps 1-7 of section To import AzureNew_Forms.def file.
2. To re-import the AzureProvider_Workflows.def, perform steps 1-8 of section To import AzureProvider_Workflows.def file.

To import data files

1. Log on to the BMC Remedy Import Tool.
2. Select File > Preferences, and then select Generate New Id For All Records under Handle Duplicate Requests.
3. Select File > New Mapping.
   
   
   The Import Mappings page is displayed.
   
   

4. Enter the field values as applicable for importing the .arx files:

    

   Source data file	Target server	Target form name
   ARSystemOnlineHelpMapping.arx	<Select the Target Server Name>	ARSystemOnlineHelpMapping
   Azure_ResourceType_VendorMapping.arx	<Select the Target Server Name>	Azure_ResourceType_VendorMapping
   SysMessageBox.arx	<Select the Target Server Name>	SysMessageBox
   Azure_ProviderVendorFormMapping.arx	<Select the Target Server Name>	Azure_ProviderVendorFormMapping

5. Click Auto Map.

6. Click Import > Start Import.
   An entry is created in the following forms when the respective data file is imported.

   Form name	Details of entry created
   ARSystemOnlineHelpMapping	Azure Help instance
   Azure_ResourceType_VendorMapping	-
   SysMessageBox	-
   Azure_ProviderVendorFormMapping	Provider = “Azure”

Clearing the Mid Tier and browser caches

Perform the steps listed below to clear the BMC Remedy Mid Tier and the web browser cache:

1. Log on to the Mid Tier Configuration Tool at the following link:
   http://<midTierHost>:<portNumber>/arsys/shared/config/config.jsp
   
2. In the left navigation pane, click Cache Settings.
3. Click Flush Cache.
4. Clear the browser cache.

Verifying the Azure installation

See to verify that the installation was completed successfully.