Install the OpenEdge Memory Profiler tool
- Last Updated: January 5, 2026
- 2 minute read
- OpenEdge
- Version 12.8
- Documentation
Installing the OpenEdge Memory Profiler tool is a straightforward process with minimal
configuration. The installation script handles the setup of the PAS for OpenEdge
instance, embedded database, and supporting files. Here are the step-by-step
installation instructions:
- Launch a Proenv session to ensure the
<DLC>and<WRKDIR>environment variables are correctly set. -
Navigate to the
<oemp-install-dir>folder, where you extracted the contents of theoemp-<version>.zipfile. This folder should contain anoempdirectory. -
To view usage instructions, along with the OpenEdge version, application version, and configurable properties such as ports, run the
oempscript without arguments from the<oemp-install-dir>directory:- On Windows:
oemp\bin\oemp.bat - On Linux:
oemp/bin/oemp.sh
For a quick reference, the following table lists the operation shortcuts to manage the PAS for OpenEdge instance:Table 1. Operation shortcuts Command Description oemp helpDisplays the usage instructions for the oemputility.oemp installCreates: - A new PAS for OpenEdge instance named
oempby default.Note: You can override the name of the PAS for OpenEdge instance during installation by setting theinstanceproperty. - The
reportdbdatabase.
oemp deleteDeletes the oempPAS for OpenEdge instance and the associatedreportdbdatabase.Note: This command also removes all.oempfiles located in the watched directories and imported data stored in the databaseoemp queryUses TCMANto query the status of the PAS for OpenEdge instance.oemp startup [timeout=300]Starts the PAS for OpenEdge instance using TCMAN.Optionally, you can specify
timeout=300to wait up to 300 seconds for startup.oemp shutdown [timeout=300]Stops the PAS for OpenEdge instance using TCMAN.Optionally, you can specify
timeout=300to wait up to 300 seconds for shutdown. - On Windows:
- To initiate installation of the OpenEdge Memory Profiler tool, run the
oemp installcommand from<oemp-install-dir>.- On Windows:
oemp\bin\oemp.bat install - On Linux:
oemp/bin/oemp.sh install
The following table lists the configuration options and their default values applied during the installation process. These parameters define the setup of the PAS for OpenEdge instance and its associated database.TheNote: These configuration options can be overridden by specifying alternative values through the command line. For a more persistent means of adjusting values, you may change parameters in theoemp.propertiesfile located in the<oemp-install-dir>/oemp/confdirectory.Table 2. Installation properties Property Default value Description http8880Specifies the port number for HTTP connections to the PAS for OpenEdge instance. https8883Specifies the port number for secure HTTPS connections. shut8884Defines the Tomcat shutdown port used to stop the PAS for OpenEdge server. db_port8896Sets the primary service port for the database. db_port_min8980Specifies the minimum port number for dynamic database connections. db_port_max8998Specifies the maximum port number for dynamic database connections. wrkDir <WRKDIR> Specifies the parent directory of the PAS for OpenEdge instance. By default, the <WRKDIR> environment variable, set during the OpenEdge installation, is used to determine this location. instanceoempSpecifies the name of the PAS for OpenEdge instance. This name is combined with wrkDirto form the full path to the instance, commonly referred to as<CATALINA_BASE>.oemp installcommand:- Creates the
oempPAS for OpenEdge instance in<WRKDIR>by default.Note: The<WRKDIR>/oempis referred to as<CATALINA_BASE>. - Extracts ABL Application files and deploys WebApps.
- Tailors the PAS for OpenEdge instance properties with suitable defaults.
- Sets up a self-contained
reportdbdatabase in<CATALINA_BASE>/db. - Creates a
<CATALINA_BASE>/importto be used as a watched directory with auto-import enabled. - Generates the
create_oemp.txtlog file in the<oemp-install-dir>/oemp/bindirectory.Note: TheoempPAS for OpenEdge instance and database are tightly coupled. Starting the instance will also start the database, and shutting it down stops both.
- On Windows: