System information

218
AS/400 IBM Network Station: Techniques for Deployment in a WAN
was made to copy the base IBM Network Station Manager environment to the
remote sites from the AS/400 system, SYSAS3 at the central site. In addition,
common system-wide and group-level preferences were determined.
Because they applied to all remote servers, the changes were made on the
master SYSAS3 system before replication. IBM Network Station Manager on
SYSAS3 was used to omit the 3270 button from the system default desktop
for the remote sites because the majority of remote users do not need access
to the S/390 system in Chicago. There is a set of users at each remote site
that do need S/390 access. Therefore, a group profile called
grp3270 was
created. The desktop preferences for the
grp3270 group was changed so that
a 3270 button appears on those users’ IBM Network Station menu bars.
Figure 126. Replicating Remote Boot Servers - Decentralized Authentication
7.2.1 IBM Network Station Manager Replication to Remote Server
The plan is to use the Network Station Manager environment on the central
site development AS/400 (SYSAS3) system as a
master copy and replicate it
to the remote AS/400 boot servers. The AS/400 system, SYSAS1, continues
to be a production boot server for the IBM Network Station users located at
the central site. Our central and remote system are both at the same OS/400
V4R3 level. We used the document referenced at the end of this paragraph to
.....
AS/400
SYSAS1
Router
Rochester
AS/400
SYSAS4
10.1.1.2
10.1.1.5
10.4.1.40
10.4.1.70
10.4.1.10
10.4.1.1
....
10.1.1.10
10.1.1.40
10.1.1.50
10.1.1.85
...
10.4.1.35
Portland
AS/400
SYSAS63
10.63.1.1
....
....
Router
Authentication
Server
Base Code
Server
DHCP
Server
Terminal Config.
Server
Authentication
Server
Base Code
Server
Terminal Config.
Server
10.4.1.2
....
S/390
SYS390
10.1.1..4
AS/400
SYSAS3
("Master Copy"
)
10.1.1.3
Base Code
Server
Terminal Config.
Server
Authentication
Server
Chicago