Installation Guide for Microsoft SQL Server with Red Hat JBoss

10.5

Back Next

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: Microsoft SQL Server

Use the following table to collect the Microsoft SQL Server details that are required for the installation:

Property	Description	Default value
Server	Host name or IP address of the machine hosting Microsoft SQL Server that contains the MDM Master Database.	localhost
Port	TCP Port number for the Hub Server to use to communicate with Microsoft SQL Server.	1433
Database Name	Name of the database that you want to use for MDM Master Database. You can define your own database name.	cmx_system
User Name	Name of a Microsoft SQL Server user that has access to the MDM Master Database.	-
Password	Password of the Microsoft SQL Server 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
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
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
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 Microsoft SQL Server that contains the ActiveVOS database.	localhost
Port	TCP Port number for the Hub Server to use to communicate with Microsoft SQL Server.	1433
Database Name	Name of the database that you want to use for ActiveVOS. You can define your own database name.	avos
User Name	Name of a Microsoft SQL Server user that has access to the ActiveVOS database.	-
Password	Password of the Microsoft SQL Server 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
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.	-

Rename Saved Search

Table of Contents

Installation Guide for Microsoft SQL Server with Red Hat JBoss

Installation Guide for Microsoft SQL Server with Red Hat JBoss

Collect the Installation Values

Collect the Installation Values

Application Server: Red Hat JBoss

Database: Microsoft SQL Server

Security - Optional

Hub Console

Informatica ActiveVOS - Optional

Product Usage Toolkit