Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
ProjectWise
  • Product Communities
ProjectWise
ProjectWise Design Integration Forum ProjectWise Integration Server Gateway Section - dmskrnl.cfg
    • Sign In

    • State Verified Answer
    • Replies 4 replies
    • Subscribers 61 subscribers
    • Views 686 views
    • Users 0 members are here

    ProjectWise Integration Server Gateway Section - dmskrnl.cfg

    Vivek Baraiya
    Offline Vivek Baraiya over 1 year ago

    HI ,

    I am trying to configure caching sever to remote location and looking at the example given by Bentley,

    The part which is not clear is gateway section,

    For example if there are 200+ users in integration server and I just need 8-10 users to be configured to access caching sever first before reaching out to integration sever,

    Do I have to list all the users under PCS and INTSEVER section ?? , I found it is NOT practical to list all of users,

    Can I just write INTSERVER part with 8-10 users ?? [omitting PCS part which has 200+ users to list] ??,

    Ideally i would like to see if these segregation can be done by PC NAME which give dynamic flexibility of whoever login to that machine or IP address but again with dynamic IP it would be a challenge.

    • Sign in to reply
    • Cancel

    Top Replies

    • Kevin van Haaren
      Offline Kevin van Haaren Tue, Apr 19 2022 12:04 PM in reply to Vivek Baraiya +1 verified
      I assumed your setup would have separate Integration and Storage servers in your first office, that would mean clients in Office 2 would need a Gateway statement for each server. Since you aren't doing…
    Parents
    • Kevin van Haaren
      0 Offline Kevin van Haaren Thu, Apr 14 2022 9:41 AM

      I think you are mis-reading this (and on reviewing it, i think it needs a lot of clarification added to it). The Allow/Deny statements in the dmskrnl.cfg only works with IP addresses or computer names, not usernames. And it works with blocks of IP addresses.

      Say you have 2 offices each with a cache server and then one storage area for the company and one gateway server that everybody will use to get their configuration system.

      Integration server is named Int1

      Storage server is named Storage1

      OfficeA is at 10.1.1.1-254 with Cache server named CacheA

      OfficeB is at 10.2.2.1-254 with Cache server named CacheB

      your one Gateway's [Gateway] would look like:

      [Gateway]
      # OfficeA
      Int1=CacheA[Allow(10.1.1.*)]
      Storage1=CacheA[Allow(10.1.1.*)]
      
      #OfficeB
      Int1=CacheB[Allow(10.2.2.*)]
      Storage1=CacheB[Allow(10.2.2.*)]
      

      (You can use IP CIDR notation instead of wildcards, so 10.1.1.0/24 or 10.2.2.0/24 also works)

      You can use Computer names to specify individual computers, but i do not believe wildcards work in computernames. I typically only use this on my dev setup where i want to test different routes from different computers.

       

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Vivek Baraiya
      0 Offline Vivek Baraiya Mon, Apr 18 2022 4:45 PM in reply to Kevin van Haaren

      Thanks a lot Kevin this really help,

      I do have few follow up questions, our setup would look like exactly same as shown in PW Admin help example and different to your example

      i.e. we would like to set integration sever as storage +caching AND caching server as storage +caching , so we have two storage location instead of one.

      So if I Can use ip addresses with wild card thing are much easier, but do you think I have to use following code in gateway section to divert each set of user ip [or PC name ] to specific sever,



      [Gateway]
      PCS=INTSERVER[Allow[Allow(10.1.1.*)]]
      INTSERVER=CacheA[Allow(10.2.2.*)]
      
      
      [Routing]
      PCS=5800

      I did not get purpose for this line in the code Storage1=CacheA[Allow(10.1.1.*)] 

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Kevin van Haaren
      +1 Offline Kevin van Haaren Tue, Apr 19 2022 12:04 PM in reply to Vivek Baraiya

      I assumed your setup would have separate Integration and Storage servers in your first office, that would mean clients in Office 2 would need a Gateway statement for each server. Since you aren't doing this you can drop that line and just have a line for INTSERVER and PCS. So replace the INTSERVER=CacheA line with:

      INTSERVER=PCS[ALLOW(10.2.2.*)]

      Note that the [Routing] on INTSERVER should only be:

      • [Routing]
      • PCS=5800

      and the [Routing] on PCS should only be:

      • [Routing]
      • INTSERVER=5800

       

      Answer Verified By: Vivek Baraiya 

      • Cancel
      • Vote Up +1 Vote Down
      • Sign in to reply
      • Reject Answer
      • Cancel
    Reply
    • Kevin van Haaren
      +1 Offline Kevin van Haaren Tue, Apr 19 2022 12:04 PM in reply to Vivek Baraiya

      I assumed your setup would have separate Integration and Storage servers in your first office, that would mean clients in Office 2 would need a Gateway statement for each server. Since you aren't doing this you can drop that line and just have a line for INTSERVER and PCS. So replace the INTSERVER=CacheA line with:

      INTSERVER=PCS[ALLOW(10.2.2.*)]

      Note that the [Routing] on INTSERVER should only be:

      • [Routing]
      • PCS=5800

      and the [Routing] on PCS should only be:

      • [Routing]
      • INTSERVER=5800

       

      Answer Verified By: Vivek Baraiya 

      • Cancel
      • Vote Up +1 Vote Down
      • Sign in to reply
      • Reject Answer
      • Cancel
    Children
    • Vivek Baraiya
      0 Offline Vivek Baraiya Tue, Apr 19 2022 3:11 PM in reply to Kevin van Haaren

      Thanks a lot Kevin...

      Really appreciate your help Slight smile

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • 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