Email Configuration and testing email in IFS Apps 10 | IFS Community
Solved

Email Configuration and testing email in IFS Apps 10

  • 23 July 2020
  • 6 replies
  • 1156 views

Badge +1

Hi,

 

I am trying to configure email setup from Setup IFS Connect, I have input the mail settings in MAIL_SENDER1. Now I want to test those setting, what is the procedure to test the mail settings on IFS Apps 10

icon

Best answer by Srikanth 23 July 2020, 14:44

View original

6 replies

Userlevel 6
Badge +16

Couple of different ways you can test the configuration:

  1. You can use the option to Email Report to a recipient and this is available when you Preview a report in IFS
  2. Second option is to create a custom Email-based event to send an email depending on the condition you define.
Userlevel 7
Badge +16

Hi @SynNajamH,

 

The easiest way is to test using the routing address : Example mail to someone from the Routing Addresses screen. After you fill up ‘To’ field with the email address that you want to send the email to, you can RMB on the screen and click ‘Test’. After that, you can type a sample message and click on ‘Send’. If everything is set up correctly, an email will be sent to the address you set up in ‘To’ field.

 

Hope this helps!

Badge +1

Hi @SynNajamH,

 

The easiest way is to test using the routing address : Example mail to someone from the Routing Addresses screen. After you fill up ‘To’ field with the email address that you want to send the email to, you can RMB on the screen and click ‘Test’. After that, you can type a sample message and click on ‘Send’. If everything is set up correctly, an email will be sent to the address you set up in ‘To’ field.

 

Hope this helps!

Its giving below error:

 

Server error messages: b7e40058-b82f-4509-81fe-077cf84d5070 Ifs.Fnd.FndSystemException: Explorer: An Unhandled Exception has occurred ---> Ifs.Fnd.FndSystemException: Unexpected error while calling server method ConnectTester/TestRouteAddress ---> Ifs.Fnd.FndServerFaultException: Error while preparing input data. Caused by: ifs.fnd.base.SystemException: Transformer error: javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Content is not allowed in prolog. Caused by: javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Content is not allowed in prolog. Caused by: javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Content is not allowed in prolog. Caused by: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Content is not allowed in prolog. at Ifs.Fnd.AccessProvider.FndConnection.ParseErrorHeader(FndBuffer buffer, FndManualDecisionCollection decisions) at Ifs.Fnd.AccessProvider.FndConnection.UnMarshalResponseHeader(Stream responseStream, FndManualDecisionCollection decisions) at Ifs.Fnd.AccessProvider.FndConnection.HandleHttpSuccessResult(HttpWebResponse result, FndManualDecisionCollection decisions, String operation, FndBodyType responseBodyType, Object responseBody) at Ifs.Fnd.AccessProvider.FndConnection.InvokeInternal(Object requestBody, Object responseBody, String intface, String operation, FndRequestContext requestContext, FndManualDecisionCollection decisions, Boolean forcedSync, Boolean integrationGateway) --- End of inner exception stack trace --- at Ifs.Fnd.AccessProvider.FndConnection.InvokeInternal(Object requestBody, Object responseBody, String intface, String operation, FndRequestContext requestContext, FndManualDecisionCollection decisions, Boolean forcedSync, Boolean integrationGateway) at Ifs.Fnd.AccessProvider.FndConnection.InvokeInternal(String intface, String operation, Object requestBody, Object responseBody, FndRequestContext requestContext, Boolean forcedSync, Boolean integrationGateway) at Ifs.Fnd.AccessProvider.Activity.FndActivityContext.InvokeIntegration(String intface, String operation, Object request, Object response) at Ifs.Fnd.AccessProvider.Activity.FndActivityCommand.ExecuteNonQuery(Object body) at Ifs.Application.MessageRouting.ServerInterface.Ifs.Application.MessageRouting.IConnectTester.TestRouteAddress(RouteAddress address, ApplicationMessage& message) at Ifs.Application.MessageRouting.TestRouteAddress.fndButtonSend_Click(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at Ifs.Fnd.Windows.Forms.FndButton.OnClick(EventArgs e) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) --- End of inner exception stack trace ---

Badge +1

Couple of different ways you can test the configuration:

  1. You can use the option to Email Report to a recipient and this is available when you Preview a report in IFS
  2. Second option is to create a custom Email-based event to send an email depending on the condition you define.

I have checked the job on Application Messages its still in Processing

Userlevel 6
Badge +16

What is job_queue_processes parameter set to in Oracle

Are your IFS background jobs running OK?

All MW Servers up and Running?

If there is an issue with your SMTP server, the Application Server message should fail with an error, which seems like not the case.

Badge +1

The environment on which I was testing this was set to the specific domain, which is why when I am trying to get emails using different domain address like gmail yahoo it was not working.

 

Thank you all for the help. :)

Reply