|
|
|
| ||||
 |
 |
 |
||
| CORE Home > Our Company > E-Bulletin |
|
Volume 3 Welcome to the third issue of our e-bulletin. Please feel free to forward it to your colleagues. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Migration Spotlight: .NET and Java vs. PowerHouse. Are they really that different? These days, many PowerHouse programmers are finding themselves in a dilemma. Because no one knows the corporate PowerHouse applications quite as intimately as the resident PowerHouse programmer, Senior Managers are turning to them for help in finding viable PowerHouse replacement solutions. The problem is, often times the implementation of a new solution leaves the PowerHouse developer out in the cold. Whether the solution is a package or a re-engineered application, once the new solution is in place the PowerHouse developer no longer has the expertise to justify his existence with the company. Or does he? Enter CORE Controls. CORE Migration technology includes a set of .NET or Java controls that replace the functions of PowerHouse verbs. PowerHouse developers will immediately recognize the powerful features and functionality provided by this rich set of controls and quickly make the association with the appropriate PowerHouse functionality. Screen design and field manipulation functionality in CORE Controls closely matches the capabilities of the PowerHouse field statement. CORE Migration also retains the concept of a PowerHouse dictionary. The PowerHouse dictionary is a powerful engine that allows programmers to easily make global changes to data element properties. CORE Migration has developed the CORE Framework, which transforms this capability in Java and .NET. The PowerHouse dictionary functionality is relatively unknown in the Java and .NET world, but is immediately understood by PowerHouse developers. The new code behind a PowerHouse application that has been migrated using CORE Migration looks strikingly similar to the original PowerHouse code, even though it is written in Java or .NET. CORE Controls and the CORE Framework are of great benefit to PowerHouse developers because the underlying code in the newly migrated application will be instantly familiar to them, enabling them to support and develop the new application from the first day that it is integrated. This also benefits the company/ IT Department in that they are able to retain the talent and expertise that they have invested heavily in; these people understand the legacy application and business logic inside and out. Losing these key people and retraining new staff is extremely expensive. In summary, a PowerHouse application that has been migrated using CORE Migration is an efficient, state-of-the-art application that leverages the advanced features found in Java and .NET. And because the code behind an application that has been migrated using CORE Migration has terminology and architecture that is consistent with the legacy PowerHouse application, PowerHouse experts can use their extensive knowledge of the legacy application to continue to deliver value to their employers, and firms need not restructure their IT departments to support the new technology. For more information on CORE Controls and the CORE Framework please contact us. Migration Tip: Migrating the Database Migrating a legacy non-relational database is a three-step process. The first step is to create a relational database that mirrors your legacy database. This can be done by examining the tables in the legacy database, and then writing SQL scripts that will create the same structure in the new relational database. Certain data structures supported by PowerHouse, such as Occurs, Redefined By, and Begin Structure, have no equivalent in relational database models and will have to be analyzed to determine the best method of conversion while still supporting the business requirements. The second step in the process is extracting the data from the legacy database. This can be done by writing PowerHouse programs that generate subfiles of the database tables. Generally, the most versatile data format is a portable subfile with comma-delimited fields. The final step is to write a program that will load your converted data into the relational tables. The CORE Migration method contains a phase called Design Preservation. The complex task of developing the database structure and data conversion programs as described above is automated during the Design Preservation Phase, which ensures highly accurate, reliable database conversions in a fraction of the time required for a manual conversion.  Question: How do I convert PowerHouse procedures to Java or .NET? Answer: PowerHouse procedures can be can be developed in your new technology in a couple of different ways. One method is to write and execute SQL in the middle tier. A second option is to use stored procedures on the back-end (database). Either way, manual coding of stored procedures is an extensive, time-consuming process, because you must decipher both the PowerHouse source code and the database. The CORE Migration method automates the development of stored procedures, which is reason why CORE is able to migrate legacy PowerHouse applications much faster than can be done manually. |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
