12

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.

Share

Tags: , , , , , , , , , , , , , , , , , , , , ,

14

Exchange Web Services Example – Part 3 – Exchange Impersonation

Posted by Bruce Gruenbaum on June 28, 2010 in Development, Exchange Web Services, Exchange Web Services Example, Java, OpenEdge |

In part 3 of this series on integrating Exchange Web Services with Java and OpenEdge, we’re going to talk about a technique for accessing mailboxes called Exchange Impersonation. The first part of this article is going to talk about what it is, how it works, and the very serious risks it can potentially introduce to your enterprise. We’ll talk a little about how you can mitigate those risks, how to set it up from an administrative point of view, and then we’ll actually use it.

As with the other articles in this series, there is also a set of sample code that you can download and install to follow along later in the article.

Share

Tags: , , , , , , , , , ,

0

OpenEdge GUI for .NET – Testing the Bridge

Posted by Bruce Gruenbaum on June 22, 2010 in .NET, C#, Exchange Web Services, OpenEdge, OpenEdge GUI for .NET |

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.

Share

Tags: , , , , , , ,

8

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. [...]

Share

Tags: , , , , , , , , , , , , , , ,

29

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

Posted by Bruce Gruenbaum on May 18, 2010 in .NET, C#, Development, Exchange Web Services, Exchange Web Services Example, Java, OpenEdge |

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) [...]

Share

Tags: , , , , , , , , , , , , , , ,

2

Research and Innovation and Enterprise Architecture

Posted by Bruce Gruenbaum on May 12, 2010 in Commentary, Enterprise Architecture, Exchange Web Services |

The thing that sets one business apart from another is the special added value that it brings to the table. It does something different. It has come up with an idea that no one else does quite the same way, or so the business believes. Even when someone else is doing exactly the same thing, the thing that differentiates the two is the way that they do it. This is the “special sauce” that makes a business special.

But how do companies go about finding that “special sauce?” And more importantly, what can they do to maintain it?

While I don’t believe for a second that all the special sauce in the world comes from technology, technology can often be at the very heart of making that special sauce, especially when we are talking about building customer relationships.

Technology can be a huge support in this area, and that’s where research and innovation come in. Using technology to build better business relationships is where the focus of technical growth is, and learning how to apply technology to do so is where research and innovation come in. [...]

Share

Tags: , , , ,

11

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.

Share

Tags: , , , , , , , , , , , , ,

8

Exchange Web Services – Starting out

A couple of months back, a gentleman who has now become a friend and business partner, came to me and asked me if there was any way to get at all the calendar items in his sales organization’s calendars with the intention of integrating it with his Progress OpenEdge CRM system. Jim is using Exchange 2007 for his e-mail and calendaring solutions.

I was aware that Microsoft had released a new API for Exchange in Exchange 2007 called Exchange Web Services (EWS), and so I said that I needed to do a little research on the API, but I was pretty sure that it was possible. Sure enough, MSDN has some documentation of the API and Microsoft is touting it as the replacement for all APIs that communicate with Exchange. Web Services – how hard can it be?

Share

Tags: , , , , , , , , , , , , , ,

Copyright © 2009-2012 The Software Gorilla All rights reserved.
This site is using the Desk Mess Mirrored theme, v2.0.4, from BuyNowShop.com.