You are on page 1of 50

LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

LUF-MDM-002 Informatica MDM


Hub Installation and Configuration
Guide

Page 1 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

Table of Contents
1. Introduction .................................................................................................................................... 4
1.1. Document Introduction ........................................................................................................... 4
1.2. Approval Status ........................................................................................................................ 4
1.3. Change Log ............................................................................................................................... 4
1 Notations and Fonts used in this Document........................................................................................ 5
2 Pre-requisites ....................................................................................................................................... 6
3 Required Files ....................................................................................................................................... 7
4 Installation Variables............................................................................................................................ 8
5 Installation Folders............................................................................................................................... 9
6 Installation Checklist .......................................................................................................................... 10
6.1 Checklist of required installation tasks ....................................................................................... 10
7 Prepare Install Software..................................................................................................................... 12
7.1 Copy and move the install files into the correct folders ............................................................. 12
8 Configure JBoss Users ........................................................................................................................ 14
8.1 Configure JBoss Management and ActiveVOS Users .................................................................. 14
9 Installation Instructions ..................................................................................................................... 17
9.1 Configure JBoss Start-Up Options ............................................................................................... 17
9.2 Configure JBoss Default Parameters ........................................................................................... 19
9.3 Configure and Run the Silent install file for the Hub Server ....................................................... 24
9.4 Configure the Hub Server properties file .................................................................................... 40
9.5 Configure and Run the Silent install file for the Process Server ................................................. 26
10 Post Installation Setup ..................................................................................................................... 28
10.1 Register the MDM ORS database.............................................................................................. 28
10.2 Register the Process server in the ORS database ..................................................................... 33
10.3 Configure ActiveVOS ................................................................................................................. 36
11 Appendix .......................................................................................................................................... 41
11.1 Appendix A Starting and Stopping JBoss................................................................................ 41
11.2 Appendix B Configure and Check the Environmental variables............................................. 42
11.3 Appendix C Configure SSL ...................................................................................................... 43
11.4 Appendix D JBoss Modules .................................................................................................... 44
11.5 Appendix E Manually Running the Post Installation Step ...................................................... 45
11.6 Appendix F Restarting a failed installation from the beginning ............................................ 46

Page 2 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

11.7 Appendix G Installation Issues ............................................................................................... 47

Page 3 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

1. Introduction

1.1. Document Introduction

This document is the Lufthansa specific installation and configuration guide that will be used going
forward when provisioning new environments for the Smile project. Please note that this is a generic
guide for the cluster installation of the Informatica MDM Hub, Process servers and ActiveVOS. This
guide assumes that the database installation tasks detailed in LUF-MDM-001 Informatica MDM
Database Installation and Configuration Guide have already been completed.

The intended audience for this guide is the operations team who will be responsible for running the
instructions detailed in this document.

This document should be updated as the installation process is updated and refined over time.

1.2. Approval Status

Name Role Signature


Jonathan Hudson Informatica Advisor
Axel Viel Operations Manager
Rene Fink Operations Advisor
Sebastian Boing Project Manager
Christian Engel Architect
Michael Massoth Program Lead

1.3. Change Log

Version Number Change Description Author


v01 Initial Version Jonathan Hudson

Page 4 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

1 Notations and Fonts used in this Document


Screenshots in this document are followed by instructions for the user to follow.

Any code snippets or directives (e.g. Windows commands) for the user to follow will be
displayed in Courier New

Text inside < > indicate that the text refers to an entry in the Build Variables section of this
document.

Italicised text should be used to indicate a potential action or outcome, or as a note for the reader.

Page 5 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

2 Pre-requisites
Before you begin, make sure that the following prerequisites are in place.

No. Prerequisites for Installation Check

1. The Informatica MDM Hub Store has been installed and configured.(DB guide)

2. The Hosts file has been set up so the Application Server has access to the
Database server via the FQDN.

3. The Oracle client has been installed and configured with access to the MDM
database. Execute the command below to ensure database connectivity

sqlplus <username>/<password>@<TNS Name>

4. The Informatica MDM Multidomain Edition 10 hub software is available.

5. The Informatica ActiveVOS server installation software is available.

6. An X-Windows environment can be configured (optional)

7. The Application Server must have X11 forwarding enabled to allow the X-
Windows environment to be utilised if configured.

8. Java JDK 1.7.0_45 or later is installed and configured correctly on both the
Application Server and Database Server. The JAVA_HOME environment variable
must be set, and the %JAVA_HOME%\bin directory must be included in the
system path.

9. Install the Application Server in the same time zone as the database server

10. Check the linux ulimits for the cup user to ensure sufficient file handles which
should be set to at least 20k. You may need to ask an administrator to up the limit
if it is not already set high enough.

vi /etc/security/limits.conf

cup hard nofile 65536
11. Check the locale is set to locale

en_US

Page 6 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

3 Required Files

File Details Check

Informatica_MDM_10.1GA_FOR_LINUX.zip The Informatica MDM software

siperian.license The Informatica MDM License file

ActiveVOSUnix9241.zip The ActiveVOS installation software

activevos.lic The ActiveVOS license file

All the above files are located on the install folder.

Page 7 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

4 Installation Variables

The following variables are referenced in the document:

Variable name Variable value Check

JBOSS_HOME The location where JBoss has been installed

JBOSS_CONSOLE_USER The JBoss Admin Console Username

JBOSS_CONSOLE_PW The JBoss Admin Console password

MDM_CONSOLE_USER The MDM Admin Console Username

MDM_CONSOLE_PW The MDM Admin Console password

APP_SERVER The application server where the MDM software



is being installed.

APP_HTTP_PORT The application server http port number

DB_SERVER The server name where the Oracle is located.

DB_PORT The port that the Oracle instance listens on.

DB_SID The Oracle database service identifier.

CMX_MASTER_PW The password for the CMX_SYSTEM user.

CMX_ORS_USER The ORS Username

CMX_ORS_PW The ORS Password

AVOS_DB_USER The ActiveVOS Schema user

AVOS_DB_PW The ActiveVOS Schema password

AVOS_CONSOLE_USER The ActiveVOS Console Username

AVOS_CONSOLE_PW The ActiveVOS Console password

BIND_ADDR This is the local network interface

Page 8 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

5 Installation Folders

The following locations will be used and referenced during the installation:

Variable name Variable value Check

JBoss Home /home/cup/jboss-eap-6.4

Informatica Home (create manually) /home/cup/infa

MDM Installation /home/cup/infa/mdm

ActiveVos Installation /home/cup/infa/avos

License File Location (create manually) /home/cup/license

SSL Certificate Location /home/cup/ssl-certs

Software Location (create manually place /home/cup/install


all s/w in this folder)

Hub Server Location /home/cup/infa/mdm/hub

Process Server Location /home/cup/infa/mdm/cleanse

Solr Data Location /home/cup/infa/mdm/cleanse/solr

Page 9 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

6 Installation Checklist

6.1 Checklist of required installation tasks

To make it easier to follow the installation process please follow the installation checklist below

No. Installation Checklist Step Check

1. Confirm all the installation pre-requisites are satisfied

2. Configure the cup user environment variables (refer apendixB)

3. Create the required directory structure in the cup home

4. Copy the required software files to the /home/cup/install folder

5. Copy the required license files to the /home/cup/license folder

6. Unzip the install files into the various locations (refer section 7.1)

7. Edit the JBoss configuration standalone.conf file (refer section 9.1)

8. Edit the JBoss standalone-full-ha.xml file (refer section 9.2)

9. Add the JBoss console admin user, MDM admin and ActiveVOS admin users
(refer to section 8.1)

10. Create the silent install files for the hub and process server installations

11. Run the silent install installation for both the hub and process servers

12. Check the standalone-full-ha.xml to ensure all settings are correct

13. Update max-pool-size for new datasources in standalone-full-ha.xml

14. Register the ORS database using the MDM console

15. Configure the Process server in the ORS using the MDM console

16. Start and Stop JBoss and check for any errors in the log files

Page 10 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

Page 11 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

7 Prepare Install Software

7.1 Copy and move the install files into the correct folders

Unzip and copy the install files as described below

No. Installation Checklist Step Check

1. Log into the cup user

2. Switch to the install folder

cd /home/cup/install

Now unzip the Informatica_MDM_10.1GA_FOR_LINUX.zip file and


ActiveVOSUnix9241.zip into a location where they can be executed and
change permissions to enable execute access

unzip Informatica_MDM_10.1GA_FOR_LINUX.zip

mv linux Informatica_Installation_Files

cd /home/cup/install/Informatica_Installation_Files
/mrmserver

chmod +x hub_install.bin

cd /home/cup/install/Informatica_Installation_Files
/mrmcleanse

chmod +x hub_cleanse_install.bin

cd /home/cup/install

unzip ActiveVOSUnix9241.zip

gunzip ActiveVOS_Server_unix_9.2.4.1.tar.gz

tar xvf ActiveVOS_Server_unix_9.2.4.1.tar


chmod +x ActiveVOS_Server_unix_9.2.4.1.sh

3. Unzip the JBoss software into the JBoss home folder

cd /home/cup/install

unzip jboss-eap-6.4.0.zip d /home/cup

Ensure that the JBoss folder name is

/home/cup/jboss-eap-6.4

Page 12 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

No. Installation Checklist Step Check

4. Remove the original compressed installation files to save space

rm Informatica_MDM_10.1GA_FOR_LINUX.zip

rm ActiveVOSUnix9241.zip

rm ActiveVOS_Server_unix_9.2.4.1.tar

rm jboss-eap-6.4.0.zip

Page 13 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

8 Configure JBoss Users

8.1 Configure JBoss Management and ActiveVOS Users

The following tasks are required to configure the JBoss users for the admin console and for
ActiveVOS.

No. Installation Instruction Step Check

1. Login to the application server using the cup user.

If you have problems setting passwords you may need to change the rules
defined in the file add-users.properties

It is important that the passwords chosen here also conform to the MDM
password policy which is defined using the MDM admin console.

2. Switch to the /home/cup/jboss-eap-6.4/bin folder

$ ./add-user.sh

What type of user do you wish to add?


a) Management User (mgmt-users.properties)
b) Application User (application-users.properties)
(a): a

Enter the details of the new user to add.

Using realm 'ManagementRealm' as discovered from the


existing property files.

Username : <JBOSS_CONSOLE_USER>
Password : <JBOSS_CONSOLE_PW>
Re-enter Password : <JBOSS_CONSOLE_PW>

What groups do you want this user to belong to? (Please


enter a comma separated list, or leave blank for none)[ ]:

Is this new user going to be used for one AS process to


connect to another AS process?
e.g. for a slave host controller connecting to the master
or for a Remoting connection for server to server EJB
calls.
yes/no? no

Page 14 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

No. Installation Instruction Step Check

3. Now we need to add the MDM console admin user

$ ./add-user.sh

What type of user do you wish to add?


a) Management User (mgmt-users.properties)
b) Application User (application-users.properties)
(a): b

Enter the details of the new user to add.

Using realm 'ApplicationRealm' as discovered from the


existing property files.

Username : <MDM_CONSOLE_USER>
Password : <MDM_CONSOLE_PW>
Re-enter Password : <MDM_CONSOLE_PW>

What groups do you want this user to belong to? (Please


enter a comma separated list, or leave blank for none)[ ]:

Is this new user going to be used for one AS process to


connect to another AS process?
e.g. for a slave host controller connecting to the master
or for a Remoting connection for server to server EJB
calls.
yes/no? no

Page 15 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

No. Installation Instruction Step Check

4. Run the command again to add the ActiveVOS admin user and role

Ensure that the password that you choose is also a valid MDM console
password.

$ ./add-user.sh

What type of user do you wish to add?


a) Management User (mgmt-users.properties)
b) Application User (application-users.properties)
(a): b

Enter the details of the new user to add.


Using realm 'ApplicationRealm' as discovered from the
existing property files.
Username : <AVOS_CONSOLE_USER>
Password : <AVOS_CONSOLE_PW>
Re-enter Password : <AVOS_CONSOLE_PW>

What groups do you want this user to belong to? (Please


enter a comma separated list, or leave blank for none)[ ]:
abAdmin

About to add user <AVOS_CONSOLE_USER> for realm


'ApplicationRealm'
Is this correct yes/no? yes

Added user <AVOS_CONSOLE_USER> to file '/.../jboss-eap-


6.4/standalone/configuration/application-users.properties'
Added user <AVOS_CONSOLE_USER> with groups abAdmin to file
'/.../jboss-eap-6.4/standalone/configuration/application-
roles.properties'

Is this new user going to be used for one AS process to


connect to another AS process?
e.g. for a slave host controller connecting to the master
or for a Remoting connection for server to server EJB
calls.
yes/no? no

5. You can check the users and roles have been added correctly by examining the
following files in the /home/cup/jboss-eap-6.4/standard/
configuration folder

application-roles.properties

application-users.properties

mgmt-groups.properties

mgmt-users.properties

Page 16 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

9 Installation Instructions

9.1 Configure JBoss Start-Up Options

The following tasks are required to configure the JBoss Start-Up options.

No. Installation Instruction Step Check

1. Log into the application server as the cup user.

Edit the standalone.conf file in the bin and add the start-up options as
2.
illustrated below

-Xms4096m -Xmx8192m
-XX:PermSize=512m -XX:MaxPermSize=2048m
-Xss2000k
-XX:ReservedCodeCacheSize=256m
-Dsolr.autoSoftCommit.maxTime=5000
-Djava.net.preferIPv4Stack=true
-Dprogram.name=$PROGNAME
-Dfile.encoding=UTF-8
-Djboss.as.management.blocking.timeout=5000
-Duser.timezone=UTC
-Dorg.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE=16384
-Djgroups.bind_addr=<BIND_ADDR>

Add the options to the file using the following format

JAVA_OPTS="-Dprogram.name=$PROGNAME -Djava.net.preferIPv4Stack=true
$JAVA_OPTS"

The edited segment of the file should look something like the illustration below
#
# Specify options to pass to the Java VM.
#
if [ "x$JAVA_OPTS" = "x" ]; then
JAVA_OPTS="-Xms4096m -Xmx8192m -XX:PermSize=512m -XX:MaxPermSize=2048m -Xss2000k"
JAVA_OPTS="$JAVA_OPTS -Dsolr.autoSoftCommit.maxTime=5000 -Djava.net.preferIPv4Stack=true"
JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -
Djava.awt.headless=true"
JAVA_OPTS="$JAVA_OPTS -Djboss.modules.policy-permissions=true"
JAVA_OPTS="$JAVA_OPTS -Dprogram.name=$PROGNAME -Dfile.encoding=UTF-8 -
Djboss.as.management.blocking.timeout=5000"
JAVA_OPTS="-XX:ReservedCodeCacheSize=256m -
Dorg.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE=16384
-Djgroups.bind_addr=10.56.34.23 <binding addr is ip address where JBOSS installed> -
Duser.timezone=UTC $JAVA_OPTS"
else
echo "JAVA_OPTS already set in environment; overriding default settings with values: $JAVA_OPTS"
fi

Please start and stop JBoss to ensure that the file has been edited correctly and
3.
that the server starts OK.

Page 17 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

Page 18 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

9.2 Configure JBoss Default Parameters

The following default parameters should be updated.

No. Installation Instruction Step Check

1. Log into the application server as the cup user.

2. Edit the standalone-full-ha.xml file in the


<JBOSS_HOME>/standalone/configuration folder.

The standalone-full-ha.xml file for clustered environments

The standalone-full.xml file for non-clustered environments

3. Edit the transactions subsystem and update the default-timeout value


from 300 to 3600 as shown below

<server xmlns="urn:jboss:domain:1.7">
...
<profile>
...
<subsystem xmlns="urn:jboss:domain:transactions:1.5">
<core-environment>
<process-id>
<uuid/>
</process-id>
</core-environment>
<recovery-environment socket-binding="txn-recovery-
environment" status-socket-binding="txn-status-manager"/>
<coordinator-environment default-timeout="3600"/>
</subsystem>
....
</profile>
...
</server>

Page 19 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

No. Installation Instruction Step Check

4.
Edit the logging subsystem and add an async-handler then update the
root-logger to use the ASYNC handler as shown below.

<server xmlns="urn:jboss:domain:1.7">
...
<profile>
...
<subsystem xmlns="urn:jboss:domain:logging:1.5">
...
<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>
...
<root-logger>
<level name="INFO"/>
<handlers>
<handler name="ASYNC"/>
</handlers>
</root-logger>
...
</subsystem>
...
</profile>
...
</server>

If you add the CONSOLE appender as shown above in BOLD you may also need
to add the following under the subsystem alongside the async-handler

<console-handler name="CONSOLE">
<level name="INFO"/>
<formatter>
<named-formatter name="COLOR-PATTERN"/>
</formatter>
</console-handler>

<formatter name="COLOR-PATTERN">
<pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t)
%s%E%n"/>
</formatter>

Ensure that the deployment scanner is setup to scan after startup otherwise
5.
the silent install will fail to deploy artifacts. Change then scan interval to 5000
<server xmlns="urn:jboss:domain:1.7">
...
<profile>
...
<subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">
<deployment-scanner path="deployments" relative-
to="jboss.server.base.dir" scan-interval="5000"/>
</subsystem>
...
</profile>
...
</server>

Page 20 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

No. Installation Instruction Step Check

6.
Edit the web subsystem and add a max-connections attribute with a
value of 300 as shown below
<server xmlns="urn:jboss:domain:1.7">
...
<profile>
...
<subsystem xmlns="urn:jboss:domain:web:2.2" default-virtual-
server="default-host" native="false">
<connector name="http" protocol="HTTP/1.1" scheme="http"
socket-binding="http" max-connections="300"/>
...
</subsystem>
...
</profile>
...
</server>

7.
Edit the ejb subsystem and edit the max-threads setting the count
attribute with a value of 300 as shown below
<server xmlns="urn:jboss:domain:1.7">
...
<profile>
...
<subsystem xmlns="urn:jboss:domain:ejb3:1.5">
...
<thread-pools>
<thread-pool name="default">
<max-threads count="300"/>
<keepalive-time time="100" unit="milliseconds"/>
</thread-pool>
</thread-pools>
...
</subsystem>
...
</profile>
...
</server>

Page 21 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

No. Installation Instruction Step Check

8.
Edit the datasources subsystem, find the xa-pool element and edit the
max-pool-size setting with a value to 300 as shown below
<server xmlns="urn:jboss:domain:1.7">
...
<profile>
...
<subsystem xmlns="urn:jboss:domain:datasources:1.2">
<datasources>
...
<xa-datasource jndi-name="...">
...
<xa-pool>
<min-pool-size>5</min-pool-size>
<max-pool-size>300</max-pool-size>
...
</xa-pool>
...
</xa-datasource>
...
</datasources>
...
</subsystem>
...
</profile>
...
</server>

Important - The datasources will only be added after the installation is


complete. You will need to edit this setting after the installation is complete
and for each new datasource that has been added.

Page 22 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

No. Installation Instruction Step Check

9. Edit the socket-binding-group section, amend the port numbers to


the values highlighted in bold below or select appropriate port numbers
depending on how the firewall has been configured.
<server xmlns="urn:jboss:domain:1.7">
...
<socket-binding-group name="standard-sockets" default-
interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
<socket-binding name="management-native" interface="management"
port="${jboss.management.native.port:8016}"/>
<socket-binding name="management-http" interface="management"
port="${jboss.management.http.port:8009}"/>
<socket-binding name="management-https" interface="management"
port="${jboss.management.https.port:8015}"/>
<socket-binding name="ajp" port="8010"/>
<socket-binding name="http" port="8011"/>
<socket-binding name="https" port="8443"/>
<socket-binding name="jacorb" interface="unsecure" port="3528"/>
<socket-binding name="jacorb-ssl" interface="unsecure"
port="3529"/>
<socket-binding name="jgroups-mping" port="0" multicast-
address="${jboss.default.multicast.address:230.0.0.4}" multicast-
port="45700"/>
<socket-binding name="jgroups-tcp" port="7600"/>
<socket-binding name="jgroups-tcp-fd" port="57600"/>
<socket-binding name="jgroups-udp" port="55200" multicast-
address="${jboss.default.multicast.address:230.0.0.4}" multicast-
port="45688"/>
<socket-binding name="jgroups-udp-fd" port="54200"/>
<socket-binding name="messaging" port="5445"/>
<socket-binding name="messaging-group" port="0" multicast-
address="${jboss.messaging.group.address:231.7.7.7}" multicast-
port="${jboss.messaging.group.port:9876}"/>
<socket-binding name="messaging-throughput" port="5455"/>
<socket-binding name="modcluster" port="0" multicast-
address="224.0.1.105" multicast-port="23364"/>
<socket-binding name="remoting" port="8018"/>
<socket-binding name="txn-recovery-environment" port="8019"/>
<socket-binding name="txn-status-manager" port="8020"/>
<outbound-socket-binding name="mail-smtp">
<remote-destination host="localhost" port="25"/>
</outbound-socket-binding>
</socket-binding-group>
...
</server>

It is important the various ports highlighted above are opened in the firewall
as needed. It is assumed here that there are no firewalls restricting access to
the systems that form the application server cluster.

Also note that the various http ports are using the management interface
which by default is restricted to the localhost ip address only. To access the
JBoss console you will need to modify the interface to provide unrestricted
access. (what modifications ? figure out)

Page 23 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

9.3 Configure and Run the Silent install file for the Hub Server

The following tasks are required to configure the silent install file for the hub server installation.

No. Installation Instruction Step Check

1. Log into the application server as the cup user.

2. Now create the parameter file for the hub server silent install called
silentInstallHubServer.properties and add the following entries
below ensuring that you replace the variable placeholders with the correct
values.

INSTALLER_UI=silent

USER_INSTALL_DIR=/home/cup/infa/mdm/hub/server

SIP.LICENSE.PATH=/home/cup/license
SIP.LICENSE.FILENAME=siperian.license
SIP.AS.CHOICE="JBoss"
SIP.AS.HOME=/home/cup/jboss-eap-6.4
JBOSS.AS.PORT_1=8018
JBOSS.AS.PORT_2=8016
SIP.JBOSS.CONFIGURATION_NAME=standalone

SIP.DB.CHOICE="Oracle"
SERVICE_NAME_SELECTED_RESULT=0
SIP.DB.SERVER=<DB_SERVER>
SIP.DB.PORT=<DB_PORT>
SIP.DB.SID=<DB_SID>
SIP.DB.SCHEMA_NAME=cmx_system
SIP.DB.PASSWORD=<CMX_MASTER_PW>

AVOS.INSTALL=Yes
AVOS_INSTALLER_PATH=/home/cup/install/ActiveVOS_Server_unix_9.2.
4.1.sh
AVOS_INSTALL_DIR=/home/cup/infa/avos/server
AVOS.ORACLE.CONNECTION.TYPE="SID"
AVOS.DB.SERVER=<DB_SERVER>
AVOS.DB.PORT=<DB_PORT>
AVOS.DB.SID=<DB_SID>
AVOS.DB.SCHEMA_NAME=<AVOS_DB_USER>
AVOS.DB.PASSWORD=<AVOS_DB_PW>

SIP.APPSERVER.WEB.URL=http://<APP_SERVER>:<APP_HTTP_PORT>
AVOS.CONSOLE.USER=<AVOS_CONSOLE_USER>
AVOS.CONSOLE.PASSWORD=<AVOS_CONSOLE_PW>

INSTALL.PLATFORM.YES=0
RUN_DEPLOYMENT_FLAG=1 (its set 1 to run the postinstallscript
automatically)
CSM_TYPE=Production
CSM_HOST=
CSM_PORT=
CSM_DOMAIN=
CSM_PROXY_USER_NAME=
CSM_PROXY_PASSWORD=

Page 24 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

No. Installation Instruction Step Check

3. Now we need to copy the silent install file


silentInstallHubServer.properties created earlier into the same
location as the installation file
cd /home/cup/install/Informatica_Installation_Files/mrmserver

./hub_install_bin -f ~/install/silentInstallHubServer.properties

4. Now check the installation check log file to ensure that all was installed ok

cd /home/cup/infa/mdm/hub/servers/logs

more installPrereq.log

5. Now check the post installation log file to ensure that all was installed ok

cd /home/cup/infa/mdm/hub/server/logs

more postInstallSetup.log

The log file may report that the build failed. This can come from an ActiveVOS
warning. As long as the installation looks ok and there are no errors or failures
and the log shows clearly Build Successful earlier then this message can be
ignored.

Buildfile: /home/cup/infa/mdm/hub/server/bin/build.xml
*** DEPLOYMENT SUCCESSFUL ***

*** View execution results in log file : ./logs/postInstallSetup.log ***

6. Stop and Start the JBoss server and check the log files for any start-up errors

Any exceptions logged as INFO can be safely ignored

Page 25 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

9.4 Configure and Run the Silent install file for the Process Server

The following tasks are required to configure the silent install file for the process server installation.

No. Installation Instruction Step Check

1. Log into the application server as the cup user.

2. Now create the parameter file for the hub server silent install called
silentInstallProcessServer.properties and add the following
entries below ensuring that you replace the variable placeholders with the
correct values.

INSTALLER_UI=silent

USER_INSTALL_DIR=/home/cup/infa/mdm/hub/cleanse

SIP.LICENSE.PATH=/home/cup/license
SIP.LICENSE.FILENAME=siperian.license
SIP.AS.CHOICE="JBoss"
SIP.AS.HOME=/home/cup/jboss-eap-6.4

JBOSS.AS.PORT_1=8018
JBOSS.AS.PORT_2=8016

SIP.JBOSS.CONFIGURATION_NAME=standalone
SIP.OS.CHOICE=Red Hat Linux

RUN_DEPLOYMENT_FLAG=1
RESTART_NEEDED=NO
USER_REQUESTED_RESTART=NO

CSM_TYPE=Production
CSM_HOST=
CSM_PORT=
CSM_DOMAIN=
CSM_PROXY_USER_NAME=
CSM_PROXY_PASSWORD=

3. Now we need to copy the silent install file


silentInstallProcessServer.properties created earlier into the
same location as the installation file
cd /home/cup/install/Informatica_Installation_Files/mrmcleanse

./hub_install_bin -f ~/install/silentInstallProcessServer.properties

4. Now check the installation check log file to ensure that all was installed ok

cd /home/cup/infa/mdm/hub/cleanse/logs

more installPrereq.log

Page 26 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

No. Installation Instruction Step Check

5. Now check the post installation log file to ensure that all was installed ok

cd /home/cup/infa/mdm/hub/cleanse/logs

more postInstallSetup.log

6. Stop and Start the JBoss server and check the log files for any start-up errors

Any exceptions logged as INFO can be safely ignored

Page 27 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

10 Post Installation Setup

10.1 Register the MDM ORS database

The following tasks are required to register the MDM ORS database using the MDM console

Note: This action should only be carried out on the first node in the cluster as the ORS can only be
registered once in the master database. You will need to add the data source manually on all JBoss
instances in the cluster. Once the data source has been added to the first node in the cluster you can
copy the data source from the standalone-full-ha.xml to all other nodes in the cluster.

No. Post Installation Setup Check

1. Log into the application server as the cup user.

2. Start the MDM admin console and login as admin

3.

Login to the admin user

Page 28 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

No. Post Installation Setup Check

4.

Then select the Master MDM database and select connect

5.

Then select Write Lock from the menu to enable you to change the ORS

Page 29 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

No. Post Installation Setup Check

6.

Then select databases from the Configuration menu on the left and add a new
database by clicking the green plus icon on the right

7.

Then select SID for the connection method and click Next

Page 30 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

No. Post Installation Setup Check

8.

Then complete the connection details as illustrated above and click Next

9.

Then test the connection details are OK by clicking on the yellow icon with a red
questionmark as shown in the image above. Click OK to continue

Page 31 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

No. Post Installation Setup Check

10.

Then the database will be registered with JBoss as shown above. Click OK to
continue

11.

Finally you will see the new database listed as shown above

Page 32 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

10.2 Register the Process server in the ORS database

The following tasks are required to register the Process server in the ORS database

No. Post Installation Setup Check

1. Log into the application server as the cup user.

2. Create the solr folder as follows

cd /home/cup/infa/infamdm/hub/cleanse

mkdir solr

3. Start the MDM admin console and login as admin

4.

Select the Process Server option from the Utilities menu on the left and select
the ORS and click Connect

Page 33 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

No. Post Installation Setup Check

5.

Click the Green Plus icon on the right and then complete the configuration as
illustrated above. Substitute the values shown for the correct ones for the
server being used.

Also enter the folder created in Step 2 above for the Zookeeper Data Directory

Page 34 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

No. Post Installation Setup Check

6.

Finally click on the orange test button to ensure that the server is configured ok

Page 35 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

10.3 Configure ActiveVOS

The following tasks are required to configure the ActiveVOS endpoints

No. Post Installation Setup Check

1. Start the JBoss server

2. Connect to the ActiveVOS console using the admin password

Connect using the admin console username and password that was setup in the
hub server silent install file

Page 36 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

No. Post Installation Setup Check

3.

From the dashboard select the admin menu and then URN mappings

4.

Update the setting for both the ae:internal-reporting urn and the ae:task-inbox
by clicking on the link and editing as shown above

Page 37 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

No. Post Installation Setup Check

5.

Add an additional urn mapping for the mdm service as shown above

URN URL
urn:mdm:service http://<host>:<port>/cmx/services/BEServices
urn:mdm:service https://<host>:<port>/cmx/services/BEServices

You can selecct either http or https from the above list

6.

Configure the Workflow engine from within the MDM console

Page 38 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

No. Post Installation Setup Check

7.

Finally click the test button to ensure that it is confured ok

8. Modify the JBoss config security domain ActiveVOS

Edit the standalone-full-ha.xml file in the


<JBOSS_HOME>/standalone/configuration folder.
<server xmlns="urn:jboss:domain:1.7">
...
<profile>
...
<subsystem xmlns="urn:jboss:domain:security:1.2">

<security-domain name="ActiveVOS">
<authentication>
<login-module code="RealmUsersRoles" flag="required">
<module-option name="usersProperties"
value="${jboss.server.config.dir}/application-users.properties"/>
<module-option name="rolesProperties"
value="${jboss.server.config.dir}/application-roles.properties"/>
<module-option name="realm" value="ApplicationRealm"/>
<module-option name="unauthenticatedIdentity" value="anonymous"/>
</login-module>
</authentication>
</security-domain>

</subsystem>
....
</profile>
...
</server>

Page 39 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

10.4 Configure the Hub Server properties file

The following tasks are required to configure the hub server properties file after installation.

No. Installation Instruction Step Check

1. Log into the application server as the cup user.

2. Now change directory to the hub server resouces folder

cd /home/cup/infa/mdm/hub/server/resources

edit the cmxserver.properties file to setup the cluster settings as


illustrated below

jboss.cluster=true
cmx.appserver.hostname=vmh-cupappt21.lpa.dlh.de,vmh-
cupappt22.lpa.dlh.de
cmx.appserver.rmi.port=8018,8018

These settings are to enable EJB clustering within JBoss

Page 40 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

11 Appendix

11.1 Appendix A Starting and Stopping JBoss

The following tasks are required to start and stop JBoss in standalone mode

No. Installation Instruction Step

1. Log in to the application server using the cup user

2. Execute the following command to start the server


./standalone.sh -c standalone-full-ha.xml -b 0.0.0.0 -u 230.0.0.4 -
Djboss.server.base.dir=/home/cup/jboss-eap-6.4/standalone -Djboss.node.name=Member1

The following values need to be substituted

-c The server configuration file to be used


-b The binding address which is the network address of the machine
-u Multicast address for Cluster communication

-Djboss.server.base.dir is for the path from where node is present


-Djboss.node.name is for the name of the node
-Djboss.socket.binding.port-offset is for the port offset on which node would be
running

We only use the socket port offset value if we are starting multiple nodes on the same
machine.

To start the server and enable it to run in the background you can use the following
command

nohup ./standalone.sh -c standalone-full-ha.xml -b 0.0.0.0 -u 230.0.0.4 -


Djboss.node.name=Member1 -Djboss.server.base.dir=/home/cup/jboss-eap-6.4/standalone
</dev/null >/dev/null 2>&1 &

when running the MDM installation process it would be better to start JBoss so that it does
not run as a background process. This makes it easier to spot errors. In this case you can
start JBoss using the following command

./standalone.sh -c standalone-full-ha.xml -b 0.0.0.0 -u 230.0.0.4 -


Djboss.node.name=Member1 -Djboss.server.base.dir=/home/cup/jboss-eap-6.4/standalone

3. Execute the following command to stop the server


./jboss-cli.sh --connect controller=127.0.0.1:8016 command=:shutdown

We use the controller setting if the server is configured to use non standard ports

Page 41 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

11.2 Appendix B Configure and Check the Environmental variables

The following tasks are required to set the appropriate environmental variables for the application
server

No. Installation Instruction Step

1. Log in to the application server using the cup user

2. Edit the .bash_profile and ensure that the following variables are configured
appropriately

See an example below


export JAVA_HOME=/opt/jdk/jdk1.7.0_80-lin-x64_JCE
export JRE_HOME=$JAVA_HOME
export JBOSS_HOME=/home/cup/jboss-eap-6.4
export ORACLE_HOME=/ora_u01/app/oraclnt/product/12.1.0.2_64/client
export OS=Linux
export NODE_ID=Member1
export PATH=$HOME/.local/bin:$HOME/bin:$ORACLE_HOME/bin:$JAVA_HOME/bin:$PATH
export ORACLE_SID=<DB_SID>
export TNS_ADMIN=$ORACLE_HOME/network/admin

3. Additional environment settings will be configured in the .profile file by the MDM
installation process and do not need to be manually setup.

See below for details


SSAPR=/home/cup/infa/mdm/hub/cleanse/resources
export SSAPR

LD_LIBRARY_PATH="${LD_LIBRARY_PATH}:/home/cup/infa/mdm/hub/cleanse/lib"
export LD_LIBRARY_PATH

Please check that these settings are present in the .profile file after running the process
server silent install.

Page 42 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

11.3 Appendix C Configure SSL

The following tasks are required to configure HTTPS for secure SSL connections

No. Installation Instruction Step Check

1. First use the java keytool to import the supplied certificate and create a
keystore

$JAVA_HOME/bin/keytool -import -alias smile_cup -keyalg


RSA -keystore smile_cup.keystore -file vmh-
cupappxxx.lpa.dlh.de.cer

It will ask if you trust this certificate, answer: yes

Make a note of the password that you use.

2. Modify the standalone-full-ha.xml file to add the SSL settings


below
<server xmlns="urn:jboss:domain:1.7">
...
<profile>
...
<subsystem xmlns="urn:jboss:domain:web:2.2" default-virtual-
server="default-host" native="false">
<connector name="http" protocol="HTTP/1.1" scheme="http"
socket-binding="http"/>
<connector name="https" protocol="HTTP/1.1" scheme="https"
socket-binding="https" enable-lookups="false" secure="true">
<ssl name="ssl"
key-alias="smile_cup"
password="smile+cup"
certificate-key-
file="../standalone/keystore/smile_cup.keystore"
protocol="TLSv1"
verify-client="false"/>
</connector>
...
</subsystem>
...
</profile>
...
</server>

3. Then add the truststore setting to the standalone.conf file as follows

JAVA_OPTS="-Djavax.net.ssl.trustStore=/path/to/keystore -
Djavax.net.ssl.trustStorePassword=smile+cup $JAVA_OPTS"

Then start JBoss and test that SSL connections can be made

Page 43 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

11.4 Appendix D JBoss Modules

The JBoss Modules are usually configured during the post installation step, however, if they have not
been configured correctly then you can set them up manually as described below

No. Installation Instruction Step

1. Log in to the application server using the cup user

2. Create the following directory structure under the modules folder

modules
com
activevos
main
informatica
mdm
jdbc
main

The main folder should contain the following two files

module.xml
ojdbc7.jar

The jar file can be obtained from the Oracle installation folder

The module.xml file should have the following contents

<module xmlns="urn:jboss:module:1.0" name="com.informatica.mdm.jdbc">


<resources>
<resource-root path="ojdbc7.jar"/>
</resources>
<dependencies>
<module name="javax.api"/>
<module name="javax.transaction.api"/>
</dependencies>
</module>

This applies to both the mdm/jdbc/main folder and the activevos/main folder

Page 44 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

11.5 Appendix E Manually Running the Post Installation Step

Sometimes you may need to manually rerun the post installation step

No. Installation Instruction Step

1. Log in to the application server using the cup user

2. cd /home/cup/infa/mdm/hub/server

./setSiperianEnv.sh

./postInstallSetup.sh -Ddatabase.password=<CMX_MASTER_PW>

The post installation step will now start

Once complete check the log folder for the post installation log file and see if it has
completed ok.

Page 45 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

11.6 Appendix F Restarting a failed installation from the beginning

If an installation fails because a parameter was wrong or through environmental issues you can
restart it from the beginning by following the steps below

No. Installation Instruction Step

1. Log in to the application server using the cup user

2. To restart you need to remove the infa sub folders, delete any partial deployments and
reset the standalone-full-ha.xml removing any changes made by the installation
process

rm -Rf /home/cup/infa/avos

rm -Rf /home/cup/infa/mdm

rm /home/cup/jboss-eap-6.4/standalone/deployments/*

cp /home/cup/install/standalone-full-ha.xml /home/cup/jboss-eap-
6.4/standalone/configuration

Page 46 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

11.7 Appendix G Installation Issues

Sometimes installations can fail here are some known issues

No. Installation Instruction Step

1. Unable to connect to MDM console with the following error No EJB requester available

Save the JNLP file by right clicking on the button on the MDM console web page and select
save as.

Open it in an editor. Then check the cmxServerName value is set to the application server
hostname and then save the file. You can then execute the file using javaws

Page 47 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

No. Installation Instruction Step

2. Problems registering an ORS database after installation is complete.

This is a known problem KB-497648 with Informatica 10.1 Hotfix 1 and will be fixed in a
future release.

This error occurs if you attempt to register an ORS database after you have configured the
jboss cluster in the cmxserver.properties file.

You should complete instructions in step 10.1 before you complete step 10.4.

The work around is to disable the jboss.cluster settings in cmxserver.properties file


and restart the server. Then register the database and reenable the cluster setting.

You will also need to manually copy the datasource configuration in the standalone-
full-ha.xml to all nodes in the cluster.

See Appendix H below for details on how to add a data source using JBoss CLI

Page 48 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

No. Installation Instruction Step

3. Unable to access ActiveVOS Central after installation

This can happen if the task url isnt configured properly. We need to open the activevos-
central.war file and set the HtTaskClientServiceUrl property.

<entry name="HtTaskClientServiceUrl" value="http://127.0.0.1:8011/active-


bpel/services/AeB4PTaskClient-taskOperations"/>

Execute the commands below to edit the xml configuration file


cp /home/cup/jboss-eap-6.4/standalone/deployments/activevos-central.war .
jar xvf activevos-central.war WEB-INF/aeworkflow-config.xml

vi WEB-INF/aeworkflow-config.xml

jar uvf activevos-central.war WEB-INF/aeworkflow-config.xml


cp activevos-central.war /home/cup/jboss-eap-6.4/standalone/deployments/

The war file will redeploy and the activevos central application will be available.

Page 49 of 50
LUF-MDM-002 Informatica MDM Hub Installation and Configuration Guide

11.8 Appendix H Adding a Data source to a JBoss config using CLI

One way to add a JBoss data source manually is to use the JBoss CLI. See below for an example

No. Installation Instruction Step

1. Log in to the application server using the cup user

2. Create a CLI batch file see example below and then execute it from the command line
cd /home/cup/install

vi jboss-add-xa-datasource.cli

Insert the folling into the CLI file


connect
batch

# Add an XA datasource

xa-data-source add \
--name=jdbc/siperian-vmh~-cupdodt21.lpa.dlh.de-tcuptwo-cmx_ors-ds \
--driver-name=com.informatica.mdm.jdbc \
--jndi-name=java:jboss/datasources/jdbc/siperian-vmh~-cupdodt21.lpa.dlh.de-tcuptwo-cmx_ors-ds \
--user-name=CMX_ORS \
--password=<password> \
--use-ccm=true \
--max-pool-size=300 \
--min-pool-size=5 \
--exception-sorter-class-name=org.jboss.jca.adapters.jdbc.extensions.oracle.OracleExceptionSorter \
--validate-on-match=false \
--background-validation=false \
--use-fast-fail=false \
--flush-strategy=FailingConnectionOnly \
--pool-prefill=false \
--pool-use-strict-min=false \
--same-rm-override=false \
--no-tx-separate-pool=true \
--track-statements=false \
--pad-xid=false \
--wrap-xa-resource=true

/subsystem=datasources/xa-data-source="jdbc/siperian-vmh~-cupdodt21.lpa.dlh.de-tcuptwo-cmx_ors-ds"/xa-datasource-
properties=URL:add(value=jdbc:oracle:thin:@vmh-cupdodt21.lpa.dlh.de:1850:TCUPTWO)
/subsystem=datasources/xa-data-source="jdbc/siperian-vmh~-cupdodt21.lpa.dlh.de-tcuptwo-cmx_ors-ds"/xa-datasource-
properties=ConnectionProperties:add(value="oracle.jdbc.J2EE13Compliant=true")
xa-data-source enable --name=jdbc/siperian-vmh~-cupdodt21.lpa.dlh.de-tcuptwo-cmx_ors-ds

# Execute and reload


run-batch

:reload

Now we execute the above cli file

cd /home/cup/jboss-eap-6.4/bin

./jboss-cli.sh --connect controller=127.0.0.1:8016 --file=/home/cup/install/jboss-add-xa-datasource.cli

Page 50 of 50