Skip to Content
Information
Unsupported content This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Importing operations into BladeLogic Portal

A standard installation of BladeLogic Portal provides a utility that can import multiple jobs from BMC Server Automation and assign them to portal security groups. This utility provides an easy way to populate BladeLogic Portal with operations and get operators up and running fast.

After you run this utility the jobs appear as operations on the home page.

To import operations

  1. Determine whether the JAVA_HOME environment variable is set. If it isn't, set the variable to the location where java is installed.
  2. Navigate to the utility. 
    <install_location>/portal/utilities/importJobs.zip.
  3. Extract the contents of the file in its current location.

  4. Edit a file that defines the properties of the import. When you are finished, save your edits.
    You can find a sample version of this file at <install_location>/import_jobs/import_job_input_sample.properties.
    In this file you can set the following values:

    Value

    Explanation

    portalServerName

    Name or IP address of the server hosting BladeLogic Portal.

    portalServerPort

    Port for accessing BladeLogic Portal. Typically, 8443 if you are using the HTTPS protocol.

    protocolServerProtocol

    HTTP or HTTPS.

    adminUser

    Administrative user who can access BladeLogic Portal.

    siteName

    Name of the BMC Server Automation site that is registered with BladeLogic Portal. For example, if the name of the site is "PrimaryBSA" in the portal, enter "PrimaryBSA" here.

    list of jobs to be imported

    Each row uses this format: job<number>=<path in BSA>/<content name>,<content type>,<list of security groups>
    job<number> is a number assigned to the job you are importing.
    <path in BSA> is the path where the job is stored in BMC Server Automation.
    <content name> is the name of the job being imported.
    <content type> is the type of job being imported. The allowed job types are:
    BATCH
    COMPLIANCE
    DEPLOY
    NSH_SCRIPT
    AIX_PATCHING
    REDHAT_PATCHING
    SOLARIS_PATCHING
    SUSE_PATCHING
    WINDOWS_PATCHING
    <list of security groups> is a comma-separated list of portal security groups that are granted access to the job.

    Here is an example of an import job properties file.

    portalServerName=portalserver1.domain.com
    portalServerPort=8443
    portalServerProtocol=https
    adminUser=BLAdmin
    password=password
    siteName=BSAserver1.domain.com
    job0=Jobs/DCAPortal/UnitTestJobs/Batch Jobs/Automation Batch Job,BATCH,WinAdmin,LinuxAdmin
    job0=Jobs/DCAPortal/UnitTestJobs/Batch Jobs/Test01 Job,BATCH,WinAdmin,LinuxAdmin

  5. Enter the following command, which points to the file you edited in the previous step:

      • Windows:bmc_job_importer.bat <path_to_import_job_properties_file>
      • Linux: ./bmc_job_importer.sh <path_to_import_job_properties_file>
  6. When prompted, enter the password for the portal's administrative user (that is the adminUser specified in the properties file in step 4).
    A series of messages display describing the progress of the job.

 

 

 

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

BMC BladeLogic Portal 2.2