Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
ProjectWise
  • Product Communities
ProjectWise
ProjectWise Design Integration Forum Viewing caching server folders
    • Sign In

    • State Not Answered
    • Replies 7 replies
    • Subscribers 61 subscribers
    • Views 1480 views
    • Users 0 members are here
    • Fetch files

    Viewing caching server folders

    Luc Poulin
    Offline Luc Poulin over 4 years ago

    I have a weird things, but I'm sure it has a logical and simple explanation

    I was fetching file o my caching server to pre-populate files

    The size limit is at 500000, which should be enough

    When I look at the folders location on the caching server, I only see 63 folders but was expecting to see like few hundred's

    did I miss something?

    All 63 folder were create when I test my setup using the client ( copy out or check-out)

    I have tries different combination of argument for the fetchfiles command. As an example, not seeing the folder is try Integration server:Datasource and try as well caching server:Datasource

    I also notice I have to " " my path

    Here one result I see in the command prompt

    17:44:22,258 INFO  [0x00003ab4] fetchfiles - Fetching project 8394, document 1, document name '660373-1APC-005-4UDM.dwg'

    I cannot find the folder 8394

    I also have this message in one on my trial

    18:56:32,409 INFO  [0x000007a8] fetchfiles - fetchfiles starting
    18:56:34,130 INFO  [0x000007a8] fetchfiles - Fetching project 348, document 2, document name 'Create additional subfolders named per this document as needed.pdf'
    18:56:35,763 INFO  [0x000007a8] fetchfiles - fetchfiles complete, 1 file(s) fetched.

    Cannot see folder 348

    • Sign in to reply
    • Cancel
    Parents
    • Kevin van Haaren
      0 Offline Kevin van Haaren Sat, Jul 13 2019 11:32 PM

      Are you running fetchfiles on the cache server itself? If so, is the cache server configured to cache requests that originate from itself?

      Do a pwping from the computer you're running fetchfiles on of the storage area server. If it doesn't show the cache server as a hop then fetchfiles won't cache on that server.

       

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Luc Poulin
      0 Offline Luc Poulin Sun, Jul 14 2019 1:05 PM in reply to Kevin van Haaren

      Yes the fetchfiles is run from the caching server and using the integration server name.

      running Pwping on the caching server give this result: XXXX= caching server name

      +>pwping -c XXXXX
      pwping: INFO  - Tracing route to host 'XXXX'
      pwping: INFO  - Hop: 1  Host: XXXX  Address: XXXX IP address  PW Version: 10.00.03.140 AvgTime: <1ms  AvgTtl: 128
      pwping: INFO  -     Caching enabled on host 'XXXX' : Cache Path: 'D:\PWCacheRoot\files'   Cache Limit 500000 MB

      The same pwping run form the integration

      +>pwping -c XXXX
      pwping: INFO  - Tracing route to host 'XXXX'
      pwping: INFO  - Hop: 1  Host: XXXX  Address: XXXX IP address  PW Version: 10.00.03.140 AvgTime: 62ms  AvgTtl: 247
      pwping: INFO  -     Caching enabled on host 'XXXX' : Cache Path: 'D:\PWCacheRoot\files'   Cache Limit 500000 MB

      «...If so, is the cache server configured to cache requests that originate from itself?...»

      That is assume should have been configure by my IT who deploy the Caching serve, I had limited access for this step, but I can take a look at the DMSkernel config

      This section should be some interest.

      «....

      ; -----------------------------------------------------------
      ; Section provides caching configuration
      ; -----------------------------------------------------------

      ; Storage server filter.  Only those storage hosts matching these hostnames or IPs will be cached. Leave
      ; this setting commented out to cache all servers.
      ;
      ;servers = myHostName, 192.168.99.23, myHost2

      servers = Integration server name, IP of integration, ( should I add additional entry here)

      ......»

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Kevin van Haaren
      0 Offline Kevin van Haaren Sun, Jul 14 2019 7:20 PM in reply to Luc Poulin

      I assume XXXX is your cache server. If so, this isn't the correct test. You need to pwping the server that the storage area is on, not the local server.

      STORE => Server the storage area is on
      CACHE => Cache server I'm logged into
      
      === Test One ===
      >pwping STORE
      pwping: INFO  - Tracing route to host 'STORE'
      pwping: INFO  - Hop: 1  Host: STORE  Address: aaa.aaa.aaa.aaa  PW Version: 10.00.03.140 AvgTime: 21ms  AvgTtl: 123
      
      === Test Two ===
      >pwping STORE
      pwping: INFO  - Tracing route to host 'STORE'
      pwping: INFO  - Hop: 1  Host: CACHE  Address: xxx.xxx.xxx.xxx  PW Version: 10.00.03.140 AvgTime: <1ms  AvgTtl: 128
      pwping: INFO  - Hop: 2  Host: STORE  Address: aaa.aaa.aaa.aaa  PW Version: 10.00.03.140 AvgTime: 24ms  AvgTtl: 123
      

      Test one is what I believe you'll see. Test Two is what you want.

      If you run fetchfiles from where you ran your PW Explorer test it will most likely work properly. If you must run fetchfiles from the server itself, you're most likely haven't configured your Network Control Panel and the server doesn't know to cache traffic originating from itself.

      Below is a suggestion that works on our network, with our dmsknrl.cfg on cache servers. No guarantee's it'll work for you.

      ProjectWise Control Panel (on the CACHE server), add to both DNS and Datasource Listing tabs:

      • Name: Cache
      • Host: cache server host name
      • Port: whatever port you use for PW. Probably 5800

      In DMSKRNL.CFG:

      Find the [Gateway] section, add an entry for each storage server you're caching:

      • STORE1 = cache server host name
      • STORE2 = cache server host name
      • etc...

      Restart the service and try your pwping (of the storage area) now.

      I don't think the problem is in your [Cache] section settings. We don't set server names in the servers = entry because we want to cache everything, which is the default. Here's our cache section:

      [cache]
      enabled=true
      storagepath=<PATH TO STORE CACHE FILES>
      ; limit is in megabytes.
      ;  20480 =>  20 GB
      ;  40960 =>  40 GB
      ;  46080 =>  45 GB
      ;  61440 =>  60 GB
      ;  98304 =>  96 GB
      ; 102400 => 100 GB
      limit=102400
      ; max # of files purged per pass, default 1000
      purgebatchsize=2000
      

       

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Luc Poulin
      0 Offline Luc Poulin Mon, Jul 15 2019 1:50 PM in reply to Kevin van Haaren

      Hi Kevin

      I think i'm almost there

       [Gateway]

      I only configure one integration server, as we have one store at the moment

      (integration server name) = (Caching server name)

      the pwing from the caching server now give me this

      +>pwping (Integration server name)
      pwping: INFO  - Tracing route to host '(Integration server name)'
      pwping: INFO  - Hop: 1  Host: (Caching server name)  Address: (IP caching server)  PW Version: 10.00.03.140 AvgTime: <1ms  AvgTtl: 128
      pwping: ERROR - Failed to ping host '(integration server name)': no route to next hop

      Seem I miss one portion of the route between the cache (hop1) and the integration ( hop2)

      Under the [Routing] section IT configure

      (integration server name) =  5800

      Based on the instruction I read I've try this entry

      (integration server name) = 5800,(caching server name)

      But did not have any luck, so revert back to  (integration server name) =  5800

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Kevin van Haaren
      0 Offline Kevin van Haaren Mon, Jul 15 2019 3:47 PM in reply to Luc Poulin

      Try what i list below, i'm assuming a bunch is already mostly what you have.

      CLIENT <===> CACHE <===> INTEGRATION
      
      Client
      ===
      ProjectWise Network Control panel:
      	DNS, Datasources list: INTEGRATION
      
      Integration
      ===
      [Gateway]
      INTEGRATION = CACHE
      
      CACHE
      ===
      ProjectWise Network Control panel:
      	DNS, Datasource list: CACHE
      
      [Gateway]
      INTEGRATION = CACHE
      
      [Routing]
      INTEGRATATION = 5800
      

       

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    Reply
    • Kevin van Haaren
      0 Offline Kevin van Haaren Mon, Jul 15 2019 3:47 PM in reply to Luc Poulin

      Try what i list below, i'm assuming a bunch is already mostly what you have.

      CLIENT <===> CACHE <===> INTEGRATION
      
      Client
      ===
      ProjectWise Network Control panel:
      	DNS, Datasources list: INTEGRATION
      
      Integration
      ===
      [Gateway]
      INTEGRATION = CACHE
      
      CACHE
      ===
      ProjectWise Network Control panel:
      	DNS, Datasource list: CACHE
      
      [Gateway]
      INTEGRATION = CACHE
      
      [Routing]
      INTEGRATATION = 5800
      

       

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    Children
    • Kevin van Haaren
      0 Offline Kevin van Haaren Mon, Jul 15 2019 3:56 PM in reply to Kevin van Haaren

      The [Gateway] of a SERVER tells any computer that is configured to connect to that via the network control panel which CACHE server it must contact to start it's communication.

      The [Routing] section of the CACHE server tells the CACHE server what the next computer in line is to reach the destination. In this manner you can route traffic from server to server to server until it finally reaches the destination.

      So the [Gateway] section of the integration server tells the CLIENT that to connect to INTEGRATION it should contact CACHE

      The [Gateway] section of the CACHE server tells the CACHE server to use itself as the gateway entry to the network. (because the cache server PNC is pointed at itself)

      The [Routing] section of CACHE tells the CACHE server to talk directly to Integration on port 5800

       

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Luc Poulin
      0 Offline Luc Poulin Fri, Jul 19 2019 5:42 PM in reply to Kevin van Haaren

      Hi Kevin just wanted to let you know I manage to get the fetch working

      create a task and it seems to work fine... thank you

      • 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