8.19.1 Migrating the project

Projects developed using previous releases of Bean Builder (4.2.2) as well as that of the Management Builder (Release 4.1.1 to Release 4.3 ) can be opened using the Bean Builder 4.4  after migration. The process of migration is necessary to convert the files used by the project to the latest version. In order to simplify  the conversion of older version projects to the latest version the Migration Wizard tool is provided.  The Migration Wizard can be invoked using the BeanBuilderMigrationWizard.bat/sh file that can be found under the <Web NMS Home>/bin/developertools directory.

Steps involved in Migration

• Conversion of the Project, Screen and Source files

• Source Generation & Compilation

Migration Support

• All Projects developed using Bean Builder Release 4.1.1, 4.2 and 4.3 can be migrated to the latest version (Release 4.4).

Resources that are converted

• <YourProject>.proj file

• Screens under <YourProject>/Screens directory

• Source files under <YourProject>/Source directory

Setting up resources for Migration

Jars required by the project(s) of older version , which are not available with the current version, need to be copied to the <Web NMS Homw>/classes directory and added to the CLASSPATH.

Projects made with previous releases of Management Builder tools can also be migrated. The extra resources such as MIBs are automatically copied into the migrated project. But when the project is opened in Bean Builder Release 4.4, the Management Builder related information will not be shown by Bean Builder. However the information will be retained and can be seen when the project is opened using the appropriate tool.

Using the Migration Wizard - Step by Step procedure

Conversion of the Project File and the Screen Files

• Start Migration Wizard from the Web NMS Launcher or by using BeanBuilderMigrationWizard.bat/sh from the <Web NMS Home>/classes directory.

• The first screen of the Wizard will ask for the 'Project File' (.proj).

• Browse and select the .proj file of the project that needs to be migrated.

• Click "Next".

• The next screen will list the 'Resources Used' as shown below.

• Click "Next".

• The next screen asks for the directory under which the converted project needs to be copied to. (By default, it is the projects directory of the latest version of the Bean Builder)

• In case you need to change the destination directory,

• Browse and specify the complete path for placing the converted project. If the directory does not exist, then the directory/directories will be created.

• It is preferable to copy <YourProject> folder and <YourProject>.proj file from the directory you have specified in the projects directory of the Bean Builder and then open the project.

• Click "Next".

• Regenerate Source: This will generate the source files for the project. CLASSPATH settings for generating the source can also be specified here.

• Custom Classpath : This can be customized by the user to add to the classpath any files that are required during regeneration of source for the project.

• An additional entry can be made to the Custom Classpath by using the Browse button.

• When the file chooser comes up after clicking on the Browse button select the .jar,.zip file or the directory that needs to be set in the CLASSPATH and then click on Open.

• To remove an entry from the CLASSPATH or change the order in which classes need to be placed in the CLASSPATH select the entry and use the Remove button and the buttons with the arrow marks respectively.

• System Classpath : This classpath cannot be customized and is the classpath of the Bean Builder tool at start up.

• You can scroll down through the entries in the System Classpath for reference.

• The next screen will have a Log display. This screen will also ask where and in which file the Log Messages should be saved. Saving the log messages to a file is optional.

• Click on the "Convert" button.

• You will see the conversion messages on the Log output and a message whether the Conversion has succeeded. You can refer to the log window for details on what the reason for failure of conversion is and how to solve the same.

• If needed click on the "Log to File " button to save the contents of the Log Output to the  specified Log file

• On Successful conversion, the Project is ready to be loaded in Bean Builder

Compilation of the source files

• The next screen helps to compile the generated source

• If you want to add an entry to the CLASSPATH then click on the Browse button.

• In the File chooser that comes up select the .jar,.zip or the directory that needs to be added to the CLASSPATH and click Open.

• To remove an entry from the CLASSPATH or change the order select the entry and use the Remove button and the buttons with the arrow marks respectively.

• Click "Next" button.

• The next screen will display the Log messages for Compilation as shown below:

• Click Finish to complete the compilation.

• On Successful compilation, the Project is ready to be run from the Bean Builder

Migration in ProListView Bean

There are a few changes in the ProListView bean from Bean Builder 4.4 Beta to Bean Builder 4.4 release. They are as follows.

The table model for ProListView, com.adventnet.beans.probeans.ProListViewTableModel, is changed to com.adventnet.dmp.model.table.RCTableModel. This change is to make the model generic.

The methods that are changed are listed below.

The methods that are removed are listed below.