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

Paths for Migration of the Technical Desktop Environment to Windows, NT Workstations,

Page 4 highlights

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 environment. Along with the required functionality and integration, performance is a prime factor indicating which path of migration should be taken, as depicted in figure 1. Figure 1: Paths for Migration of the Technical Desktop Environment to Windows NT Workstations Migrating all of the UNIX Environment A total conversion and migration of the technical desktop environment from UNIX to Windows NT workstations could provide better interoperability with data, security and system infrastructure. In addition, performance of applications with high levels of GUI interaction may benefit from NT native hosting. Also, the outcome of this migration effort can be enhanced integration with Windows office applications like spreadsheets, email and the like. There are tools for porting your UNIX applications to NT and there are tools for migrating or allowing your system scripts to run. Software porting tools like NuTCRACKER or Interix provide a basis for software development in a style similar to UNIX, with make files and UNIX APIs, but with direct WIN32 access for performance. UNIX Shell scripts can be migrated with the help of such products as MKS Toolkit, Hamilton C Shell (from 02/04/00 HP VISUALIZE WORKSTATIONS 3

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8

02/04/00
HP VISUALIZE WORKSTATIONS
3
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 environment. Along with the required
functionality and integration, performance is a prime factor indicating which path of
migration should be taken, as depicted in figure 1.
Figure 1: Paths for Migration of the Technical Desktop Environment to Windows
NT Workstations
Migrating all of
the UNIX
Environment
A total conversion and migration of the technical desktop environment from UNIX to
Windows NT workstations could provide better interoperability with data, security and
system infrastructure. In addition, performance of applications with high levels of GUI
interaction may benefit from NT native hosting. Also, the outcome of this migration effort
can be enhanced integration with Windows office applications like spreadsheets, email
and the like.
There are tools for porting your UNIX applications to NT and there are tools for migrating
or allowing your system scripts to run. Software porting tools like NuTCRACKER or
Interix provide a basis for software development in a style similar to UNIX, with make
files and UNIX APIs, but with direct WIN32 access for performance. UNIX Shell scripts
can be migrated with the help of such products as MKS Toolkit, Hamilton C Shell (from