Up to Documents in VAGen Migration to EGL Hub

VAGen Migration - Tools for Rename User Exit, Implicit Items, JSP Conversion

VERSION 4 Published

Created on: May 2, 2008 6:52 AM by Jeri - Last Modified:  Jan 7, 2009 7:47 AM by Jeri


Update on Jan 6, 2008: The 3 white papers on the developerWorks Exchange site have been updated to support EGL versions 6.0.1.2 ifix001, 7.1, 7.5, and 7.5.1.

There are 3 white papers with accompanying tools for VAGen migration that are stored on the developerWorks Exchange site. The 3 white papers and tools are:


  • Tool to create implicit items before running Stage 1 at::
http://www-128.ibm.com/developerworks/exchange/dw_entryView.jspa?externalID=591&categoryID=1063
  • Sample Rename User Exit for Stage 2:
http://www-128.ibm.com/developerworks/exchange/dw_entryView.jspa?externalID=592&categoryID=1063
  • Tool to migrate customized JSPs for Web Transactions at:
http://www-128.ibm.com/developerworks/exchange/dw_entryView.jspa?externalID=593&categoryID=1063
Tags: vagen_migration, stage_1, vagen_on_java, vagen_on_smalltalk, stage_2, web_transaction
Average User Rating
(2 ratings)




Comments (3)
Oct 10, 2008 2:35 AM Click to view starki7's profile starki7 says:

Hi Jeri!

VAGen Migration from Java - How to Split Common and Unused Parts files white paper on the page http://www-128.ibm.com/developerworks/rational/products/egl/egldoc.html#sec9 isn't updated for version 7.1.
Do you have plans to update it.

I thought to use it to move certain VAGen part types, like User Interface Records, to custom packages.

Thanks and Regards,
Goran

Oct 10, 2008 8:33 AM Click to view Jeri's profile Jeri says: in response to: starki7

As you noticed the "Splitting Common and Unused Parts" white papers are not here. This is because the Stage 1 tools were completely rewritten for RBD 7.1 and the splitting technique in the white paper cannot be used any longer. This might sound like bad news, but it is actually good news. We moved the technique inside the migration tool. You just have to enable the splitting and specify how many characters you want. We also added a technique to place all the data items in a separate (new) project. You just have to enable the placement.

See the VAGen to EGL Migration Guide,

    • Chapter 4 "Stage 1 -- Extracting from Java", section "Before you run the Stage 1 tool -- hints and tips", subsection "Customizing the Stage 1 migration tool"
    • Chapter 5 "Stage 1 -- Extracting from Smalltalk", section "Before you run the Stage 1 tool -- hints and tips", subsection "Customizing the Stage 1 migration tool"

The other thing that you will notice is that the parts placement in Stage 1 is now done by SQL queries. So it should be a bit easier to write your own queries to force parts to a particular package or project. For example, look at the code that is used for placing all the data item parts in a new project. You could do a similar thing for the User Interfacee Records, possibly including something to check for "org = USERINTERFACE" in the WHERE clause to be sure that you only modify the placement of UI records.

Oct 10, 2008 9:12 AM Click to view starki7's profile starki7 says:

I was studying that white paper, and at first thought that I could use that technique, but later "find out" that I can't separate just UI records and put them in the whole new package with custom name.

I will reread it once more and give it a try.

Thanks,
Goran

More by Jeri

View Jeri's profile
Bottom Banner