[WEB400] RE: WEB400 Digest, Vol 3, Issue 79

["Dupuis Vincent" <vdupuis@xxxxxxxxxxxxxx>]

Thanks for the precisions.

Vincent

----------------------------------------------------------------------

message: 1
date: Tue, 5 Apr 2005 16:35:39 -0400 
from: "Gibbons, Michael" <bmis04@xxxxxxxxxxxxxxx>
subject: RE: [WEB400] Who Uses WebSphere Express?

In our case we wanted to webface a menu system. The deployment issue would
be if we webfaced the entire menu system as one project it would be a very
large EAR deployed and the entire system (EAR) would have to brought down to
install updates. If we did each menu option as it's own project it would be
many EAR files but have the ability to take down one option to install an
update. This leads to the parameter issue because I would be going between
different webfacing projects and lose "state". 

The profile issue is that a webfacing request wants the requesting profile
to say limit capabilities *YES and initial program QQINVOKER. This doesn't
work for a power user like a programmer. They are limit capabilities *NO.
Also, we have different initial programs or routing data to get to a
different subsystem for 5250 sessions. There is a slight workaround in that
you can determine the request to be web facing or 5250 but if webfacing is
the first request it locks the message queue and when you log on to a 5250
session you do not get your messages because the webfacing project locked
it. 

Hope this helps!

-----Original Message-----
From: Dupuis Vincent [mailto:vdupuis@xxxxxxxxxxxxxx]
Sent: Tuesday, April 05, 2005 3:56 AM
To: web400@xxxxxxxxxxxx
Subject: RE: [WEB400] Who Uses WebSphere Express?


Hello,

We will soon deploy a WebFaced application generated with WDSC 5.2.1.4 on a
WAS Express 5.1.
Let me know why profiles and deployment can be an issue please.

Vincent