| Author |
Message |
kghammond
Guest
|
 Posted:
Fri Jan 21, 2005 12:05 am Post subject:
Developing MOM Event Rules - Best Practices |
|
|
Hello all,
We are in the initial deployment and implementation phase of Microsoft
MOM 2005. We have come across a handful of scripts that we need to
modify and we have already identified a dozen or so more events that we
want to add to MOM.
| Quote: | From our initial analysis of trying to modify some of the existing
scripts, we are finding vbscript difficult to work with relative to |
vb.net. The lack of intellisense and a strong debugging environment
have us concerned that vbscript development will take significantly
more time and resources than necessary.
We reviewed the MOM SDK and the MOM Management Server Class Library for
vb.net, but from the SDK documentation, it appears that vb.net apps
that talk to MOM will only be able to run on the MOM server.
{Applications that use the library must be developed, tested, and
deployed on MOM Management Server computers.}
So I am asking for any Microsoft or community feedback on what are some
best practices for modifying and creating event rules for MOM.
Thank You,
Kevin |
|
| Back to top |
|
 |
JesseH
Guest
|
| Posted:
Fri Jan 21, 2005 3:01 am Post subject:
Re: Developing MOM Event Rules - Best Practices |
|
|
I wish I knew more about vb.net, if you find any good MOM vb.net references
please let me know.
In response to your statement: you are right, MOM does use a lot of
VBScript. However, since most people deploying MOM are Domain Admins, most
of us are very familiar with VBScript. I expect this trend to change in the
next 3-5 years where Admins will need the skills you posses.
A number of different ways exist to create event rules, can you provide a
few specific examples of what you are trying to accomplish?
Thanks!
-Jess
"kghammond" <kghammond@nrscorp.com> wrote in message
news:1106244305.532911.100460@f14g2000cwb.googlegroups.com...
| Quote: | Hello all,
We are in the initial deployment and implementation phase of Microsoft
MOM 2005. We have come across a handful of scripts that we need to
modify and we have already identified a dozen or so more events that we
want to add to MOM.
From our initial analysis of trying to modify some of the existing
scripts, we are finding vbscript difficult to work with relative to
vb.net. The lack of intellisense and a strong debugging environment
have us concerned that vbscript development will take significantly
more time and resources than necessary.
We reviewed the MOM SDK and the MOM Management Server Class Library for
vb.net, but from the SDK documentation, it appears that vb.net apps
that talk to MOM will only be able to run on the MOM server.
{Applications that use the library must be developed, tested, and
deployed on MOM Management Server computers.}
So I am asking for any Microsoft or community feedback on what are some
best practices for modifying and creating event rules for MOM.
Thank You,
Kevin
|
|
|
| Back to top |
|
|
kghammond
Guest
|
| Posted:
Fri Jan 21, 2005 3:58 am Post subject:
Re: Developing MOM Event Rules - Best Practices |
|
|
The initial project is to modify the free disk space script to ignore
drive letter P:. This is very easy to do in the script, but I was
looking to extend the script further to reading an exclusion file for
excluded drive letters, similar to the SQL Database Exclusion file.
Once again, this is rather trivial, especially with the code snippets
from the SQL Managment Pack that already do this, but the tricky part
is debugging and testing the script. I wrote a vb.net app that did
everything I needed in few hours and I have already spent a few days
working on the vbscript to do the same task, and debugging it and
moving the file to be tested, etc. It is mainly the lack of
intellisense while coding and debugging vbscript that make them
difficult to work with, IMO. BTW, I am using PrimalScript, but it
pales in comparrison to Visual Studio and vb.net.
Other longer term projects include service state monitoring, which
seems rather straight forward from what I have read so far. Later we
look to implement some more complex SQL database events and website
events. We want write some scripts that will launch our website, login
and perform some basic tests within the website to ensure all functions
of our web portal are working. On the SQL side, we want to write some
scripts that call various stored procedures to ensure database
integrity. We are also considering using MOM to monitor our SQL Server
Agent jobs and try to do some automated recovery actions if various
problems arise *before* sending an alert to MOM. This is just a quick
hit of conceptual ideas after some brainstorm sessions since we have
had MOM running.
Vbscript would be fine for 90% of what we need to do, but without the
advanced designer such as Visual Studio .Net, it takes a lot longer to
write and debug code/scripts.
And now, my plea to Microsoft, please, either add full support for
vbscript in Visual Studio, or improve vb.net capabilities of MOM. |
|
| Back to top |
|
|
JesseH
Guest
|
| Posted:
Fri Jan 21, 2005 4:25 am Post subject:
Re: Developing MOM Event Rules - Best Practices |
|
|
I'm a bit short on time here: (so in brief)
Everything sounds feasable so far.
Try alert overides for the P: drive (quick and dirty but it works).
"kghammond" <kghammond@nrscorp.com> wrote in message
news:1106258302.637053.148120@z14g2000cwz.googlegroups.com...
| Quote: | The initial project is to modify the free disk space script to ignore
drive letter P:. This is very easy to do in the script, but I was
looking to extend the script further to reading an exclusion file for
excluded drive letters, similar to the SQL Database Exclusion file.
Once again, this is rather trivial, especially with the code snippets
from the SQL Managment Pack that already do this, but the tricky part
is debugging and testing the script. I wrote a vb.net app that did
everything I needed in few hours and I have already spent a few days
working on the vbscript to do the same task, and debugging it and
moving the file to be tested, etc. It is mainly the lack of
intellisense while coding and debugging vbscript that make them
difficult to work with, IMO. BTW, I am using PrimalScript, but it
pales in comparrison to Visual Studio and vb.net.
Other longer term projects include service state monitoring, which
seems rather straight forward from what I have read so far. Later we
look to implement some more complex SQL database events and website
events. We want write some scripts that will launch our website, login
and perform some basic tests within the website to ensure all functions
of our web portal are working. On the SQL side, we want to write some
scripts that call various stored procedures to ensure database
integrity. We are also considering using MOM to monitor our SQL Server
Agent jobs and try to do some automated recovery actions if various
problems arise *before* sending an alert to MOM. This is just a quick
hit of conceptual ideas after some brainstorm sessions since we have
had MOM running.
Vbscript would be fine for 90% of what we need to do, but without the
advanced designer such as Visual Studio .Net, it takes a lot longer to
write and debug code/scripts.
And now, my plea to Microsoft, please, either add full support for
vbscript in Visual Studio, or improve vb.net capabilities of MOM.
|
|
|
| Back to top |
|
|
JJ
Guest
|
| Posted:
Sun Jan 23, 2005 12:17 am Post subject:
Re: Developing MOM Event Rules - Best Practices |
|
|
You can debug vbscripts also... install the MOM2005SDK
in the sdk help there's a step by step howto for debugging mom scripts
with visual studio .net !!
"kghammond" <kghammond@nrscorp.com> schrieb im Newsbeitrag
news:1106244305.532911.100460@f14g2000cwb.googlegroups.com...
| Quote: | Hello all,
We are in the initial deployment and implementation phase of Microsoft
MOM 2005. We have come across a handful of scripts that we need to
modify and we have already identified a dozen or so more events that we
want to add to MOM.
From our initial analysis of trying to modify some of the existing
scripts, we are finding vbscript difficult to work with relative to
vb.net. The lack of intellisense and a strong debugging environment
have us concerned that vbscript development will take significantly
more time and resources than necessary.
We reviewed the MOM SDK and the MOM Management Server Class Library for
vb.net, but from the SDK documentation, it appears that vb.net apps
that talk to MOM will only be able to run on the MOM server.
{Applications that use the library must be developed, tested, and
deployed on MOM Management Server computers.}
So I am asking for any Microsoft or community feedback on what are some
best practices for modifying and creating event rules for MOM.
Thank You,
Kevin
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in