Configuring the CA Service Desk monitor adapter

You configure an adapter in BMC Atrium Orchestrator Grid Manager. The configuration provides information about how the adapter interacts with CA Service Desk. Although each adapter must have a unique name, you can create multiple adapters with the same adapter type to allow for different configuration properties.

The form view provides an easy-to-use interface for configuring adapters. The form view prevents errors that might occur when you copy the configuration XML from the adapter documentation to the UI during configuration. You can switch to the XML view to configure those elements and attributes that are not available as fields or to configure all the elements and attributes using XML only. However, after you switch to the XML view and save the configuration in XML from that view, you cannot thereafter use the form view to modify that configuration.

To configure the monitor adapter

  1. Log on to BMC Atrium Orchestrator Grid Manager.
  2. To access the adapters page, click the Manage tab, and then click the Adapters tab.
  3. In the Adapters in Repository list, select the bmc-adapter-ca-servicedesk-monitor check box.
  4. To include the adapter in the Adapters on Grid list, click Add to Grid.
  5. Click Configure corresponding to the newly added adapter.
  6. On the Add an Adapter Configuration page, perform the following steps to configure the adapter by using the form view, or skip to step 7 to configure the adapter by using the XML view:
    1. Enter a name for the adapter.;
    2. Enter a description for the adapter.
    3. Under Properties, enter or select values for the configuration elements. 
      Include all required elements, which are indicated with an asterisk (*).
    4. Click OK.
      The newly configured adapter is now listed in the Adapters on Grid list.
  7. (Optional) Configure the adapter in the XML view by performing the following steps:

    Note

    If you switch to the XML view, you cannot thereafter use the form view to modify the configuration.

    1. Enter a name and a description for the adapter.
    2. Click Switch to XML View.
    3. On the warning message that appears, click Switch View.
    4. In the Properties text box, use XML format to enter the configuration elements and attributes, and then click OK.

      Note

      If the default value for an optional element is acceptable, omit the element. Do not include empty elements.

    5. On the warning message that appears, click Save.
      The adapter configuration with settings is saved in the XML view permanently. The newly configured adapter is now listed in the Adapters on Grid list.

The following table describes the configuration elements for the monitor adapter. You cannot use the form view to configure elements and attributes that do not have an entry in the UI label column.

Node elements required for configuring the monitor adapter

UI label

Element

Description

Required

Target

<target>

Specifies the host name or the IP address of the IMAP server

Yes

Port

<port>

Specifies the port on which the IMAP server listens

If not specified, the adapter uses the a default value.

If the value of the <use-ssl-certificate> element is false, the default value is 143. If the value of the <use-ssl-certificate> element is true, the default is 993.

No

User Name

<user-name>

Specifies the user name for the account to be monitored

Conditional; required when the email application requires authentication

Password

<password>

Specifies the password that corresponds to the <user-name> provided

The <password> element can contain an encryption-type attribute.

Conditional; required when the email application requires authentication

Encryption Type

encryption-type

Indicates whether the password specified is encrypted; is an attribute of the <password> element, not an element itself

Valid values: Base64, Plain (default)

No

Character Set

<character-set>

Specifies the supporting character set (CharSet), which includes identifiers that describe a series of universal characters

If you do not provide the <character-set> element in the configuration, then the email will be parsed based on the CharSet returned in the Content-Type of the email.

No

Javamail Debug

<javamail-debug>

Indicates that debug message logging for JavaMail must be turned on

Valid values: true, false (default)

No

Email Address

<email-address>

Specifies the email address of the account to be monitored

Yes

Protocol

<protocol>

Specifies the email protocol to be used

Valid value: imap

Yes

Refresh

<refresh>

Specifies the interval, in seconds, for checking for new messages

Default value: 300 seconds (5 minutes)

No

Mail Timeout

<mail-timeout>

Specifies the time, in seconds, to maintain an established connection

Default value: 60 seconds (1 minute)

No

Connection Timeout

<connection-timeout>

Specifies the time, in seconds, to wait when establishing a connection

Default value: 30 seconds

No

Process All Unread Emails

<process-all-unread-mails>

Specifies whether to read the unread messages that are received when the adapter is inactive

If this element is set to true, emails that are received when the adapter is inactive are read. Otherwise, the emails that are received are ignored and only those messages that are received after the adapter is active are read.

Valid values: true, false (default)

No

Disable Auth Login

<disable-auth-login>

Prevents the use of a nonstandard AUTHENTICATE LOGIN command with IMAP servers

Valid values: true, false (default)

No

Disable Auth Plain

<disable-auth-plain>

Prevents the use of the AUTHENTICATE PLAIN command with POP servers

Valid values: true, false (default)

No

Ignore Attachments

<ignore-attachments>

Indicates whether attachments must be ignored and excluded from the adapter event

Valid values: true, false (default) (attachments permitted)

No

Expand Htmltext Attachment

<expand-htmltext-attachment>

Specifies whether the HTML data content of a message that is sent as an attachment appears in the <bodypart> element in an adapter event

Valid values: true, false (default)

If this element is set to true, the HTML data content of the message appears inside the <bodypart> element in an adapter event. Otherwise, the HTML data content of the message appears inside the <attachment> element in an adapter event.

No

Expand Plaintext Attachment

<expand-plaintext-attachment>

Specifies whether the plain text content of a message that is sent as an attachment appears in the <bodypart> element in an adapter event

Valid values: true, false (default)

If the value of <expand-plaintext-attachment> element is set to true, the plain text content of the message appears inside the <bodypart> element in an adapter event. Otherwise, the plain text content of the message appears inside the <attachment> element in an adapter event.

No

Create Subdirectory

<create-subdirectory>

Indicates whether each attachment must be downloaded into a separate directory

Valid values: true, false (default; downloads all the attachments into a single directory)

  • Subdirectory name format: attachment-download-directory/email-address/message ID/timestamp of download in epoch time
  • Sample subdirectory value: /mail/downloads/user@company.com/Message1/1196967357

No

Attachment Download Directory

<attachment-download-directory>

Specifies the path and the directory into which attachments on the monitored email messages are downloaded

Default value: Tomcat temp directory (on the computer where the CDP is installed)

No

Attachment Overwrite Existing

<attachment-overwrite-existing>

Indicates whether an attachment with the same file name has already been downloaded and overwrites that file with the current attachment

If the value of the <create-subdirectory> element is true, attachments are downloaded, ignoring the <attachment-overwrite-existing> element.

Valid values: true, false (default: preserves the original file)

No

Attachment Ttl

<attachment-ttl>

Specifies the time an attachment is permitted to reside in the download directory before being deleted

This value is specified as a numeric value followed by a time designator.

Valid values for time designators: m (minutes), h (hours), d (days)

Default value: 10d: Attachments reside for 10 days

No

Max Attachment Size

<max-attachment-size>

Specifies the maximum file size, in MB, that can be attached to a mail message

The maximum file size is defined per attachment; the total value of all the files can be greater, provided each file is less than or equal to the default value.

Default value: 10 MB

No

Max Pool Threads

<max-pool-threads>

Specifies the maximum number of threads that can be used to download attachments in parallel

Default value: 1

No

Delete Attachments On Exit

<delete-attachments-on-exit>

Deletes all downloaded attachments when the adapter is stopped or disabled

Valid values: true, false (default: preserves downloaded files)

No

Disk Cleanup Interval

<disk-cleanup-interval>

Specifies the interval at which the deletion of attachments that have exceeded the <attachment-ttl> period must occur

This value is specified as a numeric value followed by a time designator.

Valid values for time designators: m (minutes), h (hours), d (days)
Default value: 10m: Initiates cleanup every 10 minutes

No

File Name Filter

<file-name-filter>

Contains the elements that specify the file name criteria for downloading an attachment

You can use wildcard characters, * and ?, to define the file name filter. Only files that satisfy the filter criteria are downloaded. For details, see the <file-name> element.

Conditional; required if the <file-name> element is present

File Name

<file-name>

Specifies the criteria for an attached file to be downloaded, based on the file name

You can define one or more file names. A file that matches at least one file name filter is downloaded. If you do not provide criteria, a file with any file name is downloaded.

You can use wildcard characters, * and ?, to define the file name filter. With a *, the wild card portion of the file name can contain an unlimited number of characters. Each ? represents one character.
Examples:

  • Specify the value of <file-name> as *.jar to download all jar files.
  • Specify the value of <file-name> as abc.jar* to download all jar files starting with 'abc'.
  • Specify the value of <file-name> as *.* to download all files.
  • Specify the value of <file-name> as abcd.* or abcd* to download a file starting with 'abcd' and with any extension. However, if you set <file-type> to a specific extension, for example 'html', then files starting with 'abcd' and with extension 'html' are downloaded.

No

File Type Filter

<file-type-filter>

Contains the elements that specify the file type criteria for downloading a file attachment

Only files that satisfy the filter criteria are downloaded.

Conditional; required if the <file-type> element is present

File Type

<file-type>

Specifies the criteria for file download, based on the file type

You can define one or more file types. A file that matches at least one file type filter is downloaded. If you do not provide criteria, a file with any file type is downloaded.
Example: If you set <file-name> to 'abc.' and set <file-type> to 'html', the *abc.html file, if it exists, is downloaded.

Valid values:

  • DOC
  • XLS
  • XML
  • PDF
  • HTML
  • EXE

No

Use Ssl Certificate

<use-ssl-certificate>

Specifies whether SSL certificates are used for authentication

Valid values: true, false (default)

Note

To establish a secure connection with the specified target, set this element to true.

No

Allow Unsigned Certificates

<allow-unsigned-certificates>

Specifies whether unsigned certificates are permitted for SSL authentication

Note

If <use-ssl-certificate> is false or blank, you do not need this element.

If you are using self-signed SSL certificates (a common practice), set the value of this element to true.

On ecommerce sites or military installations, if you need to use signed certificates such as Verisign or Thawte, set the value of this element to false (a rare practice).

Valid values: true, false (default)

No

Install Certificate

<install-certificate>

Updates the default keystore file, java.Home\jre\lib\security\cacerts, with the certificates sent by the target URL during the SSLHandshake

If the verification of a certificate fails, the certificate is not installed. To install certificates successfully, the user who installs the peer that executes the request must have read or write access to the keystore file.

Certificates are uninstalled when the adapter is disabled on a peer. If a BMC Atrium Orchestrator peer is uninstalled without disabling this adapter, any certificates installed by the adapter continue to exist.

The validity of installed certificates is checked once every 24 hours. The first check is conducted 24 hours after the adapter is enabled.

Note

If <use-ssl-certificate> is false or blank, you do not need this element.

If you prefer to have security certificates installed automatically (a common practice), set the value of this element to true. If you prefer to manually export the security certificate from the specified target server and manually import it into the BMC Atrium Orchestrator's local peer's cacerts file (a rare practice), set the value of this element to false.

Valid values: true, false (default)

No

Passphrase

<passphrase>

Specifies the password to the keystore file (cacerts) local to the BMC Atrium Orchestrator peer.

Note

If <use-ssl-certificate> is false or blank, you do not need this element.

This value must match the passphrase in the keystore. You can change the passphrase using keytool. If you make a change, you must update this value to reflect the new passphrase.

Default value: changeit

No

Ignore Peer Name In Attachment

<ignore-peer-name-in-attachment>

Specifies whether to add or remove the peer name from an email event XML

Valid values: true, false (default)

Notes

  • The <ignore-peer-name-in-attachment> element is checked only if the <ignore-attachments> is set to false.
  • If you set <ignore-peer-name-in-attachment> to true, the <peer-name> element is not added in an email event XML (to avoid event de-duplication failure).
  • If you set <ignore-peer-name-in-attachment> to false, the <peer-name> element is added in an email event XML when <ignore-attachments> is false and the the email contains an attachment.

No

Note

The IMAP mail adapter supports the following message formats for the content of an email:

  • Plain text
  • HTML

XML sample for configuring the monitor adapter

<config name="config1">
    <target>machine.domain.com</target>
    <port>993</port>
    <user-name>casd12345</user-name>
    <password>service</password>
    <javamail-debug>true</javamail-debug>
    <email-address>casd12345@domain.com</email-address>
    <protocol>imap</protocol>
    <refresh>20</refresh>
    <mail-timeout>10</mail-timeout>
    <connection-timeout>3</connection-timeout>
    <disable-auth-login>true</disable-auth-login>
    <disable-auth-plain>true</disable-auth-plain>
    <ignore-attachments>false</ignore-attachments>
    <create-subdirectory>true</create-subdirectory>
    <attachment-overwrite-existing>false</attachment-overwrite-existing>
    <attachment-ttl>1d</attachment-ttl>
    <max-attachment-size>5</max-attachment-size>
    <max-pool-threads>2</max-pool-threads>
    <delete-attachments-on-exit>true</delete-attachments-on-exit>
    <disk-cleanup-interval>5m</disk-cleanup-interval>
    <use-ssl-certificate>true</use-ssl-certificate>
    <allow-unsigned-certificate>true</allow-unsigned-certificate>
    <install-certificate>true</install-certificate>
    <passphrase>changeit</passphrase>
    <ignore-peer-name-in-attachment>true</ignore-peer-name-in-attachment>
  </config>
Was this page helpful? Yes No Submitting... Thank you

Comments