Installation Guide for Oracle Database with WebLogic

10.5

Back Next

Configure the Java Virtual Machines

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

You can set the Java options in the following file:

On UNIX.

WebLogic domain

>/bin/setDomainEnv.sh

On Windows.

WebLogic domain

>\bin\setDomainEnv.cmd

The following table describes the Java options:

Java Options	Description
-server	Results in a slower startup but subsequent operations are faster.
-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.
-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 .
-Djava.security.egd	Reduces the startup time of Informatica Data Director in Linux environments. Set the value to: Djava.security.egd=file:/dev/./urandom
-Doracle.jdbc.J2EE13Compliant	Sets the oracle.jdbc.J2EE13Compliant system variable. Set to true . If you do not set the parameter to true, you might encounter Java Database Connectivity (JDBC) issues
-Djavax.wsdl.factory.WSDLFactory	Required for the WebLogic 12.2.1 or later environments to invoke a service WSDL that might have a default namespace prefix. Set to com.ibm.wsdl.factory.WSDLFactoryImpl .
-DANTLR_USE_DIRECT_CLASS_LOADING	Required for launching WebLogic 12.2.1 or later environments on which the MDM Hub is deployed. Set to true .
-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.
-De360.connection.channel	Communication protocol that the application server must use for communication between the Hub Server and the Data Director screens based on the Entity 360 Framework. Valid values are HTTP and HTTPS. Default is HTTP. Ensure that you set the following supporting Java options: -De360.mdm.host -De360.mdm.port
-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 .
-Dweblogic.security.SSL.trustedCAKeyStore -Dweblogic.security.SSL.enable.renegotiation -Dweblogic.security.SSL.verbose	Required if HTTPS is enabled for WebLogic. The -Dweblogic.security.SSL.trustedCAKeyStore Java option specifies the path to the keystore that contains the trusted certificates. Set to the absolute keystore path. The -Dweblogic.security.SSL.enable.renegotiation Java option enables SSL renegotiation. Set to true . The -Dweblogic.security.SSL.verbose Java option enables additional SSL debugging. Set to true .
-De360.mdm.host	Application server 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. Set the Java option in one of the following scenarios: To deploy the MDM Hub applications only on Managed Servers, add the Java option to the script of each Managed Server. Set to the IP address or symbolic name of the Managed Server. To deploy the MDM Hub applications on a WebLogic port other than 7001, add the Java option to the application server startup script. Set to the IP address or symbolic name of the WebLogic host. If you do not configure this parameter, Data Director screens based on the Entity 360 Framework might not work as expected.
-De360.mdm.port	Application server port. Set the Java option in one of the following scenarios: To deploy the MDM Hub applications only on Managed Servers, add the Java option to the script of each Managed Server. Set to the port number of the Managed Server. To deploy the MDM Hub applications on a WebLogic port other than 7001, add the Java option to the application server startup script and set to the port number. If you do not configure this parameter, Data Director screens 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 .
-Dfile.encoding -Dweblogic.http.URIDecodeEncoding	Required if you want to use 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.
-DFrameworksLogConfigurationPath	Sets the log4j.xml file configuration path.
-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 .
WLS_MEM_ARGS_64BIT	Memory variable. Set the variable to an appropriate value.
-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 .

Rename Saved Search

Table of Contents

Installation Guide for Oracle Database with WebLogic

Installation Guide for Oracle Database with WebLogic

Configure the Java Virtual Machines

Configure the Java Virtual Machines