Unsupported content

 

This version of the product is in limited support. However, the documentation is available for your convenience. You will not be able to leave comments.

BMC Client Management connectors


Service catalog administrators and internal service suppliers can build services that call BMC Client Management actions from within BMC Digital Workplace Catalog workflows. Depending on your needs, you might use either or both of the following connectors:

  • Client Management connector—Runs operational rules from BMC Client Management
  • Client Management Command connector—Runs mobile commands from BMC Client Management 

BMC Digital Workplace Catalog supports integration with BMC Client Management version 12.0 and later. Before service catalog administrators can use the BMC Client Management connectors in BMC Digital Workplace Catalog, an administrator must configure the integration, as described in Integrating BMC Digital Workplace Catalog with BMC Client Management.

Related topics

Integrating BMC Digital Workplace Catalog with BMC Client Management

Getting started with operational rules (BMC Client Management 12.7 online documentation)

Service connector overview

Service connector capabilities

Workflows for service fulfillment

External account requirements

This connector requires an administrator account for BMC Client Management with Write permission for the master server. For information about creating the account, see Creating an Administrator  in the BMC Client Management 12.7 online documentation.

Configuration parameters for the BMC Client Mangement connectors

Before you can use either of the BMC Client Management connectors to import services or in workflows, you must:

  1. Configure BMC Client Management for the integration, as described in Integrating BMC Digital Workplace Catalog with BMC Client Management.
  2. Configure a connection, as described in Configuring service connectors.
    The following table describes the parameters required to create a connection:

    ParameterExamplesDescription
    Server URL

    https://vw-tlv-bcm.calbro.com:16111

    Specifies the URL to the BMC Client Management master server in the following format: <https://host.name:port>
    LoginDWPintegrationLogin name of an administrator account with Write permission for the master service in BMC Client Management
    PasswordP4ss-w0rdPassword for the administrator account

Catalog import capabilities

With the Client Management connector, you can import operational rules from BMC Client Management as services in BMC Digital Workplace Catalog.

With the Client Management Command connector, you can import mobile commands from BMC Client Management as services in BMC Digital Workplace Catalog. For more information, see Importing service catalog items.

Workflow actions available through the BMC Client Management connectors

The following table provides an overview of all BMC Client Management connector actions:

ActionDescriptionInput parametersOutput parameters

Deploy Oprule On Device

Through the Client Management connector, deploy an operational rule on the specified device.

Deploy Oprule On Device input parameters

Not applicable

Deploy Command On DeviceThrough the Client Management Command connector, deploy a mobile command on the specified device.Deploy Command On Device input parametersNot applicable
Wait Deployment EndWait for the operational rule or mobile command to be deployed to the specified device.Connection IDOutput
Deploy Oprule On Device From Name

Deploy a client management operational rule on a device from its name.

  • Connection ID
  • Operational Rule ID
  • Device Name
Not applicable

Get Deployment Status

Get the status of the deployment that is just created. The status can be In Progress, Done, or Error.

  • Connection ID
  • Assignment ID
Not applicable
Get Device ID From Its Name

Get the device Id from the device name because the action that Client Management calls for the deployment takes device Id as the parameter. (Internal)

  • Connection ID
  • Device Name
Not applicable

Example 1: Workflow for a service that deploys an operational rule to a device

The following example is basic workflow to deploy an operational rule to a device. The specific action depends on the operational rule specified, such as an operational rule to deploy a patch.

Example 2: Workflow for a service that deploys a mobile command to a device

The following example is basic workflow to deploy a mobile command to a device. The specific action depends on the mobile command specified, such as a mobile command to install a mobile application on an Apple iPhone.

Deploy Oprule On Device input parameters

All of the following parameters are required.

Parameter nameData typeExampleDescription
Connection IDStringExampleID01Default Connection ID for this connector.
Operational Rule IDStringExternalServiceID034BMC Client Management identifier for the operational rule.
Device IDStringWIN0123

BMC Client Management identifier for the device.

Deploy Command On Device input parameters

All of the following parameters are required.

Parameter nameData typeExampleDescription
Connection IDStringExampleID01Default Connection ID for this connector.
Command IDStringExternalServiceID048BMC Client Management identifier for the mobile command.
Device IDStringWIN0123

BMC Client Management identifier for the device.

Workflow actions available through the BMC Client Management Mobile connectors

The following table provides an overview of all BMC Client Management Mobile connector actions:

ActionDescriptionInput parametersOutput parameters

Deploy Command On Device

Deploy a client management command on a mobile device (iOS) from the device Id. 

  • Connection ID
  • Command UD
  • Device ID
Not applicable

Deploy Command On Device From Name

Deploy a client management command on a mobile device from the device name.
  • Connection ID
  • Command UD
  • Device Name
Not applicable

Get Deployment Status

Get the status of the deployment that is just created. The status can be In Progress, Done, or Error.
  • Connection ID
  • Assignment ID
Not applicable

Get Device ID From Its Name

Get the device Id from the device name because the action that Client Management calls for the deployment takes device Id as the parameter. (Internal)
  • Connection ID
  • Device Name
Not applicable

Wait Deployment End

Wait for the end of the deployment. It is a loop that stops when the status is not In Progress.
  • Connection ID
  • Assignment ID
Not applicable


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.

Comments