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 1
  • 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 Server Properties for the Full Profile

Configure Server Properties for the Full Profile

Configure the server properties for the full profile of the standalone mode in the standalone-full.xml file.
The standalone-full.xml file is in the following directory:
<
JBoss installation directory
>/standalone/configuration
To configure the server properties, you can run the commands for the configuration from the JBoss Command Line Interface (CLI). To run the JBoss CLI, from a command prompt, navigate to the following directory:
<
JBoss installation directory
>/bin
For more information about configuring server properties, see the JBoss documentation.

Transaction timeout

Ensures that the MDM Hub transactions have enough time to complete. In the
subsystem
 with the name
urn:jboss:domain:transactions:<n.n>
, set
default-timeout=3600
 within the
coordinator-environment
 element.
Run the following command to configure the transaction timeout:
/subsystem=transactions:write-attribute(name=default-timeout,value=3600)

HTTPS protocol

Configures the HTTPS protocol for MDM Hub communications and for ActiveVOS communications with the MDM Hub.
Before you configure the HTTPS protocol, use the Java
keytool
 command to generate a certificate and store it in a keystore. The certificate must be signed by a trusted certificate authority. Note the key alias and keystore password that you create.
To configure the HTTPS protocol, in the subsystem with the name
urn:jboss:domain:undertow:<n.n>
, add the
https-listener
 element to the server configuration.
Run the following command to configure the HTTPS protocol: 
/subsystem=undertow/server=default-server:write-attribute(name=https,value=https)

Maximum post size

Configures the maximum size in bytes of files that you upload. Set the value to the size limit of files that you want to attach in the Data Director application. In the
subsystem
 with the name
urn:jboss:domain:undertow:<n.n>
, set the
max-post-size
 attribute of the
<https-listener name=" <listener type>">
 element to 20000000 or higher. Default is 10000000.
After installing the MDM Hub, set the same value for the Hub Server property
cmx.file.max_file_size_mb
 in the
cmxserver.properties
file.
Run the following command to configure the maximum post size: 
/subsystem=undertow/server=default-server/https-listener=<listener type>/:write-attribute(name=max-post-size,value=<maximum file size in bytes>)

Remoting-connector

Configures the remoting-connector port and socket binding. To log in to the Hub Console from a remote machine, set the port to 4447 and the socket binding to remoting.
In the
subsystem
 with the name
urn:jboss:domain:remoting:<n.n>
, set the
port
 attribute to 4447 for the child element
<socket-binding name="remoting">
 of the
socket-binding-group
 element.
Set the
socket-binding
 attribute to
remoting
 .
By default, remoting-connector security is disabled. If you want to configure remoting-connector security for the MDM Hub, ensure that you configure only the Elytron security framework that is supported.
Run the following command to configure the remoting-connector:
/socket-binding-group=standard-sockets/socket-binding=remoting:add(port=4447)
/subsystem=remoting/connector=remoting-connector:add(socket-binding=remoting)
0 COMMENTS
We’d like to hear from you!