Introduction to Oracle User Messaging Service Configuration

Configuring Oracle User Messaging Service 11-7 3. Navigate to the User Messaging Service Home page. 4. Click usermessagingserversoa_server1. The Associated Drivers page appears. Figure 11–6 Drivers Associated with the UMS Instance 5. Select the Local tab to access the drivers collocated with the UMS server instance. These drivers may or may not be registered with the UMS server depending on whether or not they are properly configured. The ALL tab lists all drivers that are deployed in the domain and registered to all the UMS server instances.

6. Find the Email driver in the list, and then click the adjacent Configure Driver icon.

The configuration page displays Figure 11–7 . Figure 11–7 The Basic Configuration Page for a Selected Driver 7. If needed, expand the Driver-Specific Configuration section and configure the driver parameters. For more information, see Section 11.4.1.1, About Driver Properties .

11.4.1.1 About Driver Properties

Oracle User Messaging Service drivers share common properties listed in Table 11–1 that are used by the Messaging Engine when routing outbound messages. Typically, administrators set such Quality of Service QoS properties as driver cost Cost and driver speed Speed, supported carriers SupportedCarriers, and supported protocols SupportedProtocols. Driver developers configure properties that typically do not require modification by the administrator, such as supported delivery types SupportedDeliveryTypes, and supported content types SupportedContentTypes. 11-8 Oracle Fusion Middleware Administrator’s Guide for Oracle SOA Suite

11.4.1.2 Securing Passwords

Sensitive driver properties namely, passwords can be stored securely in the credential store using Oracle Enterprise Manager. Properties are marked with the flag Encoded Credential and have a custom entry form field. To store a sensitive driver property securely:

1. Go to the driver configuration page of the selected driver.

2. In the Driver-Specific Configuration section, locate the property with the Encoded

Credential flag set.

3. Select the credential type Depending on the selected credential type, you will be

prompted to enter the username andor password.. There are three options: Note: Properties such as SendingQueuesInfo are for advanced use and only require modification for advanced deployment topologies. Table 11–1 Common Driver Properties Name Description Mandatory Property? Capability Sets the driver’s capability to send or receive messages. The values are SEND, RECEIVE, and BOTH. Yes Cost The cost level of the driver from 0 - 10. 0 is least expensive; 10 is most expensive. If the value is not in this range, cost is considered to be 0. No DefaultSenderAddress The default address of the sender. The driver uses these addresses when sending a message that has no sender address specified, or when the specified sender address is not in the sender addresses list and the driver does not support using the application-provided sender address. No SenderAddresses The list of sender addresses that the driver supports. If provided by the driver, the Messaging Engine can use this to route a sending message to the driver by matching against the sender address of the message. No SendingQueuesInfo The information for the Driver Sending Queue. Yes Speed The speed level of the driver from 0-10, with 10 being the fastest. No SupportedCarriers A comma-separated list of supported carriers. No SupportedContent Types The content type supported by the driver. Yes SupportedDelivery Types The delivery types supported by the driver. Yes SupportedProtocols A comma-separated list of supported protocols. Entering an asterisk for any protocol. No SupportedStatusTypes The status types supported by the driver. No SupportsCancel Supports a Cancel operation on a message. No SupportsReplace Supports a Replace operation on a message. No SupportsStatusPolling For certain protocols, an active polling of the remote gateway must be performed to check the status of a message previously sent. This property indicates whether the driver supports such status polling. If set to true, the Messaging Engine invokes the driver connections getStatus operation. No SupportsTracking Supports Tracking operation on a message. No Configuring Oracle User Messaging Service 11-9 ■ Indirect password, create new user default option—specify the username and real password; the password will be stored in the credential store with the username as part of the key. The key and a fixed folder map name will be stored in the driver deployments driverconfig.xml. ■ Indirect password, use existing user—choose an existing usernamekey in the credential store to reference the password you stored previously. ■ User a clear text password—specify the password, and it will be stored directly in driverconfig.xml.

4. Click on Apply to save the changes.

5. Restart the driver application or the container for the changes to take effect. You can check the password in the driver deployment directorys driverconfig.xml. For an indirect password, the format will be: value=-mapName:keyName mapName is the driver target name, and the key is parameter_name.username For example, here is a sample entry in driverconfig.xml for an Email Drivers OutgoingPassword property: Property value=-gt;Farm_base_domainbase_domainserver_ soausermessagingdriver-email:OutgoingPassword.ouser encodedCredential=true type=java.lang.String mandatory=no name=OutgoingPassword description=oracle.sdp.messaging.EmailDriverConfig.outgoingPassword

11.4.1.3 Configuring the E-Mail Driver

The E-Mail Driver both sends and receives messages that is, its Capability property is set to BOTH by default. The E-Mail Driver sends messages over SMTP and uses either IMAP and POP3 for receiving messages.

11.4.1.3.1 E-Mail Driver Interoperability This section details interoperability features of the

E-Mail Driver. The E-Mail driver is compatible with these protocols: POP3, IMAP4, and SMTP. E-Mail Driver features include: ■ Automatic connection retry ■ SMTP for message sending ■ IMAP4 and POP3 for message receiving using polling ■ Scalable, highly available ■ Prevents message loss and avoids duplication The Gateway Vendors and Versions in Table 11–2 have been verified. Table 11–2 E-Mail Driver Gateway Vendors and Versions Vendor Version Oracle Beehive Release 1 1.4.3 Oracle Collaboration Suite 10g Release 1 10.1.2 Microsoft Exchange 2003 Dovecot IMAP4POP3 0.99.11 sendmail SMTP 8.13.1