Upgrading from Version 10.0, 10.1, or 10.2

10.3

Back Next

Configure Java Virtual Machines

To configure a Java Virtual Machine (JVM), set Java options by using the JAVA_OPTIONS environment variable. After you edit or add any Java options, restart the JVM.

If you use a WebSphere clustered environment, set the Java options for the following cluster components:

Server. Set all the required Java options on each server in the cluster.

Deployment Manager. Set all the required Java options.

Node agent. Set only heap size by using the

-Xmx

and

-Xms

Java options.

The following table describes the Java options settings:

Java Options	Description
-server	Results in a slower startup but subsequent operations are faster.
-Djava.net.preferIPv4Stack	Specifies whether Java uses Internet Protocol version 4 (IPv4). If the operating system uses Internet Protocol version 6 (IPv6), set to true .
-Ddb2.jcc.charsetDecoderEncoder	Required to use the MDM Hub Sample Operational Reference Store. Enables the JDBC driver to return the Unicode replacement character (U+FFFD) in place of a sequence of bytes that is not a UTF-8 string. Set to 3 .
-Dcom.ibm.crypto.provider.DoRSATypeChecking	Specifies whether Java allows the RSA type encryption of data with private key and decryption with public key. Required for the MDM Hub installer to read the license certificates and for password hashing to work in the MDM Hub. Set to false . If you do not set -Dcom.ibm.crypto.provider.DoRSATypeChecking to false , the Hub Server might not start and you can encounter license errors.
-Djgroups.bind_addr	Interface on which JGroup must receive and send messages. Required in a multinode or clustered environment. Ensure that each node binds to its own network interface.
-DFrameworksLogConfigurationPath	Path to the log4j.xml file.
-Doracle.jdbc.J2EE13Compliant	Specifies whether the system variable for the Oracle driver is fully compliant with J2EE. Set to true . If you do not set the parameter to true, you might encounter Java Database Connectivity (JDBC) issues
-Dmdm.node.groupid	Specifies a group ID for Java Virtual Machines in the MDM Hub implementation. Required only if you want logical groupings of Hub Servers and Process Servers.
-Djavax.management.builder.initial	Class of the initial MBeanServerBuilder to be instantiated. Apache Solr MBeans is required to support smart search in Informatica Data Director. To register Apache Solr MBeans to support smart search in Informatica Data Director, set to javax.management.MBeanServerBuilder .
-Dfile.encoding -Dclient.encoding.override	Required if you want to use Informatica Data Director and use REST APIs to search for records. Set both the Java options to UTF-8 to ensure that you can find and save records that contain UTF-8 characters.
-Dstricttransportsecurity.flag	Specifies whether web browsers must convert all attempts to access Informatica Data Director using the HTTP requests to the HTTPS requests instead. Set to true .
-XX:codecachetotal	JIT code cache size. To enhance the performance of the MDM Hub environment, set to 512m .
-Xmx	Maximum JVM heap size. Set to 4 GB or higher. For example, to set the -Xmx to 4096m , use the following JAVA_OPTIONS environment variable setting: set "JAVA_OPTIONS=-server ... -Xmx4096m"
-Xms	Initial heap size. Set to 2048m .
-Xmso	Required for the Process Server JVMs. Initial stack size for operating system threads. Prevents the application server from shutting down unexpectedly due to low system thread stack size. Set to 4096k .
-Xss	Initial stack size. Set to 2000k .
XX:+UseCodeCacheFlushing	Specifies whether the JVM disposes of compiled code when the code cache is full.
-Dtask.pageSize=<maximum number of tasks>	Specifies the maximum number of ActiveVOS tasks that are retrieved for each request. Default is 5000 . Increase the number if your environment has a large number of tasks.

Rename Saved Search

Table of Contents

Upgrading from Version 10.0, 10.1, or 10.2

Upgrading from Version 10.0, 10.1, or 10.2

Configure Java Virtual Machines

Configure Java Virtual Machines