Execution of Program Created in Previous Version¶

Describes techniques to run a program in |common_base_product|which was run in version 7.2.

This chapter describes about the minimum required support.

Note

For details, refer to migration guide.

Items

Prerequisite
Migration Procedure
- Match With Screen Specifications Of |common_base_product|
- Display in iframe

Prerequisite ¶

Here,  Authorization remains untouched.
In case of migration, any setting can be done by menu migration.
For new/additional development, perform the settings as stated in manual.

Warning

Note the prerequisites given below for following points and modifications.

In case of using API in version 7.2, select compatible modules and module development support library in IM-Juglling.
Migration from version 7.2 is required as a prerequisite for operation of compatible modules.
Storage destination of JSP file has been changed to WEB-INF/view directory of SAStruts standards.

Migration Procedure ¶

Following are 2 techniques to run a program which was run in previous version in |common_base_product|. .

Match with screen specifications of |common_base_product|

Display in iframe.

Refer the following support technique by the application to be run and support accordingly.

Match With Screen Specifications Of |common_base_product|¶

Screen Support (HTML file)¶

Delete frameset, frame tag

It is recommended to change to Ajax loading when exchanging the data between frames

Delete html, body tag
When JavaScript is written in onload attribute of body tag, execute it by using jQuery function.
jQuery(document).ready(function() {
doSomething();
});
Delete <imarttag:imartDesignCss>

Replace head tag

Replace <head> tag with <imui:head> tag.

Replace title bar tag

Replace <imarttag:imartTitleBar> with header tag

Change target of form

Change target=”IM_MAIN” to target=”_top”.

dicon File configuration ¶

Edit the following if required.

s2jdbc.dicon

convention.dicon

app.dicon

Logic Support ¶

Provide API support after referring to ‘Compatible_sheet’.

Display in iframe ¶

iframe settings ¶

As a tenant administrator, perform iframe settings after registering the menu.

Warning

Note the following restrictions while using iframe.

If a page using IFRAME is opened in Mymenu, it may not be displayed.
If error page is customized, it is displayed in iframe of IFrame redirector
In screens for which authentication is to be confirmed, URL of the screen of the prerequisites which are to be displayed in iframe cannot be set.

no-theme settings ¶

Since theme gets displayed 2 times when iframe is used,

“no-theme” setting should be done in xml file as shown below in

<im_path>/WEB-INF/conf/theme-no-theme-path-config/.
<?xml version="1.0" encoding="UTF-8"?>
  <theme-no-theme-path-config xmlns="http://www.intra-mart.jp/theme/theme-no-theme-path-config"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://www.intra-mart.jp/theme/theme-no-theme-path-config theme-no-theme-path-config.xsd ">

   <path>/bpw\-.+\.service.*</path>
   <path>bpw/.*</path>
Mention the file path in <path> tag for which theme is not to be displayed.

It can be mentioned in full path as well as regular expression as shown above.

dicon File configuration ¶

Edit the following if required

s2jdbc.dicon

convention.dicon

app.dicon

Logic Support ¶

Provide API support after referring to ‘Compatible_sheet’.

Note

For details, refer to migration guide.