Table of Contents

Search

  1. Preface
  2. Upgrade Overview
  3. Pre-Upgrade Tasks
  4. Database Tasks
  5. Application Server Tasks
  6. Hub Store Upgrade
  7. Hub Server Upgrade (In-place Upgrade)
  8. Process Server Upgrade (In-place Upgrade)
  9. Resource Kit Upgrade (In-place Upgrade)
  10. Post-Upgrade Tasks
  11. Search Configuration Upgrade
  12. ActiveVOS Post-Installation Tasks for the Application Server
  13. ActiveVOS Post-Upgrade Tasks for Business Entity Adapter
  14. ActiveVOS Post-Upgrade Tasks for Subject Areas Adapter
  15. Troubleshooting the Upgrade Process
  16. Frequently Asked Questions
  17. Processing Existing ActiveVOS Tasks
  18. Configuring Metadata Caching

Upgrading from Version 9.7.1

Upgrading from Version 9.7.1

Configure Java Virtual Machines

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.
-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
.
-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
.
-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.
-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.
-Dmdm.ps.zk.node
Required if you want to use smart search with Solr. Set this Java option on the JVM for the Process Server that is intended to be the ZooKeeper server. Set to
true
.
-Dmdm.ps.search.node
Required if you want to use smart search with Solr. Set this Java option on the JVMs for the Process Servers that will have search processing enabled and function as Solr servers. Set it to
true
.
-Dsearch.service.port
Required if you want to use smart search with Solr. Required if you want to install multiple Process Servers on the same machine but on different JVMs and enable smart search on all the Process Servers on the machine. This Java option specifies the port used by the JVM for the search service. To avoid port conflicts, use the default port for the JVM of one Process Server, and set this Java option to the relevant port numbers for the JVMs of the remaining Process Servers.
-Didd.protocol
Required if you want to deploy Data Director with subject areas. The property is used for application server initialization. Specifies whether the communication protocol to use is HTTP or HTTPS. Default is
HTTP
.
-Didd.mdm.port
Required if you want to deploy Data Director with subject areas using a non-default HTTP or HTTPS listener port. The property is used for application server initialization. Specifies the HTTP or HTTPS listener port used by the JVM for the applications. Default is
8080
.
-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 smart 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 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"
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
.

0 COMMENTS

We’d like to hear from you!