× 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.



Thank you all.

We'll probably put WAS and webfacing on our 270-2452 DSD box running 
http://www.dekko.com and put the 5250 and data on our 840-23EA 12 way. 
(Incidentally IBM wants your firstborn male child to put WAS on the 12 
way.  But if you LPAR it, they'll only charge by the allocated processors 
to that partition.)

Glad to get a second person to pipe up about port 4004.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 





rune@xxxxxxx
Sent by: web400-bounces@xxxxxxxxxxxx
05/16/2003 05:08 PM
Please respond to Web Enabling the AS400 / iSeries
 
        To:     Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        Re: [WEB400] Webfacing - Where to run the HLL 
programs?


Hi Rob.

Try port 4004. That's the default port the WebFacing server (in your case, 

on DATA) listens to.

Good luck,
Rune




rob@xxxxxxxxx
Sent by: web400-bounces@xxxxxxxxxxxx
16.05.2003 22:16
Please respond to Web Enabling the AS400 / iSeries
 
        To:     Midrange Systems Technical Discussion 
<midrange-l@xxxxxxxxxxxx>, web400@xxxxxxxxxxxx
        cc: 
        Subject:        [WEB400] Webfacing - Where to run the HLL 
programs?


I've got an iSeries for web serving.  Let's call this WEB.  I've got 
another system where the data resides on.  Let's call this DATA.

At this time we are pursuing Webfacing some applications.

With webfacing you can have your WAS and the jsp's created by Webfacing on 


one iSeries, and your HLL programs on another.  And your data on one of 
these two, or another machine(s).

If we store our HLL (RPGLE, CLLE, etc) on WEB we can access the data on 
DATA using any number of methods:
- Stored procedures
- DDM
- SQL's CONNECT TO statement
- DATA QUEUE's, message queue's, MQSeries, etc

However we are leaning towards storing our HLL on DATA.

I want to make sure that I maximize security and performance with a 
secondary goal of making it simple.

One mandate is that there is zero replication of data.

Which machine takes the interactive hit?
A - The machine running WAS - WEB
B - The machine with all the HLL, screen files, etc - DATA

Currently WEB is in the DMZ and cannot initiate any processes on DATA.  No 


telnet, ftp, ddm, etc.  DATA can initiate most anything on WEB.
What do I have to open up on the firewall to allow WEB to run the HLL on 
DATA?

Any concerns, suggestions for improvement, etc?

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 
_______________________________________________
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.


_______________________________________________
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.



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.