Message Exchange between XI's

hello everybody,
because of company politics I need to exchange messages between two XI's, the actual landscape is as follows:
R/3 Coporate <-> XI Corporate <-> R/3 Regional,
now with new politics needs to be like this:
R/3 Coporate <-> XI Corporate <-> XI Regional <-> R/3 Regional,
like I told you before is because company politics reason this changes, now the question is how can I exchange messages between two XI's, and what should be the steps to this interfaces migration and the standard adapter to use maybe XI Adapter in communication channel????, thanks in advacne for your answers.
Regards,
Julio Cesar

Do it like a normal B2B scenario, using XI adapter (XI 3.0 protocol).
http://help.sap.com/saphelp_nw70/helpdata/en/01/d9d43fb9490c65e10000000a114b1d/frameset.htm
You could even use XI 2.0 protocol in case of compatibility with older versions of XI.
Best regards,
Henrique.

Similar Messages

IDocs or Enterprise Services in message exchange between systems

I am trying to get some qualitative and quantitative answers to the comparison of Enterprise Services or IDocs as a choice of interface technology when exchanging messages via PI with external systems.
The external systems are probably going to have their own message format, so this would concern the nature of the interfaces of the ERP system interfaces to the PI system.
I have seen one other posting in this forum related to this, but no definitive answer.
Does anybody have any system performance comparisons using the two technologies, such as message throughput / hour? Not easy to compare I know.
Does anybody have an opinion as to the suitability of Enterprise Services for such a task? Is the technology stable enough to be trusted yet?
When comparing status messages of IDocs, do the Enterprise Services have a similar way of easuly seeing the delivery status of the message using the Enterprise Service?
Would anybody or has anybody actually been brave enough to use Enterprise Services in this way yet?
Are Enterprise Services appropriate for mass messaging?
All answers very much appreciated!
Kind Regards,
Tony.

Hi Michal,
Thanks for the reply. I try to respond to your questions precisely:
if you want to compare IDocs to services then I assume
we're talking about async services right?
(and most services - just like bapis - are sync messages)
so you compare two different things
Yes, I know. What if the message scenario was asynchronous, and you chose not to handle the response message of the Enterprise Service? You could still do that, right? Then the problem becomes how do you trace the status of the Enterprise Service transaction.
IDocs have the advantage of a status message, and a good message monitoring system, but I am not sure if the visibility of errors seen with Enterprise Services if treated asynchronously would be as obvious. My knowledge of the runtime of the Enterprise Services is currently a bit limited.
The whole reason for me asking about the use of Enterprise Services is that there are so many now that could be used for message exchange, if they were suitable for the task.
Also, what about creating Asynchronous/Synchronous bridges in PI to handle the response message? Then the response is always traceable, correct? Even if the customer doesn't want the response message, the content could always be found in the PI message monitor.
Additionally, there is a transaction in ERP that wraps a BAPI into an IDoc (don't have a system in front of me at the moment and cannot recall the transaction, maybe OM69 or something similar). Now, that is taking a synchronous 'service' (the BAPI), and converting it into an asynchronous IDoc. So if this is such a bad idea, why do SAP provide the transaction? Therefore, by extension, wouldn't it be possible to do the same thing for Enterprise Services, at least from a philosophical point of view? I mean, why would SAP imply you could do this for one kind of synchronous service (the BAPIs) but not others (the Enterprise Services)?
if you're talking about migrations etc I don't believe services
will be used with LSMW but BAPIs are on the other hand
No, I was talking about high volume message scenarios, sorry for the ambiguity. I guess if the performance of Enterprise Services is comparible to that of well written BAPIs, the answer is 'yes', correct?
Kind Regards,
Tony.

Message exchange between oracle and external system

I had posted my query before. I woull appreciate if anyone could guide me that for exchange of messages bwteen Oracle and external system which AQ programmatic environment is preferred -
1. PL/SQL
or
2.JMS
hello
WE have an Oracle database 9i. we want to use JMS ( Java messaging service ) for sending XML messages from one oracle system to other external system.
we are reading and creating XML files in Oracle database, but to send messages externally in forms of a XML file generated from Oracle could ayone tell me how that can be done or suggest some usefulk links
Also how to configure Oracle with JMS, could anyone tell me any useful links where i can find more information or any suggestions on this would be fine
thanks
kb

I'm not sure I understand how this question differs from the one I answered yesterday
Re: using JMS and Oracle help urgent..
Are you looking for alternate answers? Or looking for some specific bit of information?
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

Hi I am having problems downloading and updating apps on my iPad and iPhone. The message cycles between waiting and loading then I get an error message saying unable to download app. Eventually,after many attempts it works.

Hi Guys - for a few days I have been having problems downloading and updating apps on my iPad and iPhone. The message cycles between waiting and downloading then eventually says unable to download app. Sometimes after many attempts it wil eventually work. I tested it on an old iPhone 3G and got the same problem so it is not an iOS 5 issue. My WI-FI connection is working fine. I was wondering if this is an App Store problem? Anyone else in the UK having this problem?

Hi John
iTunes Support wasn't of any use to me.
I have also been having another problem - with BBC iPlayer and other video streaming not working due to insufficient bandwidth, despite my overall download speed being consistently around 50Gb. This is also affecting AppleTV downloads
I am using Virgin Media as my ISP, and was wondering whether you do as well. This might be the common thread.
-Bernard

"Portable" way to do message passing between threads?

(I posted this on the Apple Developer Forums already, but since that forum is only accessible to registered and paid iPhone developers, I thought it would be nice to put it here as well so as to get some more potential eyeballs on it. I apologize if this kind of "cross-posting" is not kosher/is frowned upon around here.)
Hey everybody,
"Long-time listener, first-time caller," heh.
I've been working for the past 2-3 months on my very first iPhone app. Actually, what I've been working on is a framework that I plan to use in an iPhone app of my own but which I am also trying to write for the "lowest-common-denominator" so that I (and others) can use it in other apps written for both Mac and iPhone.
Not only is this my first time writing an iPhone app, it is my first time writing for any Apple platform. In fact, it is my first time using Objective-C, period. I cannot stress this enough: I am a "n00b." So go easy on me. I also have not worked with threading before this, either, on any platform, so the learning curve for me here is rather significant, I'm afraid. I am NOT afraid of either taking the time to learn something properly OR of rolling up my shirtsleeves and working. However, on account of my experiences so far, I am finding myself (not to flame or anything!) quickly becoming frustrated by and disillusioned with not so much Objective-C itself, but the Foundation frameworks.
So with that said, read on, if you dare...
The basic idea behind my project is that the framework I am writing will present an API to developers which will allow them to write client apps that interact with a particular network appliance or network-aware embedded system. I already have my basic set of classes up and functioning, and the framework works to my satisfaction both on MacOS and iPhoneOS. The platforms I am targeting are MacOS X Tiger 10.4 and later, and iPhoneOS, and up until this point, I've managed to keep a codebase that works on all of the above.
What I wanted to do next was add some multithreaded goodness to the mix. (Woe is me.) I have asynchronous network socket I/O working within the main thread, and it, in fact, works a treat. In my test app on the phone, I've managed to keep the UI nice and responsive by using the main thread's runloop efficiently. But even though TCP async I/O works fine within the main thread, I want to be able to split out and offload the processing of any data received by the app from the appliance to its own thread. (It is possible, and even desirable, for an application using this framework to be connected to multiple appliances simultaneously.)
My idea, in order to try to keep things as simple and as clean as possible, was to implement a wrapper class that presented my other main class as an "actor." So, rather than instantiating my main class, one would create an instance of the wrapper class which would in turn control a single instance of my main class and spawn its own thread that the network connection and all data processing for that particular connection would run within.
(I hope I'm making sense so far...)
Out of the gate, writing a subclass of NSThread sounds like the logical design choice for an "actor-type" thread, but because I was trying to maintain Tiger compatibility, I stuck with +detachNewThreadSelector:etc.
Once I decided to pursue the actor model, though, the main problem presented itself: how to best pass messages between the main thread and all of the "actor" threads that might be spawned?
I stumbled upon -performSelector:onThread:withObject:, and knew instantly that this was exactly what I was looking for. Unfortunately, it doesn't exist on Tiger; only its much more limited little brother -performSelectorOnMainThread:withObject: does. So I kept looking.
All of the pre-Leopard documentation, tutorials, and sample code that I read indicated that to pass messages between threads, I needed to basically pretend that the threads were separate processes and use the expensive Distributed Objects mechanism to get messages back and forth. Unfortunately, even if that WAS a desirable option, iPhoneOS does not have any support for DO! Grrr...
Finally, I thought I found the answer when I ran into a third-party solution: the InterThreadMessaging library from Toby Paterson (available @ http://homepage.mac.com/djv/FileSharing3.html). In this library, the author basically implemented his own version of -performSelector:onThread:withObject: called -performSelector:withObject:inThread:. Sounds close enough, right? And actually, it is pretty darn close. It's made to do exactly what it sounds like, and it does it in a platform-neutral way that works on pre-Leopard systems as well as iPhoneOS, using Mach ports instead of DO.
(...wellll, ALMOST. I discovered after I built a small test app around it that it actually isn't "iPhone-clean." The author used an NSMapTable struct and the NSMap*() functions, which don't exist in iPhoneOS, and he also implemented the handlePortMessage delegate method, but although iPhoneOS has NSPort, it DOESN'T have NSPortMessage. GAAARGH. So I took the time to replace the NSMapTable stuff with NSValue-wrapped objects inside of an NSMutableDictionary, and replaced the handlePortMessage method implementation with a handleMachMessage method, which took some doing because I had to figure out the structure of a Mach message, NO thanks to ANY of the available documentation...)
Once I started using it, though, I quickly discovered that this implementation wasn't up to snuff. My "actor" class and my main thread will be passing a ton of messages to each other constantly whenever there is network activity, and with InterThreadMessaging, I found that whenever activity started to ramp up, it would collapse on itself. This mostly took the form of deadlocks. I found a note that someone else wrote after experiencing something similar with this library (quoted from DustinVoss @ http://www.cocoadev.com/index.pl?InterThreadMessaging):
"It is possible to deadlock this library if thread A posts a notification on thread B, and the notification on B causes a selector or notification to be posted on thread A. Possibly under other circumstances. I have resolved this in my own code by creating an inter-thread communication lock. When a thread wants to communicate, it tries the lock to see if another thread is already using the InterThreadMessaging library, and if it can't get the lock, it posts a message to its own run-loop to try again later. This is not a good solution, but it seems to work well enough."
So I tried implementing what he described using a global NSLock, and it did help with some of the deadlocks. But not all. I believe the culprit here is the Mach ports system itself (from the NSPortMessage documentation for -sendBeforeDate:):
"If the message cannot be sent immediately, the sending thread blocks until either the message is sent or aDate is reached. Sent messages are queued to minimize blocking, but failure can occur if multiple messages are sent to a port faster than the portís owner can receive them, causing the queue to fill up."
InterThreadMessaging in fact calls -sendBeforeDate: and exposes the deadline option, so I tried setting a really short time-to-live on the Mach messages and then intercepted any NSPortTimeoutExceptions that were thrown; upon catching said exceptions, I would then re-queue up the message to be sent again. It worked, but Performance. Was. A. Dog. At least the message queue wouldn't be full indefinitely anymore, causing the main thread to block, but during the whole time that these messages were expiring because the queue was full and then being re-queued, either the main thread was trying to send more messages or the actor thread was trying to send more messages. And as far as I can tell, the Mach ports queue is global (at the very least, there is seemingly only one per process). The message would get through with this model...eventually.
JUST IN CASE the problem happened to be something I screwed up as I was rewriting portions of the InterThreadMessaging library so that it would compile and work on the iPhone SDK, I substituted in the original version of the library in my Mac test app to see if any of these problems became non-issues. I found that both versions of the library -- mine and the original -- performed identically. So that wasn't it.
Finally, in frustration I said, "screw it, I'm going to try it the Leopard way," and replaced all of the method calls I was making to InterThreadMessaging's -performSelector:withObject:inThread: with calls to Foundation's native -performSelector:onThread:withObject: instead, changing nothing else within my code in the process. And wouldn't you know: IT WORKED GREAT. Performance was (and is) fantastic, about on-par with the non-threaded version when only dealing with a single connection/instance of my class.
So, in the end, I was able to do nothing to salvage the InterThreadMessaging implementation of cross-thread method calling, and as far as I can tell, I'm out of (good) options. And thus my mind is filled with questions:
How is the Leopard -performSelector:onThread: method implemented? I'm guessing not using Mach ports, given that I didn't have the same blocking & deadlocking problems I had with InterThreadMessaging. Is it possible to re-implement this Leopard+ method in a similar manner as a category to NSObject under Tiger? Or is it possible, perhaps, to increase the size of the Mach ports queue so that InterThreadMessaging works at a sane level of performance? Or -- I'm getting desperate here -- is there any way that I could trick -performSelectorOnMainThread: to target a different thread instead? (I am assuming here that -performSelectorOnMainThread is implemented under-the-hood much like the new -performSelector:onThread: is implemented, but with a hard-coded NSThread pointer built-in to the code, and that the new method just exposes a more flexible interface to what is basically the same code. I'm probably wrong...) Is there another third-party library out there that I've missed that fits my requirements for being able to do message-passing between threads in an efficient and portable manner?
I refuse to believe that there is no way for me to maintain compatibility with all of the platforms I wish to support without having to resort to making preprocessor #ifdef spaghetti out of my code. And there SURELY has to be a better way of doing cross-thread message passing in Tiger without using Distributed Objects, for Pete's sake! Is this really how people did it for years-on-end since the dawn of NeXT up until the advent of Leopard? And if there really, genuinely wasn't another alternative, then what is up with the lack of DO in iPhoneOS?? Does Apple seriously intend for developers who have good, solid, tested and working code to just chuck it all and start over? What if there was some aspect of DO that previous implementations relied upon that cannot be recreated with simple -performSelector:onThread: calls? (I don't know what those aspects would be...just a hypothetical.) I mean, I can understand needing to write new stuff from scratch for your UI given how radically different the interface is between the Mac and iPhone, but having to reimplement back-end guts such as something as elemental as threads...really?!
I do laud the inclusion of the new method in Leopard as well as the new ability to subclass NSThread itself. But for those of us that need to support Tiger for one reason or another, some of these restrictions and omissions within iPhoneOS seem like rather pointless (and frustrating) roadblocks.
As I hope is obvious here, I have tried to do my homework before throwing up my hands and pestering y'all. If you have the patience to deal with me, please tell me what I am missing.
Thanks for taking the time to read,
-- Nathan

Thanks again for your patience. Comments below.
etresoft wrote:
It is pretty unusual that anyone would want to call perfomrSelector on any thread other than the main thread.
What I described in my original post was not a worker thread, but an "actor."
It is hard for me to answer this question because there are so many options available to do "message passing". The fact that you think there are so few tells me that you really aren't sure what you need to use.
I didn't say there were few options for message passing. I said there were few options for message passing that fit my criteria, which are that any potential solutions should both A) work efficiently and with good performance, and B) be available both pre-Leopard AND on the iPhone. -performSelector: ain't available before Leopard. Distributed Objects is overkill. Kernel Mach messages apparently have a high overhead, too, as my experience with the third-party library I wrote about in my original message shows.
...consider notifications.
I thought notifications couldn't be posted across threads, either. How do I post a notification to another thread's default notification center or notification queue from a different thread?
The notification center is owned by the process. Each run loop can listen for just the notifications it wants. You don't "pass" or "send" notifications, you run then up the flagpole for all to see.
I am aware of how to use notifications. The documentation for NSNotificationCenter clearly states that "In a multithreaded application, notifications are always delivered in the thread in which the notification was posted, which may not be the same thread in which an observer registered itself."
So, again, I don't see how one thread can post a notification in such a way that the observer's registered method is executed in another thread (posting notifications "across threads"). This probably isn't a big deal if you are using mutexes (assuming you don't actually care which thread carries out the task associated with the notification posting), but as I said before, this is not what I'm after.
I don't know what you are really after.
Allow me to attempt to explain a second time, in a more concise fashion.
My app will have multiple, persistent TCP connections open, one connection per remote device. The user will be able to select a task to execute on a particular device that we have a connection open to, and get back from the application real-time updates as to the progress or results of the execution of that task. In certain cases, the length of the task is infinite; it will keep executing forever and sending back results to my application which will update its display of the results every second that ticks by until the user STOPS that particular task.
This can be done simply using async I/O in the main runloop, sure. But if I were going to thread this so that I could be processing the results I've received back from one *or more* remote devices while also doing something else, given that I will only have one (persistent) connection open to any given remote device that I'm interacting with (that is to say, I won't be opening up a separate TCP session for every single task I want to execute on a single device simultaneously), it makes sense _to me_ to implement this as I've described: with every connection to each remote device getting its own thread that lasts for the lifetime of the TCP session (which could be the entire time the application is running, times however many devices the user wishes to be connected to while in the app). I won't be spawning a new thread for every task the user wishes to ask a remote device to do.
This is why (I think) I need bi-directional messaging between the main thread and each of these threads dedicated to a given remote device that we have an active session with/connection to. The main thread needs to be able to tell remote device X (which already has a running thread dedicated to it) to do task A, and then get real-time feedback from that remote device so that the main thread can be displaying it to the user as it is coming back. Same with remote device Y running task B, simultaneously. At any time during the execution of these tasks, the user needs to be able to tell my app to stop one of these tasks, and the main thread needs to send that message to one of the remote devices via that device's dedicated thread.
This is why I am talking about this in terms of the "actor model," and not the "worker thread model," because the former model seems to fit what I want to do.
-- Nathan

Message flow between advanced adapter engine and messaging system for ICO scenarios

Dear all,
I'm working on a PI 7.31 AEX box and created an ICO object for one interface with HTTP_AAE2IDoc scenario. The interface works quite well. When I looked in to message log of messages for this interface in PI monitor, I noticed that the internal XI message are put totally 5 times into the send queue and retrieved from send queue. In some steps I only see after retrieving a message from send queue and immediately put it back into send queue. Can someone please kindly explain the message flow between advanced adapter engine and messaging system and what exactly happens after each retrieving a message from send queue?
Below is an example of message log for one message:
12/08/2014 09:26:06.472    Information    MP: processing local module localejbs/CallSapAdapter
12/08/2014 09:26:06.472    Information    Application attempting to send an XI message asynchronously using connection HTTP_AAE_http://sap.com/xi/XI/System
12/08/2014 09:26:06.478    Information    Trying to put the message into the send queue
12/08/2014 09:26:06.499    Information    Message successfully put into the queue
12/08/2014 09:26:06.499    Information    The message was successfully retrieved from the send queue
12/08/2014 09:26:06.499    Information    The application sent the message asynchronously using connection HTTP_AAE_http://sap.com/xi/XI/System. Returning to application
12/08/2014 09:26:06.500    Information    HTTP adapter successfully processed interface PlantResponse_Out
12/08/2014 09:26:06.501    Information    Trying to put the message into the send queue
12/08/2014 09:26:06.501    Information    Message status set to DLNG
12/08/2014 09:26:06.513    Information    Message successfully put into the queue
12/08/2014 09:26:06.513    Information    The message was successfully retrieved from the send queue
12/08/2014 09:26:06.515    Information    Message status set to DLNG
12/08/2014 09:26:06.533    Information    Trying to put the message into the send queue
12/08/2014 09:26:06.548    Information    Message successfully put into the queue
12/08/2014 09:26:06.548    Information    The message was successfully retrieved from the send queue
12/08/2014 09:26:06.550    Information    Message status set to DLNG
12/08/2014 09:26:06.551    Information    Executing Request Mapping "http://styrolution.com/pi/Integration/PlantMaintenance/PlantResponse/PlantResponse_to_Zcol_Basf_Inotif02_Inotif01_Zeupm_Inotif01_Ludwigshafen" (SWCV 085d2320fb3b11e2cc0bf4d50aea8c33)
12/08/2014 09:26:06.563    Information    Trying to put the message into the send queue
12/08/2014 09:26:06.571    Information    Message successfully put into the queue
12/08/2014 09:26:06.571    Information    The message was successfully retrieved from the send queue
12/08/2014 09:26:06.573    Information    Trying to put the message into the send queue
12/08/2014 09:26:06.573    Information    Message status set to DLNG
12/08/2014 09:26:06.580    Information    Message successfully put into the queue
12/08/2014 09:26:06.580    Information    The message was successfully retrieved from the send queue
12/08/2014 09:26:06.582    Information    Message status set to DLNG
12/08/2014 09:26:06.583    Information    Delivering to channel: IDOC_R
12/08/2014 09:26:06.583    Information    MP: processing local module localejbs/IDocOutboundModuleBean
12/08/2014 09:26:06.583    Information    XI message received for processing
12/08/2014 09:26:06.587    Information    Sender Party: Sender Service:SXX Receiver Party: Receiver Service:RXXCLNT200 Communication Channel:IDOC_R
12/08/2014 09:26:06.588    Information    IDOC metadata repository is RXX
12/08/2014 09:26:06.589    Information    Control record is not mandatory - control record will be added if not available
12/08/2014 09:26:06.590    Information    XML Payload parsed to idoc document list with number of idocs: 1
12/08/2014 09:26:06.595    Information    Sending idoc message to receiver R/3 system with TID XIh{lsRI824UITC0009OalmW
12/08/2014 09:26:06.813    Information    IDOC message sent to receiver R/3 system
12/08/2014 09:26:06.817    Information    TID XIh{lsRI824UITC0009OalmW confirmed
12/08/2014 09:26:06.819    Information    Message was successfully transmitted to endpoint <local> using connection HTTP_AAE_http://sap.com/xi/XI/System
12/08/2014 09:26:06.821    Information    Message status set to DLVD
Thanks & regards
Dingjun

Hello All,
Thanks for the prompt responses and with best information, But apart from this,I need how an adapter(File/JDBC) works along
with AAE in PI 7.1. When does the job of File/JDBC adapter is completed and resumed in a synchronous case. That is,
File Location --> file adapter -
> XI(AAE) --> JDBC adapter --> database.
In file sender, lets suppose we have synchronous settings(Best Effort). Now when File adapter's job is finished and when it
gets back the response back from XI. Please explain step by step from starting(file adapter polling the location) to getting the response coming back to XI.
Regards,
Achari.

Standard XML schema for Vendor data exchange between SAP and other system

Is there a SAP standard way of XML schema that we exchange between SAP and other system? Please let me know.
Thanks.

See SAP Interface Repository (http://ifr.sap.com).
My proposal is to leave old SAP connectors staff and use SAP Exchange Infrastructure. There is a support of industry XML standards in XI 3.0 like xCBL.

My wife, daughter and I have iPhones. We all have iMessage and Send Read Receipts activated. All the messages sent between the three of us are blue except those that my wife sends to me. They are green. Can anyone explain why.

My wife, daughter and I have iPhones with iMessage and Send Read Receipts activated. All the messages sent between the three of us are blue however, when my wife messages me, the message appears in green on her iPhone. Can anyone explain why.

Because some kind of error occured. This is only from her iPhone to your iPhone? Whenever she sends a message to any other iPhone, it is sent as blue? And when anyone else sends you a message from an iPhone, it sends as blue?

Unable to create a JMS Message bridge between Weblogic 12c and Weblogic 8.1

Hi,
I am unable to successfully create a Message Bridge between Weblogic 12.1.1.0 and Weblogic 8.1. The error message being received is:
eis/jms/WLSConnectionFactoryJNDINoTX > ResourceAllocationException generated by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory, url = t3://localhost:8001, user name = System) ">
The error on the monitoring tab is WARN: failed to connect to target.
Both domains are deployed on one box for testing purposes. The bridge itself is deployed on Weblogic 12c. The areas of config that may be of interest are:
<server>
<name>AdminServer</name>
<listen-address></listen-address>
</server>
<messaging-bridge>
<name>Bridge</name>
<target>AdminServer</target>
<source-destination>JMSBridgeSource12c</source-destination>
<target-destination>JMSBridgeTarget81</target-destination>
<selector>Test</selector>
<quality-of-service>Exactly-once</quality-of-service>
<qos-degradation-allowed>false</qos-degradation-allowed>
<durability-enabled>true</durability-enabled>
<idle-time-maximum>60</idle-time-maximum>
<async-enabled>true</async-enabled>
<started>true</started>
<preserve-msg-property>false</preserve-msg-property>
</messaging-bridge>
<app-deployment>
<name>jms-xa-adp</name>
<target>AdminServer</target>
<module-type>rar</module-type>
<source-path>D:\ORACLE~3\WLSERV~1.1\server\lib\jms-xa-adp.rar</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<jms-bridge-destination>
<name>JMSBridgeSource12c</name>
<adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDIXA</adapter-jndi-name>
<user-name>System</user-name>
<user-password-encrypted>{AES}nfFzhs+0J/O2Cenf0g4zDsDyvIKENMF7cZ5sAVUehX0=</user-password-encrypted>
<classpath></classpath>
<connection-factory-jndi-name>JMSConnectionFactory12c</connection-factory-jndi-name>
<connection-url>t3://localhost:7001</connection-url>
<destination-jndi-name>JMSQueue12c</destination-jndi-name>
</jms-bridge-destination>
<jms-bridge-destination>
<name>JMSBridgeTarget81</name>
<adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDIXA</adapter-jndi-name>
<user-name>System</user-name>
<user-password-encrypted>{AES}eBkO46cHvtrzEraOMIOdXow6WvEAtA4NCUDTQ4mC+9w=</user-password-encrypted>
<classpath></classpath>
<connection-factory-jndi-name>JMSConnectionFactory81</connection-factory-jndi-name>
<connection-url>t3://localhost:8001</connection-url>
<destination-jndi-name>JMSQueue81</destination-jndi-name>
</jms-bridge-destination>
I have enforced global trust between the two domains. I have disabled the guest user on the 8.1 domain but can’t see where to do this on 12c.
Any suggestions would be much appreciated.
Regards
John
Edited by: 958336 on 13-Sep-2012 03:11

Thanks for the recommendation. Unfortunately it did not help solve the problem.
I have managed to get a JMS bridge working between 12c and 8.1 by including the 8.1 weblogic.jar on the classpath. This setup was using eis.jms.WLSConnectionFactoryJNDINoTX.
After trying to use the adapter that supports transactions, WLSConnectionFactoryJNDIXA I received the following error:
java.lang.IllegalStateException: can only be called from server
Is this because the Weblogic 12c server now views the 8.1 server as being foreign?

Bridge messages exchange generating abandon timeout

Hi,
we have a bridge located on a 8.1 SP5 domain transferring messages from a Weblogic JMS queue to another JMS queue located on a 8.1 SP3 Weblogic domain.
We see in the logs that the bridge is correctly transferring messages (interoperability between domains is fine) :
####<May 16, 2006 4:23:37 PM CEST> <Debug> <MessagingBridge> <ariel> <accdmfaup_5> <ExecuteThread: '7' for queue: 'MessagingBridge'> <<WLS Kernel>> <BEA1-367AE1C09CA850D0B9AC> <BEA-200006> <Messaging bridge debugging RUNTIME! Bridge: EboxReceptorQueueQ1Bridge (processMessages()) received message:
JMS Message Class: BytesMessage
JMSMessageID: ID:P<932610.1147789417792.0>
JMSCorrelationID: null
JMSDeliveryMode: PERSISTENT
JMSDestination: EboxReceptorQueue_accdmfaup_q+1_cluster
JMSExpiration: 0
JMSPriority: 4
JMSRedelivered: false
JMSReplyTo: null
JMSTimestamp: 1147789417792 (Tue May 16 16:23:37 CEST 2006)
JMSType: null
Transaction Id: BEA1-367AE1C09CA850D0B9AC
.>
####<May 16, 2006 4:23:37 PM CEST> <Debug> <MessagingBridge> <ariel> <accdmfaup_5> <ExecuteThread: '7' for queue: 'MessagingBridge'> <<WLS Kernel>> <BEA1-367AE1C09CA850D0B9AC> <BEA-200006> <Messaging bridge debugging RUNTIME! Bridge: EboxReceptorQueueQ1Bridge (processMessages()) successfully sent message:
JMS Message Class: BytesMessage
Old JMS MessageID: ID:P<932610.1147789417792.0>
New JMS MessageID: ID:P<262044.1147789417947.0>
.>
But about 10' later we have
####<May 16, 2006 4:33:40 PM CEST> <Error> <JTA> <ariel> <accdmfaup_5> <ExecuteThread: '0' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-110423> <Abandoning transaction after 603 seconds: Xid=BEA1-367AE1C09CA850D0B9AC(30352338),Status=Committing,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=602,seconds left=0,XAServerResourceInfo[JMS_DmfAFileStore_EboxReceptor_accdmfaup_5]=(ServerResourceInfo[JMS_DmfAFileStore_EboxReceptor_accdmfaup_5]=(state=committed,assigned=accdmfaup_5),xar=JMS_DmfAFileStore_EboxReceptor_accdmfaup_5,re-Registered = false),XAServerResourceInfo[JMS_eBoxStore2]=(ServerResourceInfo[JMS_eBoxStore2]=(state=new,assigned=acc2),xar=null,re-Registered = false),SCInfo[accdmfaup_domain+accdmfaup_5]=(state=committed),SCInfo[accdomain+acc2]=(state=committing),properties=({}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=accdmfaup_5+ariel.smals-mvm.be:9112+accdmfaup_domain+t3+, XAResources={JMS_DmfAFileStore_FlatFileEndDeclaration_accdmfaup_5, JMS_DmfAFileStore_StepDebuggerTracer_accdmfaup_5, JMS_DmfAFileStore_ReceptorBigElement_accdmfaup_5, JMS_DmfAFileStore_DeclarationNotificationSP7_accdmfaup_5, JMS_DmfAFileStore_DeclarationNotificationAckSP7_accdmfaup_5, JMS_DmfAFileStore_RaiseIdQuestion_accdmfaup_5, JMS_DmfAFileStore_WebConsolidator_accdmfaup_5, JMS_DmfAFileStore_PDFGenerator_accdmfaup_5, JMS_DmfAFileStore_FlatFileAcknowledge_accdmfaup_5, JMS_DmfAFileStore_FlatFileElementPreCondition_accdmfaup_5, JMS_DmfAJMSServer_Logger_accdmfaup_5_NotDurable, JMS_DmfAFileStore_WebConsolidatorPreCondition_accdmfaup_5, db.pool.dmfawl_Qplus1, JMS_DmfAJMSServer_NotificationMessenger_accdmfaup_5_NotDurable, accdmfaup_domain.accdmfaup_5.Weblogic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA, JMS_DmfAJMSServer_FlowResourceStatus_accdmfaup_5_NotDurable, JMS_DmfAFileStore_DereservationElement_accdmfaup_5, JMS_DmfAFileStore_FlatFileElement_accdmfaup_5, JMS_DmfAJMSServer_BatchStepStatus_accdmfaup_5_NotDurable, JMS_DmfAFileStore_EboxReceptor_accdmfaup_5, JMS_DmfAFileStore_DeleteDeclaration_accdmfaup_5, JMS_DmfAFileStore_ErrorToSolve_accdmfaup_5, JMS_DmfAFileStore_ReceptorSP7_accdmfaup_5, JMS_DmfAFileStore_EndDeclaration_accdmfaup_5, JMS_DmfAFileStore_DeclarationValidation_accdmfaup_5, weblogic.jdbc.wrapper.JTSXAResourceImpl, JMS_DmfAFileStore_ElementValidation_accdmfaup_5, JMS_DmfAFileStore_Identification_accdmfaup_5, JMS_DmfAFileStore_FlatFileElementSplitter_accdmfaup_5, JMS_DmfAFileStore_WebSP7_accdmfaup_5, JMS_DmfAJMSServer_Singleton_accdmfaup_5_NotDurable, JMS_DmfAFileStore_Splitter_accdmfaup_5, JMS_DmfAFileStore_CrossControlValidation_accdmfaup_5, JMS_DmfAFileStore_Error_accdmfaup_5, JMS_DmfAFileStore_DereservationElementSplitter_accdmfaup_5, JMS_DmfAFileStore_DereservationElementPreCondition_accdmfaup_5, JMS_DmfAFileStore_Resend_accdmfaup_5, JMS_DmfAFileStore_DeclarationNotificationAck_accdmfaup_5, JMS_DmfAFileStore_RaiseLastSituationQuestion_accdmfaup_5, JMS_DmfAFileStore_FlatFileTransfer_accdmfaup_5, JMS_DmfAFileStore_DeclarationHistoric_accdmfaup_5, JMS_DmfAFileStore_ModelValidation_accdmfaup_5bis, JMS_DmfAFileStore_DeclarationNotification_accdmfaup_5, JMS_DmfAFileStore_CodesFile_accdmfaup_5},NonXAResources={})],CoordinatorURL=accdmfaup_5+ariel.smals-mvm.be:9112+accdmfaup_domain+t3+)>
The bridge configuration is as follow :
<JMSBridgeDestination
ConnectionFactoryJNDIName="jms.factory.ebox.receptor"
DestinationJNDIName="jms.queue.ebox.receptor" Name="EboxReceptorBridgeLocalDestination"/>
<JMSBridgeDestination
ConnectionFactoryJNDIName="jms.factory.ebox.receptorBridge"
ConnectionURL="t3://loki.smals-mvm.be:9090,vali.smals-mvm.be:9090"
DestinationJNDIName="jms.queue.ebox.receptor"
Name="EboxReceptorBridgeRemoteDestination" UserName="" UserPasswordEncrypted=""/>
<MessagingBridge AsyncEnabled="false" BatchInterval="1000"
BatchSize="1" DurabilityEnabled="false"
Name="EboxReceptorQueueBridge"
SourceDestination="EboxReceptorBridgeLocalDestination"
Started="true"
TargetDestination="EboxReceptorBridgeRemoteDestination" Targets="accdmfaup_cluster"/>
Any help would be really appreciated.

Thank you for your email. I am out of the office until March 25th, I will have limited access to my e-mail during this period.
In my absence, please feel free to contact Mr Akram Allani : [email protected]
Thank you for your understanding.
Best regards,
Youssef Boukari

Message bridge between two instances

I am trying to setup messaging bridge between two instances of weblogic server.
Can the second instance belong to a different domain? If yes how to configure it?

Yes, you can configure a messaging bridge to work between two WebLogic domains.
The general instructions of configuring a message bridge, including the bridge instance itself, the bridge destinations and the adapter, can be found at
http://edocs.bea.com/wls/docs103/bridge/basics.html#wp1168461
The only extra thing that you may need to take care of for the cross-domain case is to configure cross-domain security as instructed at
http://edocs.bea.com/wls/docs103/bridge/wls_interop.html#wp1126873
Regards,
Dongbo

Basic question regarding Contract data exchange between CRM and ERP

Hi,
1) At a very general level, can somebody tell me via what technology are contract documents exchanged between CRM and ERP? IDocs, RFC modules or proxies?
2) Is it possible to sychronise changes in a contract, e.g. if the contract is changes in the ERP system, those changes are auotomatically updated in the CRM contract?
3) Can somebody point me to any documentation on this?
Kind Regards,
Tony.

contracts are exchanged between CRM ans ERP ssytem ny RFC and FM , you use object SALESCONTRACT for this,it is possible to synchronize changes between both the systems

Data exchange between SCM and ERP

Hi Guys,
Can you please tell what all data is exchanged between ERP system and SCM system.
I am doing a project to find out the exchange of data between these systems, it would be great if u can help me out or throw a direction to find these details.
Thanks a lot guys
Regards,
Kumar
POINTS ASSURED

Hi Kumar,
Please find detailed document help link as below:
http://help.sap.com/saphelp_scm70/helpdata/en/64/08533b89050863e10000000a114084/frameset.htm
For master data following data flow occurs from ECC to APO:
u2022     Products
u2022     Locations
u2022     Classes and characteristics
u2022     Batches
u2022     Setup groups
u2022     Resources
u2022     Production Process Modes / Produtc Data structures
Transaction data flow
u2022     Sales documents
u2022     Stocks
u2022     Inspection lots
u2022     Purchase orders and requisitions
u2022     Planned orders
u2022     Maintenance orders
u2022     Project / network orders
Regards
Datta

Messaging Bridge Between 2 Weblogic Server

          Hi,
          I would like to create a messaging bridge between two Weblogic Server on two different
          server. One on Windows NT and one on Solaris.
          I have created one queue on NT and one other queue on Solaris, and the corresponding
          JMS Bridge destination for each queue on one server (and the other to test).
          And on one server (and the other to test), I have created a messaging bridge to
          transfert messages from one queue to the other, but I have a message on the Weblogic
          Server.
          javax.resource.spi.ResourceAllocationException: CreateManagedConnection Error:
          ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory,
          url = http://usv9007.rtc.ch:7001, user name = null, password = null
          at weblogic.connector.common.internal.ConnectionPool.makeResources(ConnectionPool.java:978)
          at weblogic.connector.common.internal.ConnectionPool.getConnection(ConnectionPool.java:1708)
          at weblogic.connector.common.internal.ConnectionPoolManager.getConnection(ConnectionPoolManager.java:163)
          at weblogic.connector.common.internal.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:25)
          at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseConnectionFactory.java:126)
          at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:733)
          at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:899)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
          <09.01.2003 13:48:51 CET> <Error> <Connector> <190006> <Error granting connection
          request.>
          Parameter for the distant queue
          Adapter JNDI Name : eis.jms.WLSConnectionFactoryJNDIXA (I have activated the XA
          ressources for the ConnectionFactory and the corresponding adapter)
          Connection URL : http://SolarisIP:7001
          InitialContextFactory : weblogic.jndi.WLInitialContextFactory
          ConnectionFactory JNDI Name : myConnectionFactory
          Destination JNDI Name : myQueueSolaris
          Destination Type : Queue
          I don't understand why I have this error, because all the parameters are correct,
          and the http tunneling is activated.
          Could you help me to configure correctly this messaging bridge ???
          Thanks a lot.


Looks like the error occurred on the target destination
          of the bridge. One way to find out if your configuration
          is correct is to use the same parameters (initial context factory,
          url, username and password) to get a connection to the
          target server from a standalone client.
          Dongbo
          Seb wrote:
          >
          > Hi,
          >
          > I would like to create a messaging bridge between two Weblogic Server on two different
          > server. One on Windows NT and one on Solaris.
          >
          > I have created one queue on NT and one other queue on Solaris, and the corresponding
          > JMS Bridge destination for each queue on one server (and the other to test).
          >
          > And on one server (and the other to test), I have created a messaging bridge to
          > transfert messages from one queue to the other, but I have a message on the Weblogic
          > Server.
          >
          > -----------------------------------------------------------------
          > javax.resource.spi.ResourceAllocationException: CreateManagedConnection Error:
          > ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory,
          > url = http://usv9007.rtc.ch:7001, user name = null, password = null
          > at weblogic.connector.common.internal.ConnectionPool.makeResources(ConnectionPool.java:978)
          > at weblogic.connector.common.internal.ConnectionPool.getConnection(ConnectionPool.java:1708)
          > at weblogic.connector.common.internal.ConnectionPoolManager.getConnection(ConnectionPoolManager.java:163)
          > at weblogic.connector.common.internal.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:25)
          > at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseConnectionFactory.java:126)
          > at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:733)
          > at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:899)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
          > <09.01.2003 13:48:51 CET> <Error> <Connector> <190006> <Error granting connection
          > request.>
          > -----------------------------------------------------------------
          >
          > Parameter for the distant queue
          >
          > Adapter JNDI Name : eis.jms.WLSConnectionFactoryJNDIXA (I have activated the XA
          > ressources for the ConnectionFactory and the corresponding adapter)
          > Connection URL : http://SolarisIP:7001
          > InitialContextFactory : weblogic.jndi.WLInitialContextFactory
          > ConnectionFactory JNDI Name : myConnectionFactory
          > Destination JNDI Name : myQueueSolaris
          > Destination Type : Queue
          >
          > I don't understand why I have this error, because all the parameters are correct,
          > and the http tunneling is activated.
          >
          > Could you help me to configure correctly this messaging bridge ???
          >
          > Thanks a lot.

Wireless application for files exchange between two computers,pls Help

Hi everyone,
I need your help,pls.I have to make a wireless application for files exchange between two computers,but I don't know where to start from.I guess that this should be a client/server and after establishing a connection I have to be able to exchange files between each others.Please help me

the wireless connection does not matter.
This is a socket (client server as you said) same way.
look out:
http://java.sun.com/docs/books/tutorial/networking/index.html
cya

Message Exchange between XI's

Similar Messages

Maybe you are looking for