Database Outbound – Connectivity

[Jon Melin]

Hello,

I am just starting to use the Database Configuration piece within Cloverleaf 6.0 and I am having trouble getting a connection made. We’ve set everything up in the Database Configurations tab, entered the URL, are using a SQL Authenticated User, and can ever select the schema we want so I believe the connectivity is there.

Also when I go to the External Database tab, the new connection is selectable and I can choose to turn on/off message tracing and such.

The problem is when I go into NetConfig and try to create an outbound connection using the PROTOCOL: database-outbound – and try to select the new connection from the dropdown, it isn’t there.

I’ve tried cycling and restarting Cloverleaf and that threads. Any thoughts?

Thank you,

Jon

Topic

[Peter Heggie]

When you used the database schema configurator, did you select a table or view, select OK to save it and then use the File / Save to save the updated Table Schema List?

And then when setting up the thread, you picked the PROTOCOL:database-outbound protocol and then in properties the drop-down box for Database Connection had no entries in it when you clicked the down arrow?

Peter Heggie
PeterHeggie@crouse.org

[Jon Melin]

Peter,

Thank you for the response. Yes when I clicked the down arrow there was no database listed in there. Although I remember db_writeaccess and other rights accounts being what was available under schema  (I didn’t see much actual DB structure available), maybe I’ll try creating a view on that database (we are just testing so it’s just a simple test database).

Thank you,

Jon

[Peter Heggie]

well, if you have the database connection defined in the Site Options, and have selected a schema in the Database Schema Configurator, then you should have that connection available in the protocol properties.

If you were able to select/save a schema, then the userid specified on the Site Options has the authority to look at the schema (table/view) definition, and therefore should have access to the table when selected in the database protocol properties.

If you can’t even get the connection displayed in the protocol properties, then there is some other error.

You could try increasing the authority of the userid specified in the connection but I don’t think that is the error here.

Peter Heggie
PeterHeggie@crouse.org

[Jon Melin]

Peter,

It looks like we’ve figured it out. We had to select dbo schema and add all the values in order to get it to work.

I think we have what we need. I appreciate the support.

Thank you,

Jon

[Author]

Replies