Hiding one datasource from PW Web

Re: Hiding one datasource from PW Web

mpalicki — Wed, 08 Apr 2009 16:46:35 GMT

Bingo! - That did it. Thanks Gary. I've never paid attention to the dropdown list on that security tab. I never thought to look any farther than where it shows "Client Connections".

Re: Hiding one datasource from PW Web

Gary Cochrane — Wed, 08 Apr 2009 03:25:07 GMT

Hi Matt,

In a nutshell, yes, however I would encourage you to use the PW Administrator to make the change(s), rather than just editing the DMSKRNL.CFG file manually. That will help you get the syntax right.

To do so, right-click the datasource name in PW Admin, and open the datasource Properties dialog. Then change to the Security tab. Note that there are two options; Client connections, and Datasource list publishing. You'll want to set it to Datasource list publishing.

Once you do, then add your deny condition for this datasource, using the web server's IP address. If you then review the datasource section in the DMSKRNL.CFG file, you will see that the requried syntax is (that was added for you):

DsListDeny=

rather than just Deny=, which is for the first option; client connections.

Hope this helps,

Gary

Re: Hiding one datasource from PW Web

mpalicki — Wed, 08 Apr 2009 02:06:07 GMT

Hmm...so if I just put in a deny statement with the full IP address of the Web Server, that should do it in theory, right?

Re: Hiding one datasource from PW Web

Gary Cochrane — Wed, 08 Apr 2009 00:53:21 GMT

My understanding of this feature is that it disables the datasource from being advertised to PW Explorer clients only, not Web clients.

Remember though that when the Web Server starts up, it will get a list of datasources from the Integration Server, just as if it were a PW Explorer starting up. So if you have allow/deny statements in place, then those datasource (that are denied) would not show up in the Web Server pages (as seen by browsers) at all. And that would be for all clients, not on a per-client basis.

Again, the allow/deny statements are applied when clients start up, and the web server acts like a client when the service is started. Only difference is, the web server runs indefinitely (as opposed to PW Explorere clients), and so therefore does not get a new datasource list often.

At least that's my take on it,

Gary

Re: Hiding one datasource from PW Web

mpalicki — Wed, 08 Apr 2009 00:34:40 GMT

Thanks Mike,

So if I took your example and used something like:

Allow=192.168.*.*
Deny=*.*.*.*

would the net effect be that it would allow everything from the 192.168 network, and Deny everything else?

Re: Hiding one datasource from PW Web

Michael McCarty — Wed, 08 Apr 2009 00:10:53 GMT

You can use "Allow" and "Deny" statements under each datasource configuation section (e.g. "[db0]") to control the visibility of the datasource to specific clients and/or subnets.

[db0]
Description=myds
InterfaceType=ODBC
Name=myds
Type=Oracle
DBUserName=dbuser
DBUserPassword=asdkfjasdklfj
DBUsrPwdDecrypt=2
Allow=192.168.*.*
Deny=10.10.*.*

HTH

Mike