BMC Client Management connectors

Service catalog administrators and internal service suppliers can build services that call BMC Helix Client Management actions from within BMC Helix 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 Helix Client Management
Client Management Command connector—Runs mobile commands from BMC Helix Client Management

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

Required license

BMC Helix Digital Workplace Advanced

Getting started with operational rules Open link (BMC Helix Client Management online documentation)

Service connector overview

Service connector capabilities

Workflows for service fulfillment

External account requirements

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

Configuration parameters for the BMC Helix Client Management connectors

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

Configure BMC Helix Client Management for the integration, as described in Integrating BMC Helix Digital Workplace Catalog with BMC Client Management.

Configure a connection, as described in Configuring service connectors.
The following table describes the parameters required to create a connection:

Parameter	Examples	Description
Server URL	https://vw-tlv-bcm.calbro.com:1611 1	Specifies the URL to the BMC Helix Client Management master server in the following format: <https://host.name:port >
Login	DWPintegration	Login name of an administrator account with Write permission for the master service in BMC Helix Client Management
Password	P4ss-w0rd	Password for the administrator account

Catalog import capabilities

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

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

Workflow actions available through the BMC Helix Client Management connectors

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

Action	Description	Input parameters	Output 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 Device	Through the Client Management Command connector, deploy a mobile command on the specified device.	Deploy Command On Device input parameters	Not applicable
Wait Deployment End	Wait for the operational rule or mobile command to be deployed to the specified device.	Connection ID	Output
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 a 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 a 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 name	Data type	Example	Description
Connection ID	String	ExampleID01	The default Connection ID for this connector.
Operational Rule ID	String	ExternalServiceID034	BMC Helix Client Management identifier for the operational rule.
Device ID	String	WIN0123	BMC Helix Client Management identifier for the device.

Deploy Command On Device input parameters