DataDigger

DataDigger is a generic browse on your database. Browse through you data and save your queries, selected columns and changed formats. Export full tables, results of queries or selections easily to dump file or XML file.

DataDigger 14: (click to enlarge)

How to install

Installing DataDigger is just as simple as 1-2-3:

1. Create a directory called DataDigger
2. Extract the zipfile in this dir

OpenEdge Adapter for Fuse Message Broker API

The API supported by the adapter is a subset of the JMS API. Full
documentation of all details is available online. The
diagrams below only describe the part of the API that is implemented by the
OpenEdge Adapter for Fuse Message Broker.
Notes:

Using the OpenEdge Adapter for Fuse Message Broker

Getting started

Prerequisites

• The message broker must be running. If the broker requires authentication
  you must know a user name and password.
• The STOMP listener must be accessible over the network. You must know the
  host name and port number.
• The directory stompAdapter from the adapter code distribution must be in
  the PROPATH.

Defining the connection with the broker

OpenEdge Adapter for Fuse Message Broker

Overview

The OpenEdge Adapter for Fuse Message Broker enables connections from an
OpenEdge™ ABL application to Fuse™ Message Broker or Apache ActiveMQ (or
other messaging solution as described below). It consists of a number of ABL
classes that should be referenced in an ABL application that needs to exchange
messages with the outside world using one of the supported world class
messaging solutions.

Download the zipfile and follow these steps to install:

1. Create a directory called DataDigger
2. Extract the zipfile in this dir
3. Create a shortcut to prowin32.exe and use -basekey "INI" -p datadigger/DataDigger.p

Ready you are.

DataDigger v13: Click to enlarge

This profiler identifies performancebottlenecks in your application by analysing the logfile you create with the log-manager. Profiler

Progress Fuse Adapter
Written in OO ABL and supports the stomp protocol.
Code comments in Dutch

Documentation

Identifies possible memory leaks and their source by extracting those lines from logmanager output that point at created objects that are not deleted later on or allocated space that is not (fully) deallocated.
This analyser goes a bit further than http://www.oehive.org/node/846 and can handle OE 10.2A extra's

Sometimes it's neccessary to add a Caption in the titlebar to give extra information to the user of your application. The attached file does this, and makes sure the window got redrawn when windows triggers arive.
As you can see, many instances of msgblst32 are added on this window. The goal is to make it more the controlling window which always catches the events on the underlaying session applications. As every window needs its own ocx, I provided 40 instances which are hopefully enough to maintain every window.

This set of examples show various methods to test for character, integer, and decimal values.
The various test methods came from a discussion on the PEG and suggestions by members and myself.

Typical time results per 100,000 iterations of the functions.

+--------------------------------------------------+
¦-123                                              ¦
¦                                                  ¦
¦fn-ISCHAR-loop:   31510 ms no  Loop method        ¦
¦fn-ISCHAR:         3681 ms no  DEC(x) error method¦