Installation Guide for Oracle Database with WebLogic

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: Oracle WebLogic Server

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

Property	Description	Default value
WebLogic Server Domain Installation Directory	The location of the WebLogic Server domain directory.	-
Host	Host name or IP address of the machine on which WebLogic Server is installed. Do not use localhost.	localhost
Listen Port	Port number on which WebLogic Server listens.	7001
Server Name	Name of a server in the WebLogic domain on which you want to deploy the Hub Server.	-
User Name	Name of a WebLogic Server user that has administrative privileges.	weblogic
Password	Password of the WebLogic Server administrative user.	-

In a clustered environment, add details for the other WebLogic instances to the following table:

Property	Server instance 2 value	Server instance 3 value	Server instance 4 value
WebLogic Server Domain Installation Directory
Host
Listen Port
Server Name
User Name
Password

Database: Oracle Database

Use the following table to collect the Oracle Database details that are required for the installation:

Property	Description	Default value
Server	Host name of the server where Oracle Database resides.	localhost
Port	TCP port number of the Oracle listener that runs on the Oracle Database server. The Hub Server uses this port to communicate with Oracle Database.	1521
Connection Type	Type of connection that you defined when you set up Oracle Database.	Service
Service Name	Name of the Oracle Service that you defined.	orcl
Oracle SID	Name of the Oracle System ID that you defined in the tnsnames.ora file. The TNS names must be the same for both the Hub Server and MDM Process Server machines.	orcl
Master Database Schema Name	Name of the schema for the MDM Master Database.	cmx_system
Master Database Schema Password	Password for the MDM Master Database 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
Connection Type	Type of connection that you defined when you set up Oracle Database.	Service Name
Service Name	Name of the Oracle Service that you defined.	orcl
Oracle SID	Name of the Oracle System ID that you defined in the tnsnames.ora file.	orcl
Server	Host name or IP address of the machine hosting the Oracle Database that contains the ActiveVOS schema.	localhost
Port	TCP port number of the Oracle listener that runs on the server. The Hub Server uses this port to communicate with the Oracle Database server.	1521
ActiveVOS Schema Name	Name of the ActiveVOS schema user.	avos
ActiveVOS Schema Password	Password for the ActiveVOS schema 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:7001
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 Oracle Database with WebLogic

Installation Guide for Oracle Database with WebLogic

Collect the Installation Values

Collect the Installation Values

Application Server: Oracle WebLogic Server

Database: Oracle Database

Security - Optional

Hub Console

Informatica ActiveVOS - Optional

Product Usage Toolkit