Re: [ebxmlms-develop] CPP/A integration

[Marcus W. <mar...@ho...>]

Thanks for your quick reply. =3DD

=20

Is seems those parameters are message driven by the "FromParty" (MSH =
stub for Hermes implementation), right?=20

=20

Actually I'm now looking at the relationship between CPP/A and ebMS spec =
(for details, please view Appendix F of CPP/A).  In CPP/A, those =
parameters can be the following values.

1.      duplicateElimination               =3D[ always |  never |  =
perMessage]   =20

2.      ackRequested                          =3D[ always |  never |  =
perMessage]   =20

3.      messageOrderSemantics        =3D[ always |  never |  perMessage] =
 =20

4.      isNonRepudiationRequired   =3D [ Guaranteed |  NotGuaranteed]  =20

=20

"ToParty MSH" needs to validate the incoming message if the first three =
parameters in CPA are set to "always=A1=A8 or =A1=A7never=A1=A8.  Can we =
set something like that in the application context of the "ToParty =
Hermes" so that it can check against the incoming message?

=20

Marcus Wong

  ----- Original Message -----=20
  From: Gait Boxman=20
  To: ebx...@li...=20
  Sent: Tuesday, January 13, 2004 3:50 PM
  Subject: Re: [ebxmlms-develop] CPP/A integration


  Hi Marcus,

  Just a first reply, others might jump in with more detail :-)

  Hermes is based on ebXML Messaging Specification 2.0, we don't =
directly integrate with CPP/A, but the properties you mention are =
actually in ebMS as well.
  Let's see:
  1. duplicateElimination - yes, you can set the duplicateElimination =
flag in the message you send to tell the other MSH to eliminate =
duplicates, and Hermes listens for it.
  2. ackRequested - yes, another property you can set, and Hermes =
listens for it.
  3. message ordering is supported within a given application context =
(cpa,conversation)
  4. isNonRepReq'd - you can request the ack to be signed, which will =
give NRR, messages can also be sent signed.

  Actually, hermes uses the toMSHUrl property for the endpoint, and the =
applicationcontext for delivery to a listener of the received message. =
In the samples,the toMSHUrl may be the same as the toPartyId..
  toPartyId has to be a URI unless you specify a type (per ebMS2). =
Unfortunately, there is no authorative code list for the type parameter, =
but "DUNS" might work well for you. In the code where you add the =
toPartyID, simply add the type string as an extra parameter to your =
call.

  For asynchronous replies, I believe Hermes currently relies on (one =
of) the fromPartyId(s) of the original message to hold the MSH URL to =
send the reply to. Work is on the way to remove this dependency..
    ----- Original Message -----=20
    From: Marcus Wong=20
    To: ebx...@li...=20
    Sent: Tuesday, January 13, 2004 8:16 AM
    Subject: [ebxmlms-develop] CPP/A integration




    Dear all,=20

    =20

    I=A1=A6m new to Hermes.  I=A1=A6ve some questions about CPP/A =
integration.

    From the release note 0931, it shows that Hermes supporting =
syncReplyMode (mshSignalOnly and none), how about the following =
attributes in CPP/A?

    =20

    1.      duplicateElimination=20

    2.      ackRequested

    3.      messageOrderSemantics

    4.      isNonRepudiationRequired

    =20

    =20

    Also, how to define the end point of the message?  I found that =
Hermes is using the first toParty value when posting the ebxml to =
another MSH.  Can we set the toParty value as a logical name (e.g. DUNS =
number) instead of an URL?

    =20

    =20

    =20

    Regards,

    Marcus Wong =20