Domiclipse

1 - Un-freaking-believable. I'm gobsmacked.

2 - Wow.

What\ how are you determining what is a "connection" between databases?

3 - Anaxi is basically a three step process which to some extent is customised/tailored to the clients environment.

1. I export the design (and profile documents etc) of all the databases as dxl and store them in a full-text indexed Notes Database. This database on its own is very useful for finding agents when you know the name but have forgotten which database it's in etc

In my clients environment this is about 130,000 design elements. The first time I extract all the dxl it takes about 5 hours but subsequent runs take minutes because it only looks at design elements which have changed.

2. I run an agent against all the dxl which does a set of regular expression searches through all 130,000 design elements looking for matches which indicate a connection from one database to another. This is the 'tricky' bit and the bit that probably need more refinement. The output of the agent is a bunch of Notes DatabaseConnection documents, each one of which indicates a source/target db/design element etc

Luckily the clients environment has a few policies in place which make the analysis somewhat simpler than a general case analysis would be.

3. The Anaxi plug-in visualises the view of DatabaseConnection documents.

The beauty of doing it this way is that the visualisation is independent of the analysis. So, for example, one could manually create documents in step two or generate them via some other mechanism. So long as the correct type of Notes Document are created then Anaxi will be able to visualise them. It's also useful to be able to manually create DatabaseConnection documents for cases where one knows that it's impossible to programatically determine a connection. For example, if you had some obscure Lotusscript which constructs a database path by combining Country and day of the week i.e. gb/wed/orders.nsf, gb/thu/orders.nsf, us/wed/orders.nsf etc then one could manually create the necessary DatabaseConnection documents and Anaxi would still visualise them.

Since I wrote the last post I've added a bunch of filters to the graph so it's possible to see *only* the databases connected to the source database. In addition one can filter in/out source/target connections and 'freeze' the graph. These filters make it much easier to use the graph without getting to overwhelmed.

Hope that helps. Let me know if you have any more questions.

4 - Its a wonderful tool. Will this be able to identify interfaces with other technologies like oracle connections or web service calls ..

Can you post the link to code?

5 - It seems that you were quicker. I started same project { Link } not knowing about your effort. You have more features implemented and you are even paid for that. This is not my case so maybe I'll stop my project. Best of luck.