Installation Guide for Oracle Database with Red Hat JBoss

10.4 HotFix 2

Back Next

Configure Java Virtual Machines

To configure a Java Virtual Machine (JVM), set Java options by using the JAVA_OPTS environment variable.

You can set the Java options in the following file:

On UNIX.

JBoss installation directory

>/bin/standalone.conf

On Windows.

JBoss installation directory

>\bin\standalone.conf.bat

The following table describes the Java options settings:

Java Options	Description
-server	Results in a slower startup but subsequent operations are faster.
-De360.connection.channel -De360.mdm.host -De360.mdm.port	Application server communication protocol, host, and port. To deploy the MDM Hub applications on a JBoss port other than 4447, set the following Java options: -De360.connection.channel . Set to the communication protocol that you want to use. Valid values are HTTP and HTTPS. Default is HTTP. -De360.mdm.host . Set to the IP address of the JBoss host. If the environment uses the HTTPS communication protocol and the security certificate is issued to a Fully Qualified Domain Name (FQDN), set to the FQDN. -De360.mdm.port . Specifies the listener port where Data Director with business entities communicates with MDM Hub. Default is 8080. If you do not configure these parameters, Data Director screens that are based on the Entity 360 Framework might not work as expected.
-Didd.mdm.host -Didd.mdm.port -Didd.protocol	Required for Data Director with subject areas. To deploy Data Director with subject areas, set the following Java options: -Didd.mdm.host . Set to the host name or IP address of the application server host. -Didd.mdm.port . Required property, used internally by the Data Director with subject areas application during server initialization. Specifies the HTTP or HTTPS listener port used by the JVM for the applications. Default is 8080 . -Didd.protocol . Required property that is used for deploying the subject area application during server initialization. Specifies whether the communication protocol to use is HTTP or HTTPS. Default is HTTP .
-Dio.undertow.legacy.cookie.ALLOW_HTTP_SEPARATORS_IN_V0	Mandatory property if you are using JBoss Version 7.3. Set to true to set the property as a system property and prevent REST API authentication failure of a business entity service request that did not contain required credentials due to truncated cookie values. Default is false . You do not need to set this property for JBoss Version 7.1 or 7.2.
-Djava.net.preferIPv4Stack	Specifies whether Java uses Internet Protocol version 4 (IPv4). If the operating system uses Internet Protocol version 6 (IPv6), set the property to true . As a result, the application can communicate only with IPv4 hosts. Default is false.
-Djava.net.preferIPv6Addresses	Specifies whether Java uses Internet Protocol version 6 (IPv6). When a host has both IPv4 and IPv6 addresses, and the operating system uses IPv6, the default behavior is to prefer IPv4 addresses, to ensure backward compatibility. Set to true to ensure that the application communicates only with IPv6 hosts, where possible. Default is false .
-Djavax.net.ssl.trustStore -Djavax.net.ssl.trustStorePassword	Required if you want to use an HTTPS port for the Process Server. The -Djavax.net.ssl.trustStore Java option specifies the path to the truststore file to use for validating client certificates. The -Djavax.net.ssl.trustStorePassword Java option specifies the password to access the truststore file.
-Djava.security.egd	Reduces the startup time of Data Director in Linux environments. Set the value to file:/dev/./urandom .
-Djboss.as.management.blocking.timeout	Time in seconds to wait for JBoss to deploy. To ensure that JBoss does not fail to start, you can set the value to 5000 . Adjust the time period based on your environment. Default is 300 . If you do not configure the parameter, you might encounter a JBoss deployment timeout.
-Djgroups.bind_addr	Interface on which JGroup must receive and send messages. Required in multinode or cluster environments. Ensure that each node binds to its own network interface.
-DFrameworksLogConfigurationPath	Path to the log4j.xml file. Locate the log4j.xml file in the following directories, after they are created: /hub/cleanse/conf /hub/server/conf
-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.
-DUseESLegacyFqSearch	Specifies whether fielded search returns exact matches from within child nodes for a business entity type. Applicable only when you perform a fielded search on multiple fields. Indicates whether a search must return records that contain search values in the same child node if multiple query fields are at the child level. Set to true to return records that might match the child level query field from different child nodes. Default is false .
-Dfile.encoding -Dorg.apache.catalina.connector.URI_ENCODING	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.
-Dorg.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE	Maximum size of the HTTP headers, in bytes. The search requests might fail if the header size is low. Set to 16384 .
-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.
-Dstricttransportsecurity.flag	Specifies whether web browsers must convert all attempts to access Data Director using the HTTP requests to the HTTPS requests instead. Set to true .
-Xms	Initial heap size. Set to 2048m .
-Xmx	Maximum JVM heap size. Set to 6 GB or higher. For example, to set the -Xmx to 6144m , use the following JAVA_OPTIONS environment variable setting: set "JAVA_OPTIONS=-server ... -Xmx6144m"
-XX:+UseCodeCacheFlushing	Specifies whether the JVM disposes of compiled code when the code cache is full.
-XX:ReservedCodeCacheSize	JIT code cache size. To enhance the performance of the MDM Hub environment, set to 512m .
-XX:MaxMetaspaceSize	Maximum metaspace size. To prevent the JVM from running out of memory, set to 1G .

Rename Saved Search

Table of Contents

Installation Guide for Oracle Database with Red Hat JBoss

Installation Guide for Oracle Database with Red Hat JBoss

Configure Java Virtual Machines

Configure Java Virtual Machines