HP P Class 450/500/550/600/650/700/750 hp visualize workstation - Migrating UN
HP P Class 450/500/550/600/650/700/750 Manual
 |
View all HP P Class 450/500/550/600/650/700/750 manuals
Add to My Manuals
Save this manual to your list of manuals |
HP P Class 450/500/550/600/650/700/750 manual content summary:
- HP P Class 450/500/550/600/650/700/750 | hp visualize workstation - Migrating UN - Page 1
VISUALIZE Workstations Migrating UNIX Technical Environments to Windows NT By Scott Key Solution Specialist - HP P Class 450/500/550/600/650/700/750 | hp visualize workstation - Migrating UN - Page 2
considerations of this platform: § Are all required applications available? § Is sufficient application performance available? § Is the network infrastructure ready to support Windows NT? § Can the current UNIX system environment be duplicated on Windows NT? § Is the IT infrastructure ready to - HP P Class 450/500/550/600/650/700/750 | hp visualize workstation - Migrating UN - Page 3
assembly or Fortran language programs are inherently UNIXcentric with little migration support for NT. In addition, it should be ascertained whether the , the current infrastructure. For example, the NT 4.0 browsing service can increase network traffic. The lack of consistent, interoperable file - HP P Class 450/500/550/600/650/700/750 | hp visualize workstation - Migrating UN - Page 4
workstation setup, etc. that are currently dependent upon UNIX-centric tools and applications. The cost of migration from UNIX to Windows NT must be weighed against the functionality and seamless integration of the migrated applications with the standard UNIX systems and their associated technical - HP P Class 450/500/550/600/650/700/750 | hp visualize workstation - Migrating UN - Page 5
Hamilton Laboratories). Tools like XEmacs and MKS also provide UNIX style editors and some portions of a development environment. The risks involved in this path are associated with the costs of rewriting applications to ensure maximum performance levels under Windows NT. Currently, NT requires more - HP P Class 450/500/550/600/650/700/750 | hp visualize workstation - Migrating UN - Page 6
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 - HP P Class 450/500/550/600/650/700/750 | hp visualize workstation - Migrating UN - Page 7
Table 1: Migration path comparison summary Migration Path Ease of Migration Migrating all of the Difficult UNIX environment Risk to Current Systems Infrastructure High Acceptance of Performance Current Personnel High High Level of NT Integration High Migrating some of the UNIX environment - HP P Class 450/500/550/600/650/700/750 | hp visualize workstation - Migrating UN - Page 8
§ Move the source to the Windows environment. § Compile & link. § Fix any linkage issues that relate to calls for routings that don't exist in Windows NT. § Debug and test with other NT applications and environment. The "how to" of migration is predicated on the thorough understanding of when and/or
-
1 -
2 -
3 -
4 -
5 -
6 -
7 -
8
 |
 |
VISUALIZE Workstations
Migrating UNIX Technical Environments
to Windows NT
By Scott Key
Solution Specialist