Progress Explorer Tool

The Progress Explorer Tool replaces ProControl. It provides a graphical interface allowing you to manage and configure the WIN-202 server host environment interactively. The tool is most commonly used for starting and stopping the WIN-202 database.

Progress Explorer Tool Screen

Stop and Start the Database

Double-click the Progress Explorer Tool icon on your WIN-202 desktop server. Right-click the "localhost" and select "Connect" from the menu (see above figure). Use your server username and login. Once connected, expand the Databases folder in the tree view and select "win202" (see below) . In the top menu bar, click the green arrow green arrow image to start the database or the red circle X red circle x image to stop the database. If the icon is grayed out, the action is currently enabled.

Progress Explorer Tool showing win202 database

Configure the Database

Many of the database startup parameters can be set using the Progress Explorer Tool. Select "defaultConfiguration" under the win202 Configurations folder as shown below.

Progress Explorer Tool showing default configuration

Right-click "defaultConfiguration" and select "Properties" from the menu to adjust settings. NOTE: Please contact Maine WIN-202 staff before adjusting any settings.

Default configuration properties

Scheduled Tasks

The Scheduled Tasks tool is used to start and stop the Batchmanager, schedule backups, cleanup archive files, run weekly extracts and various other administrative jobs. The "win202service" account is the database user name and is the user of the various administrative jobs run on the server.

Promon Screen

Right-click "win202bk" and select Properties from the menu. The database username is displayed in the "Run as:" field (see below figure). See the WIN-202 System Recommended Backup Procedures for more information.

Promon Screen

Stop and Start the Batchmanager

Right-click the Batchmanager task and click "Run" to start the batchmanager or "End Task" to stop the batchmanager. If the option is grayed out, it is currently enabled. Note: Always ensure the batchmanager is disconnected using Promon Option 5: Activity before launching it again. Running two instances of the batchmanager may cause database resource contention and cause jobs to crash.

Promon Screen

Note: Rebooting the server automatically starts the Batchmanager.

Scripted Shutdown

To shutdown the database programatically, create a batch file with the following command: c:\progress\openedge\bin\proshut <DBPATH\DBNAME> -by

Example: c:\progress\openedge\bin\proshut g:\win202\win202 -by