| Author |
Message
|
| drgincbia |
 Posted: Mon Apr 12, 2004 6:37 am Post subject: WebClient Bundling |
 |
|
Apprentice
Joined: 23 Dec 2003
Posts: 35
Location: Omaha NE
|
It is our understanding that the MQ Workflow WebClient is tied to the Runtime Database AND there can only be one WebClient per runtime database. Is that true?
Currently we have one business application that is deployed in the same JVM as the WebClient. However, to minimize impact with future applications, we want to have each application and the WebClient in their own JVMs so when any application area deploys new code, the other applications and WebClient are not brought down and restarted also. We worked with IBM and learned how to code for the multiiple JVM solution.
The current application area does not want to recode their application for multiple JVM's, but would like to bundle the WebClient within their application, to be deployed together. Can each workflow application bundle the WebClient into their application .ear (each bundle in their own JVM) and yet access the same Runtime Database? If not, are there any alternatives for customizing their own web client (not extending MQ Workflow's WebClient) without creating a separate Runtime Database? We want to provide each application area the option to use the out of the box web client, or customize the user interface.
_________________
D. Grandia |
|
| Back to top |
|
 |
| manoj |
| Posted: Mon Apr 12, 2004 7:02 am Post subject: |
|
|
Master
Joined: 30 Jan 2002
Posts: 237
Location: Virgina
|
Did you try configuring your webclient with a Queue manager
_________________
-manoj |
|
| Back to top |
|
|
| drgincbia |
| Posted: Mon Apr 12, 2004 7:54 am Post subject: |
|
|
Apprentice
Joined: 23 Dec 2003
Posts: 35
Location: Omaha NE
|
Yes we have a queue manager for the WebClient - it is on a different server than the Runtime Database.
Our WebClient is working fine today - we are trying to prepare our installation for multiple workflow web applications that do not impact each other while implementing changes.
Would you please explain what you had in mind with the question about the queue manager?
_________________
D. Grandia |
|
| Back to top |
|
|
| jmac |
| Posted: Mon Apr 12, 2004 7:58 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
You can have as many WebClients defined as you wish. The problem is that you can only use one at a time within WAS. I am not certain exactly why this is (I mean I don't know if its an MQWF deficiency or a WAS deficiency). I have several different web client configs all pointing to the same RTDB. When I need to switch I need to restart WAS, else I get the message Configuration xxxx can not be set (This is not the exact message but it is similar).
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| manoj |
| Posted: Mon Apr 12, 2004 8:04 am Post subject: |
|
|
Master
Joined: 30 Jan 2002
Posts: 237
Location: Virgina
|
What you can try is configure two webclients each having seperate queue managers and these queue managers are part of the workflow cluster.
I think it's OK to deploy these two webclients in the same application server.
i remeber i have done something like this when i was researching...
_________________
-manoj |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Apr 12, 2004 4:22 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
What you can try is configure two webclients each having seperate queue managers and these queue managers are part of the workflow cluster.
I think it's OK to deploy these two webclients in the same application server.
i remeber i have done something like this when i was researching...
|
I have this kind of configuration and I don't have any problem. Maybe this is the reason I was unable to understand this question (which was asked so many times). I am using
MQWF 332
WAS 4.0 |
|
| Back to top |
|
|
|
|
