Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
ProjectWise
  • Product Communities
ProjectWise
ProjectWise Design Integration Forum Is there a way to determine what ProjectWise Client external users are connecting to a Datasource with?
    • Sign In

    • State Not Answered
    • Replies 4 replies
    • Subscribers 61 subscribers
    • Views 761 views
    • Users 0 members are here

    Is there a way to determine what ProjectWise Client external users are connecting to a Datasource with?

    Tim Knaus
    Offline Tim Knaus over 2 years ago

    Is there a way to determine which PW Client (Web, V8i Web, Explorer) external users are connecting to my Organization's datasource with? Is this contained in a logfile somewhere?

    • Sign in to reply
    • Cancel
    Parents
    • Kevin van Haaren
      0 Offline Kevin van Haaren Fri, Oct 9 2020 2:54 PM

      hmmm. I'm not sure it has all the data you're looking for but if in dmskrnl.log.xml you bump up both the pwise.connection and pwise.dms.login to the info level you will get reports on both the users logging in and the client they are using (and version). I'm not sure what the web clients report. You can tie the login user info with the client connection info together via the thread id in brackets on the log line.

      If you really want to make this data parsable you can push it into it's own log file. Edit the dmskrnl.log.xml, duplicate the RollingFileAppender section, give it a new name and new log file. Then modify the pwise.dms.login and pwise.connection to send their logs to the new appender.

      <appender name="LoginRollingFileAppender" class="org.apache.log4j.RollingFileAppender">
              <param name="File" value="C:\Logs\Logins.log"/> <!-- Required -->
              <param name="MaxFileSize" value="10000000" />                   <!-- Required -->
              <param name="MaxBackupIndex" value="3"/>                       <!-- Required -->
              <param name="CreatePath" value="true"/>                         <!-- Optional -->
              <!-- param name="encoding" value="UTF-16" -->                   <!-- Optional -->
              <layout class="org.apache.log4j.PatternLayout">
                  <param name="ConversionPattern" value="%d{ISO8601} %-5p [%t] %c - %m%n"/>
              </layout>
      </appender>
      
          <!-- Messages related to connections to the server. -->
          <category name="pwise.connection">
      		<priority value="info"/>
      		<appender-ref ref="LoginRollingFileAppender"/>
      	</category>
      
          <category name="pwise.dms.login">
      		<priority value="info"/>
      		<appender-ref ref="LoginRollingFileAppender"/>		
      	</category>
      

       

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    Reply
    • Kevin van Haaren
      0 Offline Kevin van Haaren Fri, Oct 9 2020 2:54 PM

      hmmm. I'm not sure it has all the data you're looking for but if in dmskrnl.log.xml you bump up both the pwise.connection and pwise.dms.login to the info level you will get reports on both the users logging in and the client they are using (and version). I'm not sure what the web clients report. You can tie the login user info with the client connection info together via the thread id in brackets on the log line.

      If you really want to make this data parsable you can push it into it's own log file. Edit the dmskrnl.log.xml, duplicate the RollingFileAppender section, give it a new name and new log file. Then modify the pwise.dms.login and pwise.connection to send their logs to the new appender.

      <appender name="LoginRollingFileAppender" class="org.apache.log4j.RollingFileAppender">
              <param name="File" value="C:\Logs\Logins.log"/> <!-- Required -->
              <param name="MaxFileSize" value="10000000" />                   <!-- Required -->
              <param name="MaxBackupIndex" value="3"/>                       <!-- Required -->
              <param name="CreatePath" value="true"/>                         <!-- Optional -->
              <!-- param name="encoding" value="UTF-16" -->                   <!-- Optional -->
              <layout class="org.apache.log4j.PatternLayout">
                  <param name="ConversionPattern" value="%d{ISO8601} %-5p [%t] %c - %m%n"/>
              </layout>
      </appender>
      
          <!-- Messages related to connections to the server. -->
          <category name="pwise.connection">
      		<priority value="info"/>
      		<appender-ref ref="LoginRollingFileAppender"/>
      	</category>
      
          <category name="pwise.dms.login">
      		<priority value="info"/>
      		<appender-ref ref="LoginRollingFileAppender"/>		
      	</category>
      

       

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    Children
    • Kevin van Haaren
      0 Offline Kevin van Haaren Fri, Oct 9 2020 2:56 PM in reply to Kevin van Haaren

      If you really want to go down a rat hole you can dig into Log4j's pattern layouts and modify the log pattern on your new appender to produce easier to parse log files.

       

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Tim Knaus
      0 Offline Tim Knaus Fri, Oct 9 2020 3:05 PM in reply to Kevin van Haaren

      Thanks Kevin, I will see what I can gather from this.

      • 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