What Novus environment is set for my Cobalt module?

mark.maruska

I can't find the Novus.Env property in CMDB Applications but I can retrieve the value from code. Where is it set or defined?

mark.maruska

Go to the attributes for your application and look for an entry like: - ^Macro(Global.Attribute(3)) = ExternalLinks_Website_NOVUS_CLIENT You can lookup the global attribute on the *Global Data* tab, then click the *Global Attributes* link. You will see that it contains a value like *Novus.Env=client*. Links to CMDB for each environemnt can be found on the [Cobalt Support site][1] or on the [Shared Ops site][2]. [1]:
http://tfsnpt.int.thomson.com/sites/cobaltsupport/Lists/Links/CMDB%20GUIs [2]:
http://sharepoint.thomson.com/sites/sharedops/Lists/OpsLinks/AllItems.aspx

Ryan Morlok

This question refers to what Novus environment is being used by a given Cobalt vertical.

Andrew Gerber

Mark's answer is correct, the `Novus.Env` property is usually found in a CMDB macro.

However, in general, if you can't find a given property in CMDB (or in a macro), take a look at the given module's ".properties" files for an entry. If there is not a value for that property in CMDB then the value in the module's "properties" file is used. ---------- What are these properties files, what exactly do they do, and where can they be found? Properties files are text files which contain a set of key/value pairs... They follow Java ".properties" convention: [
http://en.wikipedia.org/wiki/.properties][1] Each module has at least two properties files: one that is deployed with the module, and one that is used for local debugging. The file deployed with the module follows the naming convention `{ModuleName}.properties`. So, Website's property file would be named `Website.properties`. The file used locally follows the convention of `local_{ModuleName}.properties`. The deployed file (`{ModuleName}.properties`) contains a set of default property/value pairs that the module will use if no CMDB value exists for the given property. If we look at Website's file, we see the entry: `Novus.Env=prod`

This means that the `Novus.Env` value of "prod" will be used if there is no `Novus.Env` entry in CMDB. [1]:
http://en.wikipedia.org/wiki/.properties

mtaylor

In general, it is my opinion that you are safer if you actually go out to an instance of the module and see what values are deployed to the actual server. There is nothing like actually seeing the physical value set on the server to be confident you have the right answer. See [this other post][1] for information on how to do that. [1]: http://10.208.104.160/questions/37/how-can-i-review-the-files-that-are-deployed-on-a-particular-cobalt-server