Sync/async wsdl not published

Hello,
I've successfully made a sync/async wsdl from an asynchronous java process. I was able to test it via web services test explorer and a self made java client, but I need to integrate its wsdl on a third party product (ws register) and I can't find its wsdl referece from an http url.
When you make an ordinary jpd its wsdl is accessible via http. For instance, if the jpd's url is http://localhost:7001/TesteWeb/TestePD.jpd , then it's wsdl is accessible via http://localhost:7001/TesteWeb/TestePD.jpd?WSDL.
But when you make its sync/async wsdl the endpoint is, for instance, http://localhost:7001/sync2AsyncIM/TesteWeb/TestePD.sync2JPD, but if you try http://localhost:7001/sync2AsyncIM/TesteWeb/TestePD.sync2JPD?WSDL to get its wsdl then you get an error:
org.apache.xmlbeans.XmlException: error: Unexpected end of file after null
Again: the service itself is ok, but I need an http reference for its wsdl. How can I make it?
I'm using Weblogic (with WLI) version 9.2.0.
Thanks in advance.
Leo

Hi Siddhesh - yes that was a while back and am trying to remember the resolution. I have implemented sync/async bridges (as well as async/sync bridges) successfully, so I don't mind checking your settings, particularly I am interested in the settings within the Module tab of the JMS receiver. I can then compare to mine if you'd like. Also if you can let me know what underlying queuing system in that target system (e.g. MQSeries?) that would be great.
Regards,
Keith

Similar Messages

Sync-Async process

Hi Friends, 
I am in a problem, I have one jpd published as a webservice to a poral [synchronous] client. This jpd is asynchronous,meaning it have separate client request and client response node, but the same jpd is calling one more process control[async again] to do the dirty work of tranforming incoming request and then sending to legacy system using JMS control[async activity]. The question is, can we call the outer jpd [that is published as a web-service] synchronously from a portal page. I seen the weblogic docs they say to make sync-async wsdl file and define client callback method,I tried it but it doesn't work. 
I think my design fall in some limitation that the doc is talking about as in between pair of client request and client response node I have another client request to the process control [for transforming and sendng receiving message]. 
Is there anyother way to make it work? 
Did anyone got the same problem before? 
Guys, you need to help me in this pls
I already tried lots of permutation and combination to arrive at this design so pls don't ask me to change this now. :( 
Cheers, 
Shailesh 

Just to let you know that I have gotten sync-async WSDL to work.
In my situation we front an async JPD with a JWS via this sync/async WSDL. We had to do this since we had a requirement that only allows soap over http AND sync/async WSDL needs soap over jms protocol.
Can you clarify when you say "it does not work"?
There is a test project out there somewhere in dev2dev codeshare or samples area that demonstrated this procedure. The first time I tried this approach I missed one step where I forgot to add the following line in mine process definition block:
* @jws:protocol jms-soap="true"
Hope this helps.
Parvez

Sync-Async Gotchaa

Hi Friends, 
I am in a problem, I have one jpd published as a webservice to a poral [synchronous] client. This jpd is asynchronous,meaning it have separate client request and client response node, but the same jpd is calling one more process control[async again] to do the dirty work of tranforming incoming request and then sending to legacy system using JMS control[async activity]. The question is, can we call the outer jpd [that is published as a web-service] synchronously from a portal page. I seen the weblogic docs they say to make sync-async wsdl file and define client callback method,I tried it but it doesn't work. I think my design fall in some limitation that the doc is talking about as in between pair of client request and client response node I have another client request to the process control [for transforming and sendng receiving message]. 
 Is there anyother way to make it work? 
 Did anyone got the same problem before? 
 Guys, you need to help me in this pls I already tried lots of permutation and combination to arrive at this design so pls don't ask me to change this now. :( 
Cheers, 
Shailesh

Hi Rohini,
Sync/async communication enables a synchronous sender system to communicate with a receiver system that cannot process synchronous messages.
The central component of sync/async communication is the sync/async bridge, which enables the Integration Server to receive synchronous messages from a sender and send them to a receiver as asynchronous messages. Conversely, it can send the asynchronous response from the receiver back to the sender as a synchronous response.
To do this, you define an integration process, which is started as soon as a synchronous message is received from the sender system. The process uses a special receive step to open the sync/async bridge, sends the received message to the receiver system asynchronously, and waits for the asynchronous response to arrive from the receiver.
The Business Process Engine receives the asynchronous response from the receiver, correlates it with the corresponding query, and activates the waiting process, which then sends the response back to the sender synchronously.
There is an example of the Sync/Async Bridge in th SWCV: SAP BASIS.
Namespace: http://sap.com/xi/XI/System/Patterns
Go through this link to get a good idea as to how to <a href="http://help.sap.com/saphelp_nw04/helpdata/en/43/65d4dab39b0398e10000000a1553f6/frameset.htm">Define Sync/Async Communication</a>
This blog also should give you some idea...
https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/1403 [original link is broken]
Also go through these links:
http://help.sap.com/saphelp_nw04/helpdata/en/83/d2a84028c9e469e10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c4/dc06418752ef6fe10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/f9/66bf40ad090366e10000000a1550b0/RN_XI_DE_neu.pdf
I hope it helps.
Regards,
Abhy
Message was edited by: Abhy Thomas

Sync/Async - JMS receiver comm. channel not processing

I have a Sync/Async scenario (without bpm) in PI 7.11:
RFC -> PI -> JMS
whereby the JMS receiver comm. channel does not fully process the message.
More specifically, the RFC sender comm. channel gets a message in and passes the message to the JMS channel, but that JMS channel within the RWB comm. channel log only shows the entry:
- Message processing started
The odd twist to this is that when we bring the PI server down, then back up again, (or wait a period of time, still trying to determine this period) the FIRST message attempt does successfully get processed, i.e. the first message on that JMS receiver comm. channel RWB log shows as:
- Channel successfully processed the message: 08499236-387c-11e0-b002-000025bab2c2
- Stored the correlation ID 08499236-387c-11e0-b002-000025bab2c2 of the request JMS message: ID:c3e2d840d4d8d4f24040404040404040c754dc12d8b54ec6 correponding to the XI message: 08499236-387c-11e0-b002-000025bab2c2
- Message processing started
(but then because of an issue on the target system, no response comes back, so then we'll additionally get the log entry:
- Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: no message received
Any suggestions appreciated on what I can check here to try and figure this out. Possibly because the first message eventually errors out, it is stopping the other subsequent msgs from getting processed...
When I check the audit logs of a 'success' msg vs. a not-successful msg, the success msg has an entry (and subsequent entries) of:
14.02.2011 12:50:19 Information Transform: transforming the payload ...
14.02.2011 12:50:19 Information Transform: successfully transformed
14.02.2011 12:50:19 Information ROB: entering RequestOnewayBean
14.02.2011 12:50:19 Information ROB: forwarding the request message
14.02.2011 12:50:19 Information ROB: leaving RequestOnewayBean
14.02.2011 12:50:19 Information JMS Message was forwarded to the JMS provider succesfully."
14.02.2011 12:50:19 Information XMB Message as Binary was forwarded to the SAP XI JMS service succesfully.
14.02.2011 12:50:19 Information WRB: entering WaitResponseBean
14.02.2011 12:50:19 Information WRB: retrieving the message for 08499236-387c-11e0-b002-000025bab2c2 ...
wheras the non-success msg shows only:
14.02.2011 12:55:30 Information Transform: transforming the payload ...
14.02.2011 12:55:30 Information Transform: successfully transformed
14.02.2011 12:55:30 Information ROB: entering RequestOnewayBean
14.02.2011 12:55:30 Information ROB: forwarding the request message
14.02.2011 12:55:30 Information ROB: leaving RequestOnewayBean
So, we can see that the message is not "forwarded to the JMS provider..." in the non-success case.
And also the sxi_monitor shows these messages with a status of "Log version".
Keith

Hi Siddhesh - yes that was a while back and am trying to remember the resolution. I have implemented sync/async bridges (as well as async/sync bridges) successfully, so I don't mind checking your settings, particularly I am interested in the settings within the Module tab of the JMS receiver. I can then compare to mine if you'd like. Also if you can let me know what underlying queuing system in that target system (e.g. MQSeries?) that would be great.
Regards,
Keith

JDBC Async-Sync bridge does not work

Hi folks.
I read the how to guide How To Realize a sync-async and async-sync bridge within the Adapter Framework and I found some tips at SDN (i.e File - RFC - File without a BPM - Possible from SP 19.) . So on, I created a scenario JDBC<=>SOAP.
My scenario:
1 JDBC adapter sends an async request to SOAP
2 SOAP creates an object in its system and then sends a sync confirmation response to the sender (async JDBC adapter Receiver)
Module Tab of JDBC Sender
Processing Sequence
AF_Modules/RequestResponseBean 1
CallSapAdapter 2
AF_Modules/ResponseOnewayBean 3
Module Configuration
1 passThrough true
3 adapterNamespace http://sap.com/xi/XI/System
3 adapterType JDBC
3 receiverChannel JDBC_Object_Receiver
3 receiverService Legacy_Service
The problem is the scenario works fine until an error is detected on communication channel (Receiver). Any kind of error, as communication problem, insert/update problem or procedure types problem. When this thing happens, communication channel (Sender) posts the next message and a persist error appears, like that
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="PERSIST">MSGGUID_EXISTING</SAP:Code>
<SAP:Stack>Message ID XXXX for pipeline CENTRAL, version already exists in system</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
After this, all the next messages remain at "Processing started".
This persist error message becomes constant in the system. It is executed once an hour approximately.
I have already tried solving this problem deleting the adapter and recreated it again, but the behavior remains the same.
This is the SOAP Header Main
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>SystemError</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>6F5A54B3-96DF-C744-8BF6-A4D4B9289C5D</SAP:MessageId>
<SAP:RefToMessageId>F6BC6270-D94A-11DB-B6D0-00188B40F2CF</SAP:RefToMessageId>
<SAP:TimeSent>2007-03-23T14:31:30Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service />
<SAP:Interface namespace="" />
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>VUC</SAP:Service>
<SAP:Interface namespace="http://oesp0115/xi/webservices">Cliente_THOR_OB</SAP:Interface>
</SAP:Receiver>
<SAP:Interface namespace="http://oesp0115/xi/webservices">Cliente_THOR_OB</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>BestEffort</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="PERSIST">MSGGUID_EXISTING</SAP:Code>
<SAP:P1>F6BC6270D94A11DBB6D000188B40F2CF</SAP:P1>
<SAP:P2>CENTRAL</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message ID F6BC6270D94A11DBB6D000188B40F2CF for pipeline CENTRAL, version already exists in system</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2007-03-23T14:31:30Z" wasRead="false">
<SAP:Engine type="AE">af.xid.oesp0115</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
<SAP:MessageId>F6BC6270-D94A-11DB-B6D0-00188B40F2CF</SAP:MessageId>
<SAP:Info />
</SAP:Hop>
- <SAP:Hop timeStamp="2007-03-23T14:31:30Z" wasRead="false">
<SAP:Engine type="IS">is.00.oesp0115</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>F6BC6270-D94A-11DB-B6D0-00188B40F2CF</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
</SAP:HopList>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20070323</SAP:Date>
<SAP:Time>113130</SAP:Time>
<SAP:Host>oesp0115</SAP:Host>
<SAP:SystemId>XID</SAP:SystemId>
<SAP:SystemNr>00</SAP:SystemNr>
<SAP:OS>Windows NT</SAP:OS>
<SAP:DB>DB6</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>023</SAP:ProcStatus>
<SAP:AdapterStatus>000</SAP:AdapterStatus>
<SAP:User>PIAFUSER</SAP:User>
<SAP:TraceLevel>1</SAP:TraceLevel>
<SAP:Logging>1</SAP:Logging>
<SAP:LogSeqNbr>000</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
<SAP:PipelineElementId />
<SAP:PipelineService />
<SAP:QIdInternal />
<SAP:CommitActor>X</SAP:CommitActor>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="001">CENTRAL</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID" />
<SAP:EOReferenceInbound type="TID" />
<SAP:EOReferenceOutbound type="TID" />
<SAP:MessageSizePayload>1304</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>3744</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>1304</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterOutbound>AENGINE</SAP:AdapterOutbound>
<SAP:InterfaceAction>INIT</SAP:InterfaceAction>
<SAP:RandomNumber>14</SAP:RandomNumber>
<SAP:AckStatus>000</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
<SAP:Sender_Agreement_GUID>56A2F666C66538F48BCD76B50034F91C</SAP:Sender_Agreement_GUID>
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="begin" host="oesp0115">20070323143130.699</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="end" host="oesp0115">20070323143130.714</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="oesp0115">20070323143130.714</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="oesp0115">20070323143130.714</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="oesp0115">20070323143130.87</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="T">Party normalization: receiver</Trace>
<Trace level="1" type="T">Receiver scheme external =</Trace>
<Trace level="1" type="T">Receiver agency external =</Trace>
<Trace level="1" type="T">Receiver party external =</Trace>
<Trace level="1" type="T">Receiver party normalized =</Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = XID</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2007-03-23T14:31:30Z BRAZIL</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE">
<Trace level="1" type="T">Message-GUID = F6BC6270D94A11DBB6D000188B40F2CF</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = BE</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
- <Trace level="1" type="B" name="interface activity determination">
<Trace level="1" type="T">Version 000</Trace>
<Trace level="1" type="T">Message status 000</Trace>
<Trace level="1" type="T">Interface action INIT</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">Message type BEST EFFORT. -> No determination</Trace>
<Trace level="1" type="T">Set interface action INIT into *MAST*</Trace>
</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST">
- <Trace level="1" type="B" name="interface activity determination">
<Trace level="1" type="T">Version 000</Trace>
<Trace level="1" type="T">Message status 000</Trace>
<Trace level="1" type="T">Interface action INIT</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">Message type BEST EFFORT. -> No determination</Trace>
<Trace level="1" type="T">Set interface action INIT into *MAST*</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="T">SystemError message generated. Guid: 6F5A54B396DFC7448BF6A4D4B9289C5D</Trace>
<Trace level="1" type="T">Error during execution of message : F6BC6270D94A11DBB6D000188B40F2CF</Trace>
<Trace level="1" type="T">ApplicationMessage was (=RefToMsgId): F6BC6270D94A11DBB6D000188B40F2CF</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
- <Trace level="1" type="B" name="interface activity determination">
<Trace level="1" type="T">Version 000</Trace>
<Trace level="1" type="T">Message status 000</Trace>
<Trace level="1" type="T">Interface action INIT</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">Message type BEST EFFORT. -> No determination</Trace>
<Trace level="1" type="T">Set interface action INIT into MAST</Trace>
</Trace>
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
<SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7" />
</SOAP:Body>
</SOAP:Envelope>
Someone can help me?
Regards
Rafael

Hey Rafael,
I've heard of ur problem by Carol Garcia.
I still think the problem was related to the fact that you were commiting the work at JDBC adapter, even though your DB (it was Oracle, right?) supports internal commit. I do aggree that this scenario should work for non-commiting DBs, though. Thus it is a bug, and the note is relevant.
Anyway, did you try to commit the work at DB side? I think it should have resolved your case (even though the bug would still exist, but it would not impact you).
Regards,
Henrique.

Hi, Can you help me I am running an iMac 10.7.5 and iPad 6.0.1 and a macair10.8.2. iCloud is syncing emails and notes but not photos. Photo streaming is switched on on the iMac. what do I need to do to stream photos?

Hi, Can you help me I am running an iMac 10.7.5 and iPad 6.0.1 and a macair10.8.2. iCloud is syncing emails and notes but not photos. Photo streaming is switched on on the iMac. what do I need to do to stream photos?

Hi you have basicly 2 Options.
1 -if you Switch One fotostream on all 3 devices of yours which are working on the same apple id -all Fotos you Take with your iPad will be synchronized via icloud to the other 2 decvices ( w-lan and battery depending).
2- If you select foots or a whole album in iPhoto on your air or iMac and choose than puplish --> fotostream --> new or existing event you can key in a friends mail. If this friend has iCloud and iPhoto ( for iMac or MacBook ) and click on the link in the email it will download this fotos in the fotostream section in iPhoto. If he has a iPad, iPhone,... It will do it in the foto app and if he doesn't have a iCloud account at all and you choose "public web site" while publishing he can see your fotostream on a website.

Ical not publishing to dotmac--new information

Hello, I have been having a hard time with icalendar not publishing on dotmac. It started happening suddenly on my upgrade to 10.5.2.
The dotmac support people have been responding to my inquiries with the following suggestions (eached bumped to a higher level):
1) unpublish and republish--nope doesn't work
2) corrupted file, remake the calendar (which means re enter every entry)
3) the most recent is that my file size (1.9 mbytes) can't be published on ical.
Has anyone heard this before? It is news to me, and google and forum searches have not indication of a limit to ical file sizes for dotmac publication.
Now it seems my choices are:
1) Try to find a way to bulk delete old events (there have been some messed up syncs with missing sync that have created a lot of repeated events). There are literally thousands of individual events that have to be deleted over the 5 years I have been using ical.
2) Re enter my dates in a new calendar going forward and publish that new calendar. Frankly, that seems easiest, but I have to admit being peeved at the undocumented file limit.
It is not a matter of my idisk size or anything like that. According to the tech " and can see that it has a file size of 2 MB. I'm sorry, but your calendar is too large to be rendered on a web browser. iCal publishing is intended primarily for personal use, and not as a means of publishing such a large and complex schedule.
I'm very sorry for any inconvenience this may cause. To decrease the size and complexity of your calendars, you might consider decreasing the event repetition, or splitting the events from one calendar into several smaller calendars."
So, anyone have any pointers?

I'm also having this problem. Lots of things seem to be broken in 10.5.5. I see that iCal last published my calendar in August 2008. Spotlight no longer seems to be indexing iPhoto. I wonder what else doesn't work. Most aggravating is that Apple never seems to acknowledge these problems. As mysteriously as they came, they might go away. It just works => That's just the way it works!

Dynamic configuration in Sync/Async bridge in JMS

Hi
Scenario:
Portal sending request to JMS MQ and getting Response using sync/Async Bridge.
I have to written a UDF which will capture the value for cust_uid from request mapping and store it in dynamic configuration
And when the response comes from JMS MQu2026.this value gets populated in response mapping.
I have tested the UDF in a dummy Soap2rfc scenario and its working fine.
But when used in Sync/Async Bridge, the dynamic configuration fails.
For Sync/Async Bridge, there are 2 channels 1) Sender JMS 2) receiver JMS.
The synchronous request is converted to an asynchronous request in the module processor and sent.
The asynchronous system sends a response to a sender adapter. In the module processor of the sender adapter, this response is forwarded to the module processor of the original receiver adapter, where it is sent as a synchronous response of the waiting synchronous request.
Please suggest
Regards
Abhijit

Hi Abhijit,
Okay, so your data extraction/insertion is working fine for a simple synchronous request responser call.
I suppose this is working fine because your receiver adapter copies some part of the request message (at least the dc header) to the response message. (But I don't think this always works for all the adapter types). It is not working for the sync-async bridge because there are two unrelated messages in this case.
In order to copy the dc header from the first message to the second message, I think you can use the DynamicConfiguraitionBean module to store the dc header value in the module data and use this module again to recover it and set it to the second message. The whole process is somewhat complicated, but I will sketch the approach below.
First, let's call the first use of DCB the store step and the second the recover step. These store and recover steps must take place in the same module sequence so that they can use the module data to pass data from the first message to the second message. Furthermore, the store step must occur after the cust_id value is extracted into the dc header. So, your configuration must be placed in the receiver adapter side. Assuming the request message with the filled dc header coming into the module sequence, the first DCB module can be placed before the ROB module to store the dc header value in the module data. And the second DCB module can be placed after the WRB module to recover the dc header value from the module data and set it the dc header of the response message.
I hope this will work.
Regards, Yza

Sync/Async communication in JMS adapter without BPM

Hi,
as of SP19 XI's JMS adapter offers this new feature for Sync/Async communication through JMS Adapter modules instead of using a BPE.
Now I would be interested to know if anybody has already successfully used this feature especially using WebSphere MQ as a JMS Provider (preferredly in the mode JMS Compliant: WebSphere MQ (non-JMS)).
I experienced some issues with the XI Message ID being used as the JMS Correlation ID which is then mapped to the MQ Correlation ID being truncated after 24 characters. So I don't exactly know whether this is due to wrong setup or some general issues with this messaging system.
Please let me know if you have any experiences at all with this new feature (please do not just post links to the following blogs, which I have thoroughly studied as well as the How-to Guide concerning this topic)
/people/venkataramanan.parameswaran/blog/2007/01/18/syncasync-communication-in-jms-adapter-without-bpm-sp19
/people/sudheer.babu2/blog/2007/01/18/asyncsync-communication-using-jms-adapter-without-bpm-sp-19
thanks & regards,
Peter

Hi Peter,
we working on the same Problem. Using IBM Websphere MQ as JMS Provider for the new feature: sync/async bridge without BPE.
we switched on a high level trace for the adapter framework and saw a problem in the receiving Object of the JMS correlation id. The notify bean receives the JMS correlationid in hex format. so the beans have two different correlations, which could not find together.
did you have any solution to get this new feature works with IBM Websphere ?
thanks
joachim

Sync/Async brdige error in BPM

Hi,
I am working on RFC-TO-Webservice scenario(Synchronous) and I am using the BPM in this scenario.
In BPM just I have used 2 steps.
Receive - Opened Sync/Async bridge
Send - Synchrouns step
Send - Cloase the Receive step
Send - Asynchrous send step (to send the response to the file...).
When I sent my RFC message from R/3 I am getting following error.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">PL_TIMEOUT</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Timeout condition of pipeline reached</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
I am using PI 7.0 SP13 is why I am not able to receive the Sync message in BPM...I have created the abstract interface based on RFC...getting the first message itself Timeout error.
I am trying to use Sync/Asnc bridge in BPM. First message itself PL_TIMEOUT error..bpm is not able to receive my rfc request...
I need help on this...do I need to do any settings in WEBAS level..I did Timeout setting in SXMB_ADM.
Regards,
Venu.

hi,
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken]
check this blog..and same thing I did in my scenario
my scenario is RFC-TO-Webservice.
Sync/Async bridge can't we use like this ...Receiver step(open sync/async)-> Send(Synchronous)-Send(Close sync bridge)....that way can't we use ...
I am not able to receive the RFC request itself inside my BPM first step...getting the Timeout error.
But when I use the RECEIVE STEP with Asynchronous mode..I am able to receive the message inside my bpm.Incase of Synchronous I am not able to receive the message..
I am working PI 7.0 and SP13..did any body worked this version...
Thanks,
venu.

Getting Time-Out Error in Sync-Async Bridge

Hi All,
My IP has a Sync-Async Bridge. I have a fork, two senders, two switchs and a transformation step inside the bridge.
If XI takes much time to process the IP, the send step that closes sync-async bridge is not waiting for the message after a particular period and throws time out error to the sender.
Is it possible to increase the waiting time for sync-async bridge?
This IP works correctly 8 out of 10 times. Sometimes the message is sitting permenantly in the queue(smq2) and gives me system failure error.
Can u tell me why this problem happening?
Thanks & Regards,
Senthil.

Dear Michal/Senthil,
Can you pl clear a confusion that i have had for ages...
suppose there is a sync/async bridge ( i understand that it is used for sync business system too async BS communcation )
where we have 4 steps
sync receive - > async send -> async receive -> sync send..
i do understand that async send and async receive are combined through correlation
but i do not understand how do they work..
i mean when async send say send a file to a target system...does async receive reads a file from the same folder based on the corelation or wat...
basically can you pls explain me how do the steps 2 and 3 above work
Edited by: Tarang Shah on Mar 3, 2009 12:51 PM

Need help with Sync/Async BPM Scenario

I have an R/3 RFC -> XI -> HTTP (to vendor A) scenario that is working fine. It is a totally synchronous call event. The Integration Directory pieces sit in a scenario named HotkeyOutbound.
Now I need to create a process for RFC -> XI -> HTTP (to vendor Panduit). The R/3 RFC is the same sender, but vendor Panduit only supports an asynchronous HTTP connection. I followed the Sriram Vasudevan weblog on Sync/Async Bridge and created my BPM. I am stuck on trying to determine what to set up in the Integration Directory.
First off, should I be able to use the same HotkeyOutbound scenario as with vendor A so all hotkey stuff can stay together? Or do I have to create a new scenario with a copy of the R/3 business system for the sender? I moved forward with a new scenario (PanduitHotkeyOutbound).
I also need to know how many config Agreements and Determinations to use. The image at http://webpages.charter.net/kpwendel/keith1.html shows what I have so far. Which are not needed? What is missing?
And I tried setting up an HTTP communication channel for outbound async to vendor Panduit and another for inbound async from vendor Panduit. XI won't let me set up a sender HTTP channel. Why not?
Thank you in advance.

I have yet to figure this out, and probably need to go back to my Integration Repository setup since my problems may start there. This screenshot shows my Repository objects.
http://webpages.charter.net/kpwendel/intProcess.jpg
HELP! These are the steps I took, with questions embedded.
(1) Created data type and message type for xml document (note that same format is used for request and reply).
(2) Created PANRequestAbstractInterfaceSync (abstract and sync) for first part of Integration Process. Should the input message be the RFC or XML message type?
(3) Created PANRequestAbstractInterfaceAsync (abstract and async) for 2nd part of Integration Process.
(4) Created PANResponseToBPM_MessageInterface (outbound async) for interface back into XI from partner. Is this needed?
(5) Created PANHotkeySync_to_Async_IntProc Integration Process to handle sync to async bridge.
- Wondering why PANRequestAbstractInterfaceAsync is the only message interface available when I make container object (PANMessage)?
(6) Created two Message Mappings to handle RFC data to XML mappings (outbound RFC-> XML and inbound XML -> RFC).
(7) Created Interface Mapping that includes both the Request and Response message mapping programs from step six. Source is the RFC and Target is PANRequestAbstractInterfaceSync.
- Do I need another interface mapping with Source being PANRequestAbstractInterfaceAsync and Target being the RFC?
Link to these steps and app diagram:
http://webpages.charter.net/kpwendel/PAN_Hotkey_Diagram.jpg
Thank you very much for your time.

Correlation issue in JMS adapter - SYNC/ASYNC scenario without BPM

Hi,
I am working on a SYNC/ASYNC scenario with JMS adapter without using BPM. My scenario is SOAP<>PI>JMS. I configured the interface as below:
1. SOAP Sender channel
2. JMS Receiver Channel writing to Queue A.
 Module used: a. RequestOneWayBean
 b. WaitResponseBean
 Correlation Settings:
 a. Set JMS Correlation ID to "XI Message ID"
 b. Store JMS CorrelationID of request (Checked)
 c. Set JMS Property to "JMS Correlation Id"
 d. Value = "XI MEssage ID"
3. JMS Sender channel reading from queue B ( I am exporting the message from queue A and importing into queue B)
 Module used: a. NotifyResponseBean
 Correlation Settings:
 a. Set XI MEssage Id to "GUID"
 b. Set XI Conversation ID to "Stored JMS COrrelationID of Request"
I can see the cid in the message from queue A. But I observed thhat the header format of the message in Queue A is "MQSTR".
ISSUE:
1. While writing the message to queue A, below adapter log details(part b) concerned me:
 a. Message '8747a7c2-2b06-11df-8055-005056a70ed6' successfully processed by channel
 b. Could not create acknowledgements for message '8747a7c2-2b06-11df-8055-005056a70ed6'
I am not sure why I am receiving the message that " could not create acknowledgements"
2. While reading the message from the sender channel,I consistently get the error message as below:
 a. XI message ID corresponding to JMS message with ID 'ID:414d51205341504449442e514d202020c67b954b20005602'
 will be created as a new GUID with value '21bca916-424f-41f6-3347-c71090392b58'
 b. Error while processing message '21bca916-424f-41f6-3347-c71090392b58'; detailed error description:
 com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: found no correlation ID: RecoverableException:
 found no correlation ID at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:105) ...
Below are the blogs which I have already gone through:
1. JMS Synchronous Scenario without BPM - Correlation Settings and Transactional JMS Session
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b028f6f6-7da5-2a10-19bd-cf322cf5ae7b
2. Note: 1086303
3. Sync / Async Bridge without BPM
In the note, they mentioned something about header being "MQRFH2". BUt in our case, the header is "MSSTR". Not sure whether it makes any difference.
Please help.
Edited by: GP on Mar 9, 2010 4:24 AM

Hi,
detailed error description:
com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: found no correlation ID: RecoverableException:
found no correlation ID at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:105) ...
This error would generally arose when there are multiple messages, got stuck in the outbound queue. Try to stop both the sender and receiver JMS comunication channels and clear both the inbound and outbound queues.
Once all the messages in the queue are cleraed, try posting the message again.
Regards,
Swetha.

Using WAIT step in Sync/Async Bridge

I am using a sync/async bridge and placed a 1 minute wait step in between my async send and async reply. When I test my process, the async reply comes in but then my 1 minute wait eventually times out and gives me an error. Can someone guide me in fixing this BPM design (which steps to add and how)?
http://webpages.charter.net/kpwendel/bpm_with_wait.jpg
I would like it to stop waiting once the async reply comes in and not timeout. If the 1 minute mark comes and a reply never came in, it would also be nice to send back an error message.
Thanks!

I pulled my WAIT task and had this scenario working a week ago. I have not made any changes, but now my inbound replies to close the BPM and link up to the request are not "linking". The request is eventually timing out even though the reply with a good correlation id comes in successfully. Any suggestions?
UPDATE: I went through my objects in the IB:Config and resaved/activated them and now it is working. Don't know what messed them up in the first place.
Message was edited by: Keith Wendel

Sync/Async bridge via JMS with FAULT messages

Hello all, 
I set up a sync/async bridge scenario with using of JMS communication channel (SAP - JMSReceiverCC - JMSServer and application - JMSSenderCC - SAP). The normal communication works fine. 
But what we can not solve is the Fault Message handling. If there is a application error behind the JMS, a fault message is generated instead of proper application response and sent back to XI. Without any additional setup of JMS Sender CC the processing of the message ends with "MAPPING - EXCEPTION_DURING_EXECUTE", because normal "response mapping" is executed instead of "fault message mapping". This is correct behavior without any discussion. 
[SAPhelp|http://help.sap.com/saphelp_nw70/helpdata/en/45/202845de34072ce10000000a155369/frameset.htm] says that there are 2 module parameters to be set : fault, faultNamespace. The description is rather vague, so let's see, what the "NotifyResponseBean" does, when parameters fault/faultNamespace are filled: 
<pre>if(fault != null && faultNamespace != null)
if(faultNamespace.equals("http://sap.com/xi/XI/System"))
 ((XIMessage)message1).setMessageClass(MessageClass.SYSTEM_ERROR);
 ((XIMessage)message1).setError(fault, "no additional information");
} else
 ((XIMessage)message1).setMessageClass(MessageClass.APPLICATION_ERROR);
 ErrorInfo errorinfo = message1.createErrorInfo();
 errorinfo.setAttribute("ApplicationFaultInterface", fault);
 errorinfo.setAttribute("ApplicationFaultInterfaceNamespace", faultNamespace);
 errorinfo.setAttribute("ErrorCode", fault);
 errorinfo.setAttribute("AdditionalErrorText", "no additional information");
 message1.setErrorInfo(errorinfo);
} else
((XIMessage)message1).setMessageClass(MessageClass.APPLICATION_RESPONSE);
}</pre> 
The code is pretty straight forward so one could assume, that it's the name and namespace of inbound synchronnous message interface what is supposed to be filled in the values of each parameter. And from that kind of information SAP XI can evolve how to handle the response, actually the fault. 
Unfortunatelly the real situation is different - every time the fault message is generated and sent back to XI, the response is correctly corelated with the request message, "WaitResponseBean" and "NotifyResponseBean" are finished correctly and the processing crashes in messaging class on following exception: 
java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:592) at
com.sap.aii.messaging.mo.MessageContext.setAttribute(MessageContext.java:140) at
com.sap.aii.adapter.xi.ms.XIMessage.updateHeaders(XIMessage.java:4244) at
com.sap.aii.adapter.xi.ms.XIMessage.getTransportHeaders(XIMessage.java:570) at
com.sap.aii.af.ra.ms.impl.ServerConnectionImpl.request(ServerConnectionImpl.java:212) at
com.sap.aii.af.ra.ms.impl.core.transport.http.MessagingServlet.doPost(MessagingServlet.java:337) at ...
 
Is there anyone, who can put more light on JMS sync/async bridge fault handling ???
 
Thank you ... 
Regards
Tomas

Hello again,
I proceed in investigation little more, but the main problem has not been solved. I found that the problem is not even in WaitResponseBean (placed in JMCReceiverCC). This bean is woken up properly on base of proper CorrelationID. See the log:
2009-10-15 11:00:33 Success WRB: entering WaitResponseBean
2009-10-15 11:00:33 Success WRB: retrieving the message for f1ea1fc0-b96d-11de-9b68-00144f4acd86 ...
2009-10-15 11:00:46 Success WRB: retrieved the message: ApplicationError
2009-10-15 11:00:46 Success WRB: leaving WaitResponseBean
I think, that the problem is somewhere within main messaging functionality. I suppose that on base of exception message:
com.sap.aii.messaging.mo.MessageContext.setAttribute(MessageContext.java:140) at
which is generated.
Any ideas or comments ?
Thank you in advance.
Regards
Tomas

Sync/async wsdl not published

Similar Messages

Maybe you are looking for