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
  • 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. 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

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
The following table describes the server properties configuration for the full profile:
Configuration
Description
Transaction timeout
Ensures that the MDM Hub transactions complete. In the
subsystem
 with the name
urn:jboss:domain:transactions:<n.n>
, set
default-timeout=3600
 for the
coordinator-environment
 element.
HTTPS protocol
Required if you want to configure the HTTPS protocol for the 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 keystore and an alias. Note the key alias and keystore password that you create.
To configure the HTTPS protocol, in the
subsystem
 with the name
urn:jboss:domain:web:<n.n>
, add the following
connector
 configuration: 
<connector name="https" protocol="HTTP/1.1" scheme="https" socket-binding="https" secure="true">
   <ssl name="ssl" key-alias="<Key alias>" password="<keystore password>" certificate-key-file="<Security certificate key file path>" protocol="TLSv1" verify-client="false"/>
</connector>
HornetQ Security
If HornetQ security is enabled for the JBoss server, disable it. In the
hornetq-server
 element, set the
security-enabled
 configuration to
false
 as shown in the following example: 
<security-enabled>
false
</security-enabled>
Remoting-connector security
Configures remoting-connector security.
To log in to the Hub Console from a remote machine, disable the remoting-connector security. In the
subsystem
 with the name
urn:jboss:domain:remoting:<n.n>
, remove the
security-realm
 attribute from the following
connector
 configuration: 
<connector name="remoting-connector" socket-binding="remoting" security-realm=<"security realm name">/>
Asynchronous handling of loggers
If the JBoss environment runs on Java 1.7, and you want to use Informatica Data Director, configure asynchronous handling of loggers.
In the
subsystem
 with the name
urn:jboss:domain:logging:<n.n>
, add the following
async-handler
 configuration: 
<async-handler name="ASYNC">
   <level name="INFO"/>
   <queue-length value="1024"/>
   <overflow-action value="BLOCK"/>
      <subhandlers>
         <handler name="FILE"/>
         <handler name="CONSOLE"/>
      </subhandlers> 
</async-handler>
Also, add the
<handler name="ASYNC"/>
 element to the
root-logger
 configuration.
Port configuration for JBoss instances
If you want to install multiple MDM Hub instances on the same machine, you deploy each MDM Hub instance on a separate JBoss instance.
To avoid port conflicts, for each JBoss instance, set the
port-offset
 attribute of the
socket-binding-group
 element to a different value.
Access to the JBoss root welcome page
Disable access to the JBoss root welcome page. For instructions, see the JBoss documentation.
0 COMMENTS
We’d like to hear from you!