WebFacing and how it all fits in with HATS. What can I still
do with WebFacing at V5R3/V5R4 and WDSC 7.0

Hi;

I'm very new to Webfacing so be gentle with me.

Here is what I'm trying to do.

We have a current green screen mini system that we want one group of users 
to still use it with the green screen.

The second group of users that we want them to access it 'Webfaced'. I also 
want this second group of users to still be able to signon via another 
session to the system and get there normal green screen menus. (What steps 
would I need to do to do this?)

On our test system we are V5R4 and our production box is at V5R3. I'm using 
WDSC 7.0 and we have Websphere Server 6.1 running in test but not in 
production yet.

I was able to create a webfacing project and run on my local server in WDSC 
7.0 on my PC.

What things should I be aware of when I try to transfer the converted 
application to the iSeries server?

I don't think I need to create this as a combined Web/Hats project or do I?

Thanks
Andy

Andy Hautamaki wrote:
> Hi;
> 
> I'm very new to Webfacing so be gentle with me.
> 
> Here is what I'm trying to do.
> 
> We have a current green screen mini system that we want one group of users

> to still use it with the green screen.
> 
> The second group of users that we want them to access it 'Webfaced'. I also

> want this second group of users to still be able to signon via another 
> session to the system and get there normal green screen menus. (What steps

> would I need to do to do this?)
> 
> On our test system we are V5R4 and our production box is at V5R3. I'm using

> WDSC 7.0 and we have Websphere Server 6.1 running in test but not in 
> production yet.
> 
> I was able to create a webfacing project and run on my local server in WDSC

> 7.0 on my PC.
> 
> What things should I be aware of when I try to transfer the converted 
> application to the iSeries server?
> 
> I don't think I need to create this as a combined Web/Hats project or do
I?
> 
> Thanks
> Andy

Hi Andy,

No, you don't need to use HATS, just a WebFacing project would likely 
fit your requirements quite nicely.

The only things that you likely want to do when putting it into 
production is to make sure that the DSPFs on the production system match 
the source that you converted.  And also to make sure you have a runtime 
license applied to the project otherwise you will only have two active 
connections which could be limiting ;-)

For the users that you want to sign on to another session, are you 
thinking of using WF or something like Personal Communications.  If you 
are thinking about using WF you could make a simple i5 menu as the entry 
point that either launches your mini application or gives them QCMD or 
some such to do their green-screen stuff.

Thanks Mike.

For the users that you want to sign on to another session, are you
> thinking of using WF or something like Personal Communications.  If you 
> are thinking about using WF you could make a simple i5 menu as the entry 
> point that either launches your mini application or gives them QCMD or 
> some such to do their green-screen stuff.

We are currently using Client Access. So based on that.......

If I'm understanding this right I could WebFace an entry menu with two 
options,  from the Webface entry menu they could access the new 'Web Face 
Mini System' or take another option and go into there normal 'green screen' 
entry menu? Will that work?  Is there a special trick to get the User in and 
out of Webfaced applications?

Isn't the Webfacing user jobs running in a separate subsystem?




Thanks
Andy



"M.Hockings" <hockings@ca.ibm.com> wrote in message 
news:4804C35F.9000807@ca.ibm.com...
> Andy Hautamaki wrote:
>> Hi;
>>
>> I'm very new to Webfacing so be gentle with me.
>>
>> Here is what I'm trying to do.
>>
>> We have a current green screen mini system that we want one group of 
>> users to still use it with the green screen.
>>
>> The second group of users that we want them to access it 'Webfaced'. I

>> also want this second group of users to still be able to signon via 
>> another session to the system and get there normal green screen menus.

>> (What steps would I need to do to do this?)
>>
>> On our test system we are V5R4 and our production box is at V5R3. I'm 
>> using WDSC 7.0 and we have Websphere Server 6.1 running in test but not

>> in production yet.
>>
>> I was able to create a webfacing project and run on my local server in

>> WDSC 7.0 on my PC.
>>
>> What things should I be aware of when I try to transfer the converted 
>> application to the iSeries server?
>>
>> I don't think I need to create this as a combined Web/Hats project or
do 
>> I?
>>
>> Thanks
>> Andy
>
> Hi Andy,
>
> No, you don't need to use HATS, just a WebFacing project would likely fit 
> your requirements quite nicely.
>
> The only things that you likely want to do when putting it into production

> is to make sure that the DSPFs on the production system match the source 
> that you converted.  And also to make sure you have a runtime license 
> applied to the project otherwise you will only have two active connections

> which could be limiting ;-)
>
> For the users that you want to sign on to another session, are you 
> thinking of using WF or something like Personal Communications.  If you 
> are thinking about using WF you could make a simple i5 menu as the entry 
> point that either launches your mini application or gives them QCMD or 
> some such to do their green-screen stuff.
>
> Mike (webfacing.wikidot.com) 

Okay I missed the obvious.......

I create the Webface Application
Create the EAR File
Install the EAR file into the Websphere application Server
The user access's the webfaced application via a browser. <---- 
I guess when you install the EAR file into the Websphere application Server 
you would also put in which user profiles have access to the EAR file?

So the user would have two choices, they could get to the green screen like 
they currently are doing or the webfaced applications via the browser.

Right????

Andy

"Andy Hautamaki" <ahautamaki@tstoverland.com> wrote in message 
news:fu2jub$1o84g$1@news.boulder.ibm.com...
> Thanks Mike.
>
> For the users that you want to sign on to another session, are you
>> thinking of using WF or something like Personal Communications.  If you

>> are thinking about using WF you could make a simple i5 menu as the
entry 
>> point that either launches your mini application or gives them QCMD or

>> some such to do their green-screen stuff.
>
> We are currently using Client Access. So based on that.......
>
> If I'm understanding this right I could WebFace an entry menu with two 
> options,  from the Webface entry menu they could access the new 'Web Face 
> Mini System' or take another option and go into there normal 'green 
> screen' entry menu? Will that work?  Is there a special trick to get the 
> User in and out of Webfaced applications?
>
> Isn't the Webfacing user jobs running in a separate subsystem?
>
>
>
>
> Thanks
> Andy
>
>
>
> "M.Hockings" <hockings@ca.ibm.com> wrote in message 
> news:4804C35F.9000807@ca.ibm.com...
>> Andy Hautamaki wrote:
>>> Hi;
>>>
>>> I'm very new to Webfacing so be gentle with me.
>>>
>>> Here is what I'm trying to do.
>>>
>>> We have a current green screen mini system that we want one group
of 
>>> users to still use it with the green screen.
>>>
>>> The second group of users that we want them to access it
'Webfaced'. I 
>>> also want this second group of users to still be able to signon via

>>> another session to the system and get there normal green screen
menus. 
>>> (What steps would I need to do to do this?)
>>>
>>> On our test system we are V5R4 and our production box is at V5R3.
I'm 
>>> using WDSC 7.0 and we have Websphere Server 6.1 running in test but
not 
>>> in production yet.
>>>
>>> I was able to create a webfacing project and run on my local server
in 
>>> WDSC 7.0 on my PC.
>>>
>>> What things should I be aware of when I try to transfer the
converted 
>>> application to the iSeries server?
>>>
>>> I don't think I need to create this as a combined Web/Hats project
or do 
>>> I?
>>>
>>> Thanks
>>> Andy
>>
>> Hi Andy,
>>
>> No, you don't need to use HATS, just a WebFacing project would likely
fit 
>> your requirements quite nicely.
>>
>> The only things that you likely want to do when putting it into 
>> production is to make sure that the DSPFs on the production system
match 
>> the source that you converted.  And also to make sure you have a
runtime 
>> license applied to the project otherwise you will only have two active

>> connections which could be limiting ;-)
>>
>> For the users that you want to sign on to another session, are you 
>> thinking of using WF or something like Personal Communications.  If you

>> are thinking about using WF you could make a simple i5 menu as the
entry 
>> point that either launches your mini application or gives them QCMD or

>> some such to do their green-screen stuff.
>>
>> Mike (webfacing.wikidot.com)
>
> 

Andy Hautamaki wrote:
> Thanks Mike.
> 
> For the users that you want to sign on to another session, are you
>> thinking of using WF or something like Personal Communications.  If you

>> are thinking about using WF you could make a simple i5 menu as the
entry 
>> point that either launches your mini application or gives them QCMD or

>> some such to do their green-screen stuff.
> 
> We are currently using Client Access. So based on that.......
> 
> If I'm understanding this right I could WebFace an entry menu with two 
> options,  from the Webface entry menu they could access the new 'Web Face 
> Mini System' or take another option and go into there normal 'green screen'

> entry menu? Will that work?  Is there a special trick to get the User in
and 
> out of Webfaced applications?
> 
> Isn't the Webfacing user jobs running in a separate subsystem?
> 
> Thanks
> Andy

Hi Andy,

Yes, it will work, both will be shown on the browser.  With v7 on v5r4 
and later you can mix WebFaced and rendered applications more or less 
seamlessly.  I say more or less since you can't have part of the screen 
converted with WF and part rendered ;-)

Unless you have configured routing entries and the like to do otherwise 
the default on most systems that I have seen is to use QINTER.  If you 
are planning on running thousands of simultaneous users then additional 
subsystems could be set up in order to improve performance.  In that 
case these would be of interest.
Configuring the WF server
http://www-1.ibm.com/support/docview.wss?uid=swg27008283
Current PTFs for the WF server
http://www-1.ibm.com/support/docview.wss?uid=swg27002213