Considerations on merging code for upgrading iPortal

• iPortal front-end code merge considerations
  • Use WinMerge to synchronize the code
• iPortal rear-end code merge considerations

iPortal front-end code merge considerations

iPortal's js file is located at: Custom_Portal\WebContent\WEB-INF\classes\staticFiles\js Directory, ftl file is under locatedCustom_Portal\WebContent\WEB-INF\classes\templates directory.

Based on iPortal front-end code customization, create folder classes in% SuperMap iPortal_Home% \ webapps \ iportal \ WEB-INF directory, which can be the directory of the Custom_Portal project, that is, % SuperMap iPortal_Home% \ samples \ code \ CustomPortal \ Custom_Portal \ classes Directory all the static resource files copied to the% SuperMap iPortal_Home% \ webapps \ iportal \ WEB-INF \ classes directory.

Before upgrading iPortal for code merge, it is recommended to use WinMerge to compare folders, compare or decrease files, and compare the modified iPortal source code with the upgraded iPortal source code. Changes can not be synchronized to the upgrade The iPortal source code, if the changes are great, do not recommend upgrading.

Use WinMerge to synchronize the code

1. After installing WinMerge, select a folder to compare right click and click WinMerge.

2. In the pop-up dialog box fill in another directory to compare, and click OK.

3. WinMerge will be listed after the comparison of the results, usually will contain three kinds of icons, as shown in the following figure:

among them:

• Icon 1: indicates that the file or directory exists only in one of the two folders that are compared
• Icon 2: indicates that the contents of the file are exactly the same in the two folders (no synchronization required)
• Figure 3: shows that the two folders have the file, but the specific content of the file is inconsistent

4. If the file or folder exists only in one of the two folders, you can right-click on the file.

5. If the contents of a file in the two folders are inconsistent, you can double-click the file to view the inconsistent content, modify and synchronize.

note:Suggest changing iPortal ftl and js source code when custom development if the change is small; if change is big you best to create a new folder, write a separate ftl and js file into it, and then in the iPortal source code introduced (ftl File using <#include> introduction, js file using <script> introduction), this can be a certain degree of convenience for iPortal upgrades and maintenance in the future .

iPortal rear-end code merge considerations

Based on iPortal code customization, create folder classes in% SuperMap iPortal_Home% \ webapps \ iportal \ WEB-INF directory, which can be the directory of the Custom_Portal project, that is, % SuperMap iPortal_Home% \ samples \ code \ CustomPortal \ Custom_Portal \ classes Directory all the static resource files copied to the% SuperMap iPortal_Home% \ webapps \ iportal \ WEB-INF \ classes directory.

Based on jersey custom custom development, in the tomcat installation directory / webapps directory to create a new folder name for the custom, % SuperMap iPortal_HOME% \ samples \ code \ ExtendPortal \ Custom_App_Sample \ WebContent directory all the files Copy to the tomcat installation directory in the webapps directory, and then% SuperMap iPortal_HOME% \ webapps \ iportal \ WEB-INF \ lib directory as shown in the following chart to the package% apache-tomcat% \ webapps \ custom \ WEB -INF \ lib directory.