× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



The licensing piece is a bit of a mystery and perhaps someone knowledgeable from IBM can chime in here. I do understand that IBM requires that WDHT be licensed for each System i that an application is deployed to (which is what I am going to use to refer to the HATS component piece since IBM has combined HATS and Web Facing into on product now called WDHT). Since there is no product installed on the System i I am not sure where the licensing control is set. When you install the WDHT product on your PC, there is a license file that you have to install as well and that is used to control how many concurrent connections you can have to your HATS application. If you don't install the license file from the WDHT installation CD, then you are limited to one or two concurrent connections (can't remember which) to the application. This is done to allow you to deploy and test your application on a System i. However, there is nothing to prevent you (that I know of) from installing the license file into your application and set it for unlimited connections and then to deploy this application to many System i's. Well, nothing to prevent you *technically* from doing so. The license agreement that you accept when you install the license file into your application legally prevents you from doing so (I think it actually applies to *all* applications you develop and deploy from the workbench since the license file installs into the WDSC workbench). So the "spendmoney" command that IBM requires you to run is a moral obligation, not a technical one.

What do you need? To develop the application all you need is WDSC. To deploy it, all you need is WAS or some other Application Server (which I haven't attempted yet). To *license* it, you will need IBM WebSphere WebFacing Deployment Tool for WebSphere Development Studio for iSeries for the correct processor tier you plan to deploy to (Product D575WLL for the P05 tier, for example). Again, that "tool" is just a license file that installs into WDSC and is used in the EAR file during deployment. To my knowledge, there is no other licensing piece that installs on the System i so you could conceivably deploy the application to hundreds of System i's at the tier you purchased and there would be no technical hurdle to doing so. However, you would be out of compliance on your license agreement.

I can't speak to the Web Facing side since I don't use that.

Pete Helgren


jwallroff@xxxxxxxxxxxxxxx wrote:
Ok, I see, the actual transformation is done within the Web application, not on the iSeries. Thank you.
Can you explain to me what is then actually licensed on each iSeries? IBM is wanting to charge us a bunch of money for each iSeries we want to run HATS on.

Ok, the way I understand it is for WebFacing you have to have 3 components running.
1. A Web Server (doesn't have to be on the iSeries)
2. An HTTP Server (doesn't have to be on the iSeries)
3. WebFacing Server (Only piece that has to be running on the iSeries)

It would seem then that if you want to use then you actual iSeries part is the same as for WebFacing by itself without HATS.

One last question.
What exactly do I need to get for WDHT?

Thank you so much for your time.

John.





Pete Helgren <Pete@xxxxxxxxxx> Sent by: wdsci-l-bounces@xxxxxxxxxxxx
06/15/2007 10:55 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] What exactly needs to be installed and started on the iSeries for Webfacing and HATS.






John,
"I don't understand what you're saying about HATS though, what needs to be
running on the production iSeries for HATS to function, something has to
do the 5250 stream translation on the fly?"

Nothing has to be running on the System i. The HATS application starts a 5250 session, reads the 5250 data directly and transforms it on the fly. That is why you can be running HATS on your local PC in a WAS instance with nothing installed on your System i.

For example, we sell a set of HATS transformations for a particular 5250 based product. When we demo the product, we directly connect to the customer's System i and show them what their data looks like in our HATS application. We had to install exactly nothing on their system in order to have HATS to work with their applications and data. That is the cool thing about HATS. It can have zero footprint on the System i if you deploy to a different server (Windows or Linux, for example).

Pete Helgren


jwallroff@xxxxxxxxxxxxxxx wrote:
Thank you Cheri,

This is the kind of basic info I was looking for.
So... if I understand you correctly, the only thing that needs to be running on the production iSeries for WebFacing is the WebFacing server/service?

I don't understand what you're saying about HATS though, what needs to
be
running on the production iSeries for HATS to function, something has to

do the 5250 stream translation on the fly?

What about the combined WDHT product that is both WebFacing and HATS together, which is what I believe we will be wanting to use in the end because we have common system calls (like wrksplf) built into our application that can not be WebFaced.

I just want to get a good idea as a programmer what I need to tell the system admin folks as to what will need to be installed and running for
a
WebFaced/HATS application to run on each iSeries.

John.




"Cheri Duchrow" <cduchrow@xxxxxxxxxxxxxx> Sent by: wdsci-l-bounces@xxxxxxxxxxxx
06/15/2007 08:19 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
wdsci-l@xxxxxxxxxxxx
cc

Subject
Re: [WDSCI-L] What exactly needs to be installed and started on
theiSeries
for Webfacing and HATS.






Your networking and DNS entries all have to be setup and in place and I
am
in no means an expert in all of that but if that is setup correctly the only thing you need to running on the iSeries for WebFacing or HATS is to
have
the WebFacing server/service started on the iSeries.

You can have a Windows server that is running the Apache HTTP server and

you can purchase a license to run WAS on a windows machine. You can deploy your ear file to this Windows server and as long as your network is setup
that
the windows server can find your iSeries host and you may have to open a

few ports your application should work. If you have a WebFaced application then you will need the WebFacing server piece started on the iSeries. For
HATS
no special piece needed on the iSeries.

Here is a link to IBM WebFacing Troubleshooting that may give you some insight or what is needed on the iSeries

http://www-1.ibm.com/support/docview.wss?rs=3239&context=SSZND2&dc=DA400&uid=swg27005905&loc=en_US&cs=UTF-8&lang=en&rss=ct3239websphere

You will want to make sure that you have the latest PTFs on. As well as

they are slowly changing and merging WebFacing and WDHT(HATS) and depending on what version of V5R3 etc will depend on whether these products use interactive cycles and whether you need a license for WebFacing etc. The

beauty is that with WDSc you can develop and try this out before making
a
decision
HTH
Cheri


<jwallroff@xxxxxxxxxxxxxxx> wrote in message
news:OF5D0B051F.9CDDF2F6-ON862572FA.0064AE92-862572FA.0064BB2D@xxxxxxxxxxxxxxxx
.
.

Would someone please answer a couple questions for me about what HATS
and

Webfacing.

I am working on a project to Web enable a green screen application with
instances running on 100 different iSeries boxes. The application is
the

same on each box, the only difference is the data.

What exactly needs to be installed on each individual iSeries for
Webfacing and HATS to work on that box.

I understand that the application server doesn't have to be running on
the

iSeries itself, such as is the case when we are developing in WDSC and
using the provided WAS server running on the PC.
But... in the Webfacing project you specify a specific Host
name.
Is there a way to have the project published to one Web
application server and have a "portal" or initial page allow the user
to
select which "Host" iSeries to connect to or can a project only have
one
"Host"? Or do you have to have an individual project for each iSeries
"Host"????

Thank you.
--
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 thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.