Agile Integration Serving End Users Directly

Social media is beyond ubiquitous, putting the power of communication and availability of information in the hands of everyone individually and collectively. It has moved from being a thrill for the eager to being a fact of life even for the reluctant. Social sharing of unstructured data is proliferating, and its management is the subject of much conversation, posting, tweeting, and blogging.

But what does this mean and how does it relate to individuals who need structured data? Isn't it time for an end user to be able to access data without calling the boss, who calls the IT department, who calls the consultant, who plans the project, that gets a team, that does an analysis, that includes everything but the kitchen sink, that has a garbage disposer, that's the only thing that works, with which the project finally gets euthanized?

It's time to think about what this means to data integration: lean, mean, or otherwise. These days end users are empowered by SharePoint and BI tools and such to determine for themselves what information they need in order to do their job and make decisions. If an end user can sign in to SAP and to Salesforce and to JD Edwards, why can't they use their SharePoint portal or a dashboard to access the same data from those applications? Of course, one of the key reasons is the issues around security. Historically integration has been behind the scenes, working with no visibility to the actual end user. ETL, of course, has none, and EAI is also not end-user aware. Dashboards are designed for specific users who have permission to see the data displayed. Although the dashboard app may have its own login for security, the integration behind the scenes does what it's told without knowing anything about the user.

Agile Integration Software http://tinyurl.com/3yv85bw supports SSS and other layers of security so that an end user of SharePoint, for example, can see live data with updates passing back to the applications, only if the user has privileges to do so. That same security is available out of box in AIS for any vendor software, BPM, or BI that is designed to read and write data to an ADO.Net entity via an ADO.Net driver, or alternatively by web service calls.

For example, Enterprise Enabler® http://www.enterpriseenabler.com/ is an AIS that can be configured in minutes to merge and align data from multiple applications and generate the entity definition and custom connector for SharePoint (BDC) or generate the entity for the ADO.Net driver that is called from WSS or any other ADO.Net Application. If preferred, it can generate a web service just as easily. The SSS end user security is honored in all these models.

So, in response to the expectations of the "me and everybody else now" surge, integration needs to step up to the plate.

Two Laws of War, IT, and Human Nature

There are two things that I have considered to be fundamental rules of life from as far back as I can remember. In my early twenties, it dawned on me that I actually thought of them with greater conviction than I ever did any of the laws of physics I learned. I decided that these rules held equivalent un-challengeable level of "truth" as laws of physics. Of course I did, in fact challenge every "truth" handed out in my first physics class. How in the world could everyone in the class just sit there and believe that there's some Force pressing up on the floor to keep us from falling through? Because the textbook said so? Hmm. I grew up in Virginia, and everyone knew that the State published the history books, and it was in Virginia's best interest to publish that every President except Lincoln was from Virginia! So, how can you believe there's an equal and opposite arrow somewhere that you can't see?

Now for my two laws, in the order of discovery.

Pamela's Law of Set Points. This may not be a very good name for it, and since I never named it before this moment, I reserve the right to change the name some time. The law is something like this: More things than you can imagine try to obey a set point. The set point may gradually shift over a long time, especially in response fundamental change due to extraordinary events, but in general nature gravitates to that set point. I remember thinking about this law and human nature when I was "into" change management and a person's or institution's capacity for change ("resilience"). While each person or organization has a different level of tolerance, that maximum is essentially constant. The same can be applied to a person's good humor. I believe there's a set point for each of us that is fulfilled by our reactions and attitudes no matter what is actually happening in the real world outside us. Worriers manage to find a certain level of worry, easily filling the void with a new subject of worry as another gets resolved. I'd love to be one of those eternally happy people that have a set point way on the happy side. I guess it's kind of the "glass half full" conundrum, which somehow leads to:

Pamela's Law of Constants. Again a name of the moment. I grew up in the Washington, D.C. area and from the time I was six or so, through high school, I ritualistically read the front page of the Washington Post every single morning (then I read the comics if my siblings were done). The most obvious conclusion to me was that there was always a war somewhere, often in some tiny country I never heard of before. As one subsided (from the headlines) another popped up somewhere else, like the cartoons where the guy with the big hammer pounds down one bump and it pops up somewhere else. That's when I began formulating the theory that unrelated happenings like this really were fulfilling some constant amount of world-wide war. Over the years, I discovered that this same law applies in many, many areas. I could elaborate on the law of constants in the IT world, but that's for another day. You can see, though that if there are constants to be balanced by seemingly unrelated events, that means the events really are related… my crude contribution to the evolution of Chaos theory.

Five Ways to Get Immediate ROI from Agile Integration Software

One of the great things about Agile Integration Software (AIS) is that you can install it and start reaping the benefits immediately.  You don't have to change your whole company's philosophy about middleware. Think about AIS as an adjunct to what's already there, and just solve a couple of important challenges quickly.

Don't know what AIS is? Take a look at this: http://tinyurl.com/3yv85bw

Here are a few ideas that can prove the value of AIS and bring real value to your company before the rest of the team wakes up.

ONE. Get all manner of data into SharePoint. Empower your SharePoint developers and users with secure access to data from all your backend systems. That means that the people that need to see and interact with data that comes from SAP, Salesforce, and Excel, or a custom application, for example, can have that without even declaring a project. Line of business (LOB) applications built in SharePoint invariably need data from multiple systems, and it all needs to be aligned somehow to make sense together. Try AIS for this. Build a couple of interfaces to SharePoint External Lists - BDC (business data catalog) or to SharePoint Lists and see how it goes. The data is secure, and you can even use the same interfaces to handle write-backs to those systems.

TWO. Rescue a project that is way behind schedule. Chances are that the part of the project that's lagging behind is the integration with other systems. Don't displace whatever technology is in being used, but try a rapid parallel path with Agile Integration. Skip the staging database and get the data live from the systems align it on the fly and send it where it needs to go. This is what AIS is designed to do really well. If you find that the easiest way to get started is to go with a staging database that's in place, then use AIS to get the missing data into the repository quickly. Or build the integration and expose it as a web service in two clicks.. Voila! Then sit back and reap the benefits of success (and be a hero).

THREE. Fast-track your BI dashboard project. Let's say you have a dashboard project that has lots of promise. Maybe you just bought a very cool analytics software package that will allow you to understand your business and the market better so you can maintain your competitive advantage. The vendor delivered the software and gave a two-day training on how to configure and use the cool graphs and such. But now they've gone home, and it's up to you to figure out how to get all the data you need into the tool. The more data that's available, the greater the value of this investment. Big problem. Big project, fraught with all the perils of any integration project. Before you spend a year creating the database, see if the tool is just making a call that could be tied to an AIS that could grab the necessary data, align it, and pass it live to the dashboard. That's definitely faster and a much better solution. Otherwise, at least reduce your population of the staging database by 70% by using AIS.

FOUR. Close your books in half the time. If your company is like most, there are multiple ERP or financial systems as well as inventory systems and even spreadsheets involved in the process of consolidating all of the information required to close the books every month. With a changing environment, new entities must be accommodated or eliminated from the process on a regular basis. Using AIS you can automate the capture and alignment of the information from the multiple sources, but even better than that, you can update the integration in a matter of minutes to reflect the changes in your business from month to month or quarter -to-quarter.

FIVE. Improve the productivity of your IT team. Empower your Data Analysts to configure integration without programming. Free up your programmers from doing repetitive integration activities. AIS can eliminate a tremendous amount of activity that simply does not need to be done anymore. You owe it to your company to take advantage of the value of AIS. Start with new data flows that need to be done rather than initiating a lifelong switchover project.