Migration details

 

Migration practices have been tested by migrating assets built on WDK 5.3 to WDK6.0.

WDK6.0 supports backward compatibility, thus causing no major problem during migration.

It has introduced many new features which have been explained in detail in later section, but it is better to get acquainted with all the features, to have their advantages and minimize the probability of error.

These assets could not use all the functionalities of WDK, so some of the modified/deprecated concepts might not be completely tested.

1.1 Migration Practices

1. Take a backup of your customizations
2. Uninstall WDK/Webtop 5.3 or any application using DFC 5.x if you are deploying the WDK/Webtop 6.0/6.0 SP1 on the same app server which hosted 5.3.

Note: Uninstaller currently does not cleanup the classpath. This is known problem with EMC.

Webtop 5.3 and Webtop6.0 are not supported on same app server instance. One or both application fails to load.

It is recommended to have a new instance of app server and install the client on fresh instance. If needed upgrade the appserver according to the environment supported as described above.

1. Test your application.
2. EMC recommends studying out the new features introduced in WDK, and then migrate your application.

Note: Features have been explained in the later section. In this section a brief description is provided.

1. Install any docapp if required. Currently Documentum Application Installer 5.3 Sp5 will support the docapp archive installation in D6 repository.

Note: EMC has also introduced Composer tool which is built on Eclipse framework and has been developed to integrate the Docapp build and installation functionality. This can be also used to install the docapps.

1. Make changes to custom/app.xml if any.

Changes may be required in app.xml, as some of the features have been deprecated and some have been added.

7. Add your customization to the custom folder. Test and fix the application.

1.2 Deprecated Features/Functionalities

1. Streamline View : This feature is disabled by default. The functionality of streamline has been provided in right click menus. This view is supported for previous versions and can be made visible through app.xml changes.

To enable the same, make the following modification in custom/app.xml

<streamlineviewvisible>true</streamlineviewvisible>

To change the entrypoint in webtop to streamline, make the changes in main component.

Note: In D6, default main component has changed and is defined in mainex_component.xml. This component does not mention the entry page for streamline, so mention the path for streamline over here and change the entrypage to streamline.

1. Themes : Documentum 6 introduces a new version of the documentum and high contrast themes. These themes enhance performance and maintainability, and provide additional “look and feel” benefits. In order to use any 5.3 theme, other than these, enable the same in aap.xml by uncommenting the theme. These themes on enabling may not carry new changes introduced in D6.

1. Desupporting Content Transfer applet: The content transfer applet is no longer supported. It is recommended to upgrade custom applications to use the UCF file transfer utility. Even the Tag library for content transfer is also not supported anymore.

1. Checkboxes removal: In Datagrids, selection of objects through checkbox has been changed to row selection. Though the datagrids ( that leverage ActionMultiSelect and ActionMultiSelectCheckBox control ),will be migrated easily, without any modification, the checkbox will not be visible. D6 supports backward compatibility and uses the same controls for row selection as previously used for checkbox. Some new controls have been introduced which may be used according to the application requirement. Datagrids that use generic checkbox may require some modification in jsp. It is also possible to enable the checkbox functionality which has been explained in later section.

1. Hidden Toolbar: Toolbar is no more made visible in D6. It still exists, but has been hiding, as all the functionalities now have been given through right click menu.

Apart from deprecated features, may more new features have been introduced and existing has been enhanced. Most of the features have been explained in detail in later section.

1.3 Issues faced in migrating the assets

1. MenuBar

In the previous versions of webtop, menubar was placed in jsp file. But with D6 , menubar has been moved from jsp to configuration file.

Instead of copying the complete xml file, it is now possible to modify the xml file, thus inserting the customized menu options.

Step 1. Identify the menu file which defines the complete menu

Webcomponent/config/library/menubar/menubar_component.xml

Step 2. Identify the menu to be modified. In the assets , view menu was to be modified.

View menu is described in the element

<menuconfig id="menubar_view_menu">

Step 3. Modify the menu according to the modification process described in this guide

In later sections ‘New Features’ and ‘Sample Application’

Step 4. Save the file and restart the application.

1. Login Component

Login component has been modified in WDK6 to give new look and feel.

Though WDK supported the 5.3 login component, but look and feel also changed to 5.3. To have the same login component as in D6 :

Step 1. Take a backup of your login .jsp

Step 2. Copy the wdk/system/login.jsp to your custom/login.jsp.

Step 3. Merge your custom jsp changes with custom/login.jsp.

Step 4. Save the file and refresh the application

Though WDK supports previous versions, it is better to migrate the application following the newer features introduced in WDK, as they will then maintain consistency and scalability.