In general, MDM installation could be performed in 3 modes: GUI mode, console mode

and silent/unattended mode. Basically, the installation enironment re!uirements are the
same for each installation mode, and the installation logs "ill be generated once the
installation completes no matter "hich mode you choose.
#his troubleshooting guide "ill coer belo" topics "hich are focusing on:
$ Understanding installation logs
$ %o" to resole empty &M Data and &M component issue
$ MDM &lient 'pplication failure
Understanding installation logs
#he installation process is trac(ed and recorded into installation logs, once the
installation completes )or fails*, corresponding logs "ill be generated into the installation
logs folder, e.g. the MDM home is defined as /usr/IBM/MDM/MDM+erer, then the logs
could be found under /usr/IBM/MDM/MDM+erer/temp/logs/,time-stamp.
Under the root of installation directory, there/s a file named MDMInstall.log "hich is a
summary of the MDM installation 0ust completed, it contains belo" information:
$ +tatus of system health 1 en. settings : dis(space, DB command e2ecutable,
DB ersion, DB %ome, DB connection testing, application serer type, 3'+
security, port conflict etc.
$ 4eature selected: DB repository, MDM serer component, &M repository, &M
component, B'UI)Business 'dminitration UI*, D+UI)Data+te"artship UI*,
5UI)5roduct UI*, 6G&)6erGreen &onsole*
$ Installation entries:
DB 7 DB type, DB name, tablespaces, DB user, DB pass"ord, DB schema,
trigger industry type, trigger type )simple, compond*.
3'+ )application serer* 7 3'+ type )8D or base*, %9M6, 5rofile,
&ellname, 8odename, MDM serer name, 3'+ deployment manager
serer port etc.
:M+ / M;: messaging hostname, !ueue manager name, !ueue port,
messaging user and pass"ord.
MDM applications: B'UI name, B'UI port, D+UI name, D+UI port, 5UI
name, 5UI port, 6G& name 1 port
'pplications deployment status, e.g
<=><$>>$>= >?:=@:33,<3A Bmain C I849 com.ibm.mdm.deploy.logging.InstallerDog $&DEI8<=>FI: #he
Data +te"ardship application deployed successfully.: 4or more details, loo( in the file:
/usr/IBM/MDM/MDM+erer/temp/logs/>>$>=$<=><$
=>-3@-=@/D+'pplicationDeploymentDogs/Deploy-app-ds-out.log
DB ob0ects creation status, including tables, triggers, foreign (eys e.g
<=><$>>$>= >3:GH:GG,=H@ Bmain C 6II9I com.ibm.mdm.deploy.logging.InstallerDog $&DEI8<=3@I:
#ables "ere created successfully.: 4or more details, loo( in the file:
/usr/IBM/MDM/MDM+erer/temp/logs/>>$>=$<=><$
=>-3@-=@/DatabaseDogs/&oreDataDB<&reate#ables9ut.log
9nce the installation completes, follo"ing installation log directories could be
chec(ed to understand deeper if the DB ob0ects created successfullyand if
deployment process finishes appropriately:
1. In the root of installation log folder, chec( the installation summary file,
MDMInstall.log to see if there/s any e2ception e2istsJ
2. &hec( files under DatabaseDogs folder to ensure the DB ob0ects created
properly
$ CoreDataDB2CreateTablesOut.log
$ MDMDBCreateTablesOut.log
$ CoreDataDB2CreateFkIndxPopulateDataOut.log
'lso, double chec( the files under this folder ended "ith K6rr/, e.g.
MDMDB&reate#ablesErr.log, as long as the files LLLLL6rr.log are empty,
"hich indicates there/s no errors during the DB ob0ects creation stage.
3. Go into folder MDM'pplicationDeploymentDogs folder, chec(
$ DeployAppOut.log, !n "#!$# #as t#e appl!$at!on ser%er deploy&ent
!n'or&at!on, e.g. !n a su$$ess deploy&ent, !t #as 'ollo"!ng !n'o.(
'DM'G==GI: #he application LLLLLL is configured in the 3eb+phere 'pplication +erer
repository.
'DM'G>>3I: 'ctiation plan created successfully.
'DM'G=>>I: #he cleanup of the temp directory for application LLLLLL is complete.
'DM'G=>3I: 'pplication LLLLL installed successfully.
)).
$ *er%erCon'!gOut.log, !' t#ere+s no ex$ept!on, !t s#ould $onta!n t#e deta!l
appl!$at!on deploy&ent !n'or&at!on, .e.g.
*ett!ng up ser%er ,------, at node ,------, !n $ell ,------,...
*er%er ,------, does not ex!st. Creat!ng ne" ser%er 'ro& te&plate ,de'ault,...
*ett!ng ./M para&eters...
Con'!gur!ng ser%er,s "ork!ng d!re$tory...
01APP2I3*TA4425OOT678Cell23a&e97------.ear
sett!ng gener!$.%&Argu&ents 'or ser%er ,------,
./M !n!t!al #eap s!:e set to ;12M and &ax!&u& #eap s!:e to 1<2=M 'or ser%er ,------,.
>.B $a$#e s!:e set to 3;<< 'or ser%er ,------,.
gener!$.%&Argu&ents 'or ser%er ,------, set.
))..
=. Dog into MDM DB, chec( appdeployment, appsoft"are and configelement
tables to ensure the &M data has been loaded properly. #ypically, both
appdeployment, appsoft"are should hae one record for each table, and
configelement table contains hundreds of MDM configuration itemsJ if these
tables are empty, this indicates &M data loading failure, "hich may be
caused by :8DI loo(up, soc(et permission problems etc.
;. &hec( Management&onsoleDogs folder, there are < important logs can
demonstrate more detail information in case the &M data loading failed:
&MDB&reate#ables9ut.log 1 &M&onsole9ut.log.
?. UIs deployment log, basically, each UI has its o"n deployementlog files
indicate the installation/deployment status, e.g. D+UI deployment log folder,
if Deploy-app-ds-out.log has belo" message sho"s that the D+UI
application deployed successfully)other UIs hae the similar naming
symptom*:
MM..
'DM'G=>3I: 'pplication ,UI application name. installed successfully.
MM..
How to resolve empty CM Data and CM component issues
Basically, the &onfiguration and Management )&M* components support the operational
configuration and management of applications. #hey enable administratie users to
deploy, fine$tune, and manage applications "ithin their runtime enironment.
#he &onfiguration and Management components allo" customer to configure and
manage both standalone and enterprise applications. &urrently, these components are
only aailable for Info+phere MDM +erer and Info+phere MDM +erer eent manager
enterprise applications, not for the Info+phere MDM +erer Batch &ontroller application.
#o understand more about "hat the &M is and "hat the &M is doing deeperJ please refer
to MDM +ystem Management Guide or through MDM information center:
#ttp(77p!$.d#e.!b&.$o&7!n'o$enter7&d&7%1<r<&<7!ndex.@spAtop!$B
C2F$o&.!b&.&d&#s.de%.plat'or&.do$C2F$on$epts
C2F$2Ds!ng2Con'!gurat!on2and2Manage&ent2Co&ponents.#t&l
8ormally, to troubleshoot a MDM &M issue, follo"ing steps / procedures could be ta(en
to diagnose the issue and resole the issue:
>. Dog into MDM Database, chec( 3 &M tables, '55D65D9NM68#, '55+94#3'I6
1 &984IG6D6M68# to see if there/s any data has been inserted into those tables.
6.g in MDM >=.> release, '55D65D9NM68# and '55+94#3'I6 has one record
for each, and it has 3@@ records in &984IG6D6M68# tableJ
<. If all &M tables are empty, "hich means the &M data inserting does not complete
successfully, chec(ing &M 'gent log is re!uired to understand "hat happened "hile
loading the &M data
#he typical e2ception of &M data loading could be seen in &M agent log:
6II9I $ com.ibm.mdm.cache.common.&acheDoader62ception: &acheDoader 62ception in
get&ache: 0aa.lang.Iuntime62ception:
com.dwl.management.config.repository.RepositoryStoreException:
B62ception-IepositoryImpl-&reate&onnection4ailed:C &DE&I<=>@6:' failure occurred "hile trying to
create a connection to the configuration repository database.
at com.ibm.mdm.cache.generic.impl.&acheManagerImpl.get&ache)&acheManagerImpl.0aa:<3A*
at com.d"l.management.config.cache.Generic&acheImpl.,init.)Generic&acheImpl.0aa:GA*
at com.d"l.management.config.cache.&ache4actory.get&ache)&ache4actory.0aa:GH*
#his error message indicates that the DB connection bet"een &M 'gent and
MDM bac(end failed "hich may caused by :8DI loo(up failure or datasource
definition has problems. Go to 3'+ admin console $. Iesources $. datasource
$. D3D&onfig, clic( the testconnection button to alidate the datasource, also, if
DB user and DB schema are not the same, the :DB& attribute 7 current+chema
needs to be proided in custom properties to ensure the :DB& connection could
be established properly.
'nother typical e2ception of &M data loading could be seen in &M agent log:
>55O5 E $o&.!b&."ebsp#ere.na&!ng.CannotInstant!ateOb@e$t>x$ept!on( >x$ept!on o$$urred "#!le t#e .3DI
3a&!ngManager "as pro$ess!ng a @a%ax.na&!ng.5e'eren$e ob@e$t. F5oot ex$ept!on !s
java.lang.reflect.InvocationTargetExceptionG
at $o&.!b&."s.na&!ng.ut!l.Helpers.pro$ess*er!al!:edOb@e$tFor4ookup>xtIHelpers.@a%a(11<3J
at $o&.!b&."s.na&!ng.ut!l.Helpers.pro$ess*er!al!:edOb@e$tFor4ookupIHelpers.@a%a(KL?J
at $o&.!b&."s.na&!ng.@nd!$os.C3ContextI&pl.pro$essBoundOb@e$tFor4ookupIC3ContextI&pl.@a%a(2MK?J
at $o&.!b&."s.na&!ng.@nd!$os.C3ContextI&pl.pro$ess5esol%e5esultsIC3ContextI&pl.@a%a(3LK3J
at $o&.!b&."s.na&!ng.@nd!$os.C3ContextI&pl.do4ookupIC3ContextI&pl.@a%a(1KK?J
at $o&.!b&."s.na&!ng.@nd!$os.C3ContextI&pl.lookup>xtIC3ContextI&pl.@a%a(1=33J
at $o&.!b&."s.na&!ng.@nd!$os.C3ContextI&pl.lookupIC3ContextI&pl.@a%a(?1;J
#his error message demonstrates that the &M agent 7 0aa client application
does not hae permission to access 3'+ :ML, ho"eer, this is a (no"n issue
and the resolution has been documented in a technote:
#ttp(77"""E<1.!b&.$o&7support7do$%!e"."ssAu!dBs"g213M3L<2
3. #o isolate the issue and be prepared to load the &M data manually, belo" steps may
be re!uired:
Go to ,MDM-%9M6./ Management'gent/config, i bootstrap.properties file,
search line repository.uriOconfig:database:0dbc/D3D&onfig and replace it by
repository.uriOconfig:database:0dbc:db<://,hostname.:,port./,DB-8ame.:user
O,DB-User.Jpass"ordO,DB-5ass"ord.
or
repository.uriOconfig:database:0dbc:oracle:thin:P,hostname.:,port.:,DB-8am
e.:userO,DB-User.Jpass"ordO,DB-5ass"ord.
Go to ,MDM-%9M6./ Management'gent/config, i mgmt-agent.policy file,
chec(/append
permission java.net.Socet!ermission "#Host$%ame&"' "accept' connect"(
M..
permission java.lang.reflect.Reflect!ermission "suppress)ccessC*ecs"(
Disable 3'+ global security if it is possible
?. #o load the &M data manually, please follo" steps belo":
8aigate to the /,MDM-%9M6./Management'gent location and run
stop'gent.sh then start'gent.sh
8aigate to the /,MDM-%9M6./Management&onsole location and run the
follo"ing: ./console/sh $file
,MDM-%9M6./Management&onsole/scripts/0acl/deploy'pp&onfig.0acl
Q,application name.Q /,MDM-%9M6./installable'pps/MDM.ear. #he data
loading ta(es couple of minutes to complete.
&hec( &M 'gent logs to ensure there/s no e2ception, K3arning msg/ could be
ignored
&hec( '55D65D9NM68#, '55+94#3'I6 1 &984IG6D6M68# to see if the
&M data are loaded properly
Iestart MDM application serer and re$run IR# or simple MDM transaction to
alidate basic function of MDM serer.
MDM client application failure
In MDM application set, IR# 7 Installation Rerification #ool, Batch 5rocessor and
6entManager client could be treated as :aa/MDM &lient 'pplication, follo"ing ma0or
MDM client application/scripts e2isting in MDM product releases )@.=.>, @.=.<, >= and
>=.>*:
>. Batch 5rocessor $. runbatch.sh, runBul(5rocessing&ontroller.sh
<. IR# $. erify.sh and #est&lient.sh
3. eentManager&lient $. start+chedule&ontroller.sh, status+chedule&ontroller.sh etc.
?. Management'gent $. run'gent.sh, start'gent.sh
#he MDM client application scripts/assets need to be changed correspondingly to adapt
ne" settings if the situation changes, e.g 3eb+phere 'pplication +erer Global +ecurity
enabled after the MDM installation.
'll MDM client applications follo" similar file structure:
Dib S 5roperties S logs S bin/scripts
#he supporting 0ar files contains in Dib folderJ 5roperties folder has specific properties
files for each client application, log?0 properties and other re!uired properties are
included in this folder as "ellJ Dogs folder records the actions logs for each MDM client
applicationJ the client application scripts could be found under bin/scripts or the root
folder of client.
+imply spea(ing, a MDM client application script could be diided into 3 parts:
>. 6nironment setting and MDM application related arguments, "hich including +erer
type, 3'+-%9M6, :'R'-%9M6, DB-#N56, MDM port, MDM hostname, DB drier path
etc.
<. Ie!uired libs, customer 0ars and lib path definitionJ
3. +cript functions, only +#'I#-3'+ function "ill be coered in this document though.
In +#'I#-3'+ function, belo" arguments need to be set / focused "hile doing the
troubleshooting:
>. 3'+ security status. 3'+-+6&UII#N argument is used "ith alue T=T $ 3'+ security
944, T>T $ 3'+ security 98
<. &DI68#+'+/+'+-&984IG, this argument contains the configuration settings for
authentication bet"een a :aa client and a serer, it either could be the physical path S
sas properties file name)sas.client.props*, or the content of sas.client.props could be
copied directly and set as &DI68#+'+/+'+-&984IGJ
4or e2ample:
+'+-&984IGOQ$Dcom.ibm.&9IB'.security6nabledOtrue
$Dcom.ibm.&9IB'.authentication#argetOBasic'uth
$Dcom.ibm.&9IB'.authenticationIetry6nabledOtrue
$Dcom.ibm.&9IB'.authenticationIetry&ountO3
$Dcom.ibm.&9IB'.alidateBasic'uthOtrue $Dcom.ibm.&9IB'.security+erer%ostO
$Dcom.ibm.&9IB'.security+erer5ortO $Dcom.ibm.&9IB'.login#imeoutO3==
$Dcom.ibm.&9IB'.login+ourceOproperties
$Dcom.ibm.&9IB'.loginUseridOU+6I8'M6
$Dcom.ibm.&9IB'.login5ass"ordO5'++39ID $Dcom.ibm.&+I.perform+tatefulOtrue
$Dcom.ibm.&+I.perform&lient'uthenticationIe!uiredOfalse
$Dcom.ibm.&+I.perform&lient'uthentication+upportedOtrue
$Dcom.ibm.&+I.perform#D&lient'uthenticationIe!uiredOfalse
$Dcom.ibm.&+I.perform#D&lient'uthentication+upportedOfalse
$Dcom.ibm.&+I.perform#ransport'ssoc++D#D+Ie!uiredOfalse
$Dcom.ibm.&+I.perform#ransport'ssoc++D#D++upportedOtrue
$Dcom.ibm.&+I.performMessageIntegrityIe!uiredOtrue
$Dcom.ibm.&+I.performMessageIntegrity+upportedOtrue
$Dcom.ibm.&+I.performMessage&onfidentialityIe!uiredOfalse
$Dcom.ibm.&+I.performMessage&onfidentiality+upportedOtrue
$Dcom.ibm.ssl.aliasODefault++D+ettings $Dcom.ibm.&9IB'.re!uest#imeoutO>H=Q
8ote: $Dcom.ibm.&9IB'.loginUseridOU+6I8'M6 "hich needs to proide the
username and $Dcom.ibm.&9IB'.login5ass"ordO5'++39IDU+6I8'M6, pass"ord
is re!uired
4or troubleshooting purpose, paste the content of sas.client.props into MDM client
application script "ould be a better choice.
3. :'R'-6L#-DII, it holds the :aa e2tension libs and properties for authentication
bet"een a :aa client and a serer.
e.g :'R'-6L#-DIIO$D0aa.e2t.dirsOU3'+-%9M6/0aa/0re/lib/e2t:
U3'+-%9M6/0aa/lib:U3'+-%9M6/classes:U3'+-%9M6/lib:
U3'+-%9M6/installed&hannels:U3'+-%9M6/lib/e2t:U3'+-%9M6/"eb/help:
U3'+-%9M6/deploytool/itp/plugins/com.ibm.etools.e0bdeploy/runtime:
U3'+-%9M6/plugins:U3'+-%9M6/lib/3M;/0aa/lib
?. &DI68#++D/++D-&984IG, it is used to configure +ecure +oc(ets Dayer )++D* for
0aa client, similar as sas.client.props, the argument needs to be set "ith physical path S
ssl.client.props file name, e.g.
++D-&984IGO$
Dcom.ibm.++D.&onfigUIDOfile:/usr/IBM/3eb+phere/'pp+erer/profiles/Dmgr=>/properti
es/ssl.client.props
9nce aboe items set/configured, a client 0aa call may need to be concentrated on, e.g.
QUV:'R'-%9M6W/bin/0aaQ $LmsUVminMemoryW $Lm2UVma2MemoryW $classpath QUV&5WQ U
V++D-&984IGW UV+'+-&984IGW......
or QU:'R'-%9M6/bin/0aaQ U:'R'-6L#-DII U++D-&984IG U+'+-&984IG $classpath
QU&D'++5'#%Q.......
#he usage might be slightly different but the concept is the same.
In addition, there is fe" more arguments need to double chec( prior to start the client and
some arguments may need to be reised according to current enironment:
>. 3'+-%9M6, modify the location of 3eb+phere Installation
e.g /usr/IBM/3eb+phere/'pp+erer
<. 3'+ deployment manager profile name/path, the dmgr name or path need to be
modified correspondingly
e.g /usr/IBM/3eb+phere/'pp+erer/profiles/Dmgr=>
3. DB drier path and name
e.g
9I'-DIIR6I-:'IOo0dbcA.0ar
DB-DIIO/home/oracle/oracle/0dbc/lib
?. sas.client.props and ssl.client.props location, both file could be used directly under
,3'+-%9M6./profiles/,DMGI-8'M6./properties, or they could be copied into client
applicationTs properties folder.
'lso, there is a file named T&lient'uthentication.propertiesT "hich could be found under
the MDM client applicationTs properties folder, the client.idO,&DI68#-U+6I. and
client.pass"ordO,&DI68#-5'++39ID. need to be proided properly.