Salesforce

PASOE Dynamic Objects Viewer for TTY interfaces

Printable View
« Go Back

Information

 
TitlePASOE Dynamic Objects Viewer for TTY interfaces
URL NamePASOE-Dynamic-Objects-Viewer-for-TTY-interfaces
Article Number000154508
EnvironmentProduct: OpenEdge
Version: 11.7, 12.x
OS: All Supported Platforms
Question/Problem Description
Use the below tool as a guide for how to enable/disable memory leak tracking on pasoe instances and fetch a JSON file containing the leaked objects from a given agent.

 
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
This tool uses the ABLObjects REST API provided by swagger through the OE Manager.  Instructions for setting this up before using this tool are available in the article here: How to enable Swagger for PASOE instance

To use the tool, first remember the following tips:
  • Ensure that the appropriate version of the OpenEdge.Net.pl file is in the PROPATH.
  • The tool checks the PASOE registry to find instances and their port and path information using the $DLC/servers/pasoe/bin/tcman instances command by using OS-COMMAND in the (_progres, prowin) session where it's run. 
If you wish to hard-code instance information the tool stores a comma-separated list of instance names and ports in the cInstanceList and cInstancePorts variables in the main program (pasoeMemoryTracking.p).  Just update the values of these variables manually or get the information in some other way, and don't forget to comment out the following lines of code if you don't want to depend upon the pasoe registry for instances to operate on. 

RUN getInstances ( OUTPUT cInstanceList,
                   OUTPUT cInstancePorts ).
  • Extract getablobjects.tar to a folder on its own
  • To start the tool run _progres -p pasoeMemoryTracking.p
  • The below screen shot shows that the tool is gathering information about the instances on the machine and checking whether any are already tracking ABL ObjectsUser-added image
  • The below screen shot shows that it found three instances, two of which are running and one of which has ABLObjects tracking turned on already.User-added image
  • You can press Y or spacenbar when positioned on a Agent record to turn on tracking.
  • After a time you want to check for memory leaks on a given agent.  To do this, press the Get ABL Objects Report button(below) and this will automatically populate the bottom browse with the leaked objects reported by the agent.
User-added image
  • The interface also allows you to export the objects that were fetched to a json file.  Tab to the File Name field to change the path or file name, then down to the Write Objects to File button.
User-added image
Workaround
Notes
This source code is provided freely and with some comments to describe what it's doing.  If you have questions about how to use this tool or it's not working for you, please do not open a Technical Support case. 

Rather choose "No" below this article, where it asks "Was this article helpful?" and leave your comments.

If you have questions about supported functionality exploited using this tool, feel free to log a Technical Support case for assistance.

All of the code that this demonstration is made up of, and more can be found using the below Progress knowledgebase articles as a start.  These contain links to numerous other how to articles, based on what information you're trying to capture from your PASOE agents.

 How to call into the OEManager's REST API for insight into PASOE?
 How to fetch output from ABLObjects tracking REST API from PASOE?

The GUI version of this is discussed in the below Progress knowledgebase article:
 PASOE Dynamic Objects Viewer
Keyword Phrase
Last Modified Date11/20/2020 6:55 AM
Powered by