Pages

Sunday, June 4, 2017

R12 E-Business Suite Configuring Workflow Mailer with TLS for Microsoft Office365, Gmail, or Cloud Based Email Services for 12.1.3 and 12.2

R12 E-Business Suite Configuring Workflow Mailer with TLS for Microsoft Office365, Gmail, or Cloud Based Email Services for 12.1.3 and 12.2


APPLIES TO:

Oracle Workflow - Version 12.1.3 to 12.2.4 [Release 12.1 to 12.2]
Information in this document applies to any platform.
GOAL

Setup the Oracle Workflow Mailer to connect to Email servers using TLS authentication.

SOLUTION

To resolve the issue test the following steps in a development instance and then migrate accordingly:

1. Download the following patches along with any required prerequisite patches per the readme instructions:

A. For 12.1.3, apply the following patches to configure the Workflow Mailer with TLS:

Patch 9452181 to upgrade javamail api to 1.4.3 (after applying patch 9452181 you must regenerate the jar files with force option using adadmin and restart middle tier(s))
Patch 20924889 : 1OFF:12.1.3:23192128:OPTION TO SELECT DIFFERENT SECURITY PROTOCOLS NONE/SSL/TLS/STARTTLS FOR MAILER
B. For 12.2, reference the following document and apply the latest AD/TXK patches which contain the changes for Workflow Mailer with TLS:

Note 1617461.1 - Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 (Doc ID 1617461.1)
C. For the latest Cloud Email Server Patch information, review the following document and confirm all recommended patches are applied:

   Note 2077434.1 - Configuring an Oracle Workflow Notification Mailer with Cloud E-Mail Servers (Doc ID 2077434.1)

2. Set the following mailer parameters by running $FND_TOP/sql/afsvcpup.sql script:

 sqlplus apps/<pwd> @$FND_TOP/sql/afsvcpup.sql

Select component id 10006 - the default seeded mailer parameter.

Note: If there is more than one mailer configured then these actions will need to be done for each mailer component, which will have a unique ID.


 2.A.  For Outbound:

    'INBOUND_THREAD_COUNT' parameter value to '0'  - turns off the imap processing and allows us to configure SMTP and IMAP separately

    'PROCESSOR_OUT_THREAD_COUNT':  1

    Log level : 1

    Debug Mail Session : Y

    OUTBOUND_SERVER:  smtp.office365.com

    'Outbound Security Protocol':  TLS

     Note:  This parameter delivered by Patch 20540463  

    'Outbound SSL Enabled' leave at null or set to N

 2.B. For Inbound:

  'INBOUND_THREAD_COUNT' parameter value to '1'

  'IMAP_SECURE_PROTOCOL' value to 'SSL'

   Note: Some customers may need to use TLS for this parameter. This parameter is set only from the back end. Possible values are SSL, TLS, and NONE (Default).

   'INBOUND_SERVER_NAME' : outlook.office365.com:993

   By default outlook uses port 993 but some customers may need to use 143 depending on mail proxies

    Username : username@domain.com

    password: xxxxx

    'Inbound SSL Enabled' leave at null or set to N

    'REPLYTO' : username@domain.om

    'LOG_LEVEL' : 1

    'DEBUG_MAIL_SESSION' : Y

    MAILER_SSL_TRUSTSTORE:  set to default jdk keystore: $AF_JRE_TOP/lib/security/cacerts

3) Stop the Notification Mailer component from OAM UI, and then restart it so that it picks up the new values.  

4) Verify that Mailer is running, and now Inbound is enabled (and all the Inbound parameters are correctly set).

5) Setup the outbound first, and confirm the mailer starts with inbound turned off before configuring inbound.


Reference Doc ID 2051827.1

No comments:

Post a Comment