XMatters 5.1.3 and BEM Bidirectional Interface

Not Yet Reviewed

We do use the „old“ BMC Impact Manager interface. The documentation says the following:

To annotate a BMC IM incident from the Callout scripts:
1. Open the AlarmPoint Developer IDE.
2. Check out the Production Callout Script Package.
3. Open the callout CONTACT script and the authenticate INTERACTION script.
4. Add the following lines of at the end of both scripts:
SendAnnotationMessage:
IF( $initiatingEvent.agent_client_id == "bmcimxap" )
@session::respondToNotification( $notId, "callout_annotate " & $message_note )
ENDIF
RETURN
Note: If the SendAnnotationMessage is already in the callout scripts due to another integration, update it with logic to
handle when the agent_client_id equals “bmcimxap”.
5. Locate the code section that sends an ExternalServiceMessage.
6. Add the following lines after the message is added to the ServiceMessage object, and after the send method is
executed on the object:
$message_note = $connectionEventMessage.message
GOSUB SendAnnotationMessage
7. Repeat the previous two steps for each section that sends an ExternalServiceMessage.
Note: There should be a total of 10 code segments that require updatin: eight in the callout script, and two in the
authenticate script.
Example:
The following is an example of an enhanced segment of code:
$connectionEventMessage.message = "Callout to " & $targetName & " successful (" &
$result & ")."
@connectionEventMessage::send()
$message_note = $connectionEventMessage.message
GOSUB SendAnnotationMessage

Trouble is that the in the doc mentioned script is different to the format of the new Xmatters. So which scripts of the default installation do I have to modify ?

Thanks,

Stefan

0

Comments

2 comments
Date Votes

Please sign in to leave a comment.

  • Hey Stefan. Yea, my callout script looks slightly different too. Can you post yours and we can find exactly where to put it? Basically this code is just firing back to annotate in BEM that the callout was successful to the user. It is good for auditing so you can see if they hangup or don't respond. Depending on how much granularity you want, you can get away with just having the BEM business scripts handle this, which they should out of the box.

    Anyway, post up your callout script and we can dig through and figure out where to put it.... specifically I'm eyeballing this line just before $ranInteraction = @interaction::runInteractionScript(@content, @script, @session, @recipient, @phone)

    Happy Friday!
    --- Travis

    Oh, and you can use markdown for easier to read formatting if you want.

    0
  • Stefan, we don't recommend modifying Callout script unless there is definitely no other way to achieve your objective. Callout script comes from Template of new xMatters and it will be overwritten each time you patch or upgrade your xMatters instance.

    0

Didn't find what you were looking for?

New post