Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Multidomain MDM 10.3 HotFix 2
  • All Products

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. Appendix A: Troubleshooting the Upgrade Process
  16. Appendix B: Frequently Asked Questions
  17. Appendix C: Processing Existing ActiveVOS Tasks
  18. Appendix D: Configuring Metadata Caching

Upgrading from Version 9.0.1 or 9.1.0 for Oracle

Upgrading from Version 9.0.1 or 9.1.0 for Oracle

Back Next

Configure the Java Virtual Machines

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
.
-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.mdm.host
Application server host.
Set the Java option in one of the following scenarios:
  • If you want 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.
  • If you want 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 your environment uses the HTTPS communication protocol and the security certificate is issued to a Fully Qualified Domain Name (FQDN), set the hostname to the FQDN displayed in the security certificate.
If you do not configure this parameter, Informatica 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:
  • If you want 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.
  • If you want 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, Informatica Data Director screens based on the Entity 360 Framework might not work as expected
-De360.connection.channel
Specifies the communication protocol the Entity 360 application uses to communicate with the MDM Hub Server. Specify whether the communication protocol to use is EJB, HTTP or HTTPS. Default is
-De360.connection.channel=http
. Ensure you set the supporting application server host property
-De360.mdm.host
 and application server port property
-De360.mdm.port
 to the default values.
-Dfile.encoding
-Dweblogic.http.URIDecodeEncoding
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.
-DFrameworksLogConfigurationPath
Sets the
log4j.xml
 file configuration path.
-DUseSunHttpHandler
Specifies whether WebLogic uses the Sun HTTP Handler for the HTTP connection between the MDM Hub and the Informatica platform. Set to
true
.
-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 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
.
0 COMMENTS
We’d like to hear from you!