Manually installing or upgrading the IBM Bluemix Infrastructure Provider
This topic describes how to install the IBM Bluemix Infrastructure provider manually and how to verify the installation. The topic includes:
Prerequisites for installing the IBM Bluemix Infrastructure provider
Before installing IBM Bluemix Infrastructure provider, ensure that:
- You have downloaded the IBM Bluemix Infrastructure provider installer file (IBM SoftLayer Windows Installer 1.0.00.zip or IBM SoftLayer Linux Installer 1.0.00.tar), extracted the file contents, and stored the files on your local computer.
- The following BMC Cloud Lifecycle Management stack components are running when you install the IBM Bluemix Infrastructure provider:
- Cloud Platform Manager
- BMC Remedy Action Request System Server (BMC AR System Server)
- You have the same operating system (Windows or Linux) on the computer from where you will run the installer and the computer where BMC Cloud Lifecycle Management stack components are installed.
- You have the following privileges on the computer on which you want to run the installer and on which the BMC Cloud Lifecycle Management stack components are installed:
- Administrator (for Windows)
- root (for Linux)
- BMC Server Automation Network Shell (NSH) is installed, and the RSCD agent is running on the computer on which you want to run the installer and on which the BMC Cloud Lifecycle Management stack components are installed.
- You have Java 1.7.x 64-bit installed and have set the environment variables (JAVA_HOME and jre PATH).
Before you begin
Download and extract the following IBM Bluemix Infrastructure provider installer files and store them on your local computer.
Folder | Subfolder | Files |
---|---|---|
AR | def |
|
AR | arx |
|
OSGi |
|
Deploying OSGi files on the Cloud Platform Manager
- On the Platform Manager host, navigate to the Platform Manager installation folder, for example:
- C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Platform_Manager (for Windows)
- /gsf or data1/bmc/BMCCloudLifeCycleManagement/Platform_Manager (for Linux)
- (Applicable only when replacing the existing .jar files) Make a backup copy of the following files in the Platform Manager installation folder:
- PlatformManagerInstallFolder/configuration/config.ini
- PlatformManagerInstallFolder/configuration/providers.json
- PlatformManagerInstallFolder/configuration/cloudservices.json
- PlatformManagerInstallFolder/configuration/lib/softlayer-1.0.0.jar
- PlatformManagerInstallFolder/configuration/lib/softlayerconnect-1.0.0.jar
- Copy the following .jar files to the PlatformManagerInstallFolder/configuration/lib folder:
- softlayer-1.0.0.jar
- softlayerconnect-1.0.0.jar
- Edit the media.properties file as per your BMC Cloud Lifecycle Management environment.
- Copy the media.properties file to the PlatformManagerInstallFolder/configuration folder:
- Open the config.ini file and append in the end of osgi.bundles parameter value as follows:
,lib/softlayer-1.0.0.jar@start,lib/softlayerconnect-1.0.0.jar@start - (Applicable only when replacing the existing .jar files) Delete the following folder contents and folder:
- PlatformManagerInstallFolder/cache folder contents
- PlatformManagerInstallFolder/configuration/org.eclipse.osgi folder
- Start the Platform Manager service and monitor the csm log files in the PlatformManagerInstallFolder\Logs folder.
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. To do so, follow this process:
- Switch to Base Development mode in BMC Remedy Developer Studio.
- Import the IBM_New_Forms.def file.
- Import IBM_Workflows.def file.
- Configure BMC Remedy AR forms.
- Re-import the .def files.
- Import the data files.
The procedures for these steps are in the sections below.
To switch to Base Development mode
- Log on to the BMC Remedy Developer Studio as Administrator.
- To switch to Base Development mode, choose File > Switch Mode > Base Development.
To import the IBM_New_Forms.def file
- Choose File > Import.
- Select ObjectDefinitions, and click Next.
The Import Objects window is displayed. - From the Import File field, browse to the .def file, and select it.
- Click Next.
The selected object details are displayed in the Object Selection. - Select the Replace Objects on the Destination Server check box.
- Click Finish.
The .def file is imported. - Click Save.
To import IBM_Workflows.def file
- Choose File > Import.
- Select ObjectDefinitions, and click Next.
The Import Objects window is displayed. - In the Import File field, browse to the .def file and select it.
- Click Open.
- Select the Replace Objects on the Destination Server check box.
- Select the Delete Excess fields check box.
- In Handle Conflicting Types, select Display Conflict Error.
- Click Finish to import the .def file.
- Click All Objects > Applications.
- Navigate to the Application's List and double-click to open the BMC Cloud Management Administrator and BMC Cloud Management Foundation applications.
To configure BMC Remedy AR forms
Choose All Objects > Applications.
Navigate to the Applications List and double-click to open the BMC Cloud Management Administrator and BMC Cloud Management Foundation applications.
Configure the following forms as the Primary Form in the respective applications.
Application name Form name BMC Cloud Management Foundation CMF:ProviderIBM_v BMC Cloud Management Administrator IBMCMA:ManageIBMUserAccounts - In the Form Selector window, enter the form name in the Filtering options field (for example, CMF:ProviderIBM_v or CMA:ManageIBMUserAccounts).
- Click OK to add the selected form in the application.
- Click Save.
To re-import the .def files
- To re-import the IBM_New_Forms.def, perform the steps in To import the IBM_New_Forms.def file.
- To re-import the IBM_Workflows.def, perform the steps in To import IBM_Workflows.def file.
To import data files
- Log on to the BMC Remedy Import Tool.
- Choose File > Preferences, and then select Generate New Id for All Records under Handle Duplicate Requests.
- Select File > New Mapping to open the Import Mappings dialog box.
Enter the field values as applicable for importing the .arx files:
Source data file Target server Target form name ProviderVendorMapping.arx Target server name ProviderVendorFormMapping ResourceType_VendorMapping.arx Target server name ResourceType_VendorMapping SysMessage.arx Target server name SysMessageBox - Click Auto Map.
- Click on Import > Start Import.
Clearing the Mid Tier and browser cache
Perform the steps listed below to clear the BMC Remedy Mid Tier and the web browser cache:
- Log on to the Mid Tier Configuration Tool at http://<midTierHost>:<portNumber>/arsys/shared/config/config.jsp.
- In the left navigation pane, click Cache Settings.
- Click Flush Cache.
- Clear the browser cache.
To verify the installation
- In the BMC Cloud Lifecycle Management – Administration Console, click the vertical Workspaces menu on the left side of the window, and select Providers.
- Click Register .
- In the Register Provider window, verify that the IBM SOFTLAYER provider type appears in the Provider Type list.
Comments
Log in or register to comment.