Verifying the BMC BladeLogic Server Automation installation

When verifying the BMC BladeLogic Server Automation installation, you check the following components:

When verifying the components, you check the corresponding installation logs, services and processes, and configuration settings.

Verifying the installation of the BMC BladeLogic Server Automation Console and Application Server

To verify the installation of the BMC BladeLogic Server Automation Console and Application Server, perform the following tasks.

To check the installation logs for SEVERE exception errors

  1. To determine whether any SEVERE exception errors were recorded, check both the client and server installation logs.
     You can check the installation logs through the Planner after the product installation is complete. Alternatively, you can access the installation logs through the corresponding directory path.

    The [liveData] macro is a standalone macro and it cannot be used inline. Click on this message for details.

    The following example shows a SEVERE client installation exception: 

    SEVERE,com.bmc.install.product.clientinstaller.AppServerRunningDetectionValidationTask,
    LOG EVENT {Description=[APPSERVER_AGENT_MUST_BE_STOPPED],Detail=[Application Server and RSCD Agent is running. Please stop the Application Server and RSCD Agent before attempting to install.]}
  2. If a SEVERE exception error exists in either or both log files, continue with the following checks. If no SEVERE exceptions are recorded, you are done with the verification.

To check services or processes

  • (Windows) Open the Services (Local) window, and verify that the following services are running:
    • BladeLogic Application Server
    • BladeLogic Process Spawner

      If they are not running, start them from the Services (Local) window.
  • (Linux) Run the ps-f command to get a full list of processes and to check the status of the blappserv and the blprocserv processes. If they are not running, start the respective process by executing the corresponding command:
    • /etc/init.d/blappserv start
    • /etc/init.d/blprocserv start

To check parameter values and application services

  1. On the system where the BMC BladeLogic Application Server is installed, invoke Network Shell (NSH) and run the blasadmin command to verify specified application services and parameters and their values.
    • (Windows) Select Start > Program Files > NSH to launch the script.
       A Command Prompt window is displayed, showing the host name followed by the hash sign:
      hostName#
    • (Linux) Run nsh from the command line: /bin/nsh.
       The host name followed by the hash sign is displayed.
  2. Enter the blasadmin command with the -s switch and the name of the deployment that you are checking. For example:
    hostName#blasadmin -s jobServer

  3. Verify that the following application services are enabled and that the following parameters have the assigned values:

    Application service/Parameter

    Value

    EnableWebServices

    True

    EnableAtriumIntegration

    True

    MaxJobs

    120

    MaxWorkItemThreads

    200

    MaxHeapSize

    1024

To check the Application Server's components and connectivity

Access the BMC BladeLogic Application Server by logging on to the BMC BladeLogic Server Automation Console as the BLAdmin user, with the BlAdmin password that you specified when installing and configuring the BMC BladeLogic Application Server. In the BMC BladeLogic Server Automation Console, verify that specific packages, catalogs, and folders have been created and that the BMC BladeLogic Application Server is connected with BMC Atrium CMDB.

  1. Expand the BladeLogic > Component Templates folder and verify that the following component template packages are created:
    • CSM_Application_Packages
    • CSM_Virtual_Guest_Packages

      BBSA_AppServer_1.jpg
  2. Expand the Depot folder to verify that that the following folders have been created:
    • CSM_Virtual_Guest_Packages
    • CSM_OS_Packages
    • CSM_Scripts
    • CSM_Publish_Product_Catalog
  3. Expand the Depot > CSM_Scripts folder to verify that the following .nsh scripts are created:
    • create_user_linux.nsh
    • create_user_windows.nsh
    • CSM_Delayed_Reboot.nsh
    • open_port_linux.nsh
    • open_port_windows.nsh
    • set_user_password_linux.nsh
    • set_user_password_windows.nsh

      BBSA_AppServer_7.jpg
  4. Expand the Jobs > CSM_Publish_Product_Catalog subfolder to verify that the Publish_Product_Catalog_job job is present.

    BBSA_AppServer_5.jpg
  5. Select Configuration > Infrastructure Management to display the Infrastructure Management dialog box.

    blinframgmt.png
  6. Expand the Application Servers folder to verify that the config_deployment_hostName and job_deployment_hostName subfolders are present.

    BBSA_AppServer_4.jpg
  7. Expand Database Configuration Info to verify the parameters of the BMC BladeLogic Server Automation database.

    BBSA_AppServer_2.jpg
  8. Select Configuration > Atrium Integration > Configuration to open the Atrium Integration Configuration dialog box.

    BBSA_AppServer_6.jpg
  9. Verify that the values for Host Name/IP Address, CMDB Port, and CMDB User are correct.
  10. To verify that the servers are communicating, click Test Connection.

Verifying the BMC Server Automation - File Server installation

After the installer reports that the installation is successful, perform the following steps:

  1. On the system on which you installed the File Server, verify that a folder named storage has been created in the following path:
    • (Windows) C:\Program Files\BMC Software\BladeLogic\storage
    • (Linux) /opt/bmc/bladlogic/storage
      The storage folder is empty when you first install the File Server. Later, when you install BMC BladeLogic Application Server and Console, you are prompted for the location of the File Server. The installation routine populates the storage folder with subfolders and files. The standard subfolders are blassetclass, scripts, and tmp.

      bbsa_fileserver_storage.jpg
  2. Log on to the target computer.
  3. Go to the directory where the File Server was created (for example, on Linux, /opt/bmc/bladelogic/storage).
  4. Perform the following actions:
    1. Create a subdirectory under the storage folder.
    2. Create a file in that subdirectory.
       You should be able to create a subdirectory and a file without getting an exception.

Note

If you did not choose to install File Server through the installer, during the installation of the BMC BladeLogic Application Server, the installer creates a File Server instance on the host where you install the Application Server.

Verifying the BMC BladeLogic Advanced Repeater server installation

To verify the installation of the BMC BladeLogic Advanced Repeater server, perform the following tasks.

To check the installation log for SEVERE exception errors

  1. To determine whether any SEVERE exception errors were recorded, check the Advanced Repeater installation log.
     You can check the bcac_install_log.txt installation log file through the Planner after the product installation is complete. Alternatively, you can access the installation log file through the corresponding directory path.

    Planner

    Click View Log to access the corresponding log file.

    Directory path

    The bcac_install_log.txt installation log file resides under the Windows\Temp directory on Windows or under the /tmp directory on Linux.

  2. If a SEVERE exception error exists, continue with the following checks. If no SEVERE exceptions are recorded, you are done with the verification.

To check services or processes

  • (Windows) Open the Services (Local) window, and verify that the following service is running: BMC BladeLogic Advanced Repeater.
  • (Linux) Run the ps-f | grep AdvancedRepeater command to check the status of the AdvancedRepeater process. If it is not running, start the process by executing the following command:
    /etc/init.d/AdvancedRepeater start

Verifying the installation of the BMC Server Automation - Application Server (MAS)

To verify the installation of the BMC Server Automation - Application Server (Multiple Application Server, or MAS) implementation, perform the following steps:

  1. Verify that the Application Server is running:
    • (Windows) Open the Services (Local) window, and verify that the BladeLogic Application Server service is running. If it is not running, start the service from the Services (Local) window.
    • (Linux) Run the ps-ef | grep blappserv command to to check the status of the blappserv process. If it is not running, start the process by executing the following command:
      /etc/init.d/blappserv start.
  2. Access the host system where the BMC BladeLogic primary server resides.
  3. Log on to the client Automation Console.
  4. Select Configuration > Infrastructure Management to display the Infrastructure Management dialog box.
  5. Verify that the secondary server that you installed has been added to the list by checking the Application Servers and Application Server Launcher folders.

Verifying the installation of the PXE and TFTP servers

To verify the installation of the Preboot Execution Environment (PXE) and Trivial File Transfer Protocol (TFTP) servers, perform the following tasks.

To check the installation log

  1. To determine whether any SEVERE exception errors were recorded, check the PXE installation log.
     You can check the installation log file, BladeLogic_Install, through the Planner after the product installation is complete. Alternatively, you can access the installation log through the corresponding directory path.

    Planner

    Click View Log to access the corresponding log file.

    Directory path

    The BladeLogic_Install log file resides under the Windows\Temp directory on Windows or under the /tmp directory on Linux.

  2. If a SEVERE exception error exists, continue with the following checks. If no SEVERE exceptions are recorded, you are done with the verification.

To check services or processes

  • (Windows) Open the Services (Local) window, and verify that the following services are running:
    • BladeLogic PXE Server
    • BladeLogic TFTP Server
  • (Linux) Run the ps-f command to get a full list of processes and to check the status of the blpxe and bltftp processes. If either process is not running, start the process by executing the corresponding command:
    • /etc/init.d/blpxe start
    • /etc/init.d/bltftp start

To check the services running on the Application Server

  1. Access the BMC BladeLogic Application Server by logging on to the BMC BladeLogic Server Automation Console as the BLAdmin user, with the BlAdmin password that you specified when installing and configuring the BMC BladeLogic Application Server.
  2. In the BMC BladeLogic Server Automation Console, select Configuration > Infrastructure Management, and verify that the PXE server or servers are listed and that each server has the following services:
    • AppServerService
    • BIProcessService
    • DatabaseService
    • FileManagerService
    • PortProviderService
    • SupportService

      BBSA_AppServer_8_PXE.jpg