Does anyone know of a way to perform 'Impact Analysis' on the Procedures and Synonyms stored in MRE's domains?

The WF Server Console has a nice tool that does this, but it seems to analyze only the content of the APPS libraries.
[1. Select a DevStudio Environment and DataServer.
[2. Click the 'WebFOCUS Reporting Server Console' button.
[3. Select "Procedures", and open the "Reports->ImpactAnalysis" group in the left sidebar.
[4. Run either 'Synonyms by Procedures' or 'Procedures by Synonyms'.]
With some manual massaging in a text editor, data copy-n-pasted data from the resultant HTML page can be brought into EXCEL and further analyzed to find procedures and synonyms that are used (and by omission, ones that can be deleted).

I need to do the same thing for all the procedures in the set of MRE domains.
We're 'housekeeping' a 10 year old WebFOCUS server that we know must be full of unused stuff.

Any 'How-To' suggestions?

Chris Burtt.

Chris,

Impact Analysis won't tell you whether a focexec is being used or not. For that you would need Resource Analyzer.

Can you do http log scraping? Is there a way you can check the actual fex files on disk to check last accessed date?

I empathize with you. We have the same situation in a self-service world and have over 500 directories. People move on and leave their stuff behind.

Good luck.

I don't really have a solution for you, but if you're okay with it, I'd like to add my complaint. Impact Analysis definitely doesn't do anything with items in MRE. I found several things like this a year or so ago that were nice features that we couldn't use.

Maybe it's time for an NFR to IBI? I can't imagine it would be that difficult to let the impact analysis tool access MRE domains.

GinnyJakes,

I agree that Impact Analysis won't tell me if a Synonym or *.fex is actually used (executed), as Resource Analyzer does. I/A is intended to show which *.fex need a checkout when a Synonym is changed, and vice-versa. But it does help find "orphan" synonyms that have never been, or are no longer, cited in procedures.

I've already developed reports against the BOT* files to list *.fex (selfserv and MRE) associated with RCaster schedules. As I work through "Is this RCaster output actually used by anybody", I can trace back to the *.fex and purge them. Purge enough *.fex and Synonyms become orphans.

Trav,

It may be more difficult than is apparent for IBI to make the I/A tool work on the content of MRE Domains. Remember, selfservice APPS libraries exist as a true OS directory hierarchy, just as your viewing tool (MS/Windows in may case) shows it. The MRE-Domain 'tree' as DevStudio or Browser/Java show it is mostly a 'fake' hierarchial display of a two level OS directory structure. The information needed to draw the 'tree' hierarchy for each domain is recorded in HTML code in the domain's .htm file.

I would expect IBI to implement an MRE A/I tool as an extension of their 'Managed Reporting Extract Utility' that converts MRE content into CSV tables.

CB

WIN/2K running WF 7.6.4
Development via DevStudio 7.6.4, MRE, TextEditor.
Data is Oracle, MS-SQL.

If there aren't too many folders, you can attempt to add the folder via APP MAP pointing to the MR Basedir/SubFolder, and then invoke the IA.

Chris,

I do the following in Unix all the time. Using the operating system command, I 'find' all of the masters and what directories they are in and store that in a file.

I do the same thing with focexecs.

I have a generic master (actually I have several) called LINE80 where there is only one field, LINE80. I then filedef the master list to the this and parse the heck out of it so that I have a list of unique masters.

I do the same sort of thing with the focexecs. Then, using the master list as a source, I loop through and read all the lines of fexes till I get a match, then save.

I have just gone through this process looking for focexecs that are using secure masters.

Boring and ugly. But it works very well.

Let me know if you need any more detail. Or you can contact me. Send me a private post and I'll give you my work email.