RE: [dss-x] JMS transport binding

["Pim van der Eijk" <pvde@sonnenglanz.net>]

Hi Andreas,

The interface could be really simple, one in-queue for requests and one
out-queue for responses. Four if separate queues are used for signing and
verification. The DSS XML documents are transmitted as TextMessage payloads.
For correlation the JMSMessageId and JMSCorrelationId should be set, based
on the DSS RequestID.  JMS has no payload container like MIME, so the
document data should always be inline or use a file URI to point to some
shared disk space.

Pim

-----Original Message-----
From: kuehne@trustable.de [mailto:kuehne@trustable.de] 
Sent: 09 December 2008 20:59
To: Pim van der Eijk
Cc: 'dss-x'
Subject: Re: [dss-x] JMS transport binding

Hi Pim,

JMS binding sounds interesting, especially for the intranet integration
application. In our implementation we started with full blown secured SOAP
implementation. But a JMS implementation sounds like a much simplier task.

Can you supply some information how the request / response data are binded
to the JMS call ?

Greetings

Andreas
> Hello,
>
> A customer I am working with is using JMS (as interface to Oracle's 
> Advanced Queuing to be precise) as transport protocol for DSS.  For 
> interoperability reasons (this project is currently using a homegrown 
> DSS implementation but is likely to want to move to a supported 
> product over time) I would like to know if:
> (i)   anyone else is aware of interest in (or even practical use of) DSS
> over JMS?
> (ii)  people feel it is likely that current/future DSS implementations 
> will want support DSS?
> (iii) there would be interest in a standard profile for DSS over JMS 
> (and derivatives like AQ ..)
>
> Where the ebXML profile is really about cross-enterprise (B2B/G2G) 
> environments, this profile would support the enterprise (EAI) 
> environment where queuing interfaces are very common due to the 
> reliability and scalability of these interfaces.  Potential 
> applications are (high volume) document scanners, document management 
> systems, archiving systems etc. that want to interface to a DSS service.
>
> Right now in this project this is a very simple interface, but there 
> are issues like e.g. handling attachments that a profile could help 
> define and standardize.
>
> Pim
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that 
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>
>
>   


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php