Archive

Posts Tagged ‘EBI’

Small- versus Large-Scale Provisioning

September 8th, 2010 Jim OLeary No comments

As applied to business integration, the term “provisioning” has many meanings, but overall, it refers to the process of defining integration endpoints and establishing connections and integration processes between them.   If an integration service that connects a pair of endpoints is simple and tightly constrained – for example, a data syndication service with a fixed process model and limited output options – provisioning can be as simple as selecting from a fixed list of connection and data format delivery options, and specifying the delivery endpoint’s address.

In most cases, however, business integration provisioning involves more steps, because the business problem to be solved requires tailored integration between some set of sources and targets, e.g., integration of an XML transaction set with a Warehouse Management System.  Those steps might include definition or specification of endpoints, communication and interface connections, documents / messages and envelopes, data routing, business processes, and data transformations.  By combining building blocks that implement such object types, you can solve most kinds of business-to-business, application, and data integration problems. Read more…

CDI Pottsville

July 29th, 2010 Chuck Buchanan No comments

Integrating with customers, suppliers, service providers, and applications is important to EXTOL’s daily internal operations, just as it is with your company. And probably just like your company, to manage those operations we initially relied on various disparate manual and/or home-grown semi-automated yet labor-intensive processes that inevitably involved no-longer-necessary and overlapping (if not outright redundant) activities. It wasn’t planned like that − it just sort of happened.

We’ve learned many lessons while “dogfooding” our internal operations. Before using our own product − EXTOL Business Integrator (EBI) − to streamline those operations, the first (and most daunting) task was to untangle the jungle of existing processes in an attempt to understand their ultimate goal. Read more…

Chunky or ground, wet and dry EBI

July 14th, 2010 Chuck Buchanan No comments

For those old enough to remember this reference (and for those young enough to know how to Google it), sometimes I feel like the Lorne Greene of EXTOL. Not in his role as the patriarch of Bonanza’s Cartwright clan, but rather as the dog food pitchman.

The series of 1980s TV commercials for Alpo® dog food featuring Greene closed with the veteran actor claiming that Alpo is so good he feeds it to his own dogs. Hence, the notion of using one’s own product became known as “eating your own dog food”. Or so the legend goes. [A less-tasteful alternative account of the phrase’s origin has the president of a rival pet food corporation eating a can of his company's dog food at every shareholders meeting.]

During my first eight years with EXTOL, I was blissfully unaware of this term. But when I assumed the newly-created role of Special Projects Coordinator four years ago, Tony Baran (our co-founder, President, and CEO) caught me lingering at the coffeemaker and directed me to lead the effort to “eat our own dog food”. I mustered my best blank stare, nodded assuredly, scurried to my cubicle, and Googled that phrase (actually, I had one of my younger officemates show me how to Google it). Only then did Tony’s mandate to “streamline our processes by eliminating error-prone re-keying of transactional and/or persisted data by automating the exchange of information between applications, databases, spreadsheets, and other sources” − I’m paraphrasing here − make sense. And oh yeah, “use EXTOL Business Integrator to do it”. Aha! − we would “eat our own dog food”.

While “eating your own dog food” now has been elevated to acronym status, EYODF is more than a mouthful − I prefer the much more palatable and trendy “dogfooding”. While we don’t make (nor eat, for that matter) dog food at EXTOL, we do produce some seriously efficient business-to-business (B2B) and application-to-application (A2A) integration software that coordinates external partner interactions and internal business activities. And now we’re dogfooding.

In subsequent posts, I’ll share our experiences in using EXTOL Business Integrator (EBI) to solve our company’s data integration, manipulation, and migration needs. By telling our story and noting the lessons learned (mostly the hard way − those are the best-remembered lessons), we hope you can use EBI to your best advantage to tackle similar projects in your organization. You have them − just look around.

And please, if you care to share your stories with us, do. Who knows: maybe we’ll send you a can of Alpo.

Categories: EXTOL Information Tags: , , ,

Creative Integration

June 22nd, 2010 Jeff Barlow No comments

EXTOL Business Integrator is a flexible and powerful tool, similar to a Swiss Army knife, that is always nice to have tucked away in your pocket.  It is designed to be very flexible for your particular needs and for your creativity and innovative thinking. The goal of this blog is to have you think outside of the box and apply EBI to a business problem for which it may not be specifically targeted.  Or, at least open your mind to its features and how to apply them in ways that do not conform to their core functionalities. Read more…

Data Integration 101 Using the EXTOL Business Integrator

May 20th, 2010 Mike Coyle No comments

Data Integration is defined as, “the combining of fragmented data residing in different sources and locations which are aligned to support business goals”.  There are many reasons to bring data of different types (flat file, DB2, or even spreadsheets), possibly residing on different servers, to one main location to be integrated together.  If you do Electronic Data Interchange (EDI), translating data between an EDI fixed format and application variable format files, then you have already been doing a piece of the data integration puzzle. Read more…

Server Based Web Frameworks

My favorite part of building software is web development.  I have been involved in building Web Services for EBI, Dashboard development for EEI and EBI, and I’m continuing to work on the web-based administration console for EBI 3x.   A new project has cropped up where I get to do more web development.  I’ve researched new frameworks that are available, and I’ve discovered that web development just got a lot more fun!  Read more…

Categories: Integration Technology Tags: , ,

Meet JBI

April 22nd, 2010 Patrick Gombola No comments

The EBI 3 team is pretty excited about using ServiceMix as a core piece of our server. This allows EXTOL to provide you with many different configuration options and a stable platform to deploy your projects into. This series of articles will acclimate you to the architecture and describe some of the tools we’ll be using. First, I’d like to you meet JBI.

Read more…

EXTOL Business Integrator: Dealing with Proprietary Flat File Data (Part 1)

March 18th, 2010 Jeff Barlow No comments

In my next two blogs, I will be discussing a common challenge facing EXTOL users — the handling of proprietary flat file data received from trading partners. The flat file trend is becoming more popular and, more importantly, being forced on users by their trading partners. We’ve seen a trend where you are either forced to handle the data in the format it is presented or lose the business. Another side of the increase in processing flat file data is to accommodate smaller “Mom & Pop” shops without the means to present the data in a better format.

Let’s explore the different flavors of flat file data. Flat file data can fall into one of two format types: single format or multiple format. Single format files have a common record layout throughout the entire payload data. This means, for example, that every record in the payload has the same exact layout, all of the fields are identified in the same manner in every record and every record of data is treated the same way in the pending data transformation. Multiple format files contain more than a single record layout throughout the payload. This means you will see multiple record layouts needing to be identified and treated as different records in the pending transformation. Read more…

Pass the Work From Your Business Applications to Your Database

March 9th, 2010 Brandon Duncan No comments

A few months ago, my colleague Jason Honicker wrote an entry on the EXTOL Technology Blog explaining how database triggers can be used to expand the functionality of your database to do more than just store data. I wanted to further the discussion on databases and talk this time about stored procedures.

A stored procedure is a routine, or program, which resides as part of the database itself. It’s typically written in SQL, PL/SQL, Java or .NET, depending on the type of database being used. Stored procedures enable developers and system administrators to maintain only one piece of code, which may be used across multiple business applications. This takes some of the pressure for business application developers to have to develop the database function directly into the business application. Instead, they simply need to know the procedure name, the parameters it requires and what kind of data could be returned. Read more…

Eclipse Walkthrough

January 21st, 2010 Matt Rosenberger No comments

In previous blog posts, we have discussed Eclipse and how we are using this platform for our Developer Studio in the next major release of EBI.  This blog will focus on installing Eclipse, accessing its documentation, and installing a feature for Eclipse so that you become familiar with the environment for the future version of EBI Developer Studio.  Even though many link Eclipse to programming, I will focus on the non-programming aspects of Eclipse so anyone can follow along.

With that said, we will tackle installation, which will probably be the hardest part of working with Eclipse.  Read more…