ebxmlms-general — General discussions

Re: [ebxmlms-general] Using Hermes in production....

[Ronald v. K. <rtv...@xs...>]

3000 documents a week? Each document is? 10-100k ? Easilly. Even in one hour I think.

Ronald

Steven Herod probeerde me het volgende duidelijk te maken:
> Who out there uses Hermes in a real life production environment?
>
> If so, what kind of volumes do you process with it?
>
> In our case, we do use it in a production environment, transacting about
> 3000 documents a week.
>
> Anybody else?
>
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> ebxmlms-general mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
>


-- 
Kijk niet terug, maar kijk naar mij
Against all odds

Re: [ebxmlms-general] Axis incompatibilities

[David W. \(XML\) <da...@dr...>]

What information does AXIS need?  Can you just not create a default AXIS
delta?

DW

----- Original Message ----- 
From: "Mattias J" <mj...@ex...>
To: <ebx...@li...>
Sent: Thursday, June 16, 2005 7:45 AM
Subject: Re: [ebxmlms-general] Axis incompatibilities


> At 2005-06-16 13:25, you wrote:
> >...or also passing the full content via jms/webservice/file is possible.
> >
> >Look at how the monitor application communicates with the server. Two
> >different jvm's and it
> >works. That is the main part of the solution, two different jvm's
>
> (But then again, I cannot create the full content - i.e. the SOAP message
> with ebXML header - because of the Axis incompatibiltiy...)
>
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> ebxmlms-general mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
>

[ebxmlms-general] Using Hermes in production....

[Steven H. <sh...@te...>]

Who out there uses Hermes in a real life production environment?

If so, what kind of volumes do you process with it?

In our case, we do use it in a production environment, transacting about
3000 documents a week.

Anybody else?

Re: [ebxmlms-general] Axis incompatibilities

[Ronald v. K. <rtv...@xs...>]

If you want it in an ebxml object as in hermes, yes, you are right. But if you look at it as a
soap message you can parse it anyway you want it. We've used xmlbeans for this and created our
'own' ebxml objectmodel based on the xsd

Ronald


Mattias J probeerde me het volgende duidelijk te maken:
> At 2005-06-16 13:25, you wrote:
>>...or also passing the full content via jms/webservice/file is possible.
>>
>>Look at how the monitor application communicates with the server. Two
>>different jvm's and it
>>works. That is the main part of the solution, two different jvm's
>
> (But then again, I cannot create the full content - i.e. the SOAP message
> with ebXML header - because of the Axis incompatibiltiy...)
>
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> ebxmlms-general mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
>


-- 
Kijk niet terug, maar kijk naar mij
Against all odds

Re: [ebxmlms-general] Axis incompatibilities

[Mattias J <mj...@ex...>]

At 2005-06-16 13:25, you wrote:
>...or also passing the full content via jms/webservice/file is possible.
>
>Look at how the monitor application communicates with the server. Two 
>different jvm's and it
>works. That is the main part of the solution, two different jvm's

(But then again, I cannot create the full content - i.e. the SOAP message 
with ebXML header - because of the Axis incompatibiltiy...)

Re: [ebxmlms-general] Axis incompatibilities

[Ronald v. K. <rtv...@xs...>]

No, not neccesarilly. All combinations are possible.

db sharing with triggers via jms/webservice/file/... or also passing the full content via
jms/webservice/file is possible.

Look at how the monitor application communicates with the server. Two different jvm's and it
works. That is the main part of the solution, two different jvm's

Ronald


Mattias J probeerde me het volgende duidelijk te maken:
> So JMS is only used for triggering while the actual data is transferred
> elsewhere?
> That means the addressing (URL, CPA-ID, service, action) of the message
> must be handled by (or transferred to) the "second" application.
> Probably possible, but not too appealing...
>
> At 2005-06-15 17:05, you wrote:
>>Mattias,
>>
>>Yes - JMS is complicated if you are not using it already.
>>
>>I think the idea here is that both instances share the same databases, so
>>you can have a handler in the second instance triggered by a data handler
>>fromt he first instance placing the XML string object into the database.
>>
>>DW
>>
>>----- Original Message -----
>>From: "Mattias J" <mj...@ex...>
>>To: <ebx...@li...>
>>Sent: Wednesday, June 15, 2005 10:40 AM
>>Subject: Re: [ebxmlms-general] Axis incompatibilities
>>
>>
>> > Yes, but the question is how I communicate between the two instances -
>>what
>> > is their "interface". You suggested JMS, and since I am not familiar with
>> > JMS I asked what kind of message to send.
>> >
>> > You said "same as would be the case with registering a normal
>> > messagelistener in hermes", which I interpreted as an
>> > hk.hku.cecid.phoenix.message.packaging.EbxmlMessage instance object.
>> > Do you mean to send this as an XML string?
>> >
>> > At 2005-06-15 16:30, you wrote:
>> > >Mattias,
>> > >
>> > >I think you are missing the point here.
>> > >
>> > >You have two incompatible library JAR files.
>> > >
>> > >Whenever this happens you need to create two new instances (installs)
>> > >of the server.  One for each JAR file.
>> > >
>> > >Completely separate sub-directories - and so the
>> > >path settings in each case just reference the one instance.
>> > >
>> > >Then config each one on a separate port.
>> > >
>> > >DW
>> > >
>> > >----- Original Message -----
>> > >From: "Mattias J" <mj...@ex...>
>> > >To: <ebx...@li...>
>> > >Sent: Wednesday, June 15, 2005 9:58 AM
>> > >Subject: RE: [ebxmlms-general] Axis incompatibilities
>> > >
>> > >
>> > > > At 2005-06-15 15:31, you wrote:
>> > > > > > Unfortunately I have no experience with JMS. What would the
>>message
>> > >sent
>> > > > > > between the application and the Hermes client application contain?
>> > > > >
>> > > > >The same as would be the case with registering a normal
>>messagelistener
>> > >in
>> > > > >hermes.
>> > > >
>> > > > But the Hermes message listener receives a
>> > > > hk.hku.cecid.phoenix.message.packaging.EbxmlMessage...?
>> > > >
>> > > > (Besides the fact that I cannot see the meaning of the separate Hermes
>> > > > client, this will not work since I cannot produce correct EbxmlMessage
>> > > > objects in my application because of Axis).
>> > > >
>> > > >    /Mattias J
>> > > >
>> > > >
>> > > >
>> > > > -------------------------------------------------------
>> > > > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>> > > > from IBM. Find simple to follow Roadmaps, straightforward articles,
>> > > > informative Webcasts and more! Get everything you need to get up to
>> > > > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>> > > > _______________________________________________
>> > > > ebxmlms-general mailing list
>> > > > ebx...@li...
>> > > > https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
>> > > >
>> > >
>> > >
>> > >
>> > >-------------------------------------------------------
>> > >SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>> > >from IBM. Find simple to follow Roadmaps, straightforward articles,
>> > >informative Webcasts and more! Get everything you need to get up to
>> > >speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>> > >_______________________________________________
>> > >ebxmlms-general mailing list
>> > >ebx...@li...
>> > >https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
>> >
>> >
>> >
>> > -------------------------------------------------------
>> > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>> > from IBM. Find simple to follow Roadmaps, straightforward articles,
>> > informative Webcasts and more! Get everything you need to get up to
>> > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>> > _______________________________________________
>> > ebxmlms-general mailing list
>> > ebx...@li...
>> > https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
>> >
>>
>>
>>
>>-------------------------------------------------------
>>SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>>from IBM. Find simple to follow Roadmaps, straightforward articles,
>>informative Webcasts and more! Get everything you need to get up to
>>speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>>_______________________________________________
>>ebxmlms-general mailing list
>>ebx...@li...
>>https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> ebxmlms-general mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
>


-- 
Kijk niet terug, maar kijk naar mij
Against all odds

Re: [ebxmlms-general] Axis incompatibilities

[Mattias J <mj...@ex...>]

So JMS is only used for triggering while the actual data is transferred 
elsewhere?
That means the addressing (URL, CPA-ID, service, action) of the message 
must be handled by (or transferred to) the "second" application.
Probably possible, but not too appealing...

At 2005-06-15 17:05, you wrote:
>Mattias,
>
>Yes - JMS is complicated if you are not using it already.
>
>I think the idea here is that both instances share the same databases, so
>you can have a handler in the second instance triggered by a data handler
>fromt he first instance placing the XML string object into the database.
>
>DW
>
>----- Original Message -----
>From: "Mattias J" <mj...@ex...>
>To: <ebx...@li...>
>Sent: Wednesday, June 15, 2005 10:40 AM
>Subject: Re: [ebxmlms-general] Axis incompatibilities
>
>
> > Yes, but the question is how I communicate between the two instances -
>what
> > is their "interface". You suggested JMS, and since I am not familiar with
> > JMS I asked what kind of message to send.
> >
> > You said "same as would be the case with registering a normal
> > messagelistener in hermes", which I interpreted as an
> > hk.hku.cecid.phoenix.message.packaging.EbxmlMessage instance object.
> > Do you mean to send this as an XML string?
> >
> > At 2005-06-15 16:30, you wrote:
> > >Mattias,
> > >
> > >I think you are missing the point here.
> > >
> > >You have two incompatible library JAR files.
> > >
> > >Whenever this happens you need to create two new instances (installs)
> > >of the server.  One for each JAR file.
> > >
> > >Completely separate sub-directories - and so the
> > >path settings in each case just reference the one instance.
> > >
> > >Then config each one on a separate port.
> > >
> > >DW
> > >
> > >----- Original Message -----
> > >From: "Mattias J" <mj...@ex...>
> > >To: <ebx...@li...>
> > >Sent: Wednesday, June 15, 2005 9:58 AM
> > >Subject: RE: [ebxmlms-general] Axis incompatibilities
> > >
> > >
> > > > At 2005-06-15 15:31, you wrote:
> > > > > > Unfortunately I have no experience with JMS. What would the
>message
> > >sent
> > > > > > between the application and the Hermes client application contain?
> > > > >
> > > > >The same as would be the case with registering a normal
>messagelistener
> > >in
> > > > >hermes.
> > > >
> > > > But the Hermes message listener receives a
> > > > hk.hku.cecid.phoenix.message.packaging.EbxmlMessage...?
> > > >
> > > > (Besides the fact that I cannot see the meaning of the separate Hermes
> > > > client, this will not work since I cannot produce correct EbxmlMessage
> > > > objects in my application because of Axis).
> > > >
> > > >    /Mattias J
> > > >
> > > >
> > > >
> > > > -------------------------------------------------------
> > > > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > > > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > > > informative Webcasts and more! Get everything you need to get up to
> > > > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > > > _______________________________________________
> > > > ebxmlms-general mailing list
> > > > ebx...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
> > > >
> > >
> > >
> > >
> > >-------------------------------------------------------
> > >SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > >from IBM. Find simple to follow Roadmaps, straightforward articles,
> > >informative Webcasts and more! Get everything you need to get up to
> > >speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > >_______________________________________________
> > >ebxmlms-general mailing list
> > >ebx...@li...
> > >https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
> >
> >
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > informative Webcasts and more! Get everything you need to get up to
> > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > _______________________________________________
> > ebxmlms-general mailing list
> > ebx...@li...
> > https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
> >
>
>
>
>-------------------------------------------------------
>SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>from IBM. Find simple to follow Roadmaps, straightforward articles,
>informative Webcasts and more! Get everything you need to get up to
>speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>_______________________________________________
>ebxmlms-general mailing list
>ebx...@li...
>https://lists.sourceforge.net/lists/listinfo/ebxmlms-general

[ebxmlms-general] MSH documentation

[<em...@og...>]

Does the MSH monitor support the Ping service as described in Section 8 of 
Message Service Spec. 2.0?  What are the Action(s) supported.  Is there 
any limitations on the MessageHeader Element i.e. Conv. ID, CPA ID, ... 
imposed by the MSH montor?

Thank you!

[ebxmlms-general] Again, unreliable execution of message handlers.

[Steven H. <sh...@te...>]

About a week ago, we had another incident of message handler not executing
on message arrival.

In this case however, it wasn't a complete failure, instead, it seemed to
take about 10 minutes between hermes receiving the file and the message
handler picking it up.

Normal behaviour has this occuring within a few seconds, however, in this
case, about 10 minute passed before the handler fired.   Our messages are
time sensitive, so this pushed the response time window outside of normal
and raised an error with our customer.

There are no log files indications of a reason for a delay,  the message
handler usually fires off within a few seconds of the message arriving.

I realise this is a little vague, but I'm wondering if anybody else has had
this experience or observed this behaviour?

Re: [ebxmlms-general] Axis incompatibilities

[David W. \(XML\) <da...@dr...>]

Mattias,

Yes - JMS is complicated if you are not using it already.

I think the idea here is that both instances share the same databases, so
you can have a handler in the second instance triggered by a data handler
fromt he first instance placing the XML string object into the database.

DW

----- Original Message ----- 
From: "Mattias J" <mj...@ex...>
To: <ebx...@li...>
Sent: Wednesday, June 15, 2005 10:40 AM
Subject: Re: [ebxmlms-general] Axis incompatibilities


> Yes, but the question is how I communicate between the two instances -
what
> is their "interface". You suggested JMS, and since I am not familiar with
> JMS I asked what kind of message to send.
>
> You said "same as would be the case with registering a normal
> messagelistener in hermes", which I interpreted as an
> hk.hku.cecid.phoenix.message.packaging.EbxmlMessage instance object.
> Do you mean to send this as an XML string?
>
> At 2005-06-15 16:30, you wrote:
> >Mattias,
> >
> >I think you are missing the point here.
> >
> >You have two incompatible library JAR files.
> >
> >Whenever this happens you need to create two new instances (installs)
> >of the server.  One for each JAR file.
> >
> >Completely separate sub-directories - and so the
> >path settings in each case just reference the one instance.
> >
> >Then config each one on a separate port.
> >
> >DW
> >
> >----- Original Message -----
> >From: "Mattias J" <mj...@ex...>
> >To: <ebx...@li...>
> >Sent: Wednesday, June 15, 2005 9:58 AM
> >Subject: RE: [ebxmlms-general] Axis incompatibilities
> >
> >
> > > At 2005-06-15 15:31, you wrote:
> > > > > Unfortunately I have no experience with JMS. What would the
message
> >sent
> > > > > between the application and the Hermes client application contain?
> > > >
> > > >The same as would be the case with registering a normal
messagelistener
> >in
> > > >hermes.
> > >
> > > But the Hermes message listener receives a
> > > hk.hku.cecid.phoenix.message.packaging.EbxmlMessage...?
> > >
> > > (Besides the fact that I cannot see the meaning of the separate Hermes
> > > client, this will not work since I cannot produce correct EbxmlMessage
> > > objects in my application because of Axis).
> > >
> > >    /Mattias J
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > > informative Webcasts and more! Get everything you need to get up to
> > > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > > _______________________________________________
> > > ebxmlms-general mailing list
> > > ebx...@li...
> > > https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
> > >
> >
> >
> >
> >-------------------------------------------------------
> >SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> >from IBM. Find simple to follow Roadmaps, straightforward articles,
> >informative Webcasts and more! Get everything you need to get up to
> >speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> >_______________________________________________
> >ebxmlms-general mailing list
> >ebx...@li...
> >https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> ebxmlms-general mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
>

Re: [ebxmlms-general] Axis incompatibilities

[Mattias J <mj...@ex...>]

Yes, but the question is how I communicate between the two instances - what 
is their "interface". You suggested JMS, and since I am not familiar with 
JMS I asked what kind of message to send.

You said "same as would be the case with registering a normal 
messagelistener in hermes", which I interpreted as an 
hk.hku.cecid.phoenix.message.packaging.EbxmlMessage instance object.
Do you mean to send this as an XML string?

At 2005-06-15 16:30, you wrote:
>Mattias,
>
>I think you are missing the point here.
>
>You have two incompatible library JAR files.
>
>Whenever this happens you need to create two new instances (installs)
>of the server.  One for each JAR file.
>
>Completely separate sub-directories - and so the
>path settings in each case just reference the one instance.
>
>Then config each one on a separate port.
>
>DW
>
>----- Original Message -----
>From: "Mattias J" <mj...@ex...>
>To: <ebx...@li...>
>Sent: Wednesday, June 15, 2005 9:58 AM
>Subject: RE: [ebxmlms-general] Axis incompatibilities
>
>
> > At 2005-06-15 15:31, you wrote:
> > > > Unfortunately I have no experience with JMS. What would the message
>sent
> > > > between the application and the Hermes client application contain?
> > >
> > >The same as would be the case with registering a normal messagelistener
>in
> > >hermes.
> >
> > But the Hermes message listener receives a
> > hk.hku.cecid.phoenix.message.packaging.EbxmlMessage...?
> >
> > (Besides the fact that I cannot see the meaning of the separate Hermes
> > client, this will not work since I cannot produce correct EbxmlMessage
> > objects in my application because of Axis).
> >
> >    /Mattias J
> >
> >
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > informative Webcasts and more! Get everything you need to get up to
> > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > _______________________________________________
> > ebxmlms-general mailing list
> > ebx...@li...
> > https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
> >
>
>
>
>-------------------------------------------------------
>SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>from IBM. Find simple to follow Roadmaps, straightforward articles,
>informative Webcasts and more! Get everything you need to get up to
>speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>_______________________________________________
>ebxmlms-general mailing list
>ebx...@li...
>https://lists.sourceforge.net/lists/listinfo/ebxmlms-general

Re: [ebxmlms-general] Axis incompatibilities

[David W. \(XML\) <da...@dr...>]

Mattias,

I think you are missing the point here.

You have two incompatible library JAR files.

Whenever this happens you need to create two new instances (installs)
of the server.  One for each JAR file.

Completely separate sub-directories - and so the
path settings in each case just reference the one instance.

Then config each one on a separate port.

DW

----- Original Message ----- 
From: "Mattias J" <mj...@ex...>
To: <ebx...@li...>
Sent: Wednesday, June 15, 2005 9:58 AM
Subject: RE: [ebxmlms-general] Axis incompatibilities


> At 2005-06-15 15:31, you wrote:
> > > Unfortunately I have no experience with JMS. What would the message
sent
> > > between the application and the Hermes client application contain?
> >
> >The same as would be the case with registering a normal messagelistener
in
> >hermes.
>
> But the Hermes message listener receives a
> hk.hku.cecid.phoenix.message.packaging.EbxmlMessage...?
>
> (Besides the fact that I cannot see the meaning of the separate Hermes
> client, this will not work since I cannot produce correct EbxmlMessage
> objects in my application because of Axis).
>
>    /Mattias J
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> ebxmlms-general mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
>

RE: [ebxmlms-general] Axis incompatibilities

[Mattias J <mj...@ex...>]

At 2005-06-15 15:31, you wrote:
> > Unfortunately I have no experience with JMS. What would the message sent
> > between the application and the Hermes client application contain?
>
>The same as would be the case with registering a normal messagelistener in 
>hermes.

But the Hermes message listener receives a 
hk.hku.cecid.phoenix.message.packaging.EbxmlMessage...?

(Besides the fact that I cannot see the meaning of the separate Hermes 
client, this will not work since I cannot produce correct EbxmlMessage 
objects in my application because of Axis).

   /Mattias J 

RE: [ebxmlms-general] Axis incompatibilities

[Ronald v. K. <rtv...@xs...>]

> Interesting thought. Even so, I think Hermes and Axis should be made
> compatible.

I agree

>
> Unfortunately I have no experience with JMS. What would the message sent
> between the application and the Hermes client application contain?

The same as would be the case with registering a normal messagelistener in hermes.

Ronald

RE: [ebxmlms-general] Axis incompatibilities

[Mattias J <mj...@ex...>]

At 2005-06-15 10:42, you wrote:
>I think what David ment was to use e.g. one tomcat instance for hermes
>and one instance for your application. You could then communicate
>between those instances in a compatible way. This is what we have done.
>
>Remote mhs <--> hermes <--> jms <--> application

Interesting thought. Even so, I think Hermes and Axis should be made 
compatible.

Unfortunately I have no experience with JMS. What would the message sent 
between the application and the Hermes client application contain?


>Works like a charm, unfortunately it never went into production but that
>is not because of us.
>
>Ronald
>
>-----Oorspronkelijk bericht-----
>Van: ebx...@li...
>[mailto:ebx...@li...] Namens Mattias J
>Verzonden: maandag 13 juni 2005 9:56
>Aan: ebx...@li...
>Onderwerp: Re: [ebxmlms-general] Axis incompatibilities
>
>That is not the problem. It is about using Axis as the SAAJ
>implementation;
>i.e. replacing saaj-ri.jar with axis.jar.
>
>I need to do this, because we have an application that responds to SOAP
>requests using Axis, so axis.jar is already there and then we also
>wanted
>to send ebXML messages from it. So adding Hermes msh.jar (with
>dependencies; but not saaj-ri.jar) for communicating with Hermes server
>creates erroneous messages, for the reasons detailed in the Axis JIRA
>entry
>below.
>
>At 2005-06-11 18:04, you wrote:
> >Can you just put up two instances of Apache - on different ports -
> >one for Axis, the other Hermes, to avoid this conflict?
> >
> >DW
> >
> >----- Original Message -----
> >From: "Mattias J" <mat...@ex...>
> >To: <ebx...@li...>
> >Sent: Saturday, June 11, 2005 1:43 AM
> >Subject: [ebxmlms-general] Axis incompatibilities
> >
> >
> > > As stated in the (currently) bottom-most post, this isn't really an
>issue
> > > for me any more, but possibly somebody want to have a look at the
> > > incompatibility between Apache Axis and Hermes. Problems arose when
>trying
> > > to send ebXML messages from an application already using Axis for
>SOAP.
> > > See http://issues.apache.org/jira/browse/AXIS-1469

RE: [ebxmlms-general] Axis incompatibilities

[R. v. K. \(Ronald\) <rv...@ab...>]

I think what David ment was to use e.g. one tomcat instance for hermes
and one instance for your application. You could then communicate
between those instances in a compatible way. This is what we have done. 

Remote mhs <--> hermes <--> jms <--> application

Works like a charm, unfortunately it never went into production but that
is not because of us.

Ronald

-----Oorspronkelijk bericht-----
Van: ebx...@li...
[mailto:ebx...@li...] Namens Mattias J
Verzonden: maandag 13 juni 2005 9:56
Aan: ebx...@li...
Onderwerp: Re: [ebxmlms-general] Axis incompatibilities

That is not the problem. It is about using Axis as the SAAJ
implementation; 
i.e. replacing saaj-ri.jar with axis.jar.

I need to do this, because we have an application that responds to SOAP 
requests using Axis, so axis.jar is already there and then we also
wanted 
to send ebXML messages from it. So adding Hermes msh.jar (with 
dependencies; but not saaj-ri.jar) for communicating with Hermes server 
creates erroneous messages, for the reasons detailed in the Axis JIRA
entry 
below.

At 2005-06-11 18:04, you wrote:
>Can you just put up two instances of Apache - on different ports -
>one for Axis, the other Hermes, to avoid this conflict?
>
>DW
>
>----- Original Message -----
>From: "Mattias J" <mat...@ex...>
>To: <ebx...@li...>
>Sent: Saturday, June 11, 2005 1:43 AM
>Subject: [ebxmlms-general] Axis incompatibilities
>
>
> > As stated in the (currently) bottom-most post, this isn't really an
issue
> > for me any more, but possibly somebody want to have a look at the
> > incompatibility between Apache Axis and Hermes. Problems arose when
trying
> > to send ebXML messages from an application already using Axis for
SOAP.
> > See http://issues.apache.org/jira/browse/AXIS-1469



-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you
shotput
a projector? How fast can you ride your desk chair down the office luge
track?
If you want to score the big prize, get to know the little guy.  
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
ebxmlms-general mailing list
ebx...@li...
https://lists.sourceforge.net/lists/listinfo/ebxmlms-general

[ebxmlms-general] Requesting Client Authentication

[Portelli, J. F <Joe...@te...>]

            Hermes' configuration file (msh.properties.xml) allows for
SSL Server and Client Authentication. I defined the entries in
<MSH>SSH<TrustedAnchor><Keystore> and enabled server authentication -
that is Hermes now authenticates other MSH's (servers) it is attempting
to set up a session with.

=20

            What I would like to know is how to activate Client
Authentication in Hermes ie how to get Hermes to initiate a remote
client authentication process.

=20

Regards

Joseph F. Portelli

Telstra Research Laboratories

* +61 (0)2 8255 3099

7 +61 (0)2 8255 3153

* 3/400 George Street, Sydney, NSW 2000

* <mailto:joe...@te...>

=20

Re: [ebxmlms-general] Axis incompatibilities

[Mattias J <mj...@ex...>]

That is not the problem. It is about using Axis as the SAAJ implementation; 
i.e. replacing saaj-ri.jar with axis.jar.

I need to do this, because we have an application that responds to SOAP 
requests using Axis, so axis.jar is already there and then we also wanted 
to send ebXML messages from it. So adding Hermes msh.jar (with 
dependencies; but not saaj-ri.jar) for communicating with Hermes server 
creates erroneous messages, for the reasons detailed in the Axis JIRA entry 
below.

At 2005-06-11 18:04, you wrote:
>Can you just put up two instances of Apache - on different ports -
>one for Axis, the other Hermes, to avoid this conflict?
>
>DW
>
>----- Original Message -----
>From: "Mattias J" <mat...@ex...>
>To: <ebx...@li...>
>Sent: Saturday, June 11, 2005 1:43 AM
>Subject: [ebxmlms-general] Axis incompatibilities
>
>
> > As stated in the (currently) bottom-most post, this isn't really an issue
> > for me any more, but possibly somebody want to have a look at the
> > incompatibility between Apache Axis and Hermes. Problems arose when trying
> > to send ebXML messages from an application already using Axis for SOAP.
> > See http://issues.apache.org/jira/browse/AXIS-1469

Re: [ebxmlms-general] Axis incompatibilities

[Ronald v. K. <rtv...@xs...>]

Yes, you could, we've done this before, albeit not for hermes. But since we use an ASP for hosting
(so basically it is not an asp but a hosting partner), we pay per a few thousand euro per month
per instance.

I think it is better to try to add the patch that is in the axis forum to hermes with a config
parameter like "use_axis_compatibility=true/false". If I find the time next week I think I can
give it a try.

Ronald


David Webber (XML) probeerde me het volgende duidelijk te maken:
> Can you just put up two instances of Apache - on different ports -
> one for Axis, the other Hermes, to avoid this conflict?
>
> DW
>
> ----- Original Message -----
> From: "Mattias J" <mat...@ex...>
> To: <ebx...@li...>
> Sent: Saturday, June 11, 2005 1:43 AM
> Subject: [ebxmlms-general] Axis incompatibilities
>
>
>> As stated in the (currently) bottom-most post, this isn't really an issue
>> for me any more, but possibly somebody want to have a look at the
>> incompatibility between Apache Axis and Hermes. Problems arose when trying
>> to send ebXML messages from an application already using Axis for SOAP.
>> See http://issues.apache.org/jira/browse/AXIS-1469
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you
> shotput
>> a projector? How fast can you ride your desk chair down the office luge
> track?
>> If you want to score the big prize, get to know the little guy.
>> Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
>> _______________________________________________
>> ebxmlms-general mailing list
>> ebx...@li...
>> https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
>>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
> a projector? How fast can you ride your desk chair down the office luge track?
> If you want to score the big prize, get to know the little guy.
> Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
> _______________________________________________
> ebxmlms-general mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
>


-- 
Kijk niet terug, maar kijk naar mij
Against all odds

Re: [ebxmlms-general] Axis incompatibilities

[David W. \(XML\) <da...@dr...>]

Can you just put up two instances of Apache - on different ports -
one for Axis, the other Hermes, to avoid this conflict?

DW

----- Original Message ----- 
From: "Mattias J" <mat...@ex...>
To: <ebx...@li...>
Sent: Saturday, June 11, 2005 1:43 AM
Subject: [ebxmlms-general] Axis incompatibilities


> As stated in the (currently) bottom-most post, this isn't really an issue
> for me any more, but possibly somebody want to have a look at the
> incompatibility between Apache Axis and Hermes. Problems arose when trying
> to send ebXML messages from an application already using Axis for SOAP.
> See http://issues.apache.org/jira/browse/AXIS-1469
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you
shotput
> a projector? How fast can you ride your desk chair down the office luge
track?
> If you want to score the big prize, get to know the little guy.
> Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
> _______________________________________________
> ebxmlms-general mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
>

[ebxmlms-general] Axis incompatibilities

[Mattias J <mat...@ex...>]

As stated in the (currently) bottom-most post, this isn't really an issue 
for me any more, but possibly somebody want to have a look at the 
incompatibility between Apache Axis and Hermes. Problems arose when trying 
to send ebXML messages from an application already using Axis for SOAP.
See http://issues.apache.org/jira/browse/AXIS-1469 

RE: [ebxmlms-general] Triggering a Incoming Listener

[Steven H. <sh...@te...>]

I probably didn't explain properly.

This is a production system, which up until last Friday was working fine.
For reasons unknown, hermes stopped executing the handler for this
particular message type causing an outage for these documents.  There were
no error logs, our client alerted us.  

Thankfully, these messages were relatively low impact.

Last night, after reading through the source code and gaining a stronger
understanding of the system, we executed the following steps:

Hermes shutdown
Apphandler shutdown
Ran the SQL: 'Trunc msh.mshconfig' 
move aside of the 'objects*' files in  '~msh/objectStore'
Start of hermes
Start of apphandler

Hermes and the app handler immediately found the 56 delayed messages and
started extracting them for handling by the rest of our system, something it
steadfastly refused to do.

We are unsure if a restart of just hermes/tomcat would have just fixed the
problem.  But removing the config and the serialised objects was undertaken
to give it an extra kick along.

The signature of the documents in the database was that hermes believed they
were 'undelivered' (that is, a c_sequencenumber of -9998, not -9999), so
they should have been found by the query that looks for undelivered
messages.  I'll will attempt to read the code further to understand where
this could have gone amiss.

-----Original Message-----
From: ebx...@li...
[mailto:ebx...@li...] On Behalf Of David
Webber (XML)
Sent: Tuesday, 7 June 2005 12:07 AM
To: ebx...@li...
Subject: Re: [ebxmlms-general] Triggering a Incoming Listener

Steven,

You have to change the default handler, also check the CPA settings in the
CPA table in Hermes.

The documentation tells you how to write your own handler - and to modify
the existing one.

See the PDF file from the freebxml.org site on the dangerous goods example.

DW

Re: [ebxmlms-general] Triggering a Incoming Listener

[David W. \(XML\) <da...@dr...>]

Steven,

You have to change the default handler, also check the CPA settings in the
CPA table in Hermes.

The documentation tells you how to write your own handler - and to modify
the existing one.

See the PDF file from the freebxml.org site on the dangerous goods example.

DW

----- Original Message ----- 
From: "Steven Herod" <sh...@te...>
To: <ebx...@li...>
Sent: Monday, June 06, 2005 3:07 AM
Subject: [ebxmlms-general] Triggering a Incoming Listener


> Hello
>
> I have a series of messages which have been received by Hermes
>
> These messages were supposed to be handled by an Incoming Listener, for
some
> reason they weren't picked up and extracted from Hermes.
>
> I have restarted the app handler that registers the listener and handles
the
> messages, but the messages still haven't been picked up.
>
> Is there away I can fool hermes into thinking message has just arrived in
> order to force it to trigger the incoming listener to handle the file?
>
> Does this make any sense?  I'm making a few guesses about how hermes works
> and I may be fundamentally wrong
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you
shotput
> a projector? How fast can you ride your desk chair down the office luge
track?
> If you want to score the big prize, get to know the little guy.
> Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
> _______________________________________________
> ebxmlms-general mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
>

RE: [ebxmlms-general] Triggering a Incoming Listener

[Steven H. <sh...@te...>]

You guys wrote it for us, but I can pass along the source code.

The symptom is that for this particular type of message, the application
handler failed to get the messages (the message type was the 'Remittance
Advice').  It worked prior to the 27th May, but didn't work for this
Friday's batch of messages.

Oddly, for other types of message (purchase orders) it works fine and has
continued to work fine, even after remittance advices's weren't getting
retreived.  (its like 1 listener stopped working out of all the ones the app
handler handles)



-----Original Message-----
From: ebx...@li...
[mailto:ebx...@li...] On Behalf Of Patrick
Yee
Sent: Monday, 6 June 2005 5:25 PM
To: ebx...@li...
Subject: Re: [ebxmlms-general] Triggering a Incoming Listener

Do you mean Hermes has received something from the other ebMS server, but
your application handler cannot get those messages from Hermes, right? If
so, would you please post some fragment of your app program so that we can
have more understanding? Thanks.
Regards, -Patrick

Steven Herod wrote:

>Hello
>
>I have a series of messages which have been received by Hermes
>
>These messages were supposed to be handled by an Incoming Listener, for 
>some reason they weren't picked up and extracted from Hermes.
>
>I have restarted the app handler that registers the listener and 
>handles the messages, but the messages still haven't been picked up.
>
>Is there away I can fool hermes into thinking message has just arrived 
>in order to force it to trigger the incoming listener to handle the file?
>
>Does this make any sense?  I'm making a few guesses about how hermes 
>works and I may be fundamentally wrong
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you 
>shotput a projector? How fast can you ride your desk chair down the office
luge track?
>If you want to score the big prize, get to know the little guy.  
>Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 
>_______________________________________________
>ebxmlms-general mailing list
>ebx...@li...
>https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
>  
>



-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you
shotput a projector? How fast can you ride your desk chair down the office
luge track?
If you want to score the big prize, get to know the little guy.  
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
ebxmlms-general mailing list
ebx...@li...
https://lists.sourceforge.net/lists/listinfo/ebxmlms-general

RE: [ebxmlms-general] Triggering a Incoming Listener

[Steven H. <sh...@te...>]

 

-----Original Message-----
From: ebx...@li...
[mailto:ebx...@li...] On Behalf Of Patrick
Yee
Sent: Monday, 6 June 2005 5:25 PM
To: ebx...@li...
Subject: Re: [ebxmlms-general] Triggering a Incoming Listener

Do you mean Hermes has received something from the other ebMS server, but
your application handler cannot get those messages from Hermes, right? If
so, would you please post some fragment of your app program so that we can
have more understanding? Thanks.
Regards, -Patrick

Steven Herod wrote:

>Hello
>
>I have a series of messages which have been received by Hermes
>
>These messages were supposed to be handled by an Incoming Listener, for 
>some reason they weren't picked up and extracted from Hermes.
>
>I have restarted the app handler that registers the listener and 
>handles the messages, but the messages still haven't been picked up.
>
>Is there away I can fool hermes into thinking message has just arrived 
>in order to force it to trigger the incoming listener to handle the file?
>
>Does this make any sense?  I'm making a few guesses about how hermes 
>works and I may be fundamentally wrong
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you 
>shotput a projector? How fast can you ride your desk chair down the office
luge track?
>If you want to score the big prize, get to know the little guy.  
>Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 
>_______________________________________________
>ebxmlms-general mailing list
>ebx...@li...
>https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
>  
>



-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you
shotput a projector? How fast can you ride your desk chair down the office
luge track?
If you want to score the big prize, get to know the little guy.  
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
ebxmlms-general mailing list
ebx...@li...
https://lists.sourceforge.net/lists/listinfo/ebxmlms-general