HP e3000 server evolution options

Transcription

1 HP e3000 server evolution options

2 Introduction There are many reasons for choosing to buy a new package or build a new application or migrate an existing application. In fact sometimes a combination of some or all of these may be appropriate.

3 The following guide has been compiled to provide our e3000 customers with some choice. Each customer has different needs. The tools we provide from partners across the world allow you to choose how much or how little assistance you require in building your new infrastructure on HP-UX, Windows or Linux. Here are some customer examples: Customer Scenarios Customer A Small/Medium Retail Manufacturing and Accounting users PowerHouse This customer had no internal IT staff and outsourced 100% of the migration. The target platform was Windows NT with MS SQL Server and Axiant. A small VB interface was created to handle the Quiz reports using parameters. Customer B Manufacturing and Distribution 100 users COBOL and Speedware This customer has 4 inhouse developers and has chosen to do the migration themselves. They have chosen ACUCOBOL-GT with the AcuBench TM Screen Designer option to enable moving to a modern user interface. First the code will be migrated on the e3000, then it will be moved to the HP-UX system. Currently they have an entry level HP-UX test machine with Oracle Standard edition for testing of migration procedures. This will be an month project also evaluating Transoft s JCL converter for their JCL requirements. Customer C Manufacturing and Distribution 50 users COBOL This customer has 1 inhouse developer and 1 million lines of COBOL code and would like to do the migration themselves. They will be moving to a Windows environment with ACUCOBOL-GT, Eloquence, ScreenJet and MPUX to make the quickest migration with the least amount of risk. With limited resources the Eloquence and MPUX option made the most sense in being able to utilise existing skillsets and reducing the amount of code changes required. Customer D 200 users, 25 branches and more than 1000 Powerhouse and 800 COBOL programs The target platform is HP-UX, running Java, COBOL and Oracle. Using CORE TM Migration to migrate the PowerHouse code to Java (turnkey) and ACUCOBOL-GT to replace HP e3000 COBOL over time. They will continue to run some applications on the HP e3000 and use Taurus Bridgeware to synchronise (bi-directional) with the Oracle database on the UNIX server. 3

4 Buy, Build or Migrate

5 Buy a Packaged Application You may be able to purchase a packaged application solution. This is a viable alternative if the application and business requirements are fairly standard, and if the company is willing to adapt its business processes to align with those of the packaged application. You may choose to buy an application and still use some of your existing applications as well. Whatever the scenario you will still require tools to migrate your data we have explained two methods and the tools available for this purpose, in the data migration section that follows. Build a new Custom Solution If the customised functionality of your current application is to be retained, the existing application can be duplicated in a modern computing environment such as UNIX, ACUCOBOL-GT and a relational database. Although this build approach provides a better fit with current requirements and greater flexibility for future enhancements than the buy option, it will be time consuming to implement. Do not under estimate the effort involved, the budget, resources, people and training required to complete a rewrite of your applications. Migrate the Legacy Application HP e3000 application migration, in which the existing application is transformed to a modern architecture while preserving the core functionality, uses code migration software to automate the process. The migration process preserves existing application functionality in a modern architecture, while providing the necessary flexibility to meet future business requirements, and rapid time-to-market. The three key requirements for a successful migration are: 1.Procedures: The migration must follow a set of proven procedures to ensure a predictable, high quality result. 2.Technology: Software tools that are designed and optimised to migrate legacy applications and the underlying data structures and databases, to the target technologies, should be used to accelerate the transition process and ensure a quality migration result. 3.People: Use experienced professionals that are intimately familiar with the migration technologies to drive the transition process. 5

6 HP-UX Migration - COBOL Options Option 1: Components: ACUCOBOL-GT & Eloquence ACUCOBOL-GT: The base of Acucorp, Inc s extend 6 family of products is ACUCOBOL-GT. This will give you the core COBOL functionality that you are currently receiving with HP s COBOLII compiler. Each site will need to address the user interface, printing and JCL themselves. This option gives you core COBOL only keeping your Image/SQL calls intact with the use of Eloquence. The Eloquence database is almost 100% compatible with TurboIMAGE. All required database tools are part of the Eloquence product. All intrinsic calls are supported, so you don't need to change your application code. Option 2: & AcuConnect By moving to AcuBench and AcuConnect you move into thin client services which will enable you to modernise your application with a GUI interface. Your VPLUS forms willl need to be rewritten using the AcuBench development suite. Option 3: & AcuConnect + ScreenJet By adding ScreenJet into the bundle, you will be able to automate the conversion of your VPLUS forms into native AcuBench forms. This will enable HP e3000 applications thus migrated to benefit from the full ACUCOBOL-GT development and deployment options. All VPLUS calls are supported, so you don't need to change your application code. Option 4: & AcuConnect + ScreenJet + MPUX MPUX enables a seamless transfer of all platform-bound features of your applications. MPUX supplies required MPE services on top of the target operating system. This includes support for jobs, file systems, users and accounts and much more. An important benefit of MPUX is that this happens transparently: migrated applications are never isolated from the native operating environment. 6

7 Linux Migration - COBOL Options Option 1: Components: ACUCOBOL-GT & Eloquence ACUCOBOL-GT: The base of Acucorp, Inc s extend 6 family of products is ACUCOBOL-GT. This will give you the core COBOL functionality that you are currently receiving with HP s COBOLII compiler. Each site will need to address the user interface, printing and JCL themselves. This option gives you core COBOL only keeping your Image/SQL calls intact with the use of Eloquence. The Eloquence database is almost 100% compatible with TurboIMAGE. All required database tools are part of the Eloquence product. All intrinsic calls are supported, so you don't need to change your application code. Option 2: & AcuConnect By moving to AcuBench and AcuConnect you move into thin client services which will enable you to modernise your application with a GUI interface. Your VPLUS forms willl need to be rewritten using the AcuBench development suite. Option 3: & AcuConnect + ScreenJet By adding ScreenJet into the bundle, you will be able to automate the conversion of your VPLUS forms into native AcuBench forms. This will enable HP e3000 applications thus migrated to benefit from the full ACUCOBOL-GT development and deployment options. All VPLUS calls are supported, so you don't need to change your application code. Option 4: & AcuConnect + ScreenJet + MPUX MPUX enables a seamless transfer of all platform-bound features of your applications. MPUX supplies required MPE services on top of the target operating system. This includes support for jobs, file systems, users and accounts and much more. An important benefit of MPUX is that this happens transparently: migrated applications are never isolated from the native operating environment. 7

8 Windows Migration - COBOL Options Option 1: Components: ACUCOBOL-GT & Eloquence ACUCOBOL-GT: The base of Acucorp, Inc s extend 6 family of products is ACUCOBOL-GT. This will give you the core COBOL functionality that you are currently receiving with HP s COBOLII compiler. Each site will need to address the user interface, printing and JCL themselves. This option gives you core COBOL only keeping your Image/SQL calls intact with the use of Eloquence. The Eloquence database is almost 100% compatible with TurboIMAGE. All required database tools are part of the Eloquence product. All intrinsic calls are supported, so you don't need to change your application code. Option 2: & AcuConnect Option 3: & AcuConnect + ScreenJet By adding ScreenJet into the bundle, you will be able to automate the conversion of your VPLUS forms into native AcuBench forms. This will enable HP e3000 applications thus migrated to benefit from the full ACUCOBOL-GT development and deployment options. All VPLUS calls are supported, so you don't need to change your application code. Option 4: & AcuConnect + ScreenJet + MPUX MPUX enables a seamless transfer of all platform-bound features of your applications. MPUX supplies required MPE services on top of the target operating system. This includes support for jobs, file systems, users and accounts and much more. An important benefit of MPUX is that this happens transparently: migrated applications are never isolated from the native operating environment. By moving to AcuBench and AcuConnect you move into thin client services which will enable you to modernise your application with a GUI interface. Your VPLUS forms willl need to be rewritten using the AcuBench development suite. 8

9 HP-UX Migration - COBOL Options with RDBMS Option 1: Components: ACUCOBOL-GT & RDBMS ACUCOBOL-GT: The base of Acucorp, Inc s extend 6 family of products is ACUCOBOL-GT. This will give you the core COBOL functionality that you are currently receiving with HP s COBOLII compiler. Each site will need to address the user interface, printing and JCL themselves. This option will require substantial rework of the I/O calls. You will need to change your calls from DBOPEN, DBGET etc to embedded SQL or Dynamic SQL. Option 2: Components: ACUCOBOL-GT & RDBMS+ Transoft Transoft s code converter can be used to intercept the Image calls, thus allowing your COBOL code to remain unchanged. Option 3: Components: ACUCOBOL-GT & RDBMS& Transoft + AcuBench & AcuConnect By moving to AcuBench and AcuConnect you move into thin client services which will enable you to modernise your application with a GUI interface. Your VPLUS forms will need to be rewritten using the AcuBench development suite. Option 4: Components: ACUCOBOL-GT & RDBMS & Transoft + AcuBench & AcuConnect + ScreenJet By adding ScreenJet into the bundle, you will be able to automate the conversion of your VPLUS forms into native AcuBench forms. This will enable HP e3000 applications thus migrated to benefit from the full ACUCOBOL-GT development and deployment options. All VPLUS calls are supported, so you don't need to change your application code. Option 5: Components: ACUCOBOL-GT & RDBMS & Transoft + AcuBench & AcuConnect + ScreenJet + Transoft s JCL Converter Transoft's JCL Convertor is a part of its HP e3000 Legacy Liberator migration tool kit. Its purpose is to greatly reduce the amount of effort required to replace the MPE Job Control with the appropriate Job Control in an open (UNIX, Linux or Windows) environment. Because of the nature of Job Control environments it is impossible to fully automate its conversion, however this tool brings in very high level of automatic conversion to minimise the amount of manual effort. 9

10 Data Migration Many businesses and enterprises get nervous when comes the time to migrate. Understandable enough. You ve invested heavily in your third and fourthgenerational language (3GL and 4GL) applications. Not to mention your databases, which frequently constitutes years of hard work and irreplaceable information - information and material to which you constantly refer and which is the life-blood of your business. You want a migration that will not leave your invaluable resources (i.e. your data) inaccessible for any length of time and will not disrupt your business flow. You require a database migration solution that is quick and easy to use but also powerful enough to let you maintain control over the entire process. There are two main approaches that can be used for data migration. From a simpler replication which minimises application code changes and side-steps the need to introduce new structural changes - to the more complex cleaning and refining method, where application codes change as they neatly adapt while the application database accesses the new structure.

11 Data Migration Recommendations Database migration can be performed in a number of ways. We recommend one of the following methods: Replicate the source database structure in the new RDBMS to the extent possible without introducing new structure changes. This method will minimise application code change, particularly if using an intrinsic mapping technology or a 4GL that is database-independent. "Clean" and refine your database structure and the data associated to it as you migrate. This method is more complex and usually introduces application code change in order to adapt the application database access to the new structure. Most companies prefer the replication method, as it allows them to be up-and-running quickly since testing is performed earlier. There are two tool sets available that will greatly assist you in your data migration needs. migrate their TurboImage, KSAM and flat-file databases to Oracle or Microsoft SQL Server. DBmotion automates most of the conversion process, saving you time and effort. Its features and its underlying methodology are based on years of actual database migration experience. This tool is available for download from the Speedware s website. (DBmotion is not double-byte enabled) Sites requiring a phased migration approach where some applications will remain on the 3000 longer than others, but will still need to access migrated data will need the help of Taurus BridgeWare TM solution. BridgeWare, jointly developed by Taurus and Quest Software, is able to extract, transform and move data in bulk or near real time, between MPE, NT and UNIX systems. The product is used to feed data warehouses and reporting repositories, exchange data with web servers, generate test data, update HP3000 data from relational databases, and support staged migration projects with speed and ease. For those site wanting to replicate their data structures, DBmotion, from Speedware is a good tool for moving to Oracle or SQL Server. Speedware's DBmotion is an affordable database migration tool that has been specifically designed to help HP e3000 customers 11

12 For more information please contact your local Hewlett-Packard representative or Pathway Pacific. Pathway Pacific Pty Ltd Unit 8, 281 Pacific Highway North Sydney NSW 2060 Australia tel: fax: This guide has been compiled by Hewlett-Packard and Pathway Pacific Pty Ltd. Pathway Pacific has been appointed by Hewlett-Packard as its sole e3000 Platinum Migration Partner in the Asia Pacific region to solve all your migration concerns. Together with your local partners and HP, Pathway Pacific can provide tools and services to greatly simplify your migration. All products mentioned in this document are available in Asia Pacific through Pathway Pacific Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein EEP, 07/2003