Understanding a Vocera VMP Adapter Configuration |
The minimum requirements for a Vocera VMP Adapter installation are described here.
An adapter defines a default Dataset structure in order to function. Attributes are organized by Datasets and store the information required by the adapter. Adapters use this data during the process of receiving and sending messages.
Not all adapters require Datasets to function. When an adapter does require Datasets, the system will determine if they already exist. If they do not exist, the system will create the needed Datasets.
When creating or editing an adapter, use the following information to select the appropriate datasets in the Required Datasets section.
DEVICES Dataset
Element | Name | Reverse Name | Key | Reverse Key | Required | Type | Description |
---|---|---|---|---|---|---|---|
Attribute | name | N/A | True | N/A | N/A | String | Attribute that stores the name that identifies the device, often based upon the MAC address of the device. |
Attribute | status | N/A | False | N/A | True | String | Attribute that stores the current registration status of the device. Possible values are Registered, Disconnected, Virtual, or Unregistered. |
Attribute | vendor | N/A | False | N/A | True | String | Attribute that stores the vendor of the device. For example, Cisco or XMPP. |
Attribute | ip_address | N/A | False | N/A | False | String | Attribute that stores the current IP address of the device. In some cases the Vocera Platform needs to keep track of the IP address of a device, such as with a Cisco phone. |
Attribute | priority | N/A | False | N/A | False | String | Attribute that stores the priority level of the most recent message sent to a device. Required by the device management library, but not set by the XMPP adapter. It is used as a filter to prevent less important messages from being sent to a user currently handling a critical issue. |
Attribute | token | N/A | False | N/A | False | String | Attribute that stores a special identifier needed by some devices, such as smart phones, in order to deliver a message. |
Link | lines | devices | False | False | N/A | One-to-many | The DEVICES Dataset is linked to the LINES Dataset, and the link order is 1:n (one device associated to many lines) |
Link | usr | devices | False | False | N/A | Many-to-one | The DEVICES Dataset is linked to the USERS Dataset, and the link order is n:1 (many devices associated to one user) |
LINES Dataset
Element | Name | Reverse Name | Key | Reverse Key | Required | Type | Description |
---|---|---|---|---|---|---|---|
Attribute | number | N/A | True | N/A | N/A | String | Attribute that stores an actual telephone or directory number |
Link | devices | lines | False | False | N/A | Many-to-one | The LINES Dataset is linked to the DEVICES Dataset, and the link order is n:1 (many lines associated to one device) |
USERS Dataset
Element | Name | Reverse Name | Key | Reverse Key | Required | Type | Description |
---|---|---|---|---|---|---|---|
Attribute | login | N/A | True | N/A | N/A | String | Attribute that stores the login name of the user. |
Link | devices | usr | False | False | N/A | One-to-many | The USERS Dataset is linked to the DEVICES Dataset, and the link order is 1:n (one user associated to many devices) |
VMPMESSAGETORULEMAP Dataset
Element | Name | Reverse Name | Key | Reverse Key | Required | Type | Description |
---|---|---|---|---|---|---|---|
Attribute | delivery_object_id | N/A | True | N/A | N/A | Integer | Attribute that stores the delivery object id generated when the rule originally triggered. |
Attribute | core_object_id | N/A | False | N/A | True | Integer | Attribute that stores the core object id of the record that originally triggered the rule. |
Attribute | rule_template_id | N/A | False | N/A | True | Integer | Attribute that stores the id of the rule template that was triggered. |