Home
  • RapidInsight
  • RapidInformer
  • Support
  • About Us
Home

groovy

Groovy4Netcool script example: updating an event field

Posted October 24th, 2007 by berkay
in
  • groovy
  • Groovy4Netcool
  • howto
  • Netcool
  • opensource
  • scripting

In the previous post, I'd announced the Groovy4Netcool project. In this follow up post, I'll go through a simple script as an example to demonstrate how it can be used. The objective is to work with an event in the Netcool server, to get the value of a field and update that value.

First, I should highlight the files in this project are NOT required to use groovy to work
with Netcool server. Groovy language has inherent support to work with database via jdbc. The files in this project provide an infrastructure to make it easier to work with Netcool so that one does not have to know or deal with JDBC and SQL,
although they are available.

 

First, I need to set the connection parameters for the Netcool server in the NetcoolDataSource.groovy file.  read more »

Using groovy scripting to work with Netcool Omnibus

Posted October 21st, 2007 by berkay
in
  • groovy
  • Integration
  • Netcool
  • opensource
  • scripting

How do (or should) you interact/work/integrate with Netcool Omnibus servers?

If you work on systems integration, it's likely that you've run into this question at some point. There are number of options available depending on your needs. Here is a summary of the options that I could come up with:

Netcool suite components.  read more »

Standing on the shoulders of giants: say no to proprietary languages, welcome to Groovy and salute JVM

Posted September 16th, 2007 by berkay
in
  • dynamic languages
  • groovy
  • java
  • JVM
  • opensource
  • scripting

Majority of the tools in the IT management tools marketplace either have a proprietary scripting language, or set of configuration files so complex that become mini languages on their own right, and require extensive “product training” to accomplish anything significant. As a result, these tools are often “knowledge islands”. One has to investigate significant time learning them, there are “certification” programs, training classes, etc. and the skills are often not transferable.

We wanted to explicitly avoid this phenomena, hence resisted inventing a new language, or using very complicated configuration files as much as possible, and worked hard at this. As many things in life, this has been harder than we had thought.
Through our journey, we have worked with several different languages and I must admit the urge to come up with our own to meet our specific needs has been strong, but we have managed to resist for the most part :)  read more »

  • 1 trackback
Syndicate content

  • Create new account
  • Request new password