Table of Contents

Search

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

Installation Guide for Oracle Database with Red Hat JBoss

Installation Guide for Oracle Database with Red Hat JBoss

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 Process 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

Informatica Address Verification

Informatica Address Verification was previously called AddressDoctor.
If you plan to install
Informatica Address Verification
, record the following properties:
Property
Description
Default values
Server instance 1 value
Configuration File
The location of the
Informatica Address Verification
configuration file
SetConfig.xml
. You use the file for general configurations, such as reference address database, unlock code for Informatica Address Verification, and memory settings.
If you already installed
Address Verification
, use the location of your configuration file. Otherwise, use the default file location
<MDM Hub installation directory>\hub\cleanse\resources\AddressDoctor\5\SetConfig.xml
Parameters File
The location of the
Informatica Address Verification
parameters file
Parameters.xml
. You use the file to configure how Informatica Address Verification interprets, processes, and formats the addresses.
If you already installed
Address Verification
, use the location of your parameters file. Otherwise, use the default file location
<MDM Hub installation directory>\hub\cleanse\resources\AddressDoctor\5\Parameters.xml
Correction Type
The type of address processing that you want to perform.
Use one of the following correction types:
  • PARAMETERS_DEFAULT. Default correction type. Indicates the use of the correction type defined in the
    Parameters.xml
    file.
  • PARSE_ONLY. Parses and assigns address elements to the appropriate fields.
  • CORRECT_ONLY. Validates addresses against the postal data and corrects the addresses.
  • CERTIFY_ONLY. Verifies addresses in accordance with the postal certifications to meet country-specific postal authority requirements.
  • CORRECT_THEN_CERTIFY. Validates addresses against the postal data and corrects the addresses. Then verifies addresses in accordance with postal certifications to meet country-specific postal authority requirements.
  • TRY_CERTIFY_THEN_CORRECT. Verifies addresses in accordance with postal certifications to meet country-specific postal authority requirements. If the address verifications fail, the process validates the addresses against the postal data and corrects the addresses.
PARAMETERS_DEFAULT

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!