Getting Started
      Back to home
      1. ProTop Knowledge Base
      2. Getting Started

      ProTop Tweaks Required to Run Under OpenEdge 11.1

      OE 11.1 is still used in some vendor packages. ProTop runs under this version, but OE11.1 has limitations. Make the following adjustments for a smooth ProTop install and configuration.

      NOTES:

      • Not all of the ProTop's advanced features will work under OE 11.1.
      • This workaround requires either the use of a 4GL DEV license or running the ProTop processes with the -rx startup parameter with a client networking license.
      • OE11.1 cannot run secure comms (HTTPS over port 443) with the ProTop Portal; it's very old security libraries do not work with modern (minimum) SSL/TLS ciphers and protocols in use on the ProTop Portal. This OE11.1 install can only communicate with the portal using HTTP.
      • This workaround requires a replacement for $PROTOP/lib/osgetwinsize.p if you are running a version of ProTop before Version 327. Please send a message to support@wss.com and we will send you the replacement right away.

      Steps to use OE11.1 with ProTop:

      1. Start a shell using proenv.
      2. Download and install ProTop as per the install guide. Take it as far as you can, you may be blocked/hung at some point. We just need to files to be expanded and localized.
      3. Once installed, move or rename the version 11 specific procedure library out of ProTop's PROPATH. i.e. mv $PROTOP/protop-v11.pl $PROTOP/protop-v11.pl-orig
      4. cd $PROTOP/ptdefs
      5. Copy protop.json to protop.json-[date] as a backup.
      6. Edit protop.json and remove the lines that contain PASOE and Service Telemetry.
      7. cd $PROTOP/bin
      8. cp localenv.x localenv
      9. Edit localenv and find the line containing MINWAIT.
      10. Make a copy of that line and comment it out as a backup.
      11. Change MINWAIT=0.1 to MINWAIT=1 and save the file.
      12. If you do not have a 4GL-DEV license available on this server:
        1. cd $PROTOP/etc
        2. Create a file named for your site and ending .pf, e.g. acmemfg.pf.
        3. Edit your [site].pf and add one line containing: -rx
        4. Save and close the file.
      13. Close your current shell, open a new one, and run $PROTOP/protopenv to set your ProTop environment variables.
      14. Re-run pt3inst - this should work without hanging now.
      15. Test ProTop RT against one of your resources to verify that it works as expected:
        protop myDb.
      16. Proceed with your Advanced ProTop Configuration.


      If you have any issues, please don't hesitate to contact us using the options on this page.