coldfusionJedi

<cfscript>
adminObj = createObject("component","cfide.adminapi.administrator");
adminObj.login("admin");

debugger = createObject("component", "cfide.adminapi.debugging");
logfolder = debugger.getLogProperty("logdirectory");
</cfscript>
<cfoutput>#logfolder#</cfoutput>

This entry was posted on Wednesday, February 11, 2009 at 9:53 PM. It was filed in the following categories: ColdFusion. It has been viewed 1,779 times and has 9 comments.

TweetBacks

Comments

[Add Comment] [Subscribe to Comments]

• Comment 1 written by Brandon Hansen on 11 February 2009, at 11:04 PM

  

  That is pretty awesome. So I am guessing that I could just dump out the adminapi object to find out the other methods...I am really hoping that their is some sort of datasource method. That would be awesome.

• Comment 2 written by Brandon Hansen on 11 February 2009, at 11:13 PM

  

  Although I didn't see the dsn method, I did like looking through all of the methods. That was fun.
  
  I did find this article just now though, not sure how old it is-
  http://svn.riaforge.org/cfadminwsapi/test.cfm

• Comment 3 written by Brandon Hansen on 11 February 2009, at 11:18 PM

  

  So this is where the magic happens-
  <cfset admin_object = createObject("component","cfide.adminapi.datasource")>
  <cfdump var="#admin_object#">

• Comment 4 written by Raymond Camden on 12 February 2009, at 6:04 AM

  

  I wouldn't dump the CFCs. Just visit them in your browser.
  
  http://www.yourserver.com/cfide/adminapi/XXXXX.cfc...
  
  Where XXXX is the name of the CFC. You will get a nicely documented HTML page.

• Comment 5 written by JC on 12 February 2009, at 1:38 PM

  

  You don't need the adminapi for datasources.
  
  <cfset sf = CreateObject("java", "coldfusion.server.ServiceFactory")>
  <cfdump var="#sf.DataSourceService.getDatasources()#" expand="true">
  
  Or if you want something a bit more readable than cfdump, add this:
  
  <cfoutput>Server,Instance,DSN,Database,Host,Username,Select,Insert,Update,Delete,Proc,Create,Drop,Grant,Revoke,Alter<br>
  <cfloop list="#StructKeyList(foo)#" index="i">
  #host#,#cfserv#,#foo[i].name#,#foo[i].urlmap.database#,#foo[i].urlmap.host#,#foo[i].username#,
  <cfif #foo[i].select# IS "YES">Select </cfif>,
  <cfif #foo[i].insert# IS "YES">Insert </cfif>,
  <cfif #foo[i].update# IS "YES">update </cfif>,
  <cfif #foo[i].delete# IS "YES">delete </cfif>,
  <cfif #foo[i].storedproc# IS "YES">storedproc </cfif>,
  <cfif #foo[i].create# IS "YES">create </cfif>,
  <cfif #foo[i].drop# IS "YES">drop </cfif>,
  <cfif #foo[i].grant# IS "YES">grant </cfif>,
  <cfif #foo[i].revoke# IS "YES">revoke </cfif>,
  <cfif #foo[i].alter# IS "YES">alter </cfif><br>
  </cfloop>
  </cfoutput>
  
  And you can get even more db info if you want it. the cfdbinfo tag has lots... here's a script I wrote a while back that basically crawls and dumps out everything the specified data source has access to.
  http://yougiveloveabad.name/wp-content/uploads/dbi...

• Comment 6 written by Raymond Camden on 12 February 2009, at 1:42 PM

  

  The AdminAPI CFCs probably use the same serviceFactory. But - I would not recommend you use the serviceFactory like that in production. Yes it works now, but you are not guaranteed it will work in the future, whereas the AdminAPI is the _documented_ way to use these features.

• Comment 7 written by JC on 12 February 2009, at 2:09 PM

  

  well, I don't think I'd recommend using any of it in production. I assumed Brandon was asking out of either curiosity or a need to dump the info out for auditors or something.

• Comment 8 written by Raymond Camden on 12 February 2009, at 2:12 PM

  

  I think it would be fair/ok to use the Admin API in production.

• Comment 9 written by Gareth on 13 November 2009, at 12:04 PM

  

  I'm trying to build a custom log file viewer and found this post. I had this exact question, so thanks for answering it Ray!
  
  It's a pity you need to enter the admin password to get the log file location, but I suppose there are security reasons.
  
  For my own security paranoia, I don't want to put my server's password into my code. Likewise, I don't want to give it to the people using my log file viewer for them to enter via a form.
  
  In an ideal world, CFLOG would be able to specify the log file's location. As that's not possible, I think I'll need to build my own custom logger.

[Add Comment] [Subscribe to Comments]