Loop in message flow found

Hi all
I created a idoc to abap proxy for the xi adapter i used http destination with my destination defined in sm59.
In sxbm_moni i get the error:
LOOP_IN_MESSAGE_ROUTING
Loop in message flow found: system is.00.metsapxd, pipeline CENTRAL with inbound adapter XI already processed
Anyone know how to fix the error?
Thx

Hi,
I think your end business system i.e. where proxy exists -- this application system is configured as "integration engine/HUB". Try to keep it as (SXMB_ADM -> Integration engine configuration) type of business system as "applicaiton system" instead of integration engine/server.
Regards,
Rao.Mallikarjuna

Similar Messages

Xslt in message flow

hello,
i have an XSLT document and i want to use it to make a transformation in the response message flow of my proxy service.
i call a webservice through business service but i dont know which action,in the "response actions", corresponds to making an XSL transformation.
I tried "replace" without success, the others actions seem not to be for transformation.
in the xquery expression editor, i put my XSLT resource to execute.
in "2. bind input", i dont know exactly what to put, there isn't any explication for "2. bind input" in the edocs.
and for "3. bind variables", i have nothing (no variables have been found)
could someone indicate me how to configure and use the result of my xslt in a message flow ?
thank you very much.

We built a custom service and invoked it asynchronously (non-blocking) using the Publish Action (with QoS as BestEffort) in the different places wherever we needed the audit functionality.
And this service would do its work on the background as a part of a separate thread, thereby not impacting the actual service that was implementing the business logic.
This is not optimal because there is still some time consumed for the publish action (though it is less) in the actual service with the business logic. But atleast this did allow us to overcome the limitation of the handlers to some extent.
I generally do not prefer to use java callouts as the prerequisite is that the methods exposed need to be static, which might create some contention when many threads try to invoke the same java callout methods at the same time.
Thanks,
Patrick

Replacing default namespace in OSB message flow

I'm in the process of setting up a simple OSB proxy and could use some help figuring out how to change a default namespace in the response from the business service.
The proxy and business service use different namespaces which we'll call "http://foo.com/namespace/proxy" and "http://foo.com/namespace/business". In my routing request message flow, the contents of $body look like this and I'm able to use a Rename action with XQuery expression "./sof:*" to change "http://foo.com/namespace/proxy" to "http://foo.com/namespace/business":
<sof:Execute xmlns:sof="http://foo.com/namespace/proxy">
<sof:adminName>MyAdaptor</sof:adminName>
<sof:request>
[escaped payload omitted]
</sof:request>
</sof:Execute>
This works fine, but in the response message flow, I need to revert the namespace and am having difficulty because the response uses a default namespace instead of using a prefix:
<ExecuteResponse xmlns="http://foo.com/namespace/business">
<ExecuteResult>
[escaped payload omitted]
</ExecuteResult>
</ExecuteResponse>
If I define a prefix P2L in the expression editor to correspond to "http://foo.com/namespace/business", I'm able to reference the ExecuteResponse element as "./P2L:ExecuteResponse", but then I get stuck.
If I try use a Rename action to change the namespace for "./P2L:*", only the ExecuteResponse element is renamed to <sof:ExecutResponse xmlns:sof="http://foo.com/namespace/proxy">. Upstream in the calling application, there's an XML stream reader exception because (I assume) ExecuteResult is not found and parsed.
I also tried using a Replace action against "./P2L:ExecuteResponse/@xmlns" to replace its contents with "http://foo.com/namespace/proxy". I also tried "./P2L:ExecuteResponse/@P2L:xmlns". Neither worked.
Can anyone tell me what I'm doing wrong, or suggest a different approach? Assume that changing the calling application or business service is not an option.
Thanks!

>
If I define a prefix P2L in the expression editor to correspond to "http://foo.com/namespace/business", I'm able to reference the ExecuteResponse element as "./P2L:ExecuteResponse", but then I get stuck.
If I try use a Rename action to change the namespace for "./P2L:*", only the ExecuteResponse element is renamed to <sof:ExecutResponse xmlns:sof="http://foo.com/namespace/proxy">. Upstream in the calling application, there's an XML stream reader exception because (I assume) ExecuteResult is not found and parsed.
>
You pattern "./P2L:\*" matches just one element so it's ok that the payload's namespace wasn't touched. If you want to rename namespace for all elements try "//P2L:*". However, I'm not sure whether this is what you want. Try do describe what you do, what you want and what you get instead.
>
I also tried using a Replace action against "./P2L:ExecuteResponse/@xmlns" to replace its contents with "http://foo.com/namespace/proxy". I also tried "./P2L:ExecuteResponse/@P2L:xmlns". Neither worked.
>
I think it's not a good approach to replace content of xmlns as this attribute is not a common xml attribute.

Where to find detail message flow in scenario of AQ to DB adapter?

I have installed hub, aq and DB adapter. The repository, adapters seem to be run fine. I put some messages in AQ and found out that there were no messages appeared in DB. The messages could be found in AQ_OUTBOUND_QUEUE. Sine there is no error message in adapter log files(trace is turned on), I am not sure it's the hub problem or adapter problems. Where should i check the message flow so to decide the problem?
Any constructive advice is welcome.

Hi Johnson,
Have you set the queue to the event in the deploy tab of AQ application in iStudio? If not then please set your OUTBOUND_QUEUE to the corresponding event and then do push metadata after starting the adapter. You can have a look at "Appendix A -> Deployment -> Setting Queues" of Interconnect User guide for this.
regards,
Sandeep

Message flow from XI To Receiver

Hi ,
There are several IDOC to JDBC scenarios running in our XI PRD server but now all the IDOCs are reaching XI,which is visible in IDX5 or SXMB_MONI but nothing has reached the Receiver as visible from Message monitoring.
In SXMB_MONI , i can see the errors CLIENT RECEIVE FAILED.pls figure out the problem and tell me how to proceed wid.
Thanx,
Laawanya

hi
as you are doing idoc-jdbc scenario check whether the reciver MT you maintained is of JDBC-XML structure
check Document Formats for Receiver JDBC adapter
check the blog for the message flow in xi:
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
/people/siva.maranani/blog/2005/09/16/xi-how-to-on-jdbc-receiver-response
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm
Note:please reward points if solution found helpfull
Regards
Chandrakanth.k

XI Message flow

I am trying to integrate a r/3 system with XI, can someone point me to possible data flow diagrams.
What can be a possible scenario here...?
Can someone also point me to the message flow within IR and ID for the above scenario..
Regards
Ravi

Hi,
Pipeline steps for XI Message flow steps , This might help you to understand
Pipeline :
When a source message reaches the Integration server
the messages under goes this
a) Receiver Determination:
This steps determines the system that participates in the exchange of the message.
b) Interface Detremination:
For each receiver determine which interface will should receieve the message.
c) Message Split:
If more than one receievers are found, XI will instantiate new message for each receiver.
d) Message Mapping:
Mapping to transform the source message to destination message format.
e) Technical Routing:
Bind a specific destination and protocol to the message.
f) Call outbound Adapter:
Send the transformed message to the adapter or a proxy.
Regards
Agasthuri Doss

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.

Regarding message flow in sap xi

HI
i want to the flow of message from outbound system to inbound system completly.
ie i want to know ---which components like message interfaces,rd,id,sa,ra,.............such types.i want to know the complete flow and after which step which is to be taken place.
also i want to know the steps involved in pipeline and when it will be called in the above sequence.
thanks in advance.

Hi
The steps involved in XI message flow are below.
1.Receiver Identification - Determines which system to participate in an exchange with the incoming message.
2.Interface Determination - For each receiver system determines which interfaces should receive a message.
3.Message Split - If multiple receivers are found, XI will instatiate a new message for each receiver.
4.Message Mapping - Call the mapping program to transfer the message structure to the receiver format.
5.Technical routing - Bind a specific destination and protocol to the message.
6.Call adapter. Send the transformed message to the adapter or proxy.

Message Flow Control

Hello,
          as I read, WLS provides the possibility to slow down message producers when certain paging thresholds are exceeded. I'm not quite sure, if the slow down of a producer is tied to it's session lifecycle, i.e. if the producer is slowed down only within its current session - or are producers, which are created from a new session, also slowed down right from the start.
          It would be great if someone could answer that. Unfortunately I have found nothing about that in the documentation.
          Regards,
          Dirk

Hello Tom.
          First of all, thank you for your quick response. This forum is really working!
          I searched for this topic in the documentation, but didn't find anything appropriate explaining the in-depth details of the JMS flow control mechanism. Therefore, I wrote a simple test case (implementation and server configuration is attached at the end of this message) to check the flow control handling for certain conditions. Since there is no API to access the flow control properties of a message producer, I measured the JMS throughput within the test case and tried to derive some conclusions.
          Regarding the server configuration:
          - I configured one JMS Server (Test_JMSServer) with one Queue (TestQueue). I enabled the message paging at server level, starting at 1000 messages (i.e. message threshold high). The lower message threshold was set to 100 messages. As a paging store a file store (TestPagingStore) was used.
          - Message thresholds at destination level was disabled.
          - I further configured a connection factory (TestConnectionFactory) for which I enabled the flow control with a max. throughput of 50 msg/sec and a min. throughput of 1 msg/sec. The flow interval was set to 60 seconds, the number of steps was set to 6.
          Regarding the test case:
          There are 3 scenarios within the test case. Within each scenario
          - first all messages are consumed from the queue,
          - then 1000 messages are send to the queue in a row, thereby measuring the throughput,
          - finally again 1000 messages are send to the queue in a row, thereby measuring the throughput.
          The scenarios differ in how the bulk-send operation is performed.
          - The first scenario (test_noReuse) creates a new connection for each message to be send.
          - The second scenario (test_sessionReuse) creates a new session at the start and reuses that session for sending the messages. A new sender is created of each message.
          - The third scenario (test_senderReuse) creates a new sender at the start and reuses that sender for sending the messages.
          Here are the results of the test:
          ==[test_noReuse]=======================
          Cleaned up <2000> messages.
          Throughput (messages/second): 51 [startMillis=1161249409788;endMillis=1161249429210;messagesSend=1000]
          Throughput (messages/second): 62 [startMillis=1161249429210;endMillis=1161249445304;messagesSend=1000]
          ==[test_sessionReuse]=======================
          Cleaned up <2000> messages.
          Throughput (messages/second): 231 [startMillis=1161249452773;endMillis=1161249457101;messagesSend=1000]
          Throughput (messages/second): 245 [startMillis=1161249457101;endMillis=1161249461179;messagesSend=1000]
          ==[test_senderReuse]=======================
          Cleaned up <2000> messages.
          Throughput (messages/second): 790 [startMillis=1161249467351;endMillis=1161249468616;messagesSend=1000]
          Throughput (messages/second): 1 [startMillis=1161249468616;endMillis=1161249999226;messagesSend=1000]
          To me it seems, that reusing a session has no effect on the message flow control if a new sender is created for sending a message. The only scenario where a throttling occurs (at least it seems to be that way) is the last scenario, where the sender is reused for all messages.
          So my conclusion is, that message control flow is superfluous to configure, as long as
          - you don't have a small amount of (batch) message producers, each of which reusing a single sender for each message,
          - or you have some cache of senders (or a single sender) in your application and reuse the cached senders for sending messages.
          The latter is, of course, strongly discouraged, since neither JMS sessions, nor senders are thread-safe. So you need to implement some thread-safe cache and also have to deal with re-creating stalled JMS resources within that cache -- a really non-trivial implementation. Further, if many different threads produce messages, the flow control has no (or at least few) effect on the message load in the server.
          I just ask myself, what the flow control was designed for, since the cases where it really applies are rather rare, IMHO. Or have I made some error in the test or in the server configuration?
          Best regards,
          Dirk
          The test class:
          <pre>
          import java.util.Hashtable;
          import javax.jms.BytesMessage;
          import javax.jms.JMSException;
          import javax.jms.Message;
          import javax.jms.Queue;
          import javax.jms.QueueConnection;
          import javax.jms.QueueConnectionFactory;
          import javax.jms.QueueReceiver;
          import javax.jms.QueueSender;
          import javax.jms.QueueSession;
          import javax.jms.Session;
          import javax.naming.InitialContext;
          import junit.framework.TestCase;
          public class JMSFlowControlTest extends TestCase {
          private int messagesThresholdHigh = 1000;
          private QueueConnectionFactory conFactory;
          private Queue queue = null;
          protected void setUp() throws Exception {
          super.setUp();
          InitialContext ctx = null;
          Hashtable ctxEnv = null;
          ctxEnv = new Hashtable();
          ctxEnv.put(
          InitialContext.INITIAL_CONTEXT_FACTORY,
          "weblogic.jndi.WLInitialContextFactory");
          ctxEnv.put(
          InitialContext.PROVIDER_URL,
          "t3://localhost:7001");
          ctx = new InitialContext(ctxEnv);
          this.queue = (Queue) ctx.lookup("jms/queue/TestQueue");
          this.conFactory = (QueueConnectionFactory)
          ctx.lookup("jms/factory/TestConnectionFactory");
          public void test_noReuse() throws Exception {
          System.out.println();
          System.out.println("==[" + this.getName() + "]=======================");
          this.cleanupQueue();
          System.out.println(
          this.bulkSendMessage(
          this.messagesThresholdHigh,
          1024));
          System.out.println(
          this.bulkSendMessage(
          this.messagesThresholdHigh,
          1024));
          public void test_sessionReuse() throws Exception {
          QueueConnection con = null;
          QueueSession session = null;
          System.out.println();
          System.out.println("==[" + this.getName() + "]=======================");
          try {
          con = this.conFactory.createQueueConnection();
          session =
          con.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE);
          this.cleanupQueue();
          System.out.println(
          this.bulkSendMessage(
          session,
          this.messagesThresholdHigh,
          1024));
          System.out.println(
          this.bulkSendMessage(
          session,
          this.messagesThresholdHigh,
          1024));
          } finally {
          if (con != null) {
          try {
          con.close();
          } catch (JMSException e) {}
          public void test_senderReuse() throws Exception {
          QueueConnection con = null;
          QueueSession session = null;
          QueueSender sender = null;
          System.out.println();
          System.out.println("==[" + this.getName() + "]=======================");
          try {
          con = this.conFactory.createQueueConnection();
          session =
          con.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE);
          sender = session.createSender(this.queue);
          this.cleanupQueue();
          System.out.println(
          this.bulkSendMessage(
          session,
          sender,
          this.messagesThresholdHigh,
          1024));
          System.out.println(
          this.bulkSendMessage(
          session,
          sender,
          this.messagesThresholdHigh,
          1024));
          } finally {
          if (con != null) {
          try {
          con.close();
          } catch (JMSException e) {}
          private Throughput
          bulkSendMessage(
          int messagesToSend,
          int messageSizeBytes)
          throws Exception {
          int messagesSend = 0;
          long startMillis = 0L;
          long endMillis = 0L;
          QueueConnection con = null;
          QueueSession session = null;
          QueueSender sender = null;
          startMillis = System.currentTimeMillis();
          for (int i = 0; i < messagesToSend; i++) {
          try {
          con = this.conFactory.createQueueConnection();
          session =
          con.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE);
          sender = session.createSender(this.queue);
          sender.send(this.createMessage(session, messageSizeBytes));
          messagesSend++;
          } finally {
          if (con != null) {
          try {
          con.close();
          } catch (JMSException e) {}
          endMillis = System.currentTimeMillis();
          return new Throughput(startMillis, endMillis, messagesSend);
          private Throughput
          bulkSendMessage(
          QueueSession session,
          int messagesToSend,
          int messageSizeBytes)
          throws Exception {
          int messagesSend = 0;
          long startMillis = 0L;
          long endMillis = 0L;
          QueueSender sender = null;
          startMillis = System.currentTimeMillis();
          for (int i = 0; i < messagesToSend; i++) {
          sender = session.createSender(this.queue);
          sender.send(this.createMessage(session, messageSizeBytes));
          messagesSend++;
          endMillis = System.currentTimeMillis();
          return new Throughput(startMillis, endMillis, messagesSend);
          private Throughput
          bulkSendMessage(
          QueueSession session,
          QueueSender sender,
          int messagesToSend,
          int messageSizeBytes)
          throws Exception {
          int messagesSend = 0;
          long startMillis = 0L;
          long endMillis = 0L;
          startMillis = System.currentTimeMillis();
          for (int i = 0; i < messagesToSend; i++) {
          sender.send(this.createMessage(session, messageSizeBytes));
          messagesSend++;
          endMillis = System.currentTimeMillis();
          return new Throughput(startMillis, endMillis, messagesSend);
          private Message
          createMessage(
          Session session,
          int messageSizeBytes)
          throws Exception {
          BytesMessage message = null;
          message = session.createBytesMessage();
          message.writeBytes(new byte[messageSizeBytes]);
          return message;
          private void cleanupQueue() throws Exception {
          QueueConnection con = null;
          QueueSession session = null;
          QueueReceiver receiver = null;
          Message message = null;
          int messageCount = 0;
          try {
          con = this.conFactory.createQueueConnection();
          session =
          con.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE);
          receiver = session.createReceiver(this.queue);
          con.start();
          do {
          message = null;
          message = receiver.receiveNoWait();
          if (message != null) {
          messageCount++;
          } while (message != null);
          } finally {
          if (con != null) {
          try {
          con.close();
          } catch (JMSException e) {}
          System.out.println("Cleaned up <" + messageCount + "> messages.");
          private static final class Throughput {
          private final long startMillis;
          private final long endMillis;
          private final int messagesSend;
          public Throughput(long startMillis, long endMillis, int messagesSend) {
          this.startMillis = startMillis;
          this.endMillis = endMillis;
          this.messagesSend = messagesSend;
          public int value() {
          long timeElapsedMillis = 0L;
          int timeElapsedSeconds = 0;
          int value = 0;
          timeElapsedMillis = this.endMillis - this.startMillis;
          if (timeElapsedMillis == 0) {
          timeElapsedMillis = 1;
          value = (int) ((this.messagesSend * 1000L) / timeElapsedMillis);
          return value;
          public String toString() {
          StringBuffer buffer = new StringBuffer();
          buffer
          .append("Throughput (messages/second): ").append(this.value())
          .append(" [startMillis=").append(this.startMillis)
          .append(";endMillis=").append(this.endMillis)
          .append(";messagesSend=").append(this.messagesSend)
          .append("]");
          return buffer.toString();
          </pre>
          The (partial) server configuration:
          <pre>
          <JMSConnectionFactory
          DefaultDeliveryMode="Non-Persistent"
          FlowMaximum="50"
          FlowMinimum="1"
          FlowSteps="6"
          JNDIName="jms/factory/TestConnectionFactory"
          Name="TestConnection Factory"
          Targets="SchufaDev"
          XAConnectionFactoryEnabled="true"/>
          <JMSFileStore Directory="filestore/paging" Name="TestPagingStore"/>
          <JMSServer
          MessagesPagingEnabled="true"
          MessagesThresholdHigh="1000"
          MessagesThresholdLow="100"
          Name="Test_JMSServer"
          PagingStore="TestPagingStore"
          Targets="SchufaDev">
          <JMSQueue
          CreationTime="1151395702234"
          JNDIName="jms/queue/TestQueue"
          JNDINameReplicated="false"
          Name="TestQueue"
          RedeliveryDelayOverride="5000"
          RedeliveryLimit="5"
          StoreEnabled="false"/>
          </JMSServer>
          </pre>

Adapter message flow

Hi,
Any one explain the message flow in XI
Thanks in advance

Hi Deepan,
Message flow is the pipeline steps in XI.Pipeline is nothing but the steps performed in integration engine at runtime. After the message is converted to xml in adapter engine it goes to integration engine for processing. In IE these pipeline steps process the message further. These include: receiver determination, interface determination, message split, and mapping, routing, call adapter.
When a source message reaches the Integration server
the messages under goes this
a) Receiver Determination:
This steps determines the systems that sends and receive the messages.
b) Interface Determination:
For each receiver determination there should be an interface to receive the message.
c) Message Split:
If more than one receiver are found, XI will instantiate new message for each receiver.
d) Message Mapping:
Mapping to transform the source message to destination message format.
e) Technical Routing:
Bind a specific destination and protocol to the message.
f) Call outbound Adapter:
Send the transformed message to the adapter or a proxy.
http://help.sap.com/saphelp_nw04/helpdata/en/41/b714f85ffc11d5b3ea0050da403d6a/framese
More Info in the Blog <a href="/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi Message Flow in XI</a> By Siva Maranani
Regards
San

BDOC message flow and its architecture

Hi Expert,
It can be a simple question but i have a doubt regarding the flow of messages using SAP CRM middleware.
The scenario is like:
1. Message flows from ECC to CRM through a BDoc. (It can be opposite way also)
2. The BDoc fails in CRM due to some data issue.
3. A BDoc message id is generated.
4.Now the data is corrected in ECC and initial load was triggered.
5.The messages are flowing correctly.
So my doubt is:
1.What will happen to the old BDoc?
2. Do the initial or delta load processes the messages with new BDoc ID or through the old BDoc ID?
3. If the messages are processed through new BDoc id, can the old BDocs be deleted?
Please help me understand this concepts of BDocs and please provide me to some study material to get more undertsanding of the BDOC message flow architecture.
thanks,
Vicky

Hello Vicky,
i think I understand exactly what your confusion is all about.
1.What will happen to the old BDoc?
The old Bdoc will remain in error state until it is archived or set to processed state.
2. Do the initial or delta load processes the messages with new BDoc ID or through the old BDoc ID?
It will be a separate BDoc with a new BDocId. If you get an Error in SMW01 this is beyond the queueing, so later Messages will not get queued behind your faulty bdoc. They will also not "update" your BDoc in any way. Later BDocs will Bypass a bdoc in error state and update your object in CRM if the error in data has been solved in ERP before. If the data error is not corrected, you will get a second failed bdoc.
3. If the messages are processed through new BDoc id, can the old BDocs be deleted?
Best practise for the Bdoc with error would be to set it to processed state. That way there is no way that Bdoc can be processed afterwards. The BDoc will then be archived with the next run.
Best regards,
Lutz

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

Repeating error message: "acl found but not expected" during permissions repair

repeating error message: "acl found but not expected" during permissions repair
My iMac is running slow. Processor running all the time. I was told to do permissions repair, so I did that. I get 100's and 100's of "ACL found but not expected" while doing a permissions repair in 'utilities'. It says 1 minute to complete but runs for a half hour. When it finally completes, I can restart the permissions repair again and it starts all over with same endless messages. Even though its says 'repaired', these ACL issues keep coming.
SEE BELOW ... What's wrong? And How do I fix it?
Kind thanks for your suggestions,
Vic
Hardware Overview: Model Name: iMac
Model Identifier: iMac8,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.8 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 6 MB
Memory: 4 GB
Bus Speed: 1.07 GHz
Boot ROM Version: IM81.00C1.B00
SMC Version (system): 1.30f1
Serial Number (system): W884000HZE4 Hardware UUID: BF3B8113-E0F0-54DB-9062-B73A0E4DB0F2
Repairing permissions for “Vic's iMac”ACL found but not expected on “Library/Printers”Repaired “Library/Printers”ACL found but not expected on “Library/Printers/Icons”Repaired “Library/Printers/Icons”Group differs on “Library/Printers/InstalledPrinters.plist”; should be 80; group is 0.Permissions differ on “Library/Printers/InstalledPrinters.plist”; should be -rw-rw-rw- ; they are -rw-r--r-- .Repaired “Library/Printers/InstalledPrinters.plist”ACL found but not expected on “private/etc/apache2/extra/httpd-ssl.conf”Repaired “private/etc/apache2/extra/httpd-ssl.conf”ACL found but not expected on “Library/Application Support/Apple/Remote Desktop”Repaired “Library/Application Support/Apple/Remote Desktop”ACL found but not expected on “Library/Application Support/Apple/Remote Desktop/Notify”Repaired “Library/Application Support/Apple/Remote Desktop/Notify”ACL found but not expected on “Library/Preferences/Xsan”Repaired “Library/Preferences/Xsan”ACL found but not expected on “Library/Printers/Canon”Repaired “Library/Printers/Canon”ACL found but not expected on “Library/Printers/Canon/IJScanner”Repaired “Library/Printers/Canon/IJScanner”ACL found but not expected on “Library/Printers/Canon/IJScanner/Frameworks”Repaired “Library/Printers/Canon/IJScanner/Frameworks”ACL found but not expected on “Library/Printers/Canon/IJScanner/Plugins”Repaired “Library/Printers/Canon/IJScanner/Plugins”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources”Repaired “Library/Printers/Canon/IJScanner/Resources”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/CIJIcons”Repaired “Library/Printers/Canon/IJScanner/Resources/CIJIcons”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/CIJIcons/CIJCanoScan5600F.icns”Repa ired “Library/Printers/Canon/IJScanner/Resources/CIJIcons/CIJCanoScan5600F.icns”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/CIJIcons/CIJCanoScan9000F.icns”Repa ired “Library/Printers/Canon/IJScanner/Resources/CIJIcons/CIJCanoScan9000F.icns”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/CIJIcons/CIJCanoScanLiDE100.icns”Re paired “Library/Printers/Canon/IJScanner/Resources/CIJIcons/CIJCanoScanLiDE100.icns”AC L found but not expected on “Library/Printers/Canon/IJScanner/Resources/CIJIcons/CIJCanoScanLiDE110.icns”Re paired “Library/Printers/Canon/IJScanner/Resources/CIJIcons/CIJCanoScanLiDE110.icns”AC L found but not expected on “Library/Printers/Canon/IJScanner/Resources/CIJIcons/CIJCanoScanLiDE200.icns”Re paired “Library/Printers/Canon/IJScanner/Resources/CIJIcons/CIJCanoScanLiDE200.icns”AC L found but not expected on “Library/Printers/Canon/IJScanner/Resources/CIJIcons/CIJCanoScanLiDE210.icns”Re paired “Library/Printers/Canon/IJScanner/Resources/CIJIcons/CIJCanoScanLiDE210.icns”AC L found but not expected on “Library/Printers/Canon/IJScanner/Resources/CIJIcons/CIJCanoScanLiDE700F.icns”R epaired “Library/Printers/Canon/IJScanner/Resources/CIJIcons/CIJCanoScanLiDE700F.icns”A CL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters”Repaired “Library/Printers/Canon/IJScanner/Resources/Parameters”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNCICA”Repaired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNCICA”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNCICA/ICACPG_07.DAT”Rep aired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNCICA/ICACPG_07.DAT”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNCICA/ICACPG_08.DAT”Rep aired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNCICA/ICACPG_08.DAT”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNCICA/ICADAT.DAT”Repair ed “Library/Printers/Canon/IJScanner/Resources/Parameters/CNCICA/ICADAT.DAT”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ2413”Repaired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ2413”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ2413/CNQ2413N.DAT”Rep aired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ2413/CNQ2413N.DAT”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ2413/CNQ2413P.DAT”Rep aired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ2413/CNQ2413P.DAT”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ2414”Repaired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ2414”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ2414/CNQ2414N.DAT”Rep aired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ2414/CNQ2414N.DAT”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ2414/CNQ2414P.DAT”Rep aired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ2414/CNQ2414P.DAT”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ4807”Repaired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ4807”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ4807/CNQ4807N.DAT”Rep aired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ4807/CNQ4807N.DAT”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ4807/CNQ4807P.DAT”Rep aired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ4807/CNQ4807P.DAT”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ4808”Repaired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ4808”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ4808/CNQ4808A.DAT”Rep aired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ4808/CNQ4808A.DAT”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ4808/CNQ4808N.DAT”Rep aired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ4808/CNQ4808N.DAT”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ4808/CNQ4808P.DAT”Rep aired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ4808/CNQ4808P.DAT”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ4808/CNQ4808W.DAT”Rep aired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ4808/CNQ4808W.DAT”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ4809”Repaired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ4809”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ4809/CNQ4809N.DAT”Rep aired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ4809/CNQ4809N.DAT”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ4809/CNQ4809P.DAT”Rep aired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ4809/CNQ4809P.DAT”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ9601”Repaired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ9601”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ9601/CNQ9601N.DAT”Rep aired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ9601/CNQ9601N.DAT”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ9601/CNQ9601P.DAT”Rep aired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ9601/CNQ9601P.DAT”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ9602”Repaired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ9602”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ9602/CNQ1908D.TBL”Rep aired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ9602/CNQ1908D.TBL”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ9602/CNQ9602A.DAT”Rep aired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ9602/CNQ9602A.DAT”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ9602/CNQ9602N.DAT”Rep aired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ9602/CNQ9602N.DAT”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ9602/CNQ9602P.DAT”Rep aired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ9602/CNQ9602P.DAT”ACL found but not expected on “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ9602/CNQ9602W.DAT”Rep aired “Library/Printers/Canon/IJScanner/Resources/Parameters/CNQ9602/CNQ9602W.DAT”ACL found but not expected on “Library/Printers/PPDs”Repaired “Library/Printers/PPDs”ACL found but not expected on “Library/Printers/PPDs/Contents”Repaired “Library/Printers/PPDs/Contents”ACL found but not expected on “Library/Printers/PPDs/Contents/Resources”Repaired “Library/Printers/PPDs/Contents/Resources”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component”Repaired “Library/QuickTime/AppleIntermediateCodec.component”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Info.plist”Repaire d “Library/QuickTime/AppleIntermediateCodec.component/Contents/Info.plist”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/MacOS”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/MacOS”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/MacOS/AppleInterme diateCodec”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/MacOS/AppleInterme diateCodec”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/PkgInfo”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/PkgInfo”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/AppleInt ermediateCodec.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/AppleInt ermediateCodec.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/Dutch.lp roj”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/Dutch.lp roj”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/Dutch.lp roj/Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/Dutch.lp roj/Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/English. lproj”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/English. lproj”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/English. lproj/Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/English. lproj/Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/French.l proj”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/French.l proj”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/French.l proj/Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/French.l proj/Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/German.l proj”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/German.l proj”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/German.l proj/Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/German.l proj/Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/Italian. lproj”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/Italian. lproj”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/Italian. lproj/Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/Italian. lproj/Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/Japanese .lproj”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/Japanese .lproj”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/Japanese .lproj/Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/Japanese .lproj/Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/Spanish. lproj”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/Spanish. lproj”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/Spanish. lproj/Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/Spanish. lproj/Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/ar.lproj ”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/ar.lproj ”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/ar.lproj /Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/ar.lproj /Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/ca.lproj ”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/ca.lproj ”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/ca.lproj /Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/ca.lproj /Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/cs.lproj ”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/cs.lproj ”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/cs.lproj /Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/cs.lproj /Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/da.lproj ”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/da.lproj ”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/da.lproj /Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/da.lproj /Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/el.lproj ”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/el.lproj ”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/el.lproj /Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/el.lproj /Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/fi.lproj ”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/fi.lproj ”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/fi.lproj /Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/fi.lproj /Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/he.lproj ”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/he.lproj ”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/he.lproj /Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/he.lproj /Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/hr.lproj ”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/hr.lproj ”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/hr.lproj /Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/hr.lproj /Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/hu.lproj ”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/hu.lproj ”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/hu.lproj /Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/hu.lproj /Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/id.lproj ”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/id.lproj ”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/id.lproj /Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/id.lproj /Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/ko.lproj ”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/ko.lproj ”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/ko.lproj /Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/ko.lproj /Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/ms.lproj ”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/ms.lproj ”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/ms.lproj /Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/ms.lproj /Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/no.lproj ”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/no.lproj ”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/no.lproj /Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/no.lproj /Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/pl.lproj ”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/pl.lproj ”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/pl.lproj /Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/pl.lproj /Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/pt.lproj ”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/pt.lproj ”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/pt.lproj /Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/pt.lproj /Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/pt_PT.lp roj”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/pt_PT.lp roj”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/pt_PT.lp roj/Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/pt_PT.lp roj/Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/ro.lproj ”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/ro.lproj ”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/ro.lproj /Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/ro.lproj /Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/ru.lproj ”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/ru.lproj ”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/ru.lproj /Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/ru.lproj /Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/sk.lproj ”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/sk.lproj ”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/sk.lproj /Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/sk.lproj /Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/sv.lproj ”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/sv.lproj ”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/sv.lproj /Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/sv.lproj /Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/th.lproj ”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/th.lproj ”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/th.lproj /Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/th.lproj /Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/tr.lproj ”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/tr.lproj ”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/tr.lproj /Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/tr.lproj /Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/uk.lproj ”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/uk.lproj ”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/uk.lproj /Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/uk.lproj /Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/vi.lproj ”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/vi.lproj ”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/vi.lproj /Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/vi.lproj /Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/zh_CN.lp roj”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/zh_CN.lp roj”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/zh_CN.lp roj/Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/zh_CN.lp roj/Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/zh_TW.lp roj”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/zh_TW.lp roj”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/zh_TW.lp roj/Localized.rsrc”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/Resources/zh_TW.lp roj/Localized.rsrc”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/_CodeSignature”Rep aired “Library/QuickTime/AppleIntermediateCodec.component/Contents/_CodeSignature”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/_CodeSignature/Cod eResources”Repaired “Library/QuickTime/AppleIntermediateCodec.component/Contents/_CodeSignature/Cod eResources”ACL found but not expected on “Library/QuickTime/AppleIntermediateCodec.component/Contents/version.plist”Repa ired “Library/QuickTime/AppleIntermediateCodec.component/Contents/version.plist”

VicDesotelle wrote:
repeating error message: "acl found but not expected" during permissions repair
My iMac is running slow. Processor running all the time. I was told to do permissions repair, so I did that. I get 100's and 100's of "ACL found but not expected" while doing a permissions repair in 'utilities'. It says 1 minute to complete but runs for a half hour. When it finally completes, I can restart the permissions repair again and it starts all over with same endless messages. Even though its says 'repaired', these ACL issues keep coming.
ACLs are just junk left over from previously installed OSXs. Just ignore. They have no impact.
Describe your exact issue and computer specs and Linc may run you through a series of tests which may well help you find the problem to your issues. I agree, Permissions repair is rarely required.
Cheers
Pete

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

BPM error : Message pipeline PE_ADAPTER unknown XML message not found. Help

Hello All,
I have done 3 steps in BPM
RFC --- BPM --- RFC
RECEIVE step ==> Opens SYNCH ASYNCH bridge and receives RFC request message
SEND synchronous ==> to send RFC request and get the RFC response.
SEND ==> Closes SYNCH ASYNCH bridge and Send's response back to the RFC.
In my last send step (response back) I am getting message
"Message pipeline PE_ADAPTER unknown XML message not found" .
Pls help

Hi Rick,
check out this SAP Note: 1087532
Regards
Dominic

Loop in message flow found

Similar Messages

Maybe you are looking for