The OpenEdge Hive

There are a number of questions we want to ask about each candidate service. These include:

1. What kind of service is it? I.e., is it one service for a network? One per application? One for a system? One per session? Can it be replicated without change of function?

2. What inputs does it need?

3. What outputs will it return?

4. Who uses it and how frequently?

5. What does it depend on and how often?

6. How is it managed?

It seems to me that there is an interesting question that runs through several of these threads which has to do with identity. For some things, we often think of the identity of the person as established by a user name and password or some biometric or other means. But, it seems to me that there are other functions which depend on physical identity. E.g., for an AppServer agent starting up, if we are going to have it determine its configuration based on some service, then how do we know which agent it is?

This section will be used to provide general guidelines for the operation and construction of components for this project.

The OERA Open Source Initiative (OERA OSI) is a project to define, create, and refine a series of production quality components which can serve as a sound basis for those creating their own OERA implementations. The primary focus will be components which would form a portion of the Common Infrastructure portion of the standard OERA model, but we will not exclude contributions for other sorts of helper classes which might be used as part of a Data Access, Business Logic, or UI layer.

Transformation Triangle: For use in Transformation Triangle page

Associated with the presentation in this library entry were some demonstration files including some MDG technology to allow reading and writing .df files from within Enterprise Architect. These have been gathered here to make it easier for people to find this regularly requested technology.

In order to use an OpenEdge data repository in EA follow the steps below:

1. In the Open Project dialog, select the Connect to Server checkbox. This is in the upper right corner.

2. Click on the [...] (Browse) button, as you normally would to browse for a project. As you have selected Connect to Server, the Data Link Properties dialog displays instead of the Browse Directories dialog.

3. Select Microsoft OLE DB Provider for ODBC Drivers from the list.

4. Click on the Next button. The Connection tab displays.

Different people have different ideas of how they want to set up databases for SQL access, but in case this is an area unfamiliar to someone trying to setup an OpenEdge database for use with Enterprise Architect, the following describes one approach.

The standard repository for Enterprise Architect uses the JET database engine. This makes it accessible with Access and SQL, but those working with ABL may prefer to use an OpenEdge database and ABL, being more familiar and more powerful. An OpenEdge database is required for some of the ABL to UML tools available here.

The Enterprise Architect product from Sparx Systems is emerging as the preferred UML modeling tool at many OpenEdge sites. In order to make it easy for people to get started using this powerful tool, information will be collected here to assist people in this process.

The attached code represents the initial release of the ABL2UML open source tool set. This is an evolving project, so expect this code to evolve and expand over time.

A UML profile is intended to provide a mapping from a particular domain language or the language of a particular methodology onto underlying UML constructs. This mapping is a combination of “stereotypes”, which are terms from the domain or methodology equated to a particular UML constructs, as well as additional constraints, rules of “well-formedness”, and identification of which particular elements will be used to model the elements associated with the domain or methodology.