intra-mart Accel Platform 2014 Winter(Iceberg) / Release Note Initial Version 2014-12-01

Table Of Contents ≪  8.2. Platform Functions 8.2.2. Common  ≫

8.2.1. Setup / Environment Build

8.2.1.1. There are remarks when building intra-mart Accel Platform as a distributed system.

  • System clock on every server OS should have the same time.
    If the time is significantly wrong or if each system clock for each server OS has different time,
    application and each server process may not function properly.
    In case IMBox is used, clock on the server that runs Apache Cassandra should have
    the same time with clocks on the server that runs intra-mart Accel Platform.

    Please use the single JDK version (and revision) for every server process.
    For every server process, please use JDK that is provided by a single vendor.

8.2.1.2. Deployment process of WAR file may take time depending on the hardware specifications.

  • When WAR file is deployed on the application server, it takes time to do the file deployment process.
    Actual time required depends on the hardware specifications.

8.2.1.3. There are remarks for users connecting intra-mart Accel Platform to SystemDatabase, TenantDatabase, and SharedDatabase.

  • With regard to database connection, when you use the API related to SystemDatabase, TenantDatabase, and SharedDatabase,
    some functions on the operations of schema which are other than the default schema linked to the connection users of SystemDatabase, TenantDatabase, and SharedDatabase do not function properly.
    In case intra-mart Accel Platform is used, please always use the default schema that is linked to the database connection users.

8.2.1.4. Screen will not be displayed correctly unless you select one or more screen themes.

  • In case screen is accessed by Web browser on intra-mart Accel Platform, there are some items to be noted in building the environment.

    In case war file is generated by IM-Juggling, you need to select one or more screen themes.
    Screen will not be correctly displayed if no screen theme has been selected.

    If IM-Mobile Framework module has not been selected in IM-Juggling, please select one or more screen themes from the list below :
    • “intra-mart Accel Platform Standard Theme”
    • “intra-mart WebPlatform ver6.x Wind Theme”
    • “intra-mart BaseModule ver5.x Wind Theme”
    If IM-Mobile Framework module has been selected in IM-Juggling, please select one or more screen themes listed above, and also select “intra-mart Accel Platform Standard Theme for smart phones”.

8.2.1.5. Trial Version (product for trial use) cannot be installed in operations environment.

  • You ae not supposed to install and use the trial version product in the operation environment.
    If you do that, unexpected result may be caused.

8.2.1.6. If the time to session timeout is short when setting up the tenant environment, 404 error will occur when the process is completed.

  • When you do the tenant environment setup or sample data setup,
    if the time to session timeout (session-timeou) which is set in resin-web.xml is short (e.g. 1 minute),
    transition to the 404 error screen will be caused after the completion of setup.
    Please make the time to session timeout longer only when building the environment as above (time to be set depends on environment).
    <*> Session auto-keep function cannot be used to circumvent this phenomenon.
    Session auto-keep function is not available for system management function, because theme is not applied.

8.2.1.7. When intra-mart Accel Platform is started, it is assumed that Database has been already started.

  • When you start intra-mart Accel Platform, Database should have been started in advance.

8.2.1.8. Compilation option should be specified if intra-mart Accel Platform is built on Linux environment.

  • In case intra-mart Accel Platform is built in Linux environment, it is necessary to specify the compilation option depending on the distribution.

    Specific option that is required would vary depending on the distribution.
    Please check the execution result of ./configure command, and specify the necessary option.

8.2.1.9. Operation in the mixed Windows/Linux environment is not possible.

  • When you build the distributed environment in which intra-mart Accel Platform works, operation under the mixed Windows/Linux environment is not possible.

8.2.1.10. Path of the shared directory which Storage refers to should be the same.

  • When you build the distributed environment, it is necessary that the path specified
    as root directory of Storage all refer to the same shared directory.
    If each server has different reference destinations, files that are placed in Storage cannot be shared.

    [Target Setting File]
    <CONTEXT_PATH>/WEB-INF/conf/storage-config.xml

8.2.1.11. Only Japanese, Chinese (zh_CN), and English are available as OS on IM-Juggling.

  • Only Japanese, Chinese (zh_CN), and English are available as OS used on IM-Juggling.

8.2.1.12. User module cannot be placed directly in the modules folder of IM-Juggling.

  • User modules should always be added from within the juggling.im file editor (configuration editor).

8.2.1.13. Setting File and your own program should be set on IM-Juggling and created as WAR files.

  • Setting file and your own program cannot be directly placed on the deploy destinations.
    Please always set them on IM-Juggling, and generate them as WAR files.

8.2.1.14. It is required to do the operation after all the tenant environment setups are completed.

  • Tenant environment setup would be required not only at the initial start up of intra-mart Accel Platform,
    but also at the time of module addition or version update.
    Before you start the system operation, you need to log-in as a system administrator, click [System Administrator Home] > [Tenant Environment Setup],
    and confirm that the message “Tenant Environment is the latest. No module need to be set up.”
    is displayed.
    If there exist modules that need tenant environment setup, prerequisites for operating the modules are not yet met,
    and unexpected result may be generated.

8.2.1.15. Environment which is built with the own certificate is outside the scope of warranty.

  • Environment which is built with the own certificate is outside the scope of warranty.
    (example) You cannot do the file download on the smart phone version.

8.2.1.16. If integrated Windows authetication is enabled in Internet Information Services（IIS）, Web service cannot be used.

  • If integrated Windows authentication is enabled in Internet Information Services（IIS）, Web service through Internet Information Services（IIS） will not be available.

8.2.1.17. If integrated Windows authentication is enabled, some part of linkage function to external software cannot be used.

  • Linkage function to external software has been made available in the integrated Windows environment from intra-mart Accel Platform 2014 Spring.
    Please refer to the Setup Guide for details.
    This is limited when it is completed by 1 request.
    It is not possible to make 2 or more requests by generating the URL to access script development by the external software linkage function and then accessing the URL.

8.2.1.18. There is only 1 tenant that is resolved by integrated Windows authentication.

  • There is only one tenant that is resolved by integrated Windows authentication.
    Integrated Windows authentication cannot be made by multiple tenants.
    Moreover, in the integrated Windows authentication environment, operations listed below are not possible on one application server.

    ・Deploy and operate 2 types of WAR files (there are 2 or more tenants in total).
    ・Create and operate 2 or more virtual tenants (there are 2 or more tenants in total).

8.2.1.19. Character code which is used in intra-mart Accel Platform is UTF-8 only.

  • Available character code is UTF-8.

8.2.1.20. Error log is generated if mod_proxy is used.

  • Error log which is related to comet is generated to apache error log.
    [Wed Mar 13 20:53:06 2013] [error] [client 127.0.0.1] proxy: Error reading from remote server returned by /imart/_system/reverse_ajax/connect, referer: http://XXXXXXXXXX/imart/imbox/mybox?
[Wed Mar 13 20:53:49 2013] [error] [client 127.0.0.1] (20014)Internal error: proxy: error reading status line from remote server XXX.XXX.XXX.XXX:8080, referer: http://XXXXXXXXXX/imart/imbox/mybox?
    This will not impact the operation.

8.2.1.21. If reverse proxy function such as mod_proxy or load balancer is used, it is necessary to always include the context root of AP server in the request.

  • If reverse proxy function such as mod_proxy or load balancer is used, please make sure that you include the context root of AP server in the request.

    [example]

    If AP server side is http://myapp/imart, make the request URL to http://myweb/imart.

8.2.1.23. If tenant environment setup is made before tenant information setting is done, it will be outside the guarantee.

  • When you set up tenant environment using API, please first do the setting of tenant information.
    In this case, pleae make sure that you set the locale and time-zone ID of tenant information.
    Please set the locale that exists in the locale master to the locale.
    Please set the time-zone ID that exists in the time-zone master to the time-zone ID.

8.2.1.24. In case tenant auto resolution function utilizing request information is used, error may occur if the access is made by the request resolved as non existing tenant.

  • In case tenant auto resolution function utilizing request information is used, error may occur if the access is made by the request resolved as non existing tenant.

    By the “request resolved as non existing tenant”, it means for example that
    the environment that implements tenant ID resolution from subdomain
    is accessed by the URL of the subdomain resolved as non existing tenant.

    If the screen of general users is accessed under this situation, error may be generated when accessing tenant information depending on the functions.

8.2.1.25. You are not allowed to create multiple schemas in the database for use by multiple tenants.

  • It is not allowed to create the environment as below:
    [*] This applies only when SQLServer or PostgreSQL is used.
    ../../_images/id42793_01.png

    Tenant

    Database User used for Connection

    Database to be used

    Schema to be connected

    Tenant [tenant-1]

    Connection User [dbuser-1]

    Database [users]

    Schema [schema-1]

    Tenant [tenant-2]

    Connection User [dbuser-2]

    Database [users]

    Schema [schema-2]


    In case you build multiple tenants, please build them for each database connected and not for each schema.
    Additionally, we recommened to separate instances for the performance reason in the production environment.
    ../../_images/id42793_02.png

    Tenant

    Database User used for Connection

    Database to be used

    Tenant [tenant-1]

    Connection User [dbuser-1]

    Database [users-1]

    Tenant [tenant-2]

    Connection User [dbuser-2]

    Database [users-2]

Table Of Contents ≪  8.2. Platform Functions 8.2.2. Common  ≫

Copyright © 2014 NTT DATA INTRAMART CORPORATION

⇄ Sidebar ↑Top