Configuring and Deploying ibi MDM On the Tomcat Server

To configure and deploy ibi MDM on the Tomcat server, follow the steps below:

    Procedure

  1. Add the following VM parameters in standalone.conf (Linux) or standalone.conf.bat (Windows):

    --add-exports=java.base/jdk.internal.misc=ALL-UNNAMED
    --add-exports=java.base/sun.nio.ch=ALL-UNNAMED
    --add-exports=java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED
    --add-exports=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED
    --add-exports=java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED
    --illegal-access=permit
    --add-opens jdk.management/com.sun.management.internal=ALL-UNNAMED

    For example, in standalone.conf.bat (Windows) set parameters as shown in the following sample:

    "JAVA_OPTS=%JAVA_OPTS% --addexports=
    java.base/jdk.internal.misc=ALL-UNNAMED"
    "JAVA_OPTS=%JAVA_OPTS% --add-exports=java.base/sun.nio.ch=ALL-UNNAMED"
    "JAVA_OPTS=%JAVA_OPTS% --addexports=
    java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED"
    "JAVA_OPTS=%JAVA_OPTS% --addexports=
    jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED"
    "JAVA_OPTS=%JAVA_OPTS% --addexports=
    java.base/sun.reflect.generics.reflectiveObjects=ALLUNNAMED"
    "JAVA_OPTS=%JAVA_OPTS% --illegal-access=permit"
    "JAVA_OPTS=%JAVA_OPTS% --add-opens
    jdk.management/com.sun.management.internal=ALL-UNNAMED"

  2. Set the environment variable required for ibi MDM in the Tomcat server.

  3. Specify max-post-size and max-parameters-count:

    Parameter Name Description Example
    max-post-size For uploading a file either through a web service or the ibi MDM UI, the maximum file size limit is 10 MB. If you want to upload a file greater than 10MB, add the max-post-size parameter and change the file size. You also need to change the value of the Upload File Size Limit property in the Configurator.

    For information about uploading a file through the ibi MDM UI, see the section "Creating Records" in ibi MDM User Guide. 

    <server name="default-server">
<http-listener name="default" socket-binding="http" redirect-socket="https" enable-http2="true" max-post-size="974247881"/>
<https-listener name="https" socket-binding="https" security-realm="ApplicationRealm" enable-http2="true"/>
<host name="default-host" alias="localhost">
<location name="/" handler="welcome-content"/>
<filter-ref name="server-header"/>
<filter-ref name="x-powered-by-header"/>
</host>
</server>
    max-parameters-count The maximum number of parameters that can be added to the ibi MDM URL into the browser. Using this value, you can avoid the hash exposure used in the URL. This applies to both query and POST data parameters.

    By default, the size of the max-parameters-count is 1000. You can change the value as per your requirement.

    Note: For ibi™ MDM Add-on for Global Data Synchronization, the number of limits might cross due to a huge number of attributes. Therefore you must set max-parameters-count="10000". For example,

     <http-listener name="default" socket-binding="http" redirect-socket="https" enable-http2="true" max-parameters-count="10000"/>

    		 
    <server name="default-server">
<http-listener name="default" socket-binding="http" redirect-socket="https" enable-http2="true" max-post-size="974247881" max-parameters-count="5000"/>
<https-listener name="https" socket-binding="https" security-realm="ApplicationRealm" enable-http2="true"/>
<host name="default-host" alias="localhost">
<location name="/" handler="welcome-content"/>
<filter-ref name="server-header"/>
<filter-ref name="x-powered-by-header"/>
</host>
</server>

  4. Specify the session timeout.

    The Tomcat server provides the default session timeout of 30 minutes. To modify the session timeout as per your business requirement, modify the following entry in the application web.xml file. This file is present in the %TOMCAT_HOME%\conf folder.

    <session-config>
     <session-timeout>30</session-timeout>
    </session-config>

  5. Configure EMS and start the server.

  6. (Optional) Configure the ibi Patterns - Search server & start the Tomcat server.

  7. To deploy ibi MDM custom pages to a common folder in the cluster environment, set the following parameter:

    -DMQ_CUSTOMFORMS_HOME=MQ_COMMON_DIR

  8. Download the following jars from Maven and copy them into the Tomcat/lib directory.

    • tibjms.jar

    • database-specific JDBC jar

    • javax.xml.soap-api-1.4.0 (j2ee spec jar)

    • javax.jms-api-2.0 (j2ee spec jar)

    • activation-1.1.1.jar (j2ee spec jar)

    • saaj-impl-1.5.0.jar

    • stax-ex-2.1.0.jar

    • mail-1.4.jar

  9. Add the following datasource resource configuration to Tomcat/conf/context.xml
    (PostgreSQL sample):

    <Resourcename="jdbc:/eCMDataSource"
 auth="Container"
 type="javax.sql.DataSource"
 maxTotal="100"
 maxIdle="30"
 driverClassName="org.postgresql.Driver"
 url="jdbc:postgresql://localhost:5432/trunk1"
 username="trunk1"
 password="trunk1"
/>

  10. Update ApplicationServerType to TOMCAT in the ConfigValues.xml file.

  11. Start the Tomcat server.