Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 3 Next »

WebScreenshot allows automated capturing of websites into PNG format which are saved into the Station files.  These screenshots can then be exposed via a simple servlet rather than giving access to any part of the station files.  

 

This component requested the Activelogix:webScreenshot license feature to operate

Installation / Usage

After installing the JAR and license file, the WebScreenshot component can be accessed by opening the "webScreenshot" palette.  There are two components within the palette:

  • WebScreenshot - Main application, can be installed anywhere in the station.  Only one WebScreenshot should be installed per station.
  • Screenshot - Allows capturing of one website, must be placed underneath the "WebScreenshot" component.  

All screenshots will be taken and saved into the file:^screenshots folder.  WebScreenshots automatically exposes this folder with a file servlet and screenshots can be accessed with the URL: 

 

http://ip_address/webscreenshots/screenshot_name.png

  • ip_address - The IP address of the server hosting WebScreenshots
  • screenshot-name - The AX nav name given to the child Screenshot component

WebScreenshot 

  • Status - Status of WebScreenshot
  • Fault Cause - Explanation of any error (such as unlicensed)
  • Screenshot* - any number of Screenshot components can be added as children to the WebSCreenshot component

Screenshot

  • Status - Status of this Screenshot component.  Will display "Capturing" when a screenshot is taking place
  • Interval - How often this component will capture a screenshot of the webpage
  • URL - The URL of the website that will be captured
  • Min-Width - The minimum width of the resulting screenshot.  For example, if the requested screenshot is only 400px wide but "Min Width" is set to 600px, the resulting screenshot would be 600px.
  • Delay - How long the website will be allowed to load before captured in milliseconds.

 

Periscope takes 5+ seconds to load depending on the speed of the server. It's best to set the delay to at least 10 seconds (10000 ms). Also, Auto-Login can be used to automate login of specific dashboards without having to expose them publicly. Refer to the Periscope Manual for more information.

 

 

 

  • No labels