We have webFOCUS Dev, Test and Prod environments. On occasio...

[Debra Waybright]

That is a universal conundrum, isnt it Im looking forward to our next upgrade hoping to clear out all the unused junk. But how to keep up with it on a day-to-day basis

I think having a process in place is a good way to stay on top of it, when a resource or group of resources is retired, the list is passed along to the person responsible for removing them from the next environment. The difficulty is in establishing and enforcing new processes.

You could probably also dump a list of resources for each environment into a list and do a compare so you know what needs cleaned up.

If you are looking for something automated, Im afraid I dont have that answer.

Good luck!

[Jeremy Sturgill]

We have webFOCUS Dev, Test and Prod environments.

On occasion - we retire a *.fex or *.htm from dev - and delete it from Dev.

The Change Management, as far as I can tell, does not clean up Test and prod - if we delete a resource from Dev.

Is there some standard way to address leftover resources in Prod - that are no longer in Dev

We could Nuke all prod resource - the re-migrate all of our Change Management packages. But this feels kind of extreme. Im hoping theres a smarter way to deal wit these leftovers.

[Franciscus van Dortmont]

The resource delete action is logged in audit.log. You could use this log to replicate deletes to another environment. Not sure how far the source control integration is in 8207.22, but you could also use GIT for changemanagement.

[Jeremy Sturgill]

Ty. We tried GIT but ran into errors. We didnt think it was quite ready for prime time. We opted for TFS - which doesnt seem as sophisticated. I will look at the log and see we can leverage that.

[Jeremy Sturgill]

Ty. We have tentative plans to dump prod - and Dev resources - and look for discrepancies. Should be reasonably trivial to generate a report of resources in prod - that are not in dev.

This will be our plan of attack if we dont find some other option.