|
From: Patrick Y. <kc...@ce...> - 2003-03-28 03:07:52
|
RE: [ebxmlms-develop] Setup of ApplicationContextsComment inline. =
-Patrick
----- Original Message -----=20
From: Mayne, Peter=20
To: 'ebx...@li...'=20
Sent: Friday, March 28, 2003 10:56 AM
Subject: RE: [ebxmlms-develop] Setup of ApplicationContexts
>> There's a small problem here. My listener servlet registers itself =
with Hermes in its init() method. If my=20
>> listener starts for the first time while Hermes isn't up, the =
registration won't work, and Hermes will never=20
>> know about the listener. Therefore, I've added a doGet() to my =
listener servlet which also does the=20
>> registration, so I can manually register whenever I like, just in =
case.=20
>=20
> Is there anyway to control the load sequence in app server?=20
There may be in Tomcat, but I don't know it. (If anyone does, please =
tell me.) However, consider the situation where Hermes is running on a =
server in a DMZ, and the listener is running on a different server in =
the internal network. There's definitely no way to control the load =
sequence then.
In that case, manual procedure in system maintenance should be =
enforced. An analogy is that you have to start up DB server before app =
server. There should be a startup procedure which the sequence is =
significant.
> The AppContext registered (through Request object) specifies which =
kind of messages you want to=20
> receive. You can use that Request object to send out any messages. =
The AppContexts of those sent=20
> messages are not necessariliy the same as the one you registered.=20
But what if I don't want to receive any messages? I have a permanent =
listener running, registered for everything with ApplicationContext("*", =
"*", "*", "*"). Messages are sent by a separate application which starts =
up, sends the message, and finishes. I obviously don't want the sending =
application to register as a listener, because I already have a =
listener, and the sending application only runs when a message is sent.
Can I pass a null ApplicationContext or MessageListener to Request to =
not register as a MessageListener, or should I use an ApplicationContext =
with a CPAId and/or conversationId and/or service and/or action that =
will (hopefully) never be used in a real message?
Under the current architecture, you have to use an AppContext which is =
never be used in a real message for sending. We do have an alternative: =
unregistration of app context. But, I think, if you do unregistration =
everytime you sent a message. The loading to Hermes will be =
unnecessarily high.
PJDM=20
--=20
Peter Mayne=20
Technology Consultant=20
Spherion Technology Solutions=20
Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602=20
T: 61 2 62689727 F: 61 2 62689777=20
The information contained in this email and any attachments to it:
(a) may be confidential and if you are not the intended recipient, any =
interference with,=20
use, disclosure or copying of this material is unauthorised and =
prohibited; and
(b) may contain personal information of the recipient and/or the sender =
as defined=20
under the Privacy Act 1988 (Cth). Consent is hereby given by the =
recipient(s) to=20
collect, hold and use such information and any personal information =
contained in a=20
response to this email, for any reasonable purpose in the ordinary =
course of=20
Spherion's=20
business, including forwarding this email internally or disclosing it to =
a third party. All=20
personal information collected by Spherion will be handled in accordance =
with=20
Spherion's Privacy Policy. If you have received this email in error, =
please notify the=20
sender and delete it.
(c) you agree not to employ or arrange employment for any candidate(s) =
supplied in=20
this email and any attachments without first entering into a contractual =
agreement with=20
Spherion. You further agree not to divulge any information contained in =
this document=20
to any person(s) or entities without the express permission of Spherion.
|