Not sure I understand the question, John. Are you referring to the processes.log files? And do you mean configuration items in a CMDB, or context items?
In Dev Studio a process in a module could reference a configuration item in it's module or in another module. How can I take a module or a single process in the and determine all the configuration items that the process or processes in the module reference.
If I look at the PDL I see configuration items referenced as <configuration>, other than lookng at every single PDL for each process, I would like to be able to "search" "grep" all the processes and find those references.
The customer I am working for would like to migrate all the configuration items to a single configuration module that will have configurations for their Production, QA, Dev, and Beta environments. so that every process that references configuration items can pass an environment string and get back the configuration items that are for their environment.
Hope that makes sense.
If you export the module as a ROAR file, you can unzip it (depending on your archiving tool, you may need to change the file extension to .zip).
The process XML files are then available to you in an unencoded form and can be manipulated as desired. To see a great example of what you can do with this, check out the AO-Lint tool.
Thank you, exactly what I needed.
Any chance to get it directly from the running server? I mean the currently active module? under BAO_HOME/server/grids/<GRIDNAME>/library
I am thinking about the possibility of being able to direct see the current running configuration of each module (while active), just to be able to monitor the configuration parameters that are active in the grid
Thanks and Regards
Hi Javier. You can, though you reduce the level of security on your server by doing so. Modules deployed on your peers are encrypted by default, so you'll need to disable that first. You should then be able to extract the files of interest via Zip directly.
Also, don't forget that you can view the module configuration context items directly in Grid Manager just by clicking on the module name in the modules tab.