20 iSeries Access for Web V5R2 and WebSphere Host Publisher V4.0
2.5 Connecting to multiple iSeries servers
In an environment where access to multiple iSeries servers is required, from a performance
perspective, installing the full suite of software to enable iSeries Access for Web on each
machine may not be desirable. Due to financial constraints, it may not be appropriate to install
WebSphere Application Server on all iSeries servers.
This section explores the possibility of using a central iSeries server to provide a gateway-like
function to allow access to multiple iSeries servers. Figure 2-2 shows a topology that allows
the use of iSeries Access for Web to connect to more than one iSeries server.
There are several considerations when planning iSeries Access for Web connections to
multiple systems:
Network topology
Network security
Required licensed program products
Multiple application server instances
For the purposes of this example, it is understood that adequate network security is
implemented to secure the iSeries from unauthorized access. We recommend that you use
cryptographic encryption with any iSeries server accessed from the Web. When this is
implemented, the Web browser uses the SSL protocol to access the iSeries labelled as
System A. The iSeries Access for Web connections to the subsequent systems are facilitated
by Java classes shipped with iSeries Access for Web V5R2. The toolbox connections on the
central system (System A) communicate with iSeries Access servers on the remote systems
(System B, System C, System D, etc.). Figure 2-2 shows the software products that must be
installed on systems B, C, and D to access these systems via a Web browser with iSeries
Access for Web.
Figure 2-2 Connecting to multiple systems with iSeries Access for Web
Internet/intranet
Web browser
HTTP or
HTTPS
iSeries Access Family
iSeries Access for Web
HTTP or Secure HTTP connection
System A
S
y
stem
B
System
C
System
D
Toolbox
Connections
Refer to Tables 2-4 and
2-5 for the required
software products for
iSeries Access for Web
Chapter 2. Setting up iSeries Access for Web 21
Refer to Table 2-4 on page 13 or Table 2-5 on page 14 for a list of the required software
products for iSeries Access for Web for System A. You must have installed all required
software licensed program products on this system. In addition, System A requires you to
configure an additional Web application server instance for each additional iSeries server to
be accessed using iSeries Access for Web.
The additional systems represented as System B, System C, and System D do not require a
Web application server instance to be installed. However, these systems do require you to
install the following licensed programs:
iSeries Access Family (5722-XW1)
iSeries Access for Web V5R2 (5722-XH2)
Each additional system requires iSeries Access Family to provide the licensing component to
allow iSeries Access for Web connections and iSeries Access for Web V5R2 to control the
individual session functions.
Each instance of the Web application server is required to be configured for one target
system. The configuration setting that controls the target system for the instance is the
realm
definition in the webaccess.properties file.
You can find the webaccess.properties file in the IFS directory
/QIBM/UserData/Access/Web2/
appserver
/
instancename
/config/webaccess.properties.
The path depends on the unique values configured on an individual server:
appserver
: The name of the application server (for example, was40adv)
instancename
: The unique name for the instance of the application server (for example,
default)
You can edit the content of the webaccess.properties file to configure the application server
instance to connect to the target system. Figure 2-3 shows an example of the content of the
webaccess.properties file with the parameter that needs to be included.
Figure 2-3 Example webaccess.properties file
The webaccess.properties file is edited by adding a realm statement to the file. Without this
statement, the iSeries Access for Web session is directed to the local system. The format of
the realm statement is shown here:
realm=targethost.domain.com
targethost.domain.com
is the fully qualified domain name configured in the TCP/IP setup for
the desired target system. For example, it may be
systemc.ibm.com
.
#Wed Apr 24 15:29:56 GMT+00:00 2002
port=5252
nodename=<systemname>
serviceport=900
servicehost=<systemname>
realm=systemc.ibm.com

Get iSeries Access for Web V5R2 and WebSphere Host Publisher V4.0 now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.