What if the first impression your users received were a Web page "portal" for your company, instead of the drab green screen they get today? It's all possible, and I'll prove it!
If you have a license for iSeries Access then you have a license for iSeries Access for Web. More importantly, if you don't use the license in five minutes, the system turns the license in so other users can use it. The above screenshot is an example of a slightly customized page showing my system being accessed over my Intranet using Port 2016; however, there is nothing that says this can't be accessed using a standard browser port.
So, let's talk about requirements:
- 5722-DG1 needs to be installed – this is the free Apache HTTP Web Server.
- 5722-JV1 – include all options
- 5722-TC1 – TCP/IP utilities. However, if you don't have TCP/IP running in your shop yet, you're certainly not serving web pages.
- 5722-XW1 – iSeries Access Family (a license is required for this)
- 5722-XH2 – iSeries Access for Web – covered under the license of 5722-XW1
There're a few flavors of installing this product. We'll be using ASF/Tomcat for our servlet engine to help serve the iSeries Access Web pages. This has the smallest number of licensed programs required to fire up the engine.
Once there, make sure your current group PTFs for HTTP Web server, product 5722-DG1 (SF99114) , and Java Groups, or product 5722-JV1 (SF99291), are applied properly so you can start the HTTP Admin server. As a bonus, apply the TCP/IP group PTFs to make sure your system is protected from hackers (the group for the HTTP server helps with as well). You can use SSL to protect this environment as well.
Now that we've satisfied the above requirements, let's set up iSeries access for Web.
|Back||Table of contents||Next|
ABOUT THE AUTHOR: Andrew Borts is webmaster at United Auto Insurance Group in North Miami, Fla. He is a frequent speaker at COMMON and is past president of The Southern National Users Group, an iSeries-AS/400 user group based in Deerfield Beach, Fla.