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


  1.  Home
  2. OPENSOURCE
  3. June 2018

Re: [IBMiOSS] Ports and routes needed to replace very large numbers of green screens

API deployment architecture is a varied and organic subject. the mapping between 5250 programs and mapped APi’s/services is is completely dependant on the API requirement usually in three main areas:

ownership - div/department/client/partner so resources are allocated according to a specific business requirement
scale - complexity, number of transactions, hits/threads and data payload size
security - authentication, validation - OAUTH/JWT scoping etc.

each can influence the other. and so http instances/configurations should reflect each of these in some measure.
the crudest and most basic approach (sometimes completely appropriate) is to use the script aliasmatch mentioned earlier by Justin. the is built into Apache on IBM using CGI.

most companies start by using apache configs manually to allow all objects in a lib to be available as services, and of course there are ways to exclude specific objects. its possible to have a single instance and port number services hundreds of API services in this way.

but this can soon becomes complex and convoluted. its better to have a longer term view on scalability (complexity, API’s, and transaction numbers) so you can grow without disruptions. design Api infrastructure accordingly

the most common scalable approach to whats is more commonly known as API infrastructure is to use layers. you can implement layers using layered Apache instances on a single IBMi, but any serious, secure implementation that expect to scale uses a separate gateway layer. these are servers designed to handle such traffic and routes using rules and configs. the most modern, productive server used in the area is nGinx. its open source and works on IBMi too.



Stuart Milligan
Cell SA: +27 61 651 7074
Dir SA: +27 (0)21 012 5078
Dir NA: +1 917 267 7523
stuartm@xxxxxxxxxxxxxxxxxxx <mailto:stuartm@xxxxxxxxxxxxxxxxxxx>
On 4 Jun 2018, at 19:37, opensource-request@xxxxxxxxxxxx <mailto:opensource-request@xxxxxxxxxxxx> wrote:

Send OpenSource mailing list submissions to
opensource@xxxxxxxxxxxx <mailto:opensource@xxxxxxxxxxxx>

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.midrange.com/mailman/listinfo/opensource
or, via email, send a message with subject or body 'help' to
opensource-request@xxxxxxxxxxxx

You can reach the person managing the list at
opensource-owner@xxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of OpenSource digest..."


Today's Topics:

1. Re: Ports and routes needed to replace very large numbers of
green screens (Richard Schoen)
2. Re: [EXTERNAL] Re: Ports and routes needed to replace very
large numbers of green screens (Kelly Cookson)
3. Re: [EXTERNAL] Re: Ports and routes needed to replace very
large numbers of green screens (Kelly Cookson)


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

message: 1
date: Mon, 4 Jun 2018 17:10:57 +0000
from: Richard Schoen <Richard.Schoen@xxxxxxxxxxxxxxx>
subject: Re: [IBMiOSS] Ports and routes needed to replace very large
numbers of green screens

Can you explain why you would have thousands of ports listening ?

Regards,
Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com
----------------------------------------------------------------------

message: 1
date: Mon, 4 Jun 2018 17:01:47 +0000
from: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
subject: Re: [IBMiOSS] [EXTERNAL] Re: Ports and routes needed to
replace very large numbers of green screens

I share Kelly's concern about ports. How do people handle it? If I magically converted all our 5250 apps to Node apps, I'd have thousands of ports listening.










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

message: 2
date: Mon, 4 Jun 2018 17:34:20 +0000
from: Kelly Cookson <KCookson@xxxxxxxxxxxx>
subject: Re: [IBMiOSS] [EXTERNAL] Re: Ports and routes needed to
replace very large numbers of green screens

Hi John,

You may be right. Like Richard said before, I may be overthinking this.

I might feel more comfortable if someone would explain the part where "the server will handle it." Maybe it will. But I would feel a lot more comfortable knowing how that works-at least at the 10,000 foot view.

Thanks,

Kelly Cookson
IT Project Leader
Dot Foods, Inc.
217-773-4486 ext. 12676
www.dotfoods.com<http://www.dotfoods.com>

From: OpenSource [mailto:opensource-bounces@xxxxxxxxxxxx] On Behalf Of John Yeung
Sent: Monday, June 04, 2018 11:33 AM
To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxx>
Subject: Re: [IBMiOSS] [EXTERNAL] Re: Ports and routes needed to replace very large numbers of green screens

On Mon, Jun 4, 2018 at 9:56 AM, Kelly Cookson <KCookson@xxxxxxxxxxxx<mailto:KCookson@xxxxxxxxxxxx>> wrote:
I guess maybe I should ask the question more broadly. We have many hundreds (at least) of interactive COBOL programs. Many of these interactive COBOL programs have multiple green screens associated with them. Is there a way to replace all of these green screens with web pages and not create a need for multiple web servers (ports) and/or a lot of routes within those web servers?

Richard already answered this. To paraphrase, he said "don't worry -
just use one port, and the server will handle it".

I'm not an expert, but as far as I can tell, this is how everyone does
it. And until you asked, I had never heard of anyone (on any platform,
using any Web framework) expressing any concern over too many ports or
too many routes.

Please understand I am not saying your concern is unjustified. It
might be justified, especially if your situation is somehow extremely
unusual. But I don't think it is.

John Y.
--
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx<mailto:OpenSource@xxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/opensource<https://lists.midrange.com/mailman/listinfo/opensource>
or email: OpenSource-request@xxxxxxxxxxxx<mailto:OpenSource-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/opensource<https://archive.midrange.com/opensource>.


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

message: 3
date: Mon, 4 Jun 2018 17:37:19 +0000
from: Kelly Cookson <KCookson@xxxxxxxxxxxx>
subject: Re: [IBMiOSS] [EXTERNAL] Re: Ports and routes needed to
replace very large numbers of green screens

Hi Justin,

Yeah, that's what I'm getting at.

If you look at Node.JS tutorials, they almost always create a simple app that is hosted in its own Node.JS web server (i.e., the web server functionality of Node.JS). If I use this model, and treat each web service as an independent Node.JS app running in its own web server, then I potentially end up with many hundreds of ports running Node.JS web servers. I know there is routing in Node.JS frameworks like Express. But then I get back to my question: do I want one Node.JS server with large numbers of Express routes in an initial gateway app? Or is there some balance between number of Node.JS web servers and Express routes that I should be aiming at? If so, what would be recommended? What's the target?

We would never do a big-bang approach where we actually tried to convert all of our green screen apps at once. But, once we get started, the number of conversions will grow over time. I would like to have plan in place for how we will manage them. I don't want to wait until it becomes unmanageable, then realize we painted ourselves into a corner and have to re-code everything.

Thanks,

Kelly Cookson
IT Project Leader
Dot Foods, Inc.
217-773-4486 ext. 12676
www.dotfoods.com<http://www.dotfoods.com>

From: OpenSource [mailto:opensource-bounces@xxxxxxxxxxxx] On Behalf Of Justin Taylor
Sent: Monday, June 04, 2018 12:02 PM
To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxx>
Subject: Re: [IBMiOSS] [EXTERNAL] Re: Ports and routes needed to replace very large numbers of green screens

I share Kelly's concern about ports. How do people handle it? If I magically converted all our 5250 apps to Node apps, I'd have thousands of ports listening.




-----Original Message-----
From: John Yeung [mailto:gallium.arsenide@xxxxxxxxx]
Sent: Monday, June 04, 2018 11:33 AM
To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxx<mailto:opensource@xxxxxxxxxxxx>>
Subject: Re: [IBMiOSS] [EXTERNAL] Re: Ports and routes needed to replace very large numbers of green screens

On Mon, Jun 4, 2018 at 9:56 AM, Kelly Cookson <KCookson@xxxxxxxxxxxx<mailto:KCookson@xxxxxxxxxxxx>> wrote:
I guess maybe I should ask the question more broadly. We have many hundreds (at least) of interactive COBOL programs. Many of these interactive COBOL programs have multiple green screens associated with them. Is there a way to replace all of these green screens with web pages and not create a need for multiple web servers (ports) and/or a lot of routes within those web servers?

Richard already answered this. To paraphrase, he said "don't worry - just use one port, and the server will handle it".

I'm not an expert, but as far as I can tell, this is how everyone does it. And until you asked, I had never heard of anyone (on any platform, using any Web framework) expressing any concern over too many ports or too many routes.

Please understand I am not saying your concern is unjustified. It might be justified, especially if your situation is somehow extremely unusual. But I don't think it is.

John Y.

--
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx<mailto:OpenSource@xxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/opensource<https://lists.midrange.com/mailman/listinfo/opensource>
or email: OpenSource-request@xxxxxxxxxxxx<mailto:OpenSource-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/opensource<https://archive.midrange.com/opensource>.


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

Subject: Digest Footer

--
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/opensource.


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

End of OpenSource Digest, Vol 3, Issue 80
*****************************************



Stuart Milligan
Cell SA: +27 61 651 7074
Dir SA: +27 (0)21 012 5078
Dir NA: +1 917 267 7523
UK: +44 (0)238 097 1176
stuartm@xxxxxxxxxx


As an Amazon Associate we earn from qualifying purchases.

This thread ...
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.