This section will provide a detailed guide on how to configure Informatica Multidomain MDM. The environment details for this configuration are as follows:
- Operating System: Linux
- Database Server: MS SQL Server
- Application Server: Jboss
- Informatica Version: Multi-Domain MDM 10.4 HF2.
Prior to installing MDM, ensure that the following Linux parameters have been properly configured by completing the pre-install checklist.
- Confirm that the hostname has been set.
- Verify the host files located in /etc/hosts.
- Ensure that the necessary ports are open, including 8080/tcp, 8443/tcp,
and 9200/tcp.
- Set environment variables such as JAVA_HOME and PATH in the .bashrc file.
- Check that the .bash_profile is empty.
- Install the AZUL_ZULU_JDK for JAVA setup.
- Create a server keystore for Jboss setup.
- Configure the Java Virtual Machines in standalone.conf.
- Configure the server properties for the Full Profile in standalone-full.xml.
Note:- For some of the tasks, you might need to reach out to Linux Admin team (eg: Jboss Setup)
Verify JBoss is configured:
/<Jboss Installation path>/bin> vi standalone.conf
# JAVA VM options for Informatica MDM
JAVA_OPTS="$JAVA_OPTS -Djava.net.preferIPv4Stack=true "
JAVA_OPTS="$JAVA_OPTS -Djboss.as.management.blocking.timeout=5000 "
JAVA_OPTS="$JAVA_OPTS -XX:+UseCodeCacheFlushing -XX:ReservedCodeCacheSize=512m -XX:MaxMetaspaceSize=1G "
JAVA_OPTS="$JAVA_OPTS -Dorg.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE=16384 "
----standalone-full.xml file updates--/opt/EAP-7.1.0/standalone/configuration> vi standalone-full.xml
coordinator-environment default-timeout="3600"
http-listener name="default" socket-binding="http" redirect-socket="https" enable-http2="true" max-post-size="20000000"
https-listener name="https" socket-binding="https" security-realm="ApplicationRealm" enable-http2="true" max-post-size="20000000"
Installation Topology:1. Install App server - Jboss (not covered here)
2. Install Multi Domain MDM
Create Hub Store:
Create Operational Reference store:
Import the Database Schema into the ORS:
Importing the MDM Metadata
3. Hub Server Installation
4. Cleanse Server Installation
Creation of Hub Store and Operational Reference Store:
Please click here for Installation steps.
Please click here for Installation steps.
Start JBoss:
<Jboss Installation path>/bin> ./standalone.sh -c standalone-full.xml -b 0.0.0.0 -Djboss.as.management.blocking.timeout=5000
Hub Server Installation:-
- Ensure that install files and License file are in place.
- Verify permissions are set correctly on all installers.
- Ensure that you have usernames and passwords for the following users (schemas):
CMX_SYSTEM (Hub master database)
CMX_ORS (Hub operational reference store)
AVOS (ActiveVOS BPM user)
JBoss administrator UserName & Password
AVOS console Admin UserName & Password
Hub Server Installation steps in Linux: Check here
Cleanse Server Installation steps in Linux: Check here
Verify Logs & Application Access:
Jboss logs:- /<Jboss Installation Path>/standalone/log/server.log
MDM cmx server logs:- /<Infamdm Installation path>/hub/server/logs/cmxserver.log
MDM cmx cleanse logs:- /Infamdm Installation path>/hub/cleanse/logs/cmxserver.log
Jboss Admin login URL:- http://<hostname>:8080/console
MDM Hub Console:- http://<hostname>:8080/cmx/
Active Vos Console: http://<hostname>:8080/activevos/home.action