|
From: Patrick Y. <kc...@ce...> - 2004-03-30 03:55:52
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> You can try to call the following method in Request object:<br> EbxmlMessage receive(string messageid);<br> <br> Sorry for our poor documentation. :-)<br> <br> Regards, -Patrick<br> <br> <br> Mayne, Peter wrote:<br> <blockquote cite="mid...@s-..." type="cite"> <meta http-equiv="Content-Type" content="text/html; "> <meta name="Generator" content="MS Exchange Server version 5.5.2654.45"> <title>Message retrieval API</title> <p><font size="2">My MSH back end has a database of destinations for messages. For instance, incoming purchase orders are delivered to A , whereas incoming remittance notices are sent to B.</font></p> <p><font size="2">Now, suppose I send an invoice, but there is an error in delivery because the other end is down. Hermes will do the right thing and send a delivery error message to my back end. However, all I know about the message is that it is an error message, so I don't know whether I should notify A or B. Obviously, I need to keep some state, so I can look at the RefMessageId, figure out what kind of message the error refers to, and send the notification to the right place.</font></p> <p><font size="2">Hermes already keeps the state I need, since it maintains a database of all the messages that have passed through the MSH. Unfortunately, I can't see any way of officially accessing this database.</font></p> <p><font size="2">Unofficially, I could directly query the Hermes database, but a database which is accessible from the MSH server may or may not be accessible from my back end. Certainly, the MSH repository is definitely not accessible from my back end.</font></p> <p><font size="2">In summary, are there plans for an API to query the message database, so I can do things like retrieve a particular message given a messageId?</font></p> <p><font size="2">PJDM</font> <br> <font size="2">-- </font> <br> <font size="2">Peter Mayne</font> <br> <font size="2">Technology Consultant</font> <br> <font size="2">Spherion Technology Solutions</font> <br> <font size="2">Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602</font> <br> <font size="2">T: 61 2 62689727 F: 61 2 62689777</font> </p> <!--[object_id=#ap.spherion.com#]--> <p align="left"> </p> <p align="left"><font face="Tahoma" size="2"><font color="#0000ff">The information contained in this email and any attachments to it:</font></font></p> <p align="left"><font face="Tahoma" size="2"><font color="#0000ff">(a) may be confidential and if you are not the intended recipient, any interference with, <br> use, disclosure or copying of this material is unauthorised and prohibited; and</font></font></p> <p align="left"><font face="Tahoma" size="2"><font color="#0000ff">(b) may contain personal information of the recipient and/or the sender as defined <br> under the Privacy Act 1988 (Cth). Consent is hereby given by the recipient(s) to <br> collect, hold and use such information and any personal information contained in a <br> response to this email, for any reasonable purpose in the ordinary course of <br> Spherion's <br> business, including forwarding this email internally or disclosing it to a third party. All <br> personal information collected by Spherion will be handled in accordance with <br> Spherion's Privacy Policy. If you have received this email in error, please notify the <br> sender and delete it.</font></font></p> <p align="left"><font face="Tahoma" size="2"><font color="#0000ff">(c) you agree not to employ or arrange employment for any candidate(s) supplied in <br> this email and any attachments without first entering into a contractual agreement with <br> Spherion. You further agree not to divulge any information contained in this document <br> to any person(s) or entities without the express permission of Spherion.<br> </font></font></p> </blockquote> <br> </body> </html> |