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.5 HotFix 3
  • All Products

Table of Contents

Search

  1. Preface
  2. Installation Overview
  3. Pre-Installation Tasks
  4. Hub Store Installation
  5. Hub Server Installation
  6. Hub Server Post-Installation Tasks
  7. Process Server Installation
  8. Process Server Post-Installation Tasks
  9. ActiveVOS Post-Installation Tasks for the Application Server
  10. ActiveVOS Post-Installation Tasks for the Business Entity Adapter
  11. Customize ActiveVOS
  12. Troubleshooting the MDM Hub
  13. Uninstallation

Installation Guide for IBM Db2 with Red Hat JBoss

Installation Guide for IBM Db2 with Red Hat JBoss

Back Next

Collect the Installation Values

Collect the Installation Values

Before you run the installer, collect the installation values. The installer will prompt you for information about your application server, database management system, and other components. The best practice is to print out these tables and add the values for your environment.

Application Server: Red Hat JBoss

Use the following table to collect the JBoss details that are required for the installation:
Property
Description
Default value
Server instance 1 value
JBoss Installation Directory
The location where JBoss is installed.
Do not include the
bin
 directory.
-
Configuration Name
Use the default configuration name. The Hub Server is deployed to the specified configuration.
standalone
standalone
Remote Port
The JBoss remote port.
In a clustered environment, you identify multiple ports.
The JBoss remote port can conflict with the default database server port. If ports conflict, change one of the ports to resolve the conflict. For more information about changing ports, see the JBoss documentation.
4447
Management Port
JBoss HTTP management port. The HTTPS management port is not supported.
If port offset is configured for the application server, add the offset value to the default value. For example, if the port offset is 100, the management port value is 10090, which is (9990 + 100).
9990
In a clustered environment, add details for the other JBoss instances to the following table:
Property
Server instance 2 value
Server instance 3 value
Server instance 4 value
JBoss Installation Directory
Configuration Name
Remote Port
Management Native Port

Database: IBM Db2

Use the following table to collect the IBM Db2 details that are required for the installation:
Property
Description
Default value
Installation value
JDBC Driver Directory
Db2 directory that contains the following JDBC JAR files:
  • db2jcc.jar
  • db2jcc_license_cu.jar
-
Server
Host name or IP address of the machine hosting IBM Db2 that contains the Master Database.
localhost
Port
Port number that you want the Hub Server to use to communicate with IBM Db2.
50000
Database Name
Name of the database that you created for Multidomain MDM.
-
MDM Master Database Name
Name of the MDM Master Database. You create the MDM Master Database during the Hub Store installation by running the
sip_ant create_system
 script.
cmx_system
MDM Master Database User Name
Name of the IBM Db2 user that was used to import metadata into the MDM Master Database.
cmx_system
MDM Master Database Password
Password of the IBM Db2 user.
-

Security - Optional

You can choose to configure the hash algorithm, the certificate provider, or both.
Hash Key and Hash Algorithm
To configure a hash algorithm, you must implement the Java abstract class
com.siperian.sam.security.hashing.algorithms.HashAlgorithm
 in the
siperian-server-hash.jar
 file. The JAR file is located in the following directory:
<MDM installation directory>/hub/server/lib/hashing
Use the following table to collect the hash algorithm details that were used in the Java abstract class implementation in the
siperian-server-hash.jar
 file:
Property
Description
Default value
Installation value
Hash Key
Optional. A sequence of up to 32 hexadecimal characters with no delimiters. The key size can be up to 128 bits. Store the key securely.
If your custom hash key is exposed or lost, you must reset all user passwords.
-
Hash Algorithm
List of configured algorithms. To configure a custom algorithm, select
Other
.
SHA-3
Name
Name of the custom hash algorithm.
-
Implementation File
Location of the custom hash algorithm archive.
The compressed file must contain all the necessary JAR files and supporting files.
-
Canonical Class Name
Canonical class name for the hash algorithm implementation.
For example: $HASHING_CLASS_NAME$
-
Certificate Provider
To implement a custom certificate provider, you must implement the
PKIUtil.java
 interface in the
siperian-server-pkiutil.jar
 file. The JAR file is located in the following directory:
<MDM installation directory>/hub/server/lib/pkiutils
Use the following table to collect the details of the custom certificate provider that were used in the Java abstract class implementation in the
siperian-server-pkiutil.jar
 file:
Property
Description
Default value
Installation value
Certificate Provider
By default, MDM authenticates trusted applications. To configure a custom provider, select
Other
.
Default
Implementation File
Name of the custom certificate provider.
-
Class Name
Class name for the certificate provider implementation.
-

Hub Console

The Hub Console requires the server details to connect to the Hub Server machine.
Use the following table to collect the server details that the Hub Console requires:
Property
Description
Default value
Installation value
Publicly Accessible Host Name
IP address or publicly accessible host name (FQDN) of the server to which the application server binds.
-
HTTP Port
HTTP port of the server that the Hub Console must use.
-

Informatica ActiveVOS - Optional

For more information about
Informatica ActiveVOS
, ActiveVOS Central, or ActiveVOS Server, see the
Informatica ActiveVOS
 documentation.
Use the following table to collect the details that are required for ActiveVOS installation:
Property
Description
Default value
Installation value
ActiveVOS Server Installation Directory
An empty directory where you want to install the ActiveVOS server.
<
MDM Hub installation directory
>/avos/server
Server
Host name or IP address of the machine hosting IBM Db2 that contains the ActiveVOS database.
localhost
Port
Port number that you want the Hub Server to use to communicate with IBM Db2.
50000
Database Name
Name of the database that you created for ActiveVOS.
-
ActiveVOS Schema
Name of the ActiveVOS schema. You create the ActiveVOS schema when you perform the pre-installation task by running the
sip_ant create_bpm
 script.
avos
ActiveVOS Schema User Name
Name of the IBM Db2 user that was used to create the ActiveVOS schema.
avos
ActiveVOS Schema Password
Password of the IBM Db2 user.
-
Web Services URL
Host and port where the ActiveVOS Server runs. You choose to use either the http or https protocol.
The Hub Server uses the same URL that ActiveVOS Central (also called Process Central) uses to call the ActiveVOS Server. The URL is called the Process Central AeTaskService URL in the
Informatica ActiveVOS
 documentation and has the following format: http://[hostname.domainname]:[port]/active-bpel/services/AeB4PTaskClient-taskOperations.
http://localhost:8080
ActiveVOS Server Installer File
The
Multidomain MDM
 distribution package contains the installer for the ActiveVOS Server.
ActiveVOS_Server_ <operating system>_<version>
Process Console User Name
An authorized user for the ActiveVOS Process Console.
-
Process Console Password
Password for the ActiveVOS Process Console user.
-

Product Usage Toolkit

The product usage toolkit sends information about your MDM environment to Informatica. The information is used by Informatica Global Customer Support to help troubleshoot and provide recommendations for your environment. If you do not want the toolkit to send any information to Informatica, you can disable the toolkit after you install MDM.
Use the following table to collect the details that are required for installing the product usage toolkit:
Property
Description
Default value
Installation value
Industry
Type of industry that best matches your organization's business.
-
Environment
Type of environment that you are installing in.
If you install from the command line, enter one of the following numbers:
  • 1. Production environment
  • 2. Test or QA environment
  • 3. Development environment
-
Does your network have a proxy server?
If yes, provide details about the proxy server.
No
Host
Name or IP address of the proxy server.
-
Port
Port number used by the proxy server.
-
Domain Name
If your proxy server is part of a domain, the name of the domain.
-
User Name
If you use a secure proxy server, the name of a user that can access MDM.
-
Password
Password of the user.
-
0 COMMENTS
We’d like to hear from you!