Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Accessing an external oracle databaseAccessing an external oracle database
Previous
 
Next
New Post
9/1/2008 6:23 AM
 

Hi all,

I'm currently trying to figure out how I access an external database (on a different server) from a module so that it can display products in a list.

Not really sure where to start on this, I tried googling my way to some sort of guide but everything says to edit web.config and add connection strings. thing is every time i do that i get an error: Parser Error Message: Unrecognized attribute 'type'. Note that attribute names are case-sensitive. Basically it comes up with this error in every guide and tutorial I've followed.

Do i need to create a custom data provider?  Ideally i'd like to know the best/easiest/secure way to solve this. Thanks

Si

 
New Post
9/1/2008 8:14 AM
 

you only need to use the web.config connection string if you want to use the DNN dataprovider structure. Please remember that DotNetNuke is just .NET, so you can use any alternative way to connect to data (just as you would in a regular asp.net application)


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
9/1/2008 11:36 AM
 

Can you provide some more information (example) of where and what you're trying to put in your web.cofig? You can of course cross out/change the username/password...
Sanjay

 


AcuitiDP - Oracle Data Provider for DotNetNuke
 
New Post
9/2/2008 7:40 AM
 

Hi, To be honest i've not thought about this all week.  I gave up with the webconfig connection strings as it never seemed to work.  I realise i could just connect in another way but I wanted an ellegant solution which worked well with DNN.

Ok details, i deleted changes i made to web.config so its now as it was when i first installed dnn.  The database I am trying to connect to is on another server running oracle. 

What would you suggest is the easiest way to do this?  I don't think I'll have access to stored procedures or anything in the oracle databases as its used in a warehouse and i'm only allowed to read info off it for the moment so i dont end up accidentally dropping our customer table or something equally stupid.

Si

 
New Post
9/2/2008 11:00 AM
 

Si - well for starters you have to make sure you have the oracle client installed on the web server. Yes, oracle uses the native system.data classes that come with .NET, but they still require the neccesary Oracle client installed.
With regards to accidentally dropping tables, etc, I'd not be that worried. If your DBA has given you a user id/password to the system, it probably is read only in any case so that things like this wouldn't happen :)...
Once you have oracle client installed, setup the entry to point to your remote oracle server (TNS NAMES) and then use this as your value in the connection string. You can place your connection string in web.config and then use your modules to connect to Oracle. DNN already exposes ways of getting a section of web.config so you shouldn't have to do anything out of the box in order to pull your new connection string.

Sanjay


AcuitiDP - Oracle Data Provider for DotNetNuke
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Accessing an external oracle databaseAccessing an external oracle database


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out