|
Hi, Shannon. I am not sure exactly how your app is set up, but is it possible for you to create a wrapper CL to call your existing app? Perhaps you could do your pre-assignment or initialization logic in the wrapper, have the wrapper then call the existing app, and finally, have your webfacing app call the wrapper CL. Brendan -----Original Message----- From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of Shannon ODonnell Sent: Wednesday, March 23, 2005 12:14 PM To: Websphere Development Studio Client for iSeries Subject: Re: [WDSCI-L] WebFacing and Specific Device That's what I was afraid of. Well...hmmm.... I guess I could change the existing application so that it checks to see if this job is being called by the webfacing server and if it is, I can pre-assign a device at that time, otherwise I'll allow it to work as it normally does. That should take care of this. I was hoping to not have to change the existing code at all, but oh well...if that's the only change I have to make then that's not bad. Thanks for the information! Shannon O'Donnell ----- Original Message ----- From: "Mike Hockings" <hockings@xxxxxxxxxx> To: "Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx> Sent: Wednesday, March 23, 2005 10:37 AM Subject: Re: [WDSCI-L] WebFacing and Specific Device >I don't believe that is possible. They devices are created, reused and > destroyed dynamically. There is not a 1:1 connection between PC box and > device like there is with and emulation session. > > Mike > > Mike Hockings, P.Eng. > WebSphere Development Tools for AS/400 - CODE/Designer & WebFacing ! > IBM Canada Ltd. Laboratory > hockings@xxxxxxxxxx > > > > > > "Shannon ODonnell" <sodonnell@xxxxxxxxxxxxxxxxx> > Sent by: wdsci-l-bounces@xxxxxxxxxxxx > 03/23/2005 09:59 AM > Please respond to > Websphere Development Studio Client for iSeries > > > To > <wdsci-l@xxxxxxxxxxxx> > cc > > Subject > [WDSCI-L] WebFacing and Specific Device > > > > > > > Hello, > > Does anyone know if there is a way to pre-assign a specific OS/400 device > name to a given WebFacin session? > > I am working with an application that requires that it know ahead of time > what devices are going to be accessing it, and it sets certain variables > such as printer name, etc.. based on that. It's a rudimentary form of > security for a fairly old application, but it's a "feature" that's built > in so tightly to the application that removing or bypassing it would be a > major undertaking. > > If I could assign a device name on the web facing project, that would help > tremendously. > > Thanks, > > Shannon O'Donnell > -- > This is the Websphere Development Studio Client for iSeries (WDSCI-L) > mailing list > To post a message email: WDSCI-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/wdsci-l > or email: WDSCI-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/wdsci-l. > > -- > This is the Websphere Development Studio Client for iSeries (WDSCI-L) > mailing list > To post a message email: WDSCI-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/wdsci-l > or email: WDSCI-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/wdsci-l. > > > -- This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.