Skip to main content

Capturing Outbound Messages in Raw Format (Doc ID 477998.1) - Siebel

If you are troubleshooting issues with auto replies or with replies to or forwarding of inbound emails, you can capture the outbound messages in their raw format, as text files which are the MIME encoded raw Internet email messages. This allows  Technical Support to see the outbound messages as they are sent out by the Siebel Server. Follow these steps to trap outbound messages in this format:

Log in to the Siebel Web Client as SADMIN.

NOTE: You could also log in as another user who has access to the Communications Administration screen.

Choose View > Site Map > Administration - Communications > Communications Drivers and Profiles.

In the Communications Drivers applet, select the Internet SMTP/POP3 Server communications driver.

Click the Driver Parameters tab, set the following parameter:

Save Sent Messages TRUE

Restart the CommOutboundMgr task.

Raw outbound email messages will be captured in the SIEBEL_ROOT\SiebSrvr\bin\sent directory. The file names will generally look like this:

smtp_A28_1_2_40508ACA_1_1D71243.tmp

Review the .tmp files and select several examples which relate to the issue in the Service Request your have logged. Make sure you do not modify these files in any way.

Consolidate the example .tmp files and provide the consolidated file to Siebel Technical Support.

Similar articles:

How to enable tracing for POP3SMTP log for Oracle Support

Tracing Communications Outbound Manager (CommOutboundMgr) Tasks

Capturing Outbound Messages in Raw Format

Trapping the SMTP/POP3 protocol

Tracing the Send Email Button Click Event for Send Button – Siebel Dedicated Client

Tracing the Send Email Button Click Event for Send Button – Siebel Web Client

Exporting Internet SMTP/POP3 Server Communications Driver Default Settings

Exporting Communications Outbound Manager Component Configuration


Source: Oracle Support/ Doc ID 477998.1

Labels:

Comments

Post a Comment

Popular posts from this blog

How to set Profile Attribute in Siebel Workflow

For setting the Profile Attribute in Siebel Workflow, follow below steps: Add Business Service box in workflow. Open Business Service properties. Set  SessionAccessService in Business Service Name. Set  SetProfileAttr in Method Name. Then click on Business Service and set Input Arguments as below: Against Name argument you will add your profile attribute name and against Value argument you will add value for the new profile attribute, it could be from Process Property or Literal.
Post a Comment
Read more

How to call Popup Applet through Server Script in Siebel

Background: Based on the requirements you need to show data or reports on a popup applet. You can invoke popup applet using workflow (below business service will be used in business service step), applet server script or browser script and using vanilla method and setting field user properties. Procedure: Below is the script for calling popup applet through server script: if (MethodName == "MethodName") { var oServiceAF = TheApplication().GetService("SLM Save List Service"); var inputPropAF = TheApplication().NewPropertySet(); var outputPropAF = TheApplication().NewPropertySet(); inputPropAF.SetProperty("Applet Name","ABC Popup Applet"); inputPropAF.SetProperty("Applet Mode","6"); inputPropAF.SetProperty("Applet Height", "700"); inputPropAF.SetProperty("Applet Width", "700"); oServiceAF.InvokeMethod("LoadPopupApplet", inputPropAF, outputPropAF) return (CancelOperati...
Post a Comment
Read more

How to create and publish Inbound Web Service in Siebel based on Workflow

Inbound Web Services: The Inbound Web Service allows an external system to call a Siebel published Web Service. You can publish a business service or a business process as a Web Service and generate a Web Service Definition Language (WSDL) file that an external system can import. The Inbound Web Services can only be published from Siebel C using SOAP-RPC binding. Source: Oracle Docs What Is The Difference Between Web Services and APIs? An API is an interface that allows you to build on the data and functionality of another application, while a web service is a network-based resource that fulfills a specific task. Yes, there’s overlap between the two: all web services are APIs, but not all APIs are web services. Both web services and APIs are — at their core — very useful and very much used today. However, it’s the web services associated with SOAP and/or Service Oriented Architecture which are falling out of favor. Source: NordicApis Process: Prepare the workflow which will serve as Si...
Post a Comment
Read more