Configuring the BMC Remedyforce monitor adapter
You configure an adapter in Grid Manager. The configuration provides information about how the adapter interacts with the BMC Remedyforce application.
The form view provides an easy-to-use interface for configuring adapters. The form view prevents human errors that might occur as a result of copying the configuration XML from the XML sample into the UI when configuring an adapter. 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 the XML from that view, you cannot use the form view for modifying that configuration.
To configure the monitor adapter:
- Log on to the BMC Atrium Orchestrator Grid Manager.
- To access the adapters page, click the Manage tab, and then click the Adapters tab.
- In the Adapters in Repository, select the bmc-ao-adapter-remedyforce-monitor check box.
- Click Add to Grid to include the adapter in the Adapters on Grid list.
- Click Configure corresponding to the newly added adapter.
- On the Add an Adapter Configuration page, perform the following substeps to configure the adapter using the form view or skip to step 7 to configure the adapter using the XML view:
Enter a name for the adapter.
- Enter a description for the adapter.
- Under Properties, enter or select values for the configuration elements.
Include all required elements, indicated with an asterisk (*).
- (optional) Configure the adapter in the XML view using the following substeps:
- Enter a name and a description for the adapter.
- Click Switch to XML View.
- On the Warning message that appears, click Switch View.
Copy the configuration elements and attributes from the XML sample into the Properties text box, and then click OK.
- On the Warning message that appears, click Save.
This action saves the adapter configuration with settings in the XML view permanently. The newly configured adapter is now listed in the Adapters on Grid list.
The following table describes the node elements required for configuring the monitor adapter:
Node elements required to configure the monitor adapter
UI label | Element | Description | Required |
---|---|---|---|
Target | <target> | Specifies the host name or the IP address of the POP3 or IMAP mail server | Yes |
Port | <port> | Specifies the port on which the POP3 or IMAP server listens for events | No |
User Name | <user-name> | Specifies the user name for the account to be monitored | Yes |
Password | <password> | Specifies the password that corresponds to the <user-name> | Yes |
Encryption Type | encryption-type | Indicates whether the password specified is encrypted | No |
Javamail Debug | <javamail-debug> | Specifies whether to turn on the debug message logging for JavaMail | 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 | Yes |
Refresh | <refresh> | Specifies the interval, in seconds, to check for new messages | No |
Mail Timeout | <mail-timeout> | Specifies the time, in seconds, to maintain an established connection | No |
Connection Timeout | <connection-timeout> | Specifies the time, in seconds, after which the session expires | No |
Process all unread mails | <process-all-unread-mails> | Specifies whether to read the unread messages Valid values: true, false (default) | No |
Disable Auth Login | <disable-auth-login> | Prevents the use of non-standard AUTHENTICATE LOGIN command with the POP servers | No |
Disable Auth Plain | <disable-auth-plain> | Prevents the use of AUTHENTICATE PLAIN command with the POP servers | No |
Delete After Read | <delete-after-read> | Determines whether a message must be deleted from the server after it is read by the adapter Valid values: true, false (default) | Conditional; required to use the <max-messages-per-connection> element |
Max Messages Per Connection | <max-messages-per-connection> | Specifies the maximum number of messages to be pulled per connection attempt Default value: 20 | No |
Ignore Attachments | <ignore-attachments> | Indicates whether the attachments must be ignored and excluded from the adapter event | No |
Create Subdirectory | <create-subdirectory> | Indicates whether each attachment must be downloaded into a separate directory | No |
Attachment Download Directory | <attachment-download-directory> | Specifies the path and the directory where the attachments on the monitored email messages are downloaded | 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 | No |
Attachment Ttl | <attachment-ttl> | Specifies the period for which an attachment is permitted to reside in the download directory before being deleted
| No |
Max Attachment Size | <max-attachment-size> | Specifies the maximum file size, in MB, which can be attached to a mail message | No |
Max Pool Threads | <max-pool-threads> | Specifies the maximum number of threads that can be used to download the attachments simultaneously | No |
Delete Attachments On Exit | <delete-attachments-on-exit> | Deletes all downloaded attachments when the adapter is stopped or disabled | No |
Disk Cleanup Interval | <disk-cleanup-interval> | Specifies the interval after which the attachments that have exceeded the <attachment-ttl> period must be deleted
| No |
File Name Filter | <file-name-filter> | Contains the elements that specify the file name criteria for downloading a file | Conditional; required if the <file-name> element is present |
File Type Filter | <file-type-filter> | Contains the elements that specify the file type criteria for downloading an attachment | Conditional; required if the <file-type> element is present |
Use Ssl Certificate | <use-ssl-certificate> | Specifies whether SSL certificates are used for authentication | No |
Allow Unsigned Certificate | <allow-unsigned-certificate> | Specifies whether unsigned certificates are permitted for SSL authentication
| 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
| No |
Passphrase | <passphrase> | Specifies the password to the keystore file (cacerts) local to the BMC Atrium Orchestrator peer This value must match the passphrase in the keystore. You can change the passphrase using a keytool. If you make a change, you must update this value to reflect the new passphrase. | 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 | No |
Expand Htmltext Attachment | <expand-htmltext-attachment> | Specifies whether the HTML data content of a message that is sent as an attachment appears in an adapter event | No |
Character Set | <character-set> | Specifies the supporting CharSet | No |
None | <preferred-bodypart-text-format> | Specifies whether to return the bodypart in the email messages in either of the following formats:
Note: This element is not available in the Form View. You can add it by switching to the XML view. | No |
The following figure shows an XML sample for configuring the monitor adapter:
XML sample for configuring the monitor adapter
<target>pop.gmail.com</target>
<port>995</port>
<user-name>allen.brooke@gmail.com</user-name>
<password encryption-type="Plain">hasini23</password>
<javamail-debug>false</javamail-debug>
<email-address>allen.brooke@gmail.com</email-address>
<protocol>pop3</protocol>
<refresh>30</refresh>
<mail-timeout>60</mail-timeout>
<connection-timeout>30</connection-timeout>
<process-all-unread-mails>false</process-all-unread-mails>
<disable-auth-login>false</disable-auth-login>
<disable-auth-plain>false</disable-auth-plain>
<ignore-attachments>false</ignore-attachments>
<create-subdirectory>false</create-subdirectory>
<attachment-overwrite-existing>false</attachment-overwrite-existing>
<attachment-ttl>10d</attachment-ttl>
<max-attachment-size>10</max-attachment-size>
<max-pool-threads>1</max-pool-threads>
<delete-attachments-on-exit>false</delete-attachments-on-exit>
<disk-cleanup-interval>10m</disk-cleanup-interval>
<use-ssl-certificate>true</use-ssl-certificate>
<allow-unsigned-certificate>false</allow-unsigned-certificate>
<install-certificate>true</install-certificate>
<passphrase>changeit</passphrase>
<expand-plaintext-attachment>false</expand-plaintext-attachment>
<expand-htmltext-attachment>false</expand-htmltext-attachment>
<ignore-peer-name-in-attachment>false</ignore-peer-name-in-attachment>
</config>
<config>
The following figure shows an XML sample with POP3 and SSL disabled:
XML sample with protocol POP3 and SSL disabled
<target>imap.gmail.com</target>
<port>993</port>
<user-name>remedyforcemonitor </user-name>
<password encryption-type="Plain">bmcTest@1</password>
<javamail-debug>false</javamail-debug>
<email-address>remedyforcemonitor @gmail.com</email-address>
<protocol>imap</protocol>
<refresh>300</refresh>
<mail-timeout>60</mail-timeout>
<connection-timeout>30</connection-timeout>
<process-all-unread-mails>false</process-all-unread-mails>
<disable-auth-login>false</disable-auth-login>
<disable-auth-plain>false</disable-auth-plain>
<ignore-attachments>false</ignore-attachments>
<create-subdirectory>false</create-subdirectory>
<attachment-overwrite-existing>false</attachment-overwrite-existing>
<attachment-ttl>10d</attachment-ttl>
<max-attachment-size>10</max-attachment-size>
<max-pool-threads>1</max-pool-threads>
<delete-attachments-on-exit>false</delete-attachments-on-exit>
<disk-cleanup-interval>10m</disk-cleanup-interval>
<use-ssl-certificate>true</use-ssl-certificate>
<allow-unsigned-certificate>false</allow-unsigned-certificate>
<install-certificate>true</install-certificate>
<passphrase>changeit</passphrase>
<expand-plaintext-attachment>false</expand-plaintext-attachment>
<expand-htmltext-attachment>false</expand-htmltext-attachment>
<ignore-peer-name-in-attachment>false</ignore-peer-name-in-attachment>
</config>
The following figure shows an XML sample with IMAP and SSL disabled:
XML sample with IMAP and SSL disabled
<target>imap.gmail.com</target>
<port>143</port>
<user-name>remedyforcemonitor</user-name>
<password encryption-type="Plain">bmcTest@1</password>
<javamail-debug>false</javamail-debug>
<email-address>remedyforcemonitor@gmail.com</email-address>
<protocol>imap</protocol>
<refresh>300</refresh>
<mail-timeout>60</mail-timeout>
<connection-timeout>30</connection-timeout>
<process-all-unread-mails>false</process-all-unread-mails>
<disable-auth-login>false</disable-auth-login>
<disable-auth-plain>false</disable-auth-plain>
<ignore-attachments>false</ignore-attachments>
<create-subdirectory>false</create-subdirectory>
<attachment-overwrite-existing>false</attachment-overwrite-existing>
<attachment-ttl>10d</attachment-ttl>
<max-attachment-size>10</max-attachment-size>
<max-pool-threads>1</max-pool-threads>
<delete-attachments-on-exit>false</delete-attachments-on-exit>
<disk-cleanup-interval>10m</disk-cleanup-interval>
<use-ssl-certificate>false</use-ssl-certificate>
<allow-unsigned-certificate>false</allow-unsigned-certificate>
<install-certificate>true</install-certificate>
<passphrase>changeit</passphrase>
<expand-plaintext-attachment>false</expand-plaintext-attachment>
<expand-htmltext-attachment>false</expand-htmltext-attachment>
<ignore-peer-name-in-attachment>false</ignore-peer-name-in-attachment>
</config>