SSL handshake error.

The default keystore (DemoTrust.jks) for WebLogic Server may cause this error.

Change the default keystore for WebLogic Server. Configure the Custom Identity and Java Standard Trust keystore for the WebLogic Server.

For more information, see Oracle WebLogic Remote Console Online Help.

Email notification is not being sent.

The Outgoing (SMTP) Mail Server settings in the UMS Email Driver are incorrect.

Check the following settings in the UMS Email Driver using Oracle Fusion Middleware Control:

• OutgoingMailServer

• OutgoingMailServerPort

Note: Validate the values by using them in any email client for connecting to the SMTP server.

The SMTP server requires authentication or a secure connection (TLS or SSL).

Check the following settings in the UMS Email Driver using Oracle Fusion Middleware Control:

• OutgoingUsername

• OutgoingPassword

• OutgoingMailServerSecurity

Notifications are not being sent because of error message: No matching drivers found for sender address = <address>

The UMS Driver for the appropriate channel is configured with a specific list of SenderAddresses, and the message sent by the application has set a non-matching Sender Address.

Note: UMS Server matches the outbound message's sender address, if set, against the available drivers' SenderAddresses to find a matching driver to use for delivering the message. If a driver has set one or more SenderAddresses, then the UMS Server only sends messages with the matching sender address to it.

• Check the following settings in the appropriate UMS Driver using Oracle Fusion Middleware Control:

  SenderAddresses

  Note: The format for SenderAddresses is a comma-delimited list of <DeliveryType>:<Address>.

  For example:

  EMAIL:sender@example.com, EMAIL:sender@example2.com

• Leave this property blank, if you want this driver to service outbound messages for all sender addresses for this channel (delivery type).

• If there are multiple driver instances deployed for the same channel (delivery type) with different configurations, use the SenderAddresses to differentiate the driver instances. For example, one instance can be set with a value in SenderAddresses to only service outbound messages with that matching sender address, while the other instance can keep the SenderAddresses blank to service all outbound messages that do not specify any sender address or one that does not match that of the first driver instance.

• SenderAddresses that are configured with the incorrect syntax (such as missing <DeliveryType>:) are ignored by the UMS Server for driver selection.

The email client inconsistently receives notifications.

The Incoming Mail Server settings in the UMS Email Driver are configured with the same email account to which notifications are being sent.

If the notification is sent to the same account, the UMS Email Driver may download and process the email before the email client can display it.

Use an exclusive email account for Incoming Mail Server settings. Check the following settings in the UMS Email Driver using Oracle Fusion Middleware Control:

• IncomingMailIDs

• IncomingUserIDs

The application does not receive emails.

The Incoming Mail Server settings in the UMS Email Driver are incorrect.

Check the following settings in the UMS Email Driver using Oracle Fusion Middleware Control:

• MailAccessProtocol (IMAP or POP3, in uppercase)

• ReceiveFolder

• IncomingMailServer

• IncomingMailServerPort

• IncomingMailServerSSL

• IncomingMailServerSSL

• IncomingUserIDs

• IncomingUserPasswords

• ImapAuthPlainDisable

Note: Validate the values by using them in any email client for connecting to an IMAP or POP3 server.

The mail access protocol is incorrect.

Check the following settings in the UMS Email Driver using Oracle Fusion Middleware Control:

• MailAccessProtocol (IMAP or POP3, in uppercase)

The email server is SSL-enabled.

Check the following settings in the UMS Email Driver using Oracle Fusion Middleware Control:

• IncomingMailServerSS

The receive folder name is incorrect.

Check the following settings in the UMS Email Driver using Oracle Fusion Middleware Control:

• ReceiveFolder

Note: Some email servers may expect the value INBOX to be inbox or Inbox (that is, case-sensitive). Based on your email server, use an appropriate value.

The application did not register the corresponding AccessPoint.

Register an AccessPoint using the UMS API.

For more information, see Oracle Fusion Middleware Developing Applications with Oracle User Messaging Service.

The connection succeeds but gets closed immediately since there is a mismatch in the subject

The certificate used is incorrect for the environment.

Each environment (dev, test, production, etc.) needs to be provisioned with its own certificate. Verify that the correct certification is used for the remote environment.

APNS notifications are not delivered

A device token retrieved for production environment is likely being used for non-production.

Use the correct device token retrieved for each environment. For more information, see https://developer.apple.com/library/ios/technotes/tn2265/_index.html

PKIX path building is failing and is unable to find a valid certification path to the requested target for the APNS driver in Secure mode environment

The relevant APNS certificates are not imported.

To setup a remote notification server, you must establish a trusted connection to APNS. To create this connection, you must install the AAA Certificate Services root certificate on each of your servers. Download the certificate from Setting up a remote notification server.

You must import the downloaded certificate to the WebLogic’s configured keystore by using the following command:

keytool -importcert -keystore "../fmwhome12/wlserver/server/lib/DemoTrust.jks" -storepass DemoTrustKeyStorePassPhrase -file AAACertificateServices.crt  -alias "AAACertificateServices.crt"

GCM workflow throws an error while sending messages in secure mode environment after successful test connection.

Missing trusted certificates

The hostnameverifier configuration in WebLogic is not accepting wild characters.

You must import the global root certificate with keytool to the custom cert store configured in WebLogic.

Global sign root certificates can be downloaded at GlobalSign Root Certificates.

Runtime throws an error after configuring GCM driver.

Default “BEA Hostname verifier” does not support wildcards.

You must verify the hostname for the Managed Server.