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

Table 1: Migration path comparison summary

Page 7 highlights

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 Moderate Migrating only the minimal client piece Easy Moderate Moderate Moderate Low Moderate Low Moderate Low 02/04/00 The migration path of moving some of the technical UNIX environment to Windows NT workstations provides a solid direction. This path could have the best opportunity in maintaining organizational integrity and high levels of business operations in this transition period. The following points should be used when considering how to migrate to Windows NT: § Pick a networking standard. Use TCP/IP networking. § Know that when implementing NT that the network infrastructure will need to be expanded. § Suggest setting up your domains such that browsing can be turned off. § Consider development environments that provide for application construction in both Windows NT and UNIX. § Acquire system management tools that run in either environment and will manage either. § Standardize on a file access method (SMB, NFS or DFS) that has the interoperability, security and expandability required for the organization and business environment. § Standardize on data formats such that interoperability, integration and data migration costs are minimized. § Provide a security access and authentication standard like Kerberos and DCE. § Provide adequate training to affected personnel. Particularly to development teams prior to designing the new environment. The application code porting and migration steps and the associated techniques can be summarized as follows: § Verify all make files, header files and source code for Windows NT and native language issues. § Re-write non-portable sections of code, such as those portions utilizing /dev/kmem or the Journaling File System, etc. § Consider using the opportunity to re-write the application GUI to use the WIN32 API, as long as the application will only be accessed from NT clients. HP VISUALIZE WORKSTATIONS 6

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

02/04/00
HP VISUALIZE WORKSTATIONS
6
Table 1: Migration path comparison summary
Migration Path
Ease of
Migration
Risk to
Current
Systems
Infrastructure
Acceptance of
Current
Personnel
Performance
Level of NT
Integration
Migrating all of the
UNIX environment
Difficult
High
High
High
High
Migrating some of
the UNIX
environment
Moderate
Moderate
Moderate
Moderate
Moderate
Migrating only the
minimal client
piece
Easy
Moderate
Low
Low
Low
The migration path of moving some of the technical UNIX environment to Windows NT
workstations provides a solid direction. This path could have the best opportunity in
maintaining organizational integrity and high levels of business operations in this
transition period. The following points should be used when considering how to migrate to
Windows NT:
§
Pick a networking standard. Use TCP/IP networking.
§
Know that when implementing NT that the network infrastructure will need to be
expanded.
§
Suggest setting up your domains such that browsing can be turned off.
§
Consider development environments that provide for application construction in both
Windows NT and UNIX.
§
Acquire system management tools that run in either environment and will manage
either.
§
Standardize on a file access method (SMB, NFS or DFS) that has the interoperability,
security and expandability required for the organization and business environment.
§
Standardize on data formats such that interoperability, integration and data migration
costs are minimized.
§
Provide a security access and authentication standard like Kerberos and DCE.
§
Provide adequate training to affected personnel. Particularly to development teams
prior to designing the new environment.
The application code porting and migration steps and the associated techniques can be
summarized as follows:
§
Verify all make files, header files and source code for Windows NT and native
language issues.
§
Re-write non-portable sections of code, such as those portions utilizing /dev/kmem or
the Journaling File System, etc.
§
Consider using the opportunity to re-write the application GUI to use the WIN32 API,
as long as the application will only be accessed from NT clients.