No JDBC Activity reported... ever

[BobbyH]

Why would there never be any JDBC Activity reported in the Dashboard.
The JDBC tab in all requests is always "None" and the "Longest JDBC
Request" section is always empty as well.

I've ensured that JDBC logging was enabled but that is apparently not
all that is needed.

We use SQLServer JDBC Driver.

I'm new to FR so I'm sure I'm overlooking something else. Any ideas
appreciated.

[charlie arehart]

Bobby, have you done the critical first step of "wrapping" your DSN? If not,
that would explain your not seeing anything.

You need to either manually (or automatically, using a newly available tool)
configure your CF Admin's DSN so that the DSN is watched by FR. You can
learn how to do it manually (which is pretty easy, about 5 steps) in the
JDBC Wrapper User Guide or Tutorial, both available at:

http://www.fusion-reactor.com/fr/support.cfm#doc

If it's not clear, you don't want to choose the ones labelled 3.0, if you're
running FR 3.01. That's what the (unlabelled) ones in the right column are
for.

As for the automatic approach, the tool to do that is at:

http://www.fusion-reactor.com/community/developers/jdbc_tool.cfm

The changes for the DSN wrapping take effect immediately. No need to restart
CF. I have some blog entries I've done talking more about the JDBC wrapping
feature as well, at:

"What is the FusionReactor datasource monitoring feature? Why would I use
it? Powerful stuff!"
http://www.carehart.org/blog/client/index.cfm/2008/7/22/fusionreactor_dataso
urce_monitoring

"New (free) tool to assist in configuring FusionReactor datasource
monitoring"
http://www.carehart.org/blog/client/index.cfm/2008/11/14/fusionreactor_datas
ource_wrapping_tool

Using FusionReactor's datasource monitoring feature? Here's a tip
http://www.carehart.org/blog/client/index.cfm/2008/7/19/adding_name_to_FR_JD
BC_wrapper

Hope that helps.

/charlie

[BobbyH]

Great info Charlie. Thanks! I'll start reading into the wrapper and
see how it goes.

Thanks again.

On Apr 29, 12:20 pm, "charlie arehart" <charlie_li...@carehart.org>
wrote:

> Bobby, have you done the critical first step of "wrapping" your DSN? If not,
> that would explain your not seeing anything.
>
> You need to either manually (or automatically, using a newly available tool)
> configure your CF Admin's DSN so that the DSN is watched by FR. You can
> learn how to do it manually (which is pretty easy, about 5 steps) in the
> JDBC Wrapper User Guide or Tutorial, both available at:
>
> http://www.fusion-reactor.com/fr/support.cfm#doc
>
> If it's not clear, you don't want to choose the ones labelled 3.0, if you're
> running FR 3.01. That's what the (unlabelled) ones in the right column are
> for.
>
> As for the automatic approach, the tool to do that is at:
>
> http://www.fusion-reactor.com/community/developers/jdbc_tool.cfm
>
> The changes for the DSN wrapping take effect immediately. No need to restart
> CF. I have some blog entries I've done talking more about the JDBC wrapping
> feature as well, at:
>
> "What is the FusionReactor datasource monitoring feature? Why would I use

> it? Powerful stuff!"http://www.carehart.org/blog/client/index.cfm/2008/7/22/fusionreactor...

> urce_monitoring
>
> "New (free) tool to assist in configuring FusionReactor datasource

> monitoring"http://www.carehart.org/blog/client/index.cfm/2008/11/14/fusionreacto...
> ource_wrapping_tool
>
> Using FusionReactor's datasource monitoring feature? Here's a tiphttp://www.carehart.org/blog/client/index.cfm/2008/7/19/adding_name_t...

[Bobby Hartsfield]

Thanks again Charlie. I've successfully "wrapped" a datasource and can now see the activity within the JDBC Activity sections of Fusion Reactor.

I used the manual approach since it can be done completely through the CF Administrator. As you witnessed yesterday during the conference call/Adobe Connect meeting, we have to jump through a few hoops to get physical access to the production servers. Now that I have one of the datasources working though, I will try the automated approach to configure the remaining datasources. There are far too many servers and datasoruces to configure them all manually :-)

Thanks again.

[charlie arehart]

Good to hear. Yep, that’s indeed where the automated tool is so awesome. :-)

 

/charlie

[Bobby Hartsfield]

Indeed. I just wrapped 140 databases in about 10 seconds with the
automated tool :-)

JDBC Activity came to life instantly in the AIR Dashboard.

Great stuff. Thanks again.

[Patrick Sauter]

One thing I found with the automatic wrapper tool is that - at least for our Oracle datasources - the tool causes both the wrapped datasource and the original (unwrapped) one to revert to the default settings of "maintain client connections" checked, and allow clobs and blobs unchecked.  Those are bad things in our environment (especially the maintain client connections part), and, as they're in the "advanced settings," it didn't occur to me to check that (until people stopped being able to log in to our apps).

-Patrick

[charlie arehart]

Ah, very good point, Patrick. In fact, it makes sense for the User Guide to clarify that point when creating the wrapped version manually. Both approaches for now focus on obtaining the current JDBC URL for the old DSN. It’s a very good point that other aspects of the DSN should be propagated to the new one, and in fact the tool would be even better suited to doing this for you. Let’s see if the tool’s author, David Stockton, has any thoughts. He may have wrestled with this when he built it.

 

And can someone involved in the docs speak to whether you could note this as a potential fix for the Wrapper docs?

 

/charlie

[Bobby Hartsfield]

I just double checked that all settings were still correct and it did
indeed keep them all the same. Including. Maintain connections, CLOB,
and BLOB. However, all of the datasources are SQL Server and I
selected the option to "Overwrite existing datasource(s)" where it
sounds like you did not.

Do you still get the same result if you use the option?

[Patrick Sauter]

I just tried it selecting "overwrite existing" and the advanced settings were preserved. So I tried unwrapping it and deselecting that option, and the settings were also preserved.

So, I went back in and created another datasource, then wrapped it with overwrite de-selected, and, much to my surprise, once again the advanced settings were preserved.

That's pretty interesting since I wrapped several datasources with the tool a couple of weeks ago, and had to go back in and change the advanced settings.  I also wrapped another one about a week ago, and also had to re-set the advanced settings. 

So, I'm not quite sure what the deal is, unless I'm going insane (which is always a distinct possibility).  I have witnesses on this one, though.  Honest!

[Bobby Hartsfield]

Do your witnesses happen to be wearing white coats? ;-)