Integration of XM 5.1 with BMC BEM 7.3 ( NO BPPM )

Not Yet Reviewed

Dear all,
has someone integrated XM 5.1 with BMC BEM 7.3 using the "old" BEM Integration ? Will this work ?

Thanks and kind regards,
Stefan

0

Comments

10 comments
Date Votes

Please sign in to leave a comment.

  • Hello Stefan,

    we integrated a BEM 7.4 (BPPM Cell) with the old "BEM Integration". We used this document for migrating the old JavaClient Integration to the 5.1 Integration-Agent: https://support.xmatters.com/hc/en-us/articles/202156695-How-to-replace-the-Java-Client-with-the-xMatters-integration-agent

    Regards

    Markus

    0
  • Stefan, did you get what you needed on this?

    0
  • I have tried the answer from Markus, but it does not work. I can call the provided exe but it does not send and events.

    0
  • Ah well that is progress! If you crack open the IAHOME/conf/log4j.xml file, then scroll down until you see this section:

    <!-- All Integration Services -->
    <logger name="com.alarmpoint.integrationagent.services">
    <level value="WARN"/>
    <appender-ref ref="svcAppender" />
    </logger>

    Then change that value="WARN" to value="DEBUG" and save the file. This will dump a lot of useful information to the IAHOME/log/AlarmPoint.txt file.
    Then restart the IA (windows service or IAHOME/bin/stop_daemon.sh and start_daemon.sh on linux) and send in another event. In the log file you should see the incoming event in some form or another. And if you aren't getting an event into xMatters, then you will probably see an error message as well.

    If you want to post the results here, we can do some debugging.

    Happy Sunday!
    --- Travis

    0
  • We have BEM 7.3 running on AIX connected to xMatters 5.1.1 in our environment using the IA in legacy mode as Markus mentioned.
    Do you have the scripts in place that BEM uses to call the IA?

    For example:
    root@pbem1:/bem/impact# cat ./server/etc/pbem/kb/bin/p4/AlarmPoint
    #!/bin/ksh
    /bem/xmatters/integrationagent-5.1.3/integrationservices/bmcimxap/bmc_apclient.bin --submit-mapping-file /bem/xmatters/integrationagent-5.1.3/integrationservices/bmcimxap/BMCxAP.txt "$1"

    0
  • Hi Mark,
    yes we have this direction running - what is missing is the way back - meaning the update on the calls statistics in BEM. We opened cases with BMC ( no reply at all ) and with xMatters. xMatters told us that the originally stated interface from BMC for the way back - and that we should ask the community.

    At the moment we just have to live with what we have.

    0
  • Hello Stefan,

    on what OS you are running the Integration Agent. We also had problems with the backware answers to our BEM Cell on a 2008 R2 Server.
    Your Solution was running the IA Windows Service as a user and not as system user.

    Regards

    Markus

    0
  • We do use W2008 R2. The main problem I see here is, that in the doc for the "old" integration they stated several place to put in the changes for the backward communication in the default callout script. I did only find 1 place.
    So you say that you run the IA as user and do use the default Matters callout script ? On which pace did you insert the code ?
    Thanks, Stefan

    0
  • Hello Stefan,
    we are using the default callout/callin Scripts from xm 4.x. We are also using the default bmcimxap Scripts. When we have a FYI Notification we have no backward communiction to the cell.

    Regards

    Markus

    0
  • The callin/callout script may need to be updated, but ultimately the bmcimxap Action Script is what would send the responses back to the Integration Agent, which should then update BEM.
    You may want to enable DEBUG logging on your Integration Agent and see if the updates are making it that far. You should be able to see an "Acknowledge" come into the IA from xMatters. That may help troubleshoot where in the process the issue is?

    0

Didn't find what you were looking for?

New post