Tag archives for OpenEdge

  1. Exchange Web Services Example – Part 4 – Subscriptions and Notifications

    Now that we have succeeded in creating, updating and deleting calendar items and mastered Exchange Impersonation, it’s time to turn our attention to having Exchange notify us about what it is doing. Part 4 of this series is going to provide a detailed code walk-through of some code that leverages the Subscription API.

    The example includes two code examples – one for Java programmers and one for OpenEdge programmers. The OpenEdge version writes updates through the OpenClient via the OpenEdge AppServer to an OpenEdge database.

    16 Replies

  2. OpenEdge GUI for .NET – Testing the Bridge

    Progress Software Corporation has been running a program to test the OpenEdge GUI for .NET bridge with controls that have no user-interface. My company, Intangere, is very interested in this program because we are looking at releasing a control that would make it possible for OpenEdge developers to communicate directly with a Microsoft Exchange Server and receive mailbox updates for an OpenEdge client.

    Intangere thus signed up for the program and created a control that mimics the behavior of a real Exchange Web Services control. This test has been surprisingly successful, and this article provides some information about the test and the code and a document that describes its use.

    No Replies

  3. Exchange Web Services Example – Part 2 – Creating Appointments

    In part 2 of this series, we are going to spend some time looking at the CalendarItem API, how it works and what it takes to create, get and delete an appointment. Before we start, you should make sure you have your environment set up per the explanation in part 1. If you have done that, you can download the example code for both the Java portion and the OpenEdge portion so you can follow along as we walk through this code together.

    Part 2 of this series of articles is dedicated to giving you an overview of the process of connecting to Exchange and doing some basic Calendar item work. Through the sample code, you will learn how to:
    – Connect to the Exchange Web Service from Java;
    – Create calendar items on the Exchange Server;
    – Get calendar items from the Exchange Server;
    – Delete calendar items from the Exchange Server; and
    – Connect to the Java service from OpenEdge to perform the same operations.

    The Java functionality will be exposed as a Web Service so that other platforms can also leverage, which is how we will get at it from OpenEdge. The OpenEdge code leverages the new GUI for .NET and object-oriented extensions, so you may find the example interesting if you have not done this before. [...]

    9 Replies

  4. Exchange Web Services Example – Part 1 – Introduction and Set up

    A few weeks ago I wrote about my experiences starting out with the Microsoft Exchange Web Services API and on using the subscription API. In the second article, I said I would write a code walk through that shows how to do the stuff. I had thought of doing a complete walk through like the Dynamic OpenClient code that I did back in November last year, but I wasn’t as busy back then as I am now, and I had the time to actually write up the example properly.

    This is part 1 of a multi-part series that will cover the process of connecting to Microsoft Exchange Web Services, submitting requests to Exchange, receiving notifications from Exchange, creating appointments, tasks, and e-mail, and using Exchange Impersonation. There will also be OpenEdge examples interspersed within it. Each part in the series (except this one) will have a downloadable zip file with the code in it that actually runs (at least in my environment) [...]

    30 Replies

  5. OpenEdge Microsoft Exchange WebServices API Survey

    As you may have guessed from some of my recent posts, I am working on an API that allows an OpenEdge developer to interact with a Microsoft Exchange Server. From the API you will be able to do things like create, update, and delete e-mails, appointments, tasks, and contacts. You will also be able to get attendee availability, and some of the clever stuff that you can do today in Outlook from an OpenEdge application.

    The intention is that this API will be accessible from any ABL session (whether character, GUI, GUI for .NET, AppServer or WebSpeed). Obviously, this means that you will need to be able to program against the API and that’s where this survey comes in.

    The responses to this survey that was conducted between May 7th, 2010, and May 14th, 2010, are now posted.

    Comments Off

  6. Exchange Web Services – Subscriptions and Notifications

    It’s been a really busy week since I posted my first post on Exchange Web Services. I have learned a lot in that short period of time that I want to share with you. Whether you are an OpenEdge, Java or .NET developer, I think this post is going to have some information for all of you.

    In my first post, I told you about the background story – I need to enable an OpenEdge CRM application to create, modify and delete calendar and task items in Microsoft Exchange. I also need Exchange to let me know any time a calendar or task item is changed so that I can update the OpenEdge database accordingly. Simple use cases.

    When I left off last week, my next step was to get Exchange subscriptions working, and, boy, what a trip that has been.

    11 Replies

  8. OpenEdge Dynamic OpenClient

    In one of the more recent versions of OpenClient, the API that the OpenClient uses is documented so that it is now possible to dynamically construct the proxy calls at run-time. The overarching benefit in this lies in the ability to now define the temp-table definitions on the fly. The Java/.NET code can now define the temp-table dynamically at run-time so that if a change is made to the definition, the client can deal with the change with no impact on the OpenClient source code.

    4 Replies

  9. OpenEdge AppServer – Exposing Progress OpenEdge

    In 1999 Progress held a user conference in Boston where they showed the any-any-any model. Progress was going to become open. You could connect any client on any platform to any database using a Progress AppServer to handle your business logic. This was a really good idea. The preceding 10 years had taught me that Progress was an outstanding platform for writing the business logic that controlled your application and ensured your data integrity. I was sold.

    4 Replies