There should be a document on creating your own grammar file on this site, search for ‘grammar’ and look for a ‘document’ type of post.
but i know this doc already. Even had a laugh reading it, because i think it was the first documentation with examples about how not to do it...
The point is. Shouldn't there be a grammar file for BMC products?
Even Microsoft does not tell you:" So, you bought MS Windows and MS Office and you want to use them together? Well, here is the doku. Write the integration yourself. We never thought about using these products together." Come on, seriously?
From your answers i asume:
Are there any prebuild grammar files for the configuration files of BMC products?
Are there any thoughts about how to "best practise" these BMC configuration files?
-- We never thought about that.
1 of 1 people found this helpful
there are not specific pre-built grammar files for bmc products, however many of the bmc products use common config file formats like name=value or ini, which are included in the product. maintaining a catalog of every possible software product customers might use is impossible and why bladelogic provides many grammars that cover a good smattering of products, and provides the ability to create your own grammar files. I've seen products that don't even go that far.
if you can make a good business case for the addition of the grammar files, and what other bmc products should be covered, that can be put infront of product management to make a decision about how to move forward.
to use your example - how integrated was Visio with the rest of the Office suite? It took a few releases before it had the full Office look and feel.
Of course, a grammar file for every product is something no one could achieve, at least no longer than a few moments. That's why i narrowed it down to products from the same BMC company, where all configuration files and products should be known.
A business case, no, but how about a company that wants to Automate installation/changes/decomm via BLSA. And to show how easy it is you show them how to move a AR midtier to another server. And then you run into a config.properties like:
And then you have to tell the customer...? That it is easier to show the move of a non-BMC product, because the config files from BMC are to specific to be automated out of the box? I hope BMC product management will see all BMC products as one product and not everyone only his own little solution.
Visio, yep. You got me there. How many releases will BMC need...
thanks for your time and thoughts.
Don't get me wrong - I agree w/ you that we should have this. But I'm relaying the same questions Product Management asks me when I ask for stuff like this.
I'd see if you can talk to a Product Manager about this, best path is through your Sales rep. If you have a prioritized list of BMC products, I'm sure that will help.