Boomi OnDemand: Integration at the Speed of the Internet

Integration engines don’t always have to live on enterprise servers. Indeed, there are times when it make sense to leverage an integration engine that’s exists remotely, leveraged as a Service. Considering that integration is a complex and expensive proposition, the ability to deliver an integration solution over the Internet makes good sense consideirng that enterprises are now leveraging many Software as a Service (SaaS) applications.

Boomi takes this approach to integration, which provides the architect with the ability to create integration solutions they neither have to host nor maintain. Boomi’s approach makes a great deal of sense when creating integration solutions with third-party hosted resources, such as SaaS players like Salesforce.com, or when an organization requires B2B integration for linking business partner to business partner.

Is your Foundation for Continuous Change a Herman Miller Aeron or a Two-Legged Stool?

The new requirements for the Service lifecycle.

Webinar for Corticon delivered on November 30, 2007.

8-slide PowerPoint in pdf format.

ZapForum Podcast: OpenAjax: Standardizing the Web 2.0 Client

ZapForum Podcast for November 15, 2007 features

Guest Expert John Ferraiolo, Web Architect within IBM‘s Emerging Technologies Group and manager of operations at the OpenAjax Alliance.

Listen to this Podcast and you will:

• Get an introduction to the OpenAjax Alliance, what its role is, and who its members are
• Understand the challenges facing interoperability among Ajax toolkits
• Learn the distinction between Ajax components and Ajax applications

SOA as a Corporate Responsibility

In these days of corporate responsibility and compliance, we need to consider the efficiencies of our IT infrastructure along with other corporate assets. For most companies, enterprise architectures are the single most limiting factor to their business economics since they don’t have the ability to adapt to business changes in …

Vordel: Centralized Policy Management Infrastructure

Policy management is quickly becoming a core need when considering the implementation of operational and effective SOA implementations. However, many people don’t consider policy management until it’s too late, and difficult to retrofit. Indeed, the use and management of policies provide the central control mechanism that provides clear value when considering the return on investment of SOA. . Policies are as important to SOA as Services themselves, and they should be managed throughout their lifecycles as such.

Policy management requires operational lifecycle support, like any other development effort. Such management includes the migration through development, testing, staging, and finally the operations of the policy in the production environment. Moreover, policy management requires other facilities, including centralized logging of all critical metrics gathered during the policy operations, allowing the managers of the SOA implementation to gather key data points used to enhance operational efficiencies.

Why SOA Governance Must Start at Development Time

Now that SOA is moving from the planning to the project levels, there is a clear need to manage SOA’s assets, as well as maximize its key values: Agility and reuse. Thus, the use of a well-defined and well-implemented SOA governance system is critical to the success of SOA. Choosing the right governance system requires that you carefully consider specific attributes of the enterprise domain, including an inventory of the major SOA resources such as data, Services, and processes, as well as interactions and dependencies, and how all relate to the notions of policy management, service agreements, and security. Clearly, these interrelationships are so complex and far reaching that a SOA governance system is an absolute necessity.

So, how do you select and implement a governance system? There are a few key things to consider as you define and build your SOA, and clear steps you must follow to achieve success. In this paper we’ll take a look at the concept of SOA governance, as well as the steps needed to implement governance within your SOA problem domain.

Avoid Vendor Driven Architecture (VDA)!

When looking at the technology buying patterns in the world of SOA, there is one common thread. The Global 2000 and many government agencies purchase SOA technology from their existing vendors, no matter what their needs or requirements might be. I call these purchasing solutions “comfort technologies” since they consider …