Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Configuring BMC Server Automation

Use the following procedure to configure BMC Server Automation in an upgrade.

To run database migration and SQL update

Perform the following steps to run database migration and SQL update.

Microsoft Windows database migration and SQL update steps

Note

Step 1 to Step 6 apply only to 2.1.x and 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. Extract the external-files.zip file.
  3. Open a Command prompt, change directories to the C:\Program Files\BMC Software\BladeLogic\NSH\bin folder, and then press Enter.
  4. Type blmigration_mgr.exe <external_files_zip>\bl_8.5.01\db_scripts\sqlserver\upgrade and press Enter. 
    For example:
    blmigration_mgr.exe C:\Windows\Temp\Common\external-files\bl_8.5.01\db_scripts\sqlserver\upgrade 
  5. In the Data Migration Manager, select Validate Environment and ensure that the validation results are successful.
    ValidateEnvironment.png
  6. Select Run migration and ensure that the migration results are successful.
    RunMigration.png
  7. Click OK and then close the Data Migration Manager. 
  8. Copy the <clmInstallDir>\media\Applications\BL-OpsManager\Common\SQL_Update_Scripts.zip file to the BMC Server Automation – Application Server & Console host and then extract it.
  9. At command prompt, change directories to the sqlserver  folder.
    For example:
    cd <parent_dir>\8.5.01\Remediation\sqlserver 
  10. Execute the following script:
    install_hotfix_update_sqlserver_script.bat <Server> <DB_Name> <Bladelogic_DB_user> <Bladelogic_DB_Pass>
    install_hotfix_update_sqlserver_script.bat vw-sjc-bsm-dv10 BLADE bladelogic password 
  11. Start the BladeLogic Application Server.
    For more information, see Migrating an SQL database on the BMC Server Automation 8.5 documentation portal. 

Linux database migration and SQL update steps

Note

Step 1 to Step 11 apply only to 2.1.x and 3.x upgrades. If you are upgrading 4.0 to 4.x, start with Step 12. 

  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 clm40_build/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.5.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. From the BMC Server Automation – Application Server & Console host, open shell prompt.
  8. Type cd <Install_dir>/Operations Manager/NSH/bin and press Enter.
  9. Type ./blmigration_mgr <external_files_zip>/bl_8.5.00/db_scripts/oracle/upgrade and press Enter.
  10. In the Data Migration Manager, select Validate Environment and ensure that the validation results are successful.
  11. Select Run migration and ensure that the migration results are successful.
  12. Copy the <clmInstallDir>/media/Applications/BL-OpsManager/Common/SQL_Update_Scripts.zip to the BMC Server Automation – Application Server & Console host.and extract it.

  13. Open a command window and execute the following commands:

    chown -R oracle:dba <extracted_folder>
    su - oracle
    cd <parent_dir>\8.5.01\Remediation\oracle
    sqlplus <bsa_db_user>/<bsa_db_pass>@<oracle_sid>
    @install_hotfix_update_oracle_script.sql
  14. Start the BladeLogic Application Server.
    For more information, see Migrating an Oracle database on the BMC Server Automation 8.5 documentation portal. 

To upgrade the Virtual Center Agent

Perform the following steps to manually upgrade the Virtual Center (VC) agent.

Note

Before upgrading, note the Connection name and Virtualization name in the Property Dictionary View that is displayed on the BMC Server Automation Console.

  • 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 Built-In Property Classes > Virtualization > Instances. Double-click the 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 Exports-file-overview and exports file permission examples in the BMC Server Automation 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.

To upgrade the VM template

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 Exports-file-overview and exports file permission examples in the BMC Server Automation 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.

To 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.

To update the Distribute Configuration Objects jobs

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 Distribute Configuration Objects jobs.

  1. In the Folder section of the left panel, expand Servers.
  2. Select VC and right-click to view the context menu.
  3. Click Browse and verify that the VMware vCenter Server appears in the Browse section.
  4. If the vCenter server does not appear, right-click VC and select Administration Tasks > Distribute Configuration Objects.
  5. On the New Distribute Configuration Objects job window, specify a name and location for the job.
  6. Click Next.
  7. Select the VMware vCenter Server for the upgraded BMC Server Automation version.
  8. From the Global Configuration Objects list, select the required configuration objects and click the > arrow.
  9. Click Next.
  10. On the Select Target window, select the required VCs.
  11. Click Next and select Execute Job Now.
  12. Click Finish.
  13. To review the job result, go to the folder that you specified in step 5.
  14. Right-click the file and click Show Result.

To 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.

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. For 2.x upgrades, set AppServer DefaultRestVersion to 8.1.02.

  2. 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.

Where to go next

Configuring-Cloud-Platform-Manager

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*