Shyam,
For IM 4.0, the Java has been completely refactored from one main project into three different component packages. Most of the class names remain the same, but some have been merged or renamed. The method names are mostly identical I believe, so you could use those to find certain code blocks from 3.2 in the new 4.0 structure. The classes were also further enhanced to support using factory create methods for objects, stephandler and bapi classes. This was done to allow for easier extension of the base classes using parameters set up in the configuration panel. The Agentry definitions were also changed to fix 3.2 bugs and add tablet, phone and Windows WPF screen support.
First, you or your customer needs to seek permission from SAP through your sales representative to own the source code for IM 4.0. The source is no longer available out of the box as it was in 3.2.
I would suggest starting with the new 4.0 and merging both your Java and Editor changes into the new version from your modified 3.2. Trying to go the other way from 4.0 into your 3.2 is the wrong way to approach things, and would be nearly impossible.
Identify the changes in your 3.2 compared to the out of box 3.2, then find these integration points one by one in the new 4.0 version.
If merging a java section, Identify where the java code needs to go in the new structure by searching the new components for the same class name, or do a file search in Eclipse to look for the method names if the class name has changed. You will probably need to modify your original changes to make them fit into the new coding and factory class style of the 4.0 java.
For editor definitions, you will need to modify all screen platforms you plan to deploy on. Other changes will probably be pretty easily integrated because there was no new functionality added to base IM. You will notice Warehouse Management definitions that were added, but you should be able to work around these. Use the "Compare With" option after right clicking the open IM 4.0 Agentry project to import your 3.2 changes. Some modifications will need to be hand entered, but use the import tool where possible. Make sure you aren't overwriting any new essential definitions that have been modified since 3.2 with your changes. Examine the differences first visually between the new 4.0 and unmodified 3.2 to make sure nothing has been added that your modifications would damage.
Jason Latko - Senior Product Developer at SAP
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.