Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
ProjectWise
  • Product Communities
ProjectWise
ProjectWise Design Integration Forum Hiding one datasource from PW Web
    • Sign In

    • Replies 6 replies
    • Subscribers 59 subscribers
    • Views 5542 views
    • Users 0 members are here

    Hiding one datasource from PW Web

    mpalicki
    mpalicki over 14 years ago
    I have several datasources running off the same integration server. For users working with PW Explorer, the default of letting all of them be displayed is fine. But for users accessing PW from the Web client, there are specific datasources I would not like displayed when the user connects to our ProjectWise Web. Can I selectively hide specific datasources to Web users only? Thanks
    • Sign in to reply
    • Cancel
    • Michael McCarty
      Michael McCarty Tue, Apr 7 2009 8:10 PM

      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
      
       
      

       



      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Cancel
    • mpalicki
      mpalicki Tue, Apr 7 2009 8:34 PM in reply to Michael McCarty

      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? 

       

       

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Cancel
    • Gary Cochrane
      Offline Gary Cochrane Tue, Apr 7 2009 8:53 PM in reply to mpalicki

      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

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Cancel
    • mpalicki
      mpalicki Tue, Apr 7 2009 10:06 PM in reply to Gary Cochrane
      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?
      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Cancel
    • Gary Cochrane
      Offline Gary Cochrane Tue, Apr 7 2009 11:25 PM in reply to mpalicki

      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

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Cancel
    >

    Communities
    • Home
    • Getting Started
    • Community Central
    • Products
    • Support
    • Secure File Upload
    • Feedback
    Support and Services
    • Home
    • Product Support
    • Downloads
    • Subscription Services Portal
    Training and Learning
    • Home
    • About Bentley Institute
    • My Learning History
    • Reference Books
    Social Media
    •    LinkedIn
    •    Facebook
    •    Twitter
    •    YouTube
    •    RSS Feed
    •    Email

    © 2023 Bentley Systems, Incorporated  |  Contact Us  |  Privacy |  Terms of Use  |  Cookies