Hey folks,
I'm curious if anyone out there has had success in installing the CDI 8.2
integration into a CMDB which has or had an older (v8.1) CDI already in place.
We have been fighting multiple issues with the various components the installer
lays down, and are curious if we are the only ones having these "challenges"
and if there are any lessons learned floating around that might help us along.
Many components of the install (RE, AIE, etc.) are cmdb extensions, arx files,
etc. but there is a lot of black-box magic happening within the InstallShield
package. This is quite frustrating, since there is no clear way to validate
what the installer lays down, combined with the fact that you are not able to
execute the individual bits by hand when troubleshooting.
Instructions state to uninstall the previous integration before putting in the
new one -- this contributes to some of the issues we have experienced, listed
below:
- Installer fails on extending BaseElement & BMC_Software.
Cause: The CDI attributes already exist from a previous version, and
the uninstall (thankfully) does not drop the attributes.
Workaround: Create a dummy SHARE:Application Properties record for the
schema extensions, so that they are skipped. The uninstall removes these
records, you have to put them back. You can let the others run, since the
uninstall does clean that data out correctly.
remedy.cmdbextloader.install.details.1=Configuration Discovery Schema Extension
for BMC Atrium CMDB:SKIP
remedy.cmdbextloader.install.details.2=Configuration Discovery Integration for
BMC Atrium CMDB: SUCCESS
remedy.cmdbextloader.install.details.3=Configuration Discovery Trusted Dataset
Import Into BMC Atrium CMDB:SUCCESS
remedy.cmdbextloader.install.details.4=Configuration Discovery Federation Data:
:SUCESS
- Installer fails on setting up the Normalization Jobs and rule modifications
Cause: No clue
Workaround: BMC support provided a shell script hotfix to execute the
Java class which the installer calls. We have dug into the 8753 error below,
but all of the NE functions seem to be operating properly.
[Thu 01/26/2012 17:09:05.69]: Configuration Discovery Integration (CDI) 8.2.00
NE Settings started.
[Thu 01/26/2012 17:09:05.69]: ARServer Name: server
[Thu 01/26/2012 17:09:05.69]: ARServer UserName: user
ERROR (8753): Error in plugin; BMC.FILTERAPI.NORM.ENGINE
at com.bmc.arsys.api.ProxyJRpcBase.verifyStatus(Unknown Source)
at com.bmc.arsys.api.ProxyJRpcBase.a(Unknown Source)
at com.bmc.arsys.api.ProxyJRpcBase.arCall(Unknown Source)
at com.bmc.arsys.api.ProxyJRpc.ARServiceEntry(Unknown Source)
at com.bmc.arsys.api.ARServerUser.executeService(Unknown Source)
at
com.bmc.ne.api.NEClientFactory$ClientInvocationHandler.invoke(Unknown Source)
at $Proxy4.createJob(Unknown Source)
at CDINESettings.createNEBatchJob(CDINESettings.java:238)
at CDINESettings.main(CDINESettings.java:30
[Thu 01/26/2012 17:09:07.83]: Configuration Discovery Integration (CDI) 8.2.00
NE Settings is Failed.
- Installer fails on creating the federated plugin, along with required
federated class for BCAC Software Usage
Cause: No clue
Workaround: None yet
[Thu 01/26/2012 17:10:37.02]: Configuration Discovery Integration (CDI) 8.2.00
Federation Manager Settings Started.
[Thu 01/26/2012 17:10:37.02]: ARServer Name: server
[Thu 01/26/2012 17:10:37.02]: ARServer UserName: user
[Thu 01/26/2012 17:10:37.02]: Federation Manager Settings are not Applicable to
Install.
Our goal is to run the installer end-to-end, without error and have all bits
installed. We are working with BMC Support, but I wanted to reach out to the
community to see if anyone has any "been there done that" info they could share.
Thanks,
Tony
ARS 7.5p6
AtriumCore 7.6p2
ITSM 7.6p2
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
