HP Visualize J5000 hp visualize workstation - Migrating UNIX Technical Environ - Page 6

Conclusion

Get HP Visualize J5000 - Workstation PDF manuals and user guides View all HP Visualize J5000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 6 highlights

Migrating Only the Minimal Client Piece Conclusion The migration of the client or interface portion allows this path to provide for utilizing technical NT workstation and the Windows NT GUI as a "front end" to the technical applications and environment on UNIX. For example, this could entail providing an interface on an NT workstation to a technical database on a UNIX system. It could also be as simple as configuring an X Window from the NT platform onto the UNIX environment. This path requires the least amount of migration and only a moderate amount of interoperability or integration. In an environment such as this, the technical user is provided with the ability to run NT applications with minimal integration to UNIX applications. Use of an X Window emulator is one of the easiest methods of providing a simple interface into the UNIX system. Some of the available emulators for Windows NT are Reflection X, WinTED and Exceed. In addition, a Telnet emulator is included with Windows NT. If a more integrated client/server environment is required, than tool kits with UNIX APIs and development libraries may be required. These tool kits would be similar in nature as those discussed in the migration path of porting the entire UNIX environment to NT. These would include NuTCRACKER, OpenNT, MKS Toolkit and even DFS. Although the risks are minimal with this type of migration, the performance of the applications will be constrained on the network performance. The network infrastructure will need to be expanded and some client application code will need to be rewritten. Training will still need to be provided to those developers, administrators and users effected. This migration path is less costly since few UNIX technical desktop systems or applications are being ported. Some new system procedures and processes will probably need to be created for the technical NT environment. When each migration path is compared based upon the costs and possible performance as well as the level of NT integration, an informed choice can be made. This comparison is summarized in Table 1. 02/04/00 HP VISUALIZE WORKSTATIONS 5

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
02/04/00
HP VISUALIZE WORKSTATIONS
5
Migrating Only
the Minimal
Client Piece
The migration of the client or interface portion allows this path to provide for utilizing
technical NT workstation and the Windows NT GUI as a "front end" to the technical
applications and environment on UNIX. For example, this could entail providing an
interface on an NT workstation to a technical database on a UNIX system. It could also be
as simple as configuring an X Window from the NT platform onto the UNIX environment.
This path requires the least amount of migration and only a moderate amount of
interoperability or integration.
In an environment such as this, the technical user is
provided with the ability to run NT applications with minimal integration to UNIX
applications.
Use of an X Window emulator is one of the easiest methods of providing a simple
interface into the UNIX system. Some of the available emulators for Windows NT are
Reflection X, WinTED and Exceed. In addition, a Telnet emulator is included with
Windows NT. If a more integrated client/server environment is required, than tool kits
with UNIX APIs and development libraries may be required. These tool kits would be
similar in nature as those discussed in the migration path of porting the entire UNIX
environment to NT. These would include NuTCRACKER, OpenNT, MKS Toolkit and
even DFS.
Although the risks are minimal with this type of migration, the performance of the
applications will be constrained on the network performance. The network infrastructure
will need to be expanded and some client application code will need to be rewritten.
Training will still need to be provided to those developers, administrators and users
effected. This migration path is less costly since few UNIX technical desktop systems or
applications are being ported.
Some new system procedures and processes will probably
need to be created for the technical NT environment.
Conclusion
When each migration path is compared based upon the costs and possible performance as
well as the level of NT integration, an informed choice can be made. This comparison is
summarized in Table 1.