| Author |
Message
|
| SDS |
 Posted: Thu Sep 22, 2016 2:15 am Post subject: Generate BMC Remedy Incident from Message flow |
 |
|
Apprentice
Joined: 13 Jun 2011
Posts: 47
|
Hi,
I have a requirement to create BMC remedy incident for any exception occurred in message flow in IIB V10.
Could anyone please help on this? Any lead will be highly appreciated. |
|
| Back to top |
|
 |
| timber |
| Posted: Thu Sep 22, 2016 3:36 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
| Same answer as always. Please tell us what you have read, what you have tried, and list the things that you are unsure about. Then we can fill in the gaps. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Sep 22, 2016 3:58 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
So, you have a requirement?
And that's your work to do?
And we all have our own work to do?
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Sep 22, 2016 4:56 am Post subject: Re: Generate BMC Remedy Incident from Message flow |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| SDS wrote: |
| Any lead will be highly appreciated. |
How about posting in a BMC forum about the best way to programmatically raise an incident?
Knowing that, code it into IIB.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| SDS |
| Posted: Thu Sep 22, 2016 5:07 am Post subject: |
|
|
Apprentice
Joined: 13 Jun 2011
Posts: 47
|
Actually I am not getting much idea from internet on how to start on it.
The only logical thing I came across from a topic which says that Msend is a BMC executable which enables events to be sent into a BPPM (BMC ProactiveNet Performance Manager) cell for processing. This executable can be called from scripts like batch or shell etc.
Need to know how to integrate to BPPM environment in local and how to call the same from a batch file.
Also it would be really helpful if anyone shares any other workaround to create BMC remedy incidents from IIB. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Sep 22, 2016 5:26 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| SDS wrote: |
| Actually I am not getting much idea from internet on how to start on it. |
Have you tried asking BMC?
Presumably this BPPM thing has documentation.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Sep 22, 2016 5:30 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Or how about this:
You presumably want to raise incidents in BMC Remedy because your site uses BMC Remedy to control events.
Your site presumably has other applications aside from IIBv10. These, like all applications, sooner or later go wrong.
From this, it can be inferred that these applications need incidents in BMC Remedy to get resolution.
So reach out to these other application teams to find out how they're raising incidents programmatically. Or to the team which owns BMC Remedy on your site to find out how they're receiving incidents programmatically.
Use this method in IIB v10.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| SDS |
| Posted: Fri Sep 23, 2016 2:44 am Post subject: |
|
|
Apprentice
Joined: 13 Jun 2011
Posts: 47
|
Today I was able to create alert event in BMC by executing msend method. I have created one batch file to wrap the method in it and executed the batch file from command prompt and it worked as expected.
But when I am executing the same .bat file from JCN in IIB. It is not creating any event and I am not getting any error either.
To check whether my JCN is working or not, I executed another simple batch file and it is working properly.
Can anybody give me any idea on what can be the issue here and how to resolve it? |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Sep 23, 2016 3:10 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Why not use the job control node (Support pack) at least then you may see what is going on.
As an aside, the JCN will be trying to execute the .bat file with a different user name to what you may be using when you execute it manually. Does the broker user have the rights to create a remedy ticket?
Why not put some logging in this file that puts output to a separate log file that way you can see what is going on?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| SDS |
| Posted: Fri Sep 23, 2016 4:20 am Post subject: |
|
|
Apprentice
Joined: 13 Jun 2011
Posts: 47
|
I have used Job Execution Node to check the issue.
I am getting an error as "'msend' is not recognized as an internal or external command, operable program or batch file."
However, the environment variables are set and I am able to execute the msend command properly from the same batch file from command prompt. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Sep 23, 2016 5:33 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| SDS wrote: |
I have used Job Execution Node to check the issue.
I am getting an error as "'msend' is not recognized as an internal or external command, operable program or batch file."
However, the environment variables are set and I am able to execute the msend command properly from the same batch file from command prompt. |
That means that whatever you have done to make 'msend' work in your account command shell has to be done in the script that you are using to run msend.
It might be something as simple as replacing the path to the msend executable
eg in your environment you use
| Code: |
msend ..... args ....
|
to something like
| Code: |
c:\Progrma files\BMs\msend .... args ...
|
In a windows environment.
I'd start by putting the following commands in the script
| Code: |
env > c:\temp\env.txt
echo %PATH% >> c:\temp\env.txt
|
Then compare this with what you have in your environment.
Leave nothing to chance. do noyt assume that anything is setup for you.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| SDS |
| Posted: Fri Sep 23, 2016 7:07 am Post subject: |
|
|
Apprentice
Joined: 13 Jun 2011
Posts: 47
|
Thanks for the reply. It was really helpful to figure out the error.
Actually the error is related to path from where the batch is calling the msend method.
IIB was always executing it from it's runtime path and that's why it could not recognize the msend command.
The clue is to execute the batch from the path where the msend.exe is present. By following the same the issue got resolved. |
|
| Back to top |
|
|
|
|
