Use logging action in message flow

Hi,
I have created a log action in my message flow. By default all my log messages goes to AdminServer.log.
Instead, i want the messages to be logged into a different file using log4j.
How do i achieve this?
Thanks.

Re: OSB Log file
Re: Using Log4J with OSB to Store Audit Information
Regards,
Anuj

Similar Messages

How to log the exception using Log action in Oracle Service Bus

Hi,
Whenever an exception is raised how to log the exception using Log action in oracle service bus.After logging where I have to find the logged message.

It would be in the log file for the managed server which ran the request. If you are logging the message at a lower level than your app server, however, you won't see it. You should be logging the exception at Error level.

Message Flow in Integration Engine

Dear Friends,
Kindly can someody share how the message is flowing in Intergration engine after the message taken from Adapter engine.
If you have any block diagram it will be helpful for me

Hi Karthik,
There are 6 stpes for the message processing thats only called
PIPELINE Steps.
what are all the steps involved in the Pipeline processing.
Sender Adapter picks up the file from the file system, converts it to XML and places it in the payload of an XI-SOAP message. Then it posts this message to the Integration Server pipeline via http(s).
XI pipeline steps are:-
->Sender Agreement
->Receiver Determination
->Interface Determination
->Interface Mapping
->Receiver Agreement.
When a source message reaches the Integration server, it performs 6 steps before the message reaches the destination. The steps are:
1) Receiver Determination: This steps determines the system that participates in the exchange of the message.
2) Interface Determination: For each receiver determine which interface will should receiver the message.
3) Message Split: If more than one receivers are found, Xi will instantiate new message for each receiver.
4) Message Mapping: Mapping to transform the source message to destination message format.
5) Technical Routing: Bind a specific destination and protocol to the message.
6) Call outbound Adapter: Send the transformed message to the adapter or a proxy.
One can examine these steps in Runtime Workbench using the Transaction: SXMB_MONI.
message flow in XI
The life cycle of the message is explained in detail by taking an example scenario. The file is picked up by the Sender File adapter and the data is inserted into DB table by Receiver DB Adapter.
       The adapter engine uses the messaging system to log the messages at every stage. This log is called the Audit Log. The audit log can be viewed from the runtime work bench (RWB) to look into the details of the lifecycle of the message. During our journey we will also have a look at the messages that are logged at different stages.
Note: This article is targeted for the newbieu2019s who want to understand the message flow in Adapter Engine. So the insight into the message lifecycle is provided here by taking only the Technical adapters (File/ JDBC/ JMS/ Mail) into consideration. It doesnu2019t delve into the lifecycle of the messages that have reached XI Adapter Engine using RNIF/ BC/ CIDX adapters.
ONWARD JOURNEY:
Fig1. Message flow from Adapter Engine to Integration Server
1.     For the message to be picked up by the communication channel, the channel should be associated with a sender agreement. Here creation of a communication channel doesnu2019t ensure the message to be polled and picked up by the adapter. The message reaches the adapter in its native message format. As the communication in SAP XI happens in XI message format, a module inside the adapter converts the message in native format into XI message format.
2.     During this process, a message ID is generated for the message. To build the XI header (sender agreement details like the sender system, sender message interface and the interface namespace) the details are fetched by performing a CPA lookup(collaboration-partner-agreement are the configuration object details that have been created using the configuration time. The details are updated into the runtime cache when you activate the Configuration objects in Integration builder u2013Configuration time. This cache is referred to as CPA cache).
3.     This message is then sent to module processor for further processing. During the process of sending the message to module processor, the message u201CApplication attempting to send an XI message asynchronously using connection AFWu201D is logged.
4.     The module processor performs steps like structure conversion, communication channel specific conversions (that have been specified in the u201Cmodule tabu201D of the adapter channel). These conversion modules are executed in the same sequence as mention in the communication channel.
5.     After the successful execution of the conversion modules, the appropriate module (call SAP adapter module) of the module processor is called which will send this message for persistent storage. This message is put into the Send Queue of the messaging system for further processing. Messages like u201CMessage trying to put into the send Queueu201D and u201CMessage successfully put into the queueu201D are logged during this process. A confirmation message (success/ failure) is sent back to the sender application at this stage. This confirmation message is used by the channel to perform various steps like deleting the file that has a processing mode as delete.
6.     The message that has been put in the Send Queue has to be picked up and sent to the Integration Engine. The Adapter Engine and XI Integration server use XI Adapter for internal communication purposes. So the XI Adapter picks up message from the send queue and parses the XI message. In this process, the status of the message is set to DLNG and. Messages like u201CThe message was successfully retrieved from the send queue and message status set to DLNGu201Dare logged.
7.     The XI adapter performs a SLD look up (System landscape Directory) to find the Integration server with which the Adapter framework has register itself.
8.     On successful SLD look up, the message is sent via HTTP to the XI IS pipeline, using the pipeline URL (http://hostname:abap-httpport/sap/xi/engine?type=entry). . If this is successful, a message u201CThe message was successfully transmitted to endpoint http://hostname:8000/sap/xi/engine?type=entry using connection AFWu201D is logged and the message statues is set to DLVD means message has been successfully delivered to the endpoint( XI IS in this case)
Fig2. Audit Log of message during onward journey
RETURN JOURNEY:
The return journey commences when the IS has successfully processed the message and delivers it to the Messaging system using the URL u201Chttp://hostname:50000/MessagingSystem/receive/AFW/XIu201D
br>
Fig3. Message flow from Integration Server to Adapter Engine
1.     When the Integration Server (XI IS) finishes processing of the pipeline steps (like receiver determination, interface determination and interface mapping), the message has to be delivered to the required Receiving system. So the XI Integration server will send the message to the messaging system of the Adapter Engine (AE) using the mentioned above. Once the message is successfully received by messaging system, the message u201CThe message was successfully received by the messaging system. Profile: XI URL: http://hostname:50000/MessagingSystem/receive/AFW/XIu201D is logged.
2.     As discussed Integration server and Adapter Engine use XI adapter for internal communication purposes. So the XI message that has been received by the messaging system URL is parsed by the XI Adapteru2019s protocol handler.
3.     The XI message is put into the receive queue and persisted. During this stage messages like u201CUsing connection AFW. Trying to put the message into the request queue; Message successfully put into the queue.u201D are logged.
4.     The XI messages that are put in the receive queue are retrieved by an application (Worker thread) and are sent to AFWListenerBean. AFWListenerBean is a module (an EJB) in Adapter Engine that is capable of parsing the XI message. On successful receive of the XI message by the AFWListenerBean, messages like u201CThe message was successfully retrieved from the request queue.u201D are logged and the status of the XI message is set to DLNG.
5.     The AFWListenerBean reads the receiver agreement and the corresponding channel from the XI header to determine the appropriate adapter. In this stage the adapter channel is logged in the audit log. u201CDelivering to channel: XYZ_Channelu201D
6.     The message is forwarded to the module processor where additional steps like structure conversions and extra modules specified in the adapter are performed.
7.     The exit module is called and the message is sent to the appropriate adapter (DB Adapter in this case). The format conversion will be executed within the specific adapter and sent to the Receiving system (DB in this case) using the channel that has been determined by the AFWListenerBean and the required action is reformed (select statement is performed in this case). On successful processing of the message the status is set to DLVD.

Using report action

I wanted to know if there are any performance impact due to the use of report actions. I am using report action to record the request and response message when an unexpected condition is in encountered in a service callout. My message flow has multiple service callout and as a result I have quiet a few report actions.
Is it is better to use Log action than a report action ? Where does the output of a log action end up ?
Rahul Phadnis

Is it is better to use Log action than a report action ? Depends on our use case. If you can putup with sifting through your webLogic log file, then Log action could also be used.Would recommend to use log action for administration(more of technical nature) than for business logic.
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/operations/reporting.html#wp1046607 -- Reporting framework is very simple and straight forward as documented above. Theoretically there will be slight degradation in performance due to extra layers of code for reporting but practically that should be negligible. Performance of built in reporting provider does suffice for most of the use cases.
Where does the output of a log action end up ?In the server log for the domain.
Manoj

"Log" action is not working in OSB10.3.1.0

Hi All,
I need a help. I am using a proxy which is listening to inbound JMS queue.Then the proxy is calling to a Business Service which also inturn pointing to a outbound JMS queue. In the proxy service i am doing a simple xslt transformation.To debug the process, i have added "Log" action tag inside pipelinepairnode/stage.
Now problem is when i am putting a XML into inbound JMS queue message is passing through proxy service & business service and then reaching to outbound queue,but i am not able to trace the message using "Log" action,so in server log nothing is getting update.
I am using OSB10.3.1.0 version.
can any one pls help me !!!!!!!
Thanks
Deba

Hi Deba,
Please change the Log file severity to DEBUG in Weblogic managed servers through Weblogic Console. Goto -
Server --> Logging --> General --> Advanced --> Log File --> Severity Level
Also change the severity level of Standard Out to DEBUG if you want those debug messages to be shown at STDOUT.
This has been discussed here -
Re: OSB: Debug logging
There is a workaround that separates all osb messages from weblogic logs, if you need it. It is discussed here:
alsb logging
Regards,
Anuj

Action replace in message flow

i try to change dynamically an email URI in message flow of a proxy service.
so i use : replace ./ctx:transport/ctx:uri in variable outbound with "mailto:...."
but it doesn't work, no change is made.
is it normal ?

Hi,
I got it to work by using the insert action instead of reaplce: (if you print the value of outbound context variable, the uri element doesn't exist in that), so you have to insert, it can't do replace on a non-existent element)
Insert
<uri xmlns="http://www.bea.com/wli/sb/context">jms://localhost:7001/weblogic.jws.jms.QueueConnectionFactory/EchoServiceResponseQueue</uri>
as first child of ./ctx:transport in outbound
Letme know if it doesn't work.

Goods Receipt in PO AND Message Flow Update in Inb. Delivery using WMMBXY

Dear All
This question is related to a previous one posted in:
Post Goods Receipt for Inbound Delivery using WHSCON IDoc
We have a stock transport order (PO) for which we create an inbound delivery. The despatch advice (EANCOM D96A DESADV) is sent to our logistics partner who returns the same EDI message with the received quantities (goods receipt).
Using the inbound IDoc WMMBID02.WMMBXY I have successfully posted the goods receipt for the original PO. However, the message flow in the delivery is not updated. When we post the goods receipt (transaction MIGO) in dialog for the delivery we see the GR in the message flow.
I have used the following values with the segments of WMMBID02.WMMBXY (SAP release = 4.6c):
E1MBXYH:
Reference = <number of delivery>
Transaction code = 'MIGO'
E1MBXYI:
Movement type = '101'
Purchasing doc. = <number of PO>
Item = <Item no. in PO>
Movement ind. = 'B'
I am not sure about the correct movement indicator but failed when using a value different from 'B':
The movement indicator is derived from the transaction code.
Permitted values:
'' Goods movement w/o reference
'B' Goods movement for purchase order
'F' Goods movement for production order
'L' Goods movement for delivery note
'K' Goods movement for kanban requirement (WM - internal only)
'O' Subsequent adjustment of "material-provided" consumption
'W' Subsequent adjustment of proportion/product unit material
QUESTION: Does anybody know if and how inbound WMMBID02.WMMBXY can be used for both the goods receipt in the purchase order AND the message flow in the inbound delivery?
Regards
Uwe

Hello Everybody
My initial mapping of the WMMBXY IDoc proved to be correct.
For more details please refer to:
[Note 833603 - EDI: Goods receipt for stock transport order|https://service.sap.com/sap/support/notes/833603]
Regards
Uwe

How to use's mail's "perform mail action with message"

I can't for the life of me figure out how to use "perform mail action with message", I basically want to create a script that get's used on a rule from Mail, but nothing I try will work.
This is what I started with...
tell application "Mail"
perform mail action with message msgs for rule theRule
end
end
This doesn't compile i've seen an example of it being used like this...
using terms from application "Mail"
perform mail action with message msgs for rule theRule
end perform
end using
this also doesn't compile, so I'm not sure what it's wanting

This is one of those annoying things about programming - you have to arrange and spell things exactly right (this gets worse if you have fat fingers). You can look at the dictionary for Mail to see the specifics - in your example you are missing an "s" at the end of the word "message":
<pre title="this text can be pasted into the Script Editor" style="font-family: Monaco, 'Courier New', Courier, monospace; font-size: 10px; padding: 5px; width: 720px; color: #000000; background-color: #E0E0E0; overflow: auto">tell application "Mail"
perform mail action with messages msgs for rule theRule
end tell
</pre>

How to use logging in the actions classes extends standart actions?

Hello!
I have some action classes extends standart actions, for example Z_ExtMaintainBasketDispatcherAction extends MaintainBasketDispatcherAction. I tried to use logging functionality in my classes but there were no my lines in log and trace files.
For example I added followed lines in basketPerform() method of Z_ExtMaintainBasketDispatcherAction:
boolean isDebugEnabled = log.isDebugEnabled();
if(isDebugEnabled){
log.debug("++++++++++++++++ Test tracing in B2B_SNG. ++++++++++++++++");
but in there was no such line neither in log file nor in trace file.
How I can use logging functionality in my own classes? I need it for tracing and logging.
CRM 5.0
regards, Lev

Well, here is solution. I created a log formatter and log destination like this:
<log-formatters>
<log-formatter name="application_sap.com/crm~b2b" type="TraceFormatter" pattern="%d,%-3p %t %s %l %m"/>
</log-formatters>
<log-destinations>
<log-destination name="application_sap.com_crm.b2b" type="FileLog"
count="10" effective-severity="ALL" limit="10000000" pattern=".\log\applications\isa_ru.log">
<formatter-ref name="application_sap.com/crm~b2b"/>
</log-destination>
</log-destinations>
and new log controller like this:
<log-controller effective-severity="ALL" name="ru.sng.isa">
<associated-destinations>
<destination-ref name="application_sap.com_crm.b2b" association-type="LOG"/>
</associated-destinations>
</log-controller>
in file META-INF\log-configuration.xml
Thanks everybody for help!
Regards, Lev.

Logging a synchronous message using diagnostic header (WITHOUT LOGGING_SYNC

This [link|http://help.sap.com/saphelp_nw70/helpdata/EN/d6/49543b1e49bc1fe10000000a114084/frameset.htm] indicates that a synchronous message can be logged by using:
<SAP:Logging>1</SAP:Logging>
within the message header even if LOGGING_SYNC is deactivated at the server configuration.
I'm using HTTP client tool to submit a message and trying to figure out how to pass this tag. Any ideas?
Regards,
Shahab

If LOGGING_SYNC is deactivated in IE Configuration, then you cannot see th req. and resp. message in MONI.
Synch. messages are not persistence by default. To acheive it, we need to set the logging.
Thanks
Farooq.

General Error message using Kubota Actions?

I keep getting a "general error message" when attempting to use an action from my Kubota Dashboard. I'm using CS6 version 13.0.6 on a Mac computer. Anyone familiar with this issue? It works fine on my older laptop using CS6 version 13.0 and same Kubota Action palette.

Now my angles are out of sync and I can only see 2 at a time in the viewer window when there are supposed to be 3 but it switches between which 2 it wants to show. I have only a little experience with the multiclip settings. Is there something I need to do when re-opening a project with multiclip?

Cannot capture using log & transfer because warning message

Hi,
I recently switched cameras - from using a Canon Mini DV ZR 900 to a Panasonic SDR-H85. Of course when I plug in the new camera to the computer via USB, FCE4 doesn't recognize it because it's AVCHD. The media (video clips & stills) is transferred anyway via Adobe Bridge and stored in a designated folder on my hard drive. I then converted the video clips from .MOD to .MOV with MPEG Streamclip. The converted clips are saved in a different folder. I also did the easy set up changing the format to Apple Intermediate Codec and use to AVCHD 1440X1080i60. So then I start a new project and try to do log and transfer but when I try to add the folder containing the converted clips, I get a warning window that says that the folder contains unsupported media or has an invalid directory structure and to please choose a folder whose directory structure matches supported media. Can someone please tell me what is wrong or what I'm missing? I need to have a way to identify and organize these clips. Thanks!

Okay, as soon as I get my next check. Judging by your response and what I read on the Apple site, that will solve my problem? I sure hope so. One of the reasons I switched from recording to tape to hard drive is because an Apple Store techie assured me it would be much easier capturing using log and transfer rather than the long drawn out process I was using with tape (making subclips, etc.). So I was pretty upset to encounter this obstacle. I wasn't warned about the perils of AVCHD, and reading the process in your book it didn't seem like it should have been a problem anyway. So I'm still quite confused. But that's okay. I'll be happy enough just to have something working finally! Thanks

Proxy Message Flow

Hello everyone,
I am new to OSB and proxy services. I have some questions:
1. In proxy message flow, what is the difference between Pipeline node and routing node?
2. How to call more than one backend?
Any help is appreciated.
Thanks

In the message flow Pipeline Pair is added to do processing on the request before sending it to an external service or processing of the response which is received from the external service. This processing may include transformations, logging/reporting, validations and enrichment as well which can be done by calling other services using Service Callout.
Route is the node you use to send the request to an external service via a business service or even another Proxy Service within OSB which performs a set of functionality.
Pipeline pair and route both are optional, you can have a service with just pipeline pair and still call one or more backend services using Publish or Service Callout. You can also have a service without pipeline pair and just Route node and still do transformation in the Route node.
The choice is yours to design the service message flow in a logical way.
To answer your second question, there are multiple ways to invoke more than one backend service.
You can use Service Callout and Publish in the Pipelines to call any number of backend services. You can also call multiple backends by using Route action in Route node for one backend and having Service CAllouts in the Request actions section of Route action. You can also use Split Join if you want to call multiple backend services in parallel.
Again, it is upto you to design the message flow in a logical way.
For example, for a use case of creating an order in a backend system for a customer, Lets say you have to call a service A to get some customer data based on customer id and then send customer data to another backend service B to create order for that customer. Then ideally you should have a service callout in Request pipeline to Service A, as this is enrichment and then use a Route to call the backend service B to create the Order with enriched customer data.

Invoke secured service in splitjoin in an osb proxy message flow

Hello,
I create a new Split-Join (in the OSB workshop application). Then
I use an action "Invoke Service" to call a not secured business service. So far no problem. When I assign a security policy to my business service, the OSB does not accept. Here is the error message in the OSB workshop:
[Parallel, Scope, Invoke Service] Binding contains Security policy assertions, which is not supported.
Binding: "{http://testsplitjoin/v1}TestSplitJoinSOAPBinding"
Service: "BusinessService TestSplitJoin/BusinessServiceNotSecure"
TestSplitJoin SplitJoinTest.flow line 43 1316955334516 3695
How can I call a secured business service in a splitJoin?
Thanks

Are you sure that your for-each definition is correct? Does the flow within the for-each get executed multiple times?
You can check this by logging the variable to which you assign the message in the for-each. Don't forget to put the log level to Error, so you're sure that it's logged.
Let's say you get a list of persons like the following xml in a variable personList
<Persons>
<Person>Glenn</Person>
<Person>Prasanth</Person>
</Persons>
Your for-each definition should be the following.
For each variable: person
XPath: +./Person+
In Variable: personList
You don't mention the Persons element in the XPath expression since it is the root element of the XML. The root element is represented by . (dot).
In the for-each, the variable person can be used like any other variable.

ON PREM Outbound emails showing in dummy non-configured office 365 account message flow trace

Dear Community,
We have an on-prem exchange 2013 server and an office 365 account which is completly standalone.
Whilst the office 365 account is standalone, it does feature the email address we use for on-prem (Ie. the domain name in office 365 account is not active for any office 365 services however has passed ownership verification thus it's just sitting there)
We DON'T use EOP nor do we have any connector rules on our on-prem system that go to office 365 however when I randomly went into the 'Message Flow Trace' section in our office 365 account, there is recorded outbound mail which was sent from our On-prem
server.
The ONLY mail that was recorded in the message Trace in Office 365 was emails we had sent from On-prem to other office 365 accounts (For example btconnect.com, and some of our clients whom also use office 365) .
How is office 365 picking up mail we've sent from our On-Prem server? Is there integration out of the box in exchange 2013 which auto interfaces with office 365? What on earth has happened here?
I'm really confused.
-------- For troubleshooting purposes...
Headers in the email which arrived in my personal office 365 account from the ON-PREM SERVER
Received: from AMSPR05MB065.eurprd05.prod.outlook.com (10.242.89.142) by
DBXPR05MB079.eurprd05.prod.outlook.com (10.242.138.22) with Microsoft SMTP
Server (TLS) id 15.1.93.16 via Mailbox Transport; Thu, 5 Mar 2015 16:16:31
+0000
Received: from DBXPR05CA0014.eurprd05.prod.outlook.com (10.255.178.14) by
AMSPR05MB065.eurprd05.prod.outlook.com (10.242.89.142) with Microsoft SMTP
Server (TLS) id 15.1.99.14; Thu, 5 Mar 2015 16:16:30 +0000
Received: from DB3FFO11FD028.protection.gbl (2a01:111:f400:7e04::145) by
DBXPR05CA0014.outlook.office365.com (2a01:111:e400:9434::14) with Microsoft
SMTP Server (TLS) id 15.1.106.15 via Frontend Transport; Thu, 5 Mar 2015
16:16:29 +0000
Received: from emea01-am1-obe.outbound.protection.outlook.com (157.56.112.128)
by DB3FFO11FD028.mail.protection.outlook.com (10.47.217.59) with Microsoft
SMTP Server (TLS) id 15.1.99.6 via Frontend Transport; Thu, 5 Mar 2015
16:16:28 +0000
Received: from DB4PR04CA0010.eurprd04.prod.outlook.com (25.160.41.20) by
DB3PR04MB236.eurprd04.prod.outlook.com (10.242.130.24) with Microsoft SMTP
Server (TLS) id 15.1.99.14; Thu, 5 Mar 2015 16:16:26 +0000
Received: from DB3FFO11FD040.protection.gbl (2a01:111:f400:7e04::184) by
DB4PR04CA0010.outlook.office365.com (2a01:111:e400:9852::20) with Microsoft
SMTP Server (TLS) id 15.1.106.15 via Frontend Transport; Thu, 5 Mar 2015
16:16:26 +0000
Received: from mail.localdomainhere (<IP OF OUR ON-PREM SERVER GOES HERE>) by
DB3FFO11FD040.mail.protection.outlook.com (10.47.217.71) with Microsoft SMTP
Server (TLS) id 15.1.99.6 via Frontend Transport; Thu, 5 Mar 2015 16:16:25
+0000
Received: from INT-EX-01.localdomainhere (192.168.142.20) by
INT-EX-01.localdomainhere (192.168.142.20) with Microsoft SMTP Server (TLS) id
15.0.913.22; Thu, 5 Mar 2015 16:15:55 +0000
Received: from INT-EX-01.localdomainhere ([fe80::aca4:88cf:3eaf:57dc]) by
INT-EX-01.localdomainhere ([fe80::aca4:88cf:3eaf:57dc%12]) with mapi id
15.00.0913.011; Thu, 5 Mar 2015 16:15:55 +0000
From: Jake Ives <[email protected]>
To: Jake Ives <[email protected]>
Subject: Test01
Thread-Topic: Test01
Thread-Index: AdBXX6dyI5u99OGoSKmXroKKyMA3Tg==
Date: Thu, 5 Mar 2015 16:15:54 +0000
Message-ID: <[email protected]>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.142.73]
Content-Type: multipart/related;
boundary="_004_081f834d85b7436193fa887613b9dac7INTEX01localdomainhere_";
type="multipart/alternative"
MIME-Version: 1.0
Return-Path:
[email protected]
X-EOPAttributedMessage: 1
Received-SPF: Pass (protection.outlook.com: domain of domain.com
designates <IP OF ONPREM SERVER HERE> as permitted sender)
receiver=protection.outlook.com; client-ip=<IP OF OUR ON-PREM SERVER GOES HERE;
helo=mail.domain.co.uk;
Authentication-Results: spf=pass (sender IP is <IP OF OUR ON-PREM SERVER GOES HERE>)
[email protected]; ives.gb.net; dkim=none (message not
signed) header.d=none;ives.gb.net; dkim=none (message not signed)
header.d=none;ives.gb.net; dmarc=none action=none header.from=domain.com;
X-Forefront-Antispam-Report-Untrusted: CIP:<IP OF ON PREM SERVER HERE>;CTRY:GB;IPV:NLI;EFV:NLI;BMV:0;SFV:NSPM;SFS:(10019020)(438002)(189002)(199003)(71364002)(87936001)(2656002)(98436002)(92726002)(102836002)(108616004)(19625215002)(19618635001)(512954002)(92566002)(229853001)(107886001)(66926002)(18206015028)(84326002)(16796002)(19300405004)(450100001)(19580395003)(2900100001)(77156002)(15974865002)(62966003)(5250100002)(5310100001)(99936001)(15395725005)(16236675004)(110136001)(17760045003)(67866002)(86362001)(19617315012)(19627595001)(15975445007)(19580405001)(54356999)(22756005)(50986999)(6806004)(46102003)(74482002)(106466001)(33646002)(7099025)(24736002)(15669805003);DIR:OUT;SFP:1102;SCL:1;SRVR:DB3PR04MB236;H:mail.domain.co.uk;FPR:;SPF:Pass;MLV:ovrnspm;MX:1;A:1;PTR:mail.domain.co.uk;LANG:en;
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DB3PR04MB236;UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AMSPR05MB065;
X-Microsoft-Antispam-PRVS: <[email protected]outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:(601004)(5001007)(5005006);SRVR:DB3PR04MB236;BCL:0;PCL:0;RULEID:;SRVR:DB3PR04MB236;BCL:0;PCL:0;RULEID:(601004);SRVR:AMSPR05MB065;BCL:0;PCL:0;RULEID:;SRVR:AMSPR05MB065;
X-Forefront-PRVS: 05066DEDBB
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB3PR04MB236
X-MS-Exchange-Organization-MessageDirectionality: Incoming
Received-SPF: Fail (protection.outlook.com: domain of domain.com does not
designate 157.56.112.128 as permitted sender)
receiver=protection.outlook.com; client-ip=157.56.112.128;
helo=emea01-am1-obe.outbound.protection.outlook.com;
Authentication-Results: spf=fail (sender IP is 157.56.112.128)
[email protected];
X-Forefront-Antispam-Report: CIP:157.56.112.128;CTRY:US;IPV:NLI;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:(339900001)(489007)(189002)(71364002)(199003)(102836002)(92726002)(15975445007)(92566002)(17760045003)(62966003)(106466001)(15395725005)(16236675004)(77156002)(110136001)(107886001)(450100001)(5310100001)(229853001)(22756005)(98436002)(2900100001)(5250100002)(19625215002)(66926002)(99936001)(33646002)(15974865002)(19617315012)(19627595001)(67866002)(54356999)(108616004)(19300405004)(19618635001)(87836001)(2656002)(18206015028)(85426001)(512954002)(86362001)(6806004)(46102003)(74482002)(84326002)(19580395003)(50986999)(19580405001)(7099025)(24736002)(15669805003);DIR:INB;SFP:;SCL:1;SRVR:AMSPR05MB065;H:emea01-am1-obe.outbound.protection.outlook.com;FPR:;SPF:Fail;MLV:ovrnspm;MX:1;A:1;PTR:mail-am1on0128.outbound.protection.outlook.com;LANG:en;
X-MS-Exchange-Transport-CrossTenantHeadersStripped: DB3FFO11FD028.protection.gbl
X-MS-Exchange-Transport-CrossTenantHeadersPromoted: DB3FFO11FD028.protection.gbl
X-MS-Exchange-Organization-Network-Message-Id: 927151e3-02c4-4c46-5539-08d22576df82
X-MS-Exchange-Organization-AVStamp-Service: 1.0
X-MS-Exchange-Organization-SCL: 1
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 05 Mar 2015 16:16:28.9728
(UTC)
X-MS-Exchange-CrossTenant-Id: cd52bfe2-da2e-446d-b8f1-e78db861d489
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bfa61dad-1543-4f3b-8075-03498e9f4fcb;Ip=[IP OF ON PREM SERVER HERE]
X-MS-Exchange-CrossTenant-FromEntityHeader: Internet
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMSPR05MB065
X-MS-Exchange-Organization-AuthSource: DB3FFO11FD028.protection.gbl
X-MS-Exchange-Organization-AuthAs: Anonymous
X-MS-Exchange-Transport-EndToEndLatency: 00:00:03.5565465

MX records are not set to office 365, the MX is pointing directly to the on-prem exchange server.
The problem is; Office 365 Mail Delivery Trace is displaying mail we've sent via our On-Prem server - We are having trouble understanding why this is happening.
To clarify, the message tracer in Office 365 is displaying outbound mail (Which for example, a user has sent out from their outlook) BUT only outbound mail which is being sent to other office 365 users.
We do not have mail on office 365, only on-premise hence the reason why we are flabbergasted to why the mail we are sending out would be displaying on the office 365 message tracer.
To further clarify, we are only seeing addresses in the office 365 message trace which belong to recipients whom use office 365 for their mail.
Hope this makes sense.
getting messy O365 users to another O365 you mean?
You mentioned if they send email using their MS Outlook Client.
I'd suggest you to send another email to the same recipient but using OWA
There may have been an office 365 connector in Outlook.
Where Technology Meets Talent

Use logging action in message flow

Similar Messages

Maybe you are looking for