Configuring BMC Server Automation

Use the following procedure to configure BMC Server Automation after you finish upgrading the cloud stack.

Before you begin

Open your back-up copy of the C:\Program Files\BMC Software\BladeLogic\RSCD\daal (Windows) or /opt/bmc/bladeLogic\rscd\daal (Linux) folders. You need this information to manually configure various settings (for example, MaxHeapSize). 

Step 1 – Run Linux database migration and SQL updates

Note

Step 1 to Step 6 apply only to 3.x upgrades. If you are upgrading 4.0 to 4.x, start with Step 7. 
  1. Copy the external-files.zip file from the <clmInstallDir>/media/Applications/BL-OpsManager/Common subdirectory to the BMC Server Automation – Application Server & Console host.
  2. If you installed the BMC Server Automation – Application Server & Console database on a different host, copy the external-files.zip file from the <clmInstallDir>/media/Applications/BL-OpsManager/Common subdirectory on the database host. Otherwise, skip this step.
  3. Extract the external-files.zip file.
  4. Log on to the database computer as sysdba.
  5. Type @"<external_files_zip>/bl_8.7.01/db_scripts/oracle/upgrade/migration_setup_OM.sql".
    The migration_setup_OM.sql script grants permissions to the user that runs the database migration. By default, the script grants the permissions to the BLADELOGIC user. If you assigned a different user name, before you run the script you must edit the migration_setup_OM.sql script and replace each occurrence of BLADELOGIC with the user name that you assigned.
  6. Type commit.
  7. Copy the <clmInstallDir>/media/Applications/BL-OpsManager/Common/SQL_Update_Scripts.zip to the BMC Server Automation – Application Server & Console host.and extract it.
  8. Open a command window and execute the following commands:

    chown -R oracle:dba <extracted_folder>
    su - oracle
    cd <parent_dir>\8.7.01\Remediation\oracle
    sqlplus <bsa_db_user>/<bsa_db_pass>@<oracle_sid>
    @install_hotfix_update_oracle_script.sql
  9. Start the BladeLogic Application Server.

Step 2 – Upgrade the RSCD Agent on the Virtual Center

Perform the following steps to manually upgrade the RSCD Agent on the Virtual Center (VC).

Note

Before you start upgrading, write down and save the Connection name and Virtualization name in the Property Dictionary View that is displayed on the BMC Server Automation Console. You must keep this information handy when you finish the upgrade.

  • In the BMC Server Automation Console, select Configuration > Property Dictionary View > Property Dictionary > Built-In Property Classes > Connection. Double-click Connection. Select the Instances tab. Double-click the connector (for example, the Default Connection PSI Instance) and note the NAME of the instance.
  • To find the Virtualization name, select Configuration > Property Dictionary View > Property Dictionary > Built-In Property Classes > Virtualization > Instances. Double-click the virtual entity instance of the VC (your environment might have more than one virtual entity instance) and note the NAME of the instance.
  1. On the installer computer, navigate to the BL-RSCD folder:
  2. Navigate to:
    • On Microsoft Windows: C:\InstallPlanner\media\Applications\BL-RSCD\Windows.
    • On Linux: /opt/InstallPlanner/media/Applications/BL-RSCD/Linux.
  3. Copy the setup executable file to your Virtual Center target host.
  4. Manually launch the RSCD Agent installer and select Upgrade.
  5. Edit the last line in the rsc exports file to restrict access to the VC Agent.
    For more information, see Configuring the exports file in the BMC Server Automation 8.7.00 documentation.
    • On Windows:
      1. Edit C:\Windows\rsc.
      2. Modify the exports file to tighten the security of the Access Control List.
    • On Linux:
      1. Edit /usr/lib/rsc.
      2. Modify the exports file to tighten the security of the Access Control List.
  6. Log on to the BMC Server Automation console and run a Update Server Properties Job against the Virtual Center (VC).
  7. After the Update Server Properties job is completed, right-click on the VC Server and select Verify.
  8. Run the Distributed Configuration Object job against the VC server.
  9. Validate whether the Virtual Center is accessible from BMC Server Automation by right-clicking the VC target connection and then clicking Browse
    Using LiveBrowse, you can verify that all VC details are listed and can be browsed. This final step completes the VC Agent upgrade.

Step 3 – Upgrade the VM template (optional)

Optionally, perform the following steps to upgrade the VM template:

  1. Log on to VC hosting the target templates.
  2. Select the target template and convert it to VM.
  3. Power On the VM.
  4. From the <installation folder>/Applications directory, copy the BL-RSCD installer on the VM.
  5. Launch the installer
    The installer detects the existing RSCD Agent and upgrades it.
  6. Edit the last line in the rsc exports file to restrict access to the VC Agent.
    For more information, see Configuring the exports file in the BMC Server Automation 8.7.00 documentation.
    • On Windows:
      1. Edit C:\Windows\rsc.
      2. Modify the exports file to tighten the security of the Access Control List.
    • On Linux:
      1. Edit /usr/lib/rsc.
      2. Modify the exports file to tighten the security of the Access Control List.
  7. Shut down the VM.
  8. Select the VM and convert to template.

Step 4 – Update the Server Properties job

Note

If you plan to enable job deletion when editing or Registering resource providers, see Preparing for BMC Server Automation job deletion from BMC Cloud Lifecycle Management to avoid performance issues.

When you upgrade the VMware Virtual Center (VC) agent, its version information does not get automatically updated in the BMC Server Automation Server Properties tab. Perform the following procedures to update the Server Properties jobs.

  1. From your BMC Server Automation host, click Start > All Programs > BMC Software > BlageLogic Server Automation Suite.
  2. Click Server Automation Console <version number> and log on.
  3. In the Folder section of the left panel, expand Servers.
  4. Right-click VC and select Administration Tasks > Update Server Properties.
  5. On the Update Server Properties Job window, specify a name and location for the job.
  6. Save the job and click Next.
  7. If you have additional servers in your environment, add them to the Selected Server List and click Next.
  8. Click Next and select Execute Job Now.
  9. Click Finish.
  10. To review the job result, go to the folder that you specified in step 6.
  11. Right-click the file and click Show Result.
    If a green check mark appears beside the job, the job executed successfully.

Step 5 – Update the Distribute Configuration Objects jobs

Note

Before you start, find the Connection name and Virtualization name from the Property Dictionary View that you saved. You must have this information handy when you perform this procedure.

When you upgrade the VMware Virtual Center (VC) agent, its version information does not get automatically updated in the BMC Server Automation Server Properties tab. Perform the following manual steps to deprecate and un-deprecate the connection and VC instances, re-create the instances, and then update the Distribute Configuration Objects jobs.

  1. Deprecate the VC and connection instances:
    1. Select Configuration > Property Dictionary View > Property Dictionary > Built-In Property Classes > Virtualization > Instances
    2. Select the virtual entity instance of the VC and then click Remove.
    3. At the prompt, click Yes that you want to delete the VC property instance. 
    4. At the prompt that the VC property instance is being used by BMC Server Automation Server, click Yes to deprecate it. 
       
    5. Repeat these steps to deprecate the connection instance (Configuration > Property Dictionary View > Property Dictionary > Built-In Property Classes > Connection). 
  2. Un-deprecate the VC and connection instances:
    1. Choose Configuration > Property Dictionary View Built-In Property Classes.
    2. Navigate to the property class for which you want to create an instance, for example, Virtualization.
    3. Click the Instances tab.
    4. Click Add New Property Set Instance . The New Instance wizard opens, displaying the General panel.
    5. In the New Instance wizard, enter the name of the VC.
    6. Click Finish
    7. When you are prompted to un-deprecate this property set instance, click Yes
       
    8. When you are prompted that you successfully un-deprecated the instance, click OK
       
    9. Exit the wizard by clicking Cancel
    10. Repeat these steps to un-deprecate the connection instance.
  3. In the Folder section of the left panel, expand Servers.
  4. Locate the VC server from the list and then right-click to view the context menu. 
  5. Click Browse and verify that the VMware vCenter Server appears in the Browse section.
  6. If the vCenter server does not appear, right-click the VC and select Administration Tasks > Distribute Configuration Objects.
  7. On the New Distribute Configuration Objects Job wizard, specify a name and location for the job.
  8. Click Next.
  9. Select the VMware vCenter Server for the upgraded BMC Server Automation version from Available Configuration Objects.
  10. From Global Configuration Objects, select the upgraded VMware vCenter Server and then click the > arrow to add it to the list.
  11. Click Next.
  12. On the Select Targets panel, select the required VC and add it to the list.
  13. Click Next and add an optional job run notification. 
  14. Click Next and select Execute Job Now.
  15. Click Finish.
  16. To review the job result, go to the Jobs folder and select the job you created in Step 7.
  17. Right-click the file and click Show Result.

Step 6 – Verify that the VC is browsable from BMC Server Automation

Use LiveBrowse in BMC Server Automation to validate if the VC is accessible from BSA. 

  1. In the Folder section of the left panel, expand Servers.
  2. Select VC and right-click the VC target connection.
  3. Click Browse
  4. In the Live Browse tab or the content editor, expand the Live node.
    All the VC details should be listed and browsable. You confirmed and completed post-upgrade BMC Server Automation configuration.

Step 7 – Use the BLASAdmin utility to configure BMC Server Automation to support backward compatibility

Configure the following properties using BLASAdmin utility to support backward compatibility:

  1. Set Appserver RestAssetAttributesUseInternalName to false.

    Note

    Reset the above properties to their default values after you successfully complete the upgrade.

    For more information, see Managing Application Server behavior using the Application Server Administration console in the BMC Server Automation online technical documentation.

  2. Save your changes. 

Where to go next

Configuring Cloud Platform Manager

Was this page helpful? Yes No Submitting... Thank you

Comments