Using Outlook 365 for Workflow Notification Mailer

Start Here

Get in touch with a
TriCore Solutions specialist

Blog | Jan 12, 2016

Using Outlook 365 for Workflow Notification Mailer


The benefit we get here by moving away from Traditional SMTP/IMAP Server is to minimize In-house Exchange Overheads. It keeps you updated on the Critical Patches as well.

Introduction:

There is high demand for integrating Outlook 365 with Workflow Notification Mailer in Oracle E-Business Suite to reduce Overheads for the upkeep of the internal Exchange Infrastructure.

The steps below explain the process in detail: 

1. Export the Certificate from the Email server. 

https://outlook.office365.com/owa

Clicked on Lock to download Cert

Downloaded Cert (Name it as outlook.cer)

 

2. Create a keystore on the Concurrent Manager Tier. Import the certificate to the keystore: 

          a. Create a keystore that holds the certificate, use the default location (i.e. /home/applmgr)

keytool -genkey -alias -keystore -storetype JKS

Kept all passwords as "changeit" ß This is the Default Password

Enter keystore password:

Re-enter new password:

What is your first and last name?

  [Unknown]:  <Name>

What is the name of your organizational unit?

  [Unknown]:  IT

What is the name of your organization?

  [Unknown]:  <Company>

What is the name of your City or Locality?

  [Unknown]:  <City>

What is the name of your State or Province?

  [Unknown]:  <State>

What is the two-letter country code for this unit?

  [Unknown]:  US

Is CN=, OU=IT, O=, L=,ST=, C=US correct?

  [no]:  yes

 

Enter key password for <-keystore>

        (RETURN if same as keystore password):

b. Upload the Certificate to the Concurrent Manager Tier using a FTP tool then import the certificate into the created keystore:

Copied outlook.cer at $HOME <-- Open in TEXT and copy/paste in vi

keytool -import -alias outlook -file outlook.cer -keystore .keystore -storepass changeit

c. Verify the certificate

keytool -list -keystore -keystore

Enter keystore password:

Keystore type: JKS

Keystore provider: SUN

Your keystore contains 2 entries

outlook, <Date>, trustedCertEntry,

Certificate fingerprint (MD5):

-keystore, <Date, PrivateKeyEntry,

Certificate fingerprint (MD5): 

d. Set MAILER_SSL_TRUSTSTORE (i.e. /home/applmgr/.keystore )

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

outlook365

Next Screen Snippet 


outlook365_1

outlook265_2

Command Line Test scripts

With IMAP, SSL

$AFJVAPRG -classpath $AF_CLASSPATH -Dprotocol=imap -Ddbcfile=$FND_SECURE/$TWO_TASK.dbc -Dserver=outlook.office365.com -Dport=993 -Dssl=Y -Dtruststore=/home/applmgr/.keystore -Daccount=<emailaccount> -Dpassword=<Pass> -Dconnect_timeout=120 -Ddebug=Y -Dlogfile=365ImapSSLTest.log -DdebugMailSession=Y oracle.apps.fnd.wf.mailer.Mailer 

With SMTP, Non-SSL

$AFJVAPRG -classpath $AF_CLASSPATH -Dprotocol=smtp -Ddbcfile=$FND_SECURE/$TWO_TASK.dbc -Dserver=outlook.office365.com -Dport=587 -Dssl=N -Dtruststore=/home/applmgr/.keystore -Daccount=<emailaccount> -Dpassword=<Pass> -Dconnect_timeout=120 -Ddebug=Y -Dlogfile=365smtpNSSLTest.log -DdebugMailSession=Y oracle.apps.fnd.wf.mailer.Mailer 

With IMAP, Non-SSL

$AFJVAPRG -classpath $AF_CLASSPATH -Dprotocol=imap -Ddbcfile=$FND_SECURE/$TWO_TASK.dbc -Dserver=outlook.office365.com -Dport=25 -Dssl=N -Dtruststore=/home/applmgr/.keystore -

Daccount=<emailaccount> -Dpassword=<pass> -Dconnect_timeout=120 -Ddebug=Y -Dlogfile=365ImapNSSLTest.log -DdebugMailSession=Y oracle.apps.fnd.wf.mailer.Mailer

Expand IMAP and SSL

The Final Workflow Screen is given below:

outlook_3

**Restart All the Workflow Containers after the above steps

 

The following message appears after integrating the workflow log with outlook365:

-         Simple Work around would be to restart the Workflow Mailer to re-establish the connection:

 

NOTE:

-         Always take Full Backup as the back out plan

-         To be executed by an Experienced Oracle Apps DBA resource

-         Keep check on Outlook365 Certificate validity as new certificate needs to be imported in Oracle upon expiration 

Conclusion:

The benefit we get here by moving away from Traditional SMTP/IMAP Server is to minimize In-house Exchange Overheads. It keeps you updated on the Critical Patches as well.

For any questions on the topic click below:

 Ask Shyamal