C.1 Migration from Old Versions (version 09-50 or later)

(1) Procedure for migrating plugins developed in old versions

By migrating I/O Plugins and Suspend/Resume Plugins developed in an old version (version 09-50 or later), you can use them in Navigation Platform. To migrate such plugins:

1. See 4.1 Creating template plugins and create a new template plugin.

   Apply the values specified in version 09-50 or later to the plugin information property file of the new template.

   Values you must apply:

   The value specified for the userplugin.id key

   The value specified for the userplugin.name key

   The value specified for the userplugin.server.controller.ioaction.type key

   For details about the storage location of the plugin information property file for plugins of version 09-50 or later, see the manual used for development.

2. Overwrite the new template plugin files with the files of version 09-50 or later.

   Table C‒1: List of files for overwriting (common)

   No.	Files of version 09-50 or later	Copy destination folder	Copy is required if:
   1	Files directly under Navigation-Platform-installation-directory\pluginSDK\plugin\plugin-name\WEB-INF\lib	Navigation-Platform-installation-directory\pluginSDK\plugin\plugin-name\WEB-INF\lib	The file to be loaded to Application Class Loader is added.
   2	Files directly under Navigation-Platform-installation-directory\usrlib\app#1
   3	Files directly under Navigation-Platform-installation-directory\usrlib\sys#2	Navigation-Platform-installation-directory\usrlib\sys	The file to be loaded to System Class Loader is added.
   4	Files directly under the path specified for the add.class.path key added by the developer to the option definition file for J2EE servers (usrconf.cfg)#2
   5	Navigation-Platform-installation-directory\pluginSDK \base\dd\META-INF\cosminexus.xml#1	Navigation-Platform-installation-directory\pluginSDK\plugin\plugin-name\dd\META-INF	Resource adapter settings are added.
   6	portal-project\WEB-INF\web.xml#1	Navigation-Platform-installation-directory\pluginSDK\plugin\plugin-name\WEB-INF

   #1

   These files were shared by all plugins in old versions, but are no longer shared in Navigation Platform. Therefore, you need to place these files in all plugins individually.

   #2

   You also need to set the class path in the Option definition file for J2EE servers (usrconf.cfg).

3. For I/O Plugins, further overwrite the files listed below in the new template plugin files.

   Table C‒2: List of files for overwriting (I/O Plugin)

   No.	Files of version 09-50 or later	Copy destination folder	Note
   1	Files directly underNavigation-Platform-installation-directory\pluginSDK\plugin\plugin-name\images	Navigation-Platform-installation-directory\pluginSDK\plugin\plugin-name\images	Copy all the files even if there are more old version files than new template plugin files.
   2	Navigation-Platform-installation-directory\pluginSDK\plugin\plugin-name\WEB-INF\conf\ioaction.xml	Navigation-Platform-installation-directory\pluginSDK\plugin\plugin-name\WEB-INF\conf	Apply the contents of the old version file by editing the file of the same name in the copy destination folder, rather than copying the old file to overwrite the new one. Note that the URL specified for the iconURL tag is different from that of old versions. The value specified for the iconURL tag in old versions "/plugin-name/images/file-name" The value specified for the new iconURL tag "/ucnpPlugins/plugin-name/images/file-name" For migration from 09-60 The button type specified for the diableButtonType tag allows you to distinguish between transfer by buttons and direct transfer. If you want the same operation as that in 09-60, specify true for the legacy attribute.
   3	Navigation-Platform-installation-directory\pluginSDK\plugin\plugin-name\WEB-INF\src\Java-package\controller\I/O-action-controller.java	Navigation-Platform-installation-directory\pluginSDK\plugin\plugin-name\WEB-INF\src\Java-package\controller	Change the character code to UTF-8 while retaining the file contents, and then overwrite the file.

4. For Suspend/Resume Plugins, further overwrite the files listed below in the new template plugin files.

   Table C‒3: List of files for overwriting (Suspend/Resume Plugin)

   No.	File of version 09-50 or later	Copy destination folder	Note
   1	Navigation-Platform-installation-directory\pluginSDK\plugin\plugin-name\WEB-INF\src\Java-package\controller\I/O-action-controller.java	Navigation-Platform-installation-directory\pluginSDK\plugin\plugin-name\WEB-INF\src\Java-package\controller	Change the character code to UTF-8 while retaining the file contents, and then overwrite the file.

5. If the plugin uses a resource adapter, see 4.4 Adding database connection processing and then add resource adapter settings.

6. Build, deploy, and then debug the plugin in the same way as for creating a new plugin.

   • 4.6 Building plugins

   • 4.7 Deploying plugins

   • 4.10 Debugging plugins

To Page Top

(2) Migration of the menu area developed in old versions

In old versions, the menu area was able to be customized by using HTML or JSP files. However, the menu area in Navigation Platform cannot be customized.

To Page Top

(3) Migration of custom windows (new windows) developed in old versions

In old versions, custom windows (new windows) were developed separately from plugins. In Navigation Platform, custom windows (new windows) must also be developed again as plugins.

In old versions, a custom window was required to use the search function. However, you do not need to develop a custom window for the search function in Navigation Platform because the search function is provided by default.

For details about how to develop plugins for custom windows, see Chapter 4. Developing Plugins.

To Page Top

(4) J2EE server settings in old versions

If you have changed J2EE server settings in the development environment of an old version, return the settings to the default values, except for the items described in 4.13.1 J2EE server setting items that can be changed during plugin development.

To Page Top