EZBus
ESB made easy!by iTrajectum
EZBus 

EZBus 

The world of Business Process Automation of growing more and more complex at an ever increasing rate. More and more businesses, organisations, people and systems need to communicate and integrate with each other. We've gone from connecting a few local applications to large scale integration of services or applications that run either locally or in the cloud. Connecting all these services and applications is a hard job. Supporting all these connections is an even harder job. It's not hard to lose control, especially now many departments can (and do) order their ‘own’ SaaS solutions. To stay on top and ahead of such problems we need to take charge.

 

The business requires that all these processes need to be flexible: they need to be able to change and change quickly to suit new business demands. Meanwhile, the entire integration landscape must be reliable (can’t lose any orders (or any other data) flowing through it!) as well as scalable: the landscape must be able to grow without a redesign of the software running in it. Even better, it should be able to grow without any downtime for the business! To boot, all these requirements must be met efficiently and in an affordable way, especially when we don’t have an ‘enterprise budget’ to spend.

 

 

There are several Enterprise Service Bus products available. They help out to leverage some of more of these requirements. We found that these products are often very expensive, hard to develop with, hard to support, hard to monitor and most of the time: all of the above. We know that building an integration landscape and keeping up with business demands is hard enough in itself, without having to fight the software used to build your Service Bus. We also know that building and maintaining that landscape is costly enough without having to buy very expensive software. And it doesn’t have to be that way. iTrajectum’s EZBus is an Enterprise Service Bus that will help you meet all of the above requirements in a cost effective way.

 

EZBus is an extensive software suite that will help you build, run and maintain an Enterprise Service Bus in your organization that can be the backbone of your integration landscape, however small or large that landscape is. It is based on Microsoft BizTalk Server and Microsoft SQL Server. Developing modules that run in EZBus is done by using a combination of Visual Designers and C#, using a Software Factory in Visual Studio.

You may already be familiar with these products or have administrators and developers working with them. EZBus includes a web accessible monitoring client that enables functional monitoring: in the first place it will show information about the business process, as a whole, designed by you. From the same functional view, a business process can easily be restarted or resumed, without having to consult technical staff. Drilling down on that information will lead to more technical information you can then give to your technical support staff.

 

Please contact us for information, integration advice and solutions, applicability to your organisation and/or product demonstration.

 

Solution 
Tooling 
iTrajectum 
EZBus 

Solution 

When facing the day to day challenges of supporting your business by building and maintaining your organisations’ IT environments, most of us run into common problems.
We see that many organisations encounter similar problems like (but certainly not limited to!) the ones below.

Do you recognize any of these problems?
Maybe even, you're trying to ignore them because you don't think they can be solved?

It often indeed seems like a poor choice between big bucks or big bugs!?!!
We have seen it before and may be able to help you out!

 

Problem

The business demands a fast growing number of connections between applications and services. You start out building an interface between two applications. Then another interface and then another. Because these interfaces are specific to both applications, they can’t be reused.

 

Solution

ezbus box Using EZBus the strategy is always to ask whether any interface could ever be reused and to standardize the way how an application should be addressed. This becomes a generic EZBus endpoint that can then be reused by any module that is running in the EZBus landscape. All that’s left is to gather the data needed to supply to that generic endpoint to make it work. You don’t worry about the plumbing: the endpoint already knows all there is to know about the specifics of the application it’s talking to.

 

Problem

You are aware that there are platforms available to help you with integration. But you know these platforms are expensive and at the least, require expertise. You also know or fear this expertise is not readily available within your own organization, having to resort to expensive external consultants.

Solution

The EZBus suite and methodology is designed with businesses and organizations of any size in mind
and is intended to be used by your own staff or otherwise with help of generally available local consultants. The intelligent landscape and smart tooling lets you focus on the business problem.

EZBus takes care of the plumbing and steers you clear of most pitfalls. You don’t have to know what the best architecture looks like, or how to build such a platform. It’s already done for you.

 

Problem

You made the decision that external expertise is required to meet your organization’s integration demands, but now experience you have become dependent on specific parties or individuals.

Solution

By using its software-factory and configuration tooling, EZBus generates over 90% of code and configurations for you and figures out what information is available or needed. All you need to do is drag&drop and fill in the blanks. Now any developer or party can add new components to your service bus or maintain your current components if needed.

 

Problem

 
 

Problem

Nobody in your organization has a well bird’s-eye view on the entire landscape.

Solution

Because of the complexity of the multitude of connections and the different technologies they are based on, the landscape is not transparent and hard and time-consuming to support. EZBus eases this problem by providing consistent generated software components, consistent deploy packages and management. All couplings are uniformly recognized by the intelligent landscape and can be monitored in the same tool.

 

Problem

Supporting all these connections must be done in many places by many people.

Solution

All connections are governed by EZBus & BizTalk Server and are therefore supported by 1 role:
The EZBus administrator. Additionally, all management tasks and settings are done in a standardized way within a singular context.
Not by many people in many different locations in many different config files, event-logs, obscure text-files or database tables.

 
 

Solution

 

Problem

You’re losing track of the multitude of interfaces between all your applications.

Solution

Connections may exist in many separate places, and each connection has its own disparate configuration. Using EZBus all interfaces are governed by BizTalk Server and can be technically monitored by several tools that are already in use by many organizations, like the BizTalk Administrations console, System Center Operations Manager or BizTalk360.
To functionally support all interfaces, EZBus comes with a web accessible monitoring interface, that shows which business processes have completed, and  which ones have failed, and why. EZBus intelligently differentiates between technical, functional or configuration errors, and notifies the appropriate staff. No need to bother database support with a malformed zip code nor alarm your functional administrators when a database is no longer available. EZBus supplies the right people with the right information to keep operations as smooth as possible.

 

Problem

You have a requirement to interface with external or incompatible systems.

Solution

By the EZBus generic onramp or any of the dedicated BizTalk adapter options, EZBus can interface with many different applications, out of the box. You don’t worry about how to get data into your business process, you worry about what to do with the information. For interfaces that cannot be connected to using standardized protocols, the adapter framework is C# based and extremely flexible, so that it can still be realized within the EZBus framework with minimal effort.

 

Problem

You want to be able to connect with Cloud services.

Solution

Because EZBus extends the capabilities of BizTalk, it integrates seamlessly with the Windows Azure cloud strategy. Using EZBus as your Enterprise Service Bus allows you to easily connect your existing applications to services that run in Windows Azure, whether you need to get data into or from the cloud.

 

Problem

Integration projects are expensive for your company.
Programmers spend too much time building trivial functionality
(i.e. application and infrastructure plumbing)

Solution

EZBus uses its software-factory and tooling to generate most of your code resulting in consistent components that are fast to develop, aim at reusability, easier to test and easy to deploy.
Take a look at the available videos and get inspired.

 

Problem

When a disturbance occurs in your production environment, it is hard and time-consuming to find and pinpoint the cause.

Solution

EZBus’ functional monitor applications shows all processes that flow over your service bus.
It visually indicates per step what happened, what finished, what went wrong.
By simply clicking your mouse, you drill down on the details.
 

Problem

What integration platform should you choose?
You want to start easy, but not implement the next bottleneck in your organization,
yet you can’t spend excessively on products and personnel.

Solution

EZBus extends BizTalk and is therefore highly scalable. With EZBus you can start off with a single server solution and when requirements demand, scale up to an entire forest if needed.
Yet how you develop and maintain your components and solutions remains steadily the same. Everything you used or created in the past can be reused tomorrow.

Solution 
Tooling 
iTrajectum 
EZBus 

Tooling 

 

Building your ESB

 

Implementing an ESB is hard. You can’t simply install an ESB, let magic happen and hope to have it handle all your integration problems. Every business process is specific to your situation and every connection you need to implement needs careful planning, you want to build it well and you want to build it only once.

 

Many providers will tell you that with their product or (SaaS-) solution it is easy to interface with other software because they use standard protocols. This is only partly true, speaking the language does not necessarily mean all parties involved understand each other.
Even interfaces that are using standard protocols are hard to implement because you need to program against another application’s functional behavior.

 

On the daily workfloor, this usually means that projects are much harder then they seems at first glance. Despite hard labour they take a much longer time to complete, are more expensive and even worse: in the end often result in components that still contain opaque logic and code specific to a single business problem or even completely fail.
Integration remains serious business, but you can iron out many of the issues so many others have seen (and solved) before you. By using a clever methodology and smart tools you can get ahead of the game!

 

This means that when, through smart design and dedication, you’ve created a software component that knows how to interface with some party, service or application, the next time around all you need to say is “we can already do this!”.
All that is left to do, is implementing the last bits of functionality specific to the use case at hand without you having to go through all of the hardships you went through the first time around.

 

EZBus is a software suite that helps you do exactly that. It helps you to design and set up generic endpoints that you can reuse and/or extend over and over.
When you encounter the need for a new connection, EZBus helps you design, set up the 'plumbing' and create it for you. The next time around, EZBus only needs you to fill in the blanks and help you (re-)configure and deploy the same reusable component.

 

The following specific EZBus features help you develop your ESB:

 

 

Dynamic mapping

If you have any integration, or even more specific, BizTalk knowledge, you know that using transformations/mappings in orchestrations are usually hardcoded which makes them anything but reusable. It restricts you to just those specific types of input messages required by the first business process you came across, Dynamic mappingwhich makes them specific for that component. Next time you need similar functionality with a different message or source, you will need to build, deploy and maintain practically the same thing again.
EZBus takes away this restriction by offering dynamic mappings. Effectively, you can use any input data and/or any mapping in your, now generic, endpoint, dramatically improving the reusability and hence reducing development time.
Most of the time even executing faster at runtime too!

 

 

Software Factory

Developing these endpoints is done using the EZBus Solution Factory, a software factory that is hosted in the trusted Visual Studio (any version from 2006 R2 and up) your developers are already familiar with.
EZBus developers to create endpoints in an easy and sustainable way by offering guidance and extending the standard functionality of Visual Studio.


Some of our key features:

 

The Solution Factory
EZBus creates an entire solution and the entire project structure for you according to best practices, ensuring you have a correct project structure, consistent naming and namespaces for your artefacts.
In fact, it will instantly create a readily compilable solution that you only need to extend for the intended business logic. Sample code and reusable building-blocks for the most common functionality are built in and can be easily reused.

 

Schema viewer
EZBus gives you an extra window inside Visual Studio that shows you all available schemas at a glance. And that is not only all schemas in the solution, but any schemas currently available to solve your business problem!

 

MultiMapperA MultiMapper
This special editor in Visual Studio provides an easy way to create a BizTalk map that has multiple input or output messages. This type of maps is crucial in an integration scenario, it’s the most powerful and flexible way for you to combine information from all different sources and therefore is where most time is spent developing the required business-logic.
Using the standard BizTalk plugin for Visual Studio, the only way to create such mappings is to first create an orchestration, gather all required schemas, create typed message instances, then use the transform shape and configure it for multiple inputs and outputs. When you managed that and you now have a single mapping you need to remove all typed messages and transformations. Next mapping: same story. Using the EZBus plugin, you can just choose Create MultiMap from your context menu. Then just drag and drop any schemas from your Visual Studio solution, from the EZBus schema viewer or even from any BizTalk assembly you received from a business partner or stored anywhere in your file system and you have yourself a MultiMap. Save it and then add links to it from the regular BizTalk Mapping Editor that all BizTalkers know how to use!
You can even add additional messages or change the order afterwards without having Visual Studio destroying the contents of the mapping!

 

 

EZBus configuration editor

EZBus endpoints are available for reuse during runtime because they can be configured to be part of any runtime process. You can reuse all of your components in many solutions and/or reuse those same components multiple times in a single solution, with the same, new or multiple mappings.
It lets you draft what the process should look like, not the other way around. Each business process is represented by an itinerary (what we call an EZBus configuration), which effectively is a list of ‘steps to take’.
Every EZBus artefact you develop is such a step (aka endpoint) to take. EZBus comes with a comprehensive tool that runs outside Visual Studio that combines all technical artefacts produced by developers, and merges it with the knowledge of a person who has a more functional view of the business process.
Using this editor you can drag and drop any BizTalk artefacts onto its surface and it will analyse its contents for required settings/properties and available endpoints & mappings. These endpoints, settings and mappings will then be available for easy configuration within the editor.
Of course you do document your software well, as we all do, but you no longer need to depend on the in-depth technical knowledge only individual developers in practice always end up having!

Just drag and drop any endpoint from the left to the middle pane, drop any mappings from the right side to the mapping pane, set any relevant properties and you have an executable business process!

 

 

Supporting your ESB

The ESB landscape is mostly invisible. It takes many services to support a single business process and services are, if all is well, invisible to users and administrators. The only way to tell if anything has gone wrong is when data is not present in applications or when actions are not executed as should be. There are many tools to do technical support of all separate parts of business processes. Tools like System Center Operations Manager or BizTalk 360 provide an excellent way of managing a BizTalk environment, or even the out-of the-box BizTalk Administrator provides a good way to get a technical understanding of the state of things. Provided you have a very keen technical understanding of the inner workings of BizTalk. Usually the people that have a technical view on your business processes are not functional experts (and vice versa). You do not need to bother a database administrator with an incorrect zipcode a customer encountered, nor need you bother a functional administrator with a message that the database diskspace may be running low. To properly support a business process you need an integrated view of the whole business process with labels that have a functional meaning, that simply shows the right people where in the process an error has occurred and the means to do something about it, for instance, to retry the current step or maybe restart the entire process from the start. You need to see important information right away and then, if still necessary, be able to drill down to more technical information that you can maybe hand over to a more technical person.

 

And this exactly is what EZBus offers:

 

MultiMapper A web deployed monitoring tool that displays an integrated view of processes, like a box of index cards that you can browse through and where you can instantly see which one has gone wrong. You can just click on that index card and it will show you the entire process in a graphical way, so you can instantly spot which step has failed.  From there you can either resubmit the process or go into more detail, like look at the original incoming message. This may be XML or a pdf file, the monitoring tool will let you view it or save it somewhere for further analyses.

 

 

Intelligent landscape

EZBus helps you to build an intelligent landscape. EZBus comes with a single installer tool that will deploy any component of EZBus on any server for any role in your IT landscape. Though we recommend you follow the DTAP strategy, that is, you have separate staging environments for your development, testing, quality assurance and production, EZBus will follow the development-strategy you want to follow, not dictate it. While installing, EZBus gathers and maintains knowledge about your entire EZBus installation. It keeps track of what components are installed on what servers, what machines developers use etc. The appropriate tools know what settings to ask for, where to store what information and by using a smart auto-discovery strategy, EZBus prevents installations from going rogue! This way setting up, monitoring and configuring your infrastructure and processes becomes almost too easy.

Solution 
Tooling 
iTrajectum 
EZBus 

About us 

 

iTrajectum is a company of specialists in the field of software integration and service bus technology using mainly Microsoft technologies. Our experienced consultants have been working in software development, - architecture and - support for over 17 years, and have worked on many different solutions using many different technologies, for many customers in both private and public sector. Lessons learned from all these projects enable us to have a clear understanding what it takes to design, build and support automated business processes. iTrajectumWe specialized in software integration over 10 years ago, because we saw the importance of this every faster growing field and felt this would be a both exciting and challenging field of operation. Our expertise is at your disposal for a broad range of activities, ranging from architectural review via technical design to development. Having seen many integration projects not only as architects or developers but as administrators as well, and having seen many platforms and tools used in ESB scenarios, we could only conclude: "this needs to and can be done better!". Building on the already powerful basis of the Microsoft stack, we aim to deliver a product that has all the advantages of BizTalk and SQL Server, but adds an extra few layers that turn your Microsoft stack in an Enterprise ready Service Bus!

 

Please visit our company site at: www.itrajectum.nl

Solution 
Tooling 
iTrajectum 
Editions 

Editions 

We keep your enterprise service bus easy, and we also keep our licensing model easy. There are no hidden or special restrictions such as on number of cpu-cores, physical or virtual server, on premises or cloud deployment.

All you need to choose from is the 3 EZBus license options:


 

Any of the EZBus licenses can of course be installed on-premises but is also available as a Cloud SaaS-solution.
(Restrictions set by Microsoft on BizTalk Server Cloud deployment apply without change.)

 

Browse these sections to find out what license-type would best suit the needs of your organisation and please do not hesitate to contact us if you have additional questions/requests or would like to discuss what license would be appropriate in your specific situation.


EZBus licensing 2016q1

 

* Licenses and their prices may be subjected to change without notice.

Enterprise licenses include escrow program participation. Escrow is optionally available for Standard licenses at additional cost.

 

Standard 
Enterprise 
Developer 
Editions 

Standard 

By installing EZBus in your environment, you can instantly turn BizTalk into a powerful Enterprise Service Bus. When you’re already running BizTalk you can (usually) install EZBus side-by-side to your existing components and solutions without breaking them or restricting EZBus.

 

The basic license of EZBus ‘Standard’ allows you to install the EZBus-engine on 1 virtual or physical server, independent of the number of cores, memory, on premises or cloud. Other EZBus components such as the central configuration service, monitoring service and database may still be deployed on several servers in order to optimize performance without additional licenses or cost.

 

For many ‘small to medium’ businesses and/or organisations, this license-type allows for a good starting point. When you’re looking at your first few connections and/or processes, this provides you with a full-featured yet affordable platform that can be scaled up when necessary. All components you develop now, remain fully reusable in the future when switching to a ‘heavier’ license.

 

The ‘Standard’ license includes ‘3 support incidents’ when your developers or administrators require extra assistance in the rare event an issue arises when installing or configuring any of the EZBus components and gives you access to the latest version of EZBus upon installation or license renewal (annual).

 

When you consider setting up a DTAP (i.e. Development, Testing, Acceptance and Production) strategy, which we highly recommend when you have more than a few connections and/or processes or plan considerable extensions in the foreseeable future, you may need an additional license for Acceptance. Development and Testing environments can be covered with the low-cost ‘Developer’-license.

You may save considerably with the 'Enterprise'-licenses when you require multiple production (and acceptance) environments. This is very common in failover- and/or load-balancing scenarios or when process-chains have to remain entirely separated for, for example, security reasons.

 

EZBus is currently compatible with all versions of BizTalk Server editions from 2006-R2 to the recently released version 2013. The EZBus license does not include licenses required for Microsoft BizTalk Server and/or Microsoft SQL Database Server. Cost of these licenses may vary as they strongly depend on licenses already owned or leased by your company, such as volume licensing and/or MSDN enterprise subscriptions. Please do not hesitate to contact us if you’d appreciate some assistance on sorting out the required licenses for your specific situation.

Standard 
Enterprise 
Developer 
Editions 

Enterprise 

When your organisation is relying on multiple process-chains, connections to external (trading-) partners, supply chains, data from sources via the internet or the cloud, chances are they are to be considered, at least to some level, “mission-critical”. You want them up and running 24/7. This of course means that you take extra precaution when changing or installing components and configuration in production, but also you probably have implemented a DTAP (i.e. Development, Testing, Acceptance, Production) or QA (Quality Assurance) strategy. Projects carefully roll a component from one stage to the next to allow for vigorous testing before going into production, minimizing the chances of interrupting business. You may even have multiple systems share the messaging-load (load-balancing) and/or have systems on standby to kick in when a production server fails (fail-over). While good precaution and sensible strategy, and as such on the wish-list of most organisations, the downside usually is multiplying your licensing-cost. Something simply not all of us can afford.

 

The EZBus ‘Enterprise’-license allows you to install the EZBus-engine and other components onto a maximum of 3 complete production streets (i.e. Production, Acceptance or QA, Testing and Development) on virtual or physical server, independent of the number of cores, memory, on premises or cloud. Other EZBus components such as the central configuration service, monitoring service and database may be deployed on several servers in order to optimize performance without additional licenses or cost.

 

For businesses/organisations, this license-type covers all bases while saving over 30% on licensing-fees.
You can optimize and safeguard production, structure your development and testing, implement rapid application development and still be able to afford it. When you’re looking at supporting multiple business-processes, multiple connections to multiple partners and/or systems, this is would be the appropriate license for you.

 

EZBus is currently compatible with all versions of BizTalk Server editions from 2006-R2 to the recently released version 2013. The EZBus license does not include licenses required for Microsoft BizTalk Server and/or Microsoft SQL Database Server. Cost of these licenses may vary as they strongly depend on licenses already owned or leased by your company, such as volume licensing and/or MSDN enterprise subscriptions. Please do not hesitate to contact us if you’d appreciate some assistance on sorting out the required licenses for your specific situation.

Standard 
Enterprise 
Developer 
Editions 

Developer 

All software products and infrastructure start with planning, development and testing. No matter what project methodology you use, be it RUP, Waterfall or Scrum, when you start building your solution, just like a carpenter, all developers need good tools to create the reliable components that let us do our business. The EZBus 'Developer'-license is your developers' toolbox!

 

This license allows you to install the EZBus-engine, the EZBus Solution Factory and other required components onto a virtual or physical workstation, in order for developers to create, configure and support the EZBus endpoints, mappings and processes. It is to be considered a 'per seat' license. In order not to complicated the licenses, this type also suffices for your testing environment (per virtual or physical machine). You do not require additional licenses for administrators that use the EZBus Monitor or Configuration Designer. However, to function correctly, the 'Developer' expects at least one valid Standard or Enterprise license to be activated within your domain.

 

EZBus is currently compatible with all versions of BizTalk Server editions from 2006-R2 to the recently released version 2013. The EZBus license does not include licenses required for Microsoft BizTalk Server and/or Microsoft SQL Database Server. Cost of these licenses may vary as they strongly depend on licenses already owned or leased by your company, such as volume licensing and/or MSDN enterprise subscriptions. Please do not hesitate to contact us if you’d appreciate some assistance on sorting out the required licenses for your specific situation.

Standard 
Enterprise 
Developer 
Sample UC 1 

Use Case 1 

 

Consider the following scenario:

 

You use webforms as a standard interface between your organization and your customers. All webforms are specific to the needs of specific customers, order-types, departments or a business-partner and hence serve specific purposes. While any webform in the end can possibly trigger very different business process, the way they are taken in for processing however, is always the same.

When you start processing, sometimes you may need to just archive the webform in a Document Management System (DMS). Next you may want to register the customer information and therefore you will probably need to check whether the customer is an existing customer with your Customer Relation Management (CRM) application. If not, make sure the customer is saved. Either way, you need to obtain the Customer-Id so that you can use it later on in the process. Further on, you may need some data from the webform to be processed by another back end system (like SAP) as well, which could require both the Document-Id that was returned from the DMS and the Customer-Id from the CRM application to be submitted. After that, a lookup may be necessary in some SAP database to get the customer’s status. With all the aggregated information from your business-systems, you may want to notify, for example, the customer and/or and employee by email.

 

Some next webform may be very similar, except you don’t need to do the check with CRM or SAP, you just want to archive the webform and notify the sender by email.

 

For another process you may need to publish some information from your DMS to your Content Management System (CMS), but first you need to enrich that data from some peripheral legacy application.

 

All these requirements may change rapidly. New webforms may start very similar or very different processes. Back end applications may change their versions or the organization may replace some application. Of course, you do not want to redesign your whole process or rebuild very similar logic over and over.

 

 

Monolithic Orchestration

It’s obvious that this calls for some sort of ESB solution. The requirements are too complex and are too much subject to change to build into an monolithic application. But even if you were to go ahead and try to build this into a Message Broker like BizTalk, it’s easy to get into trouble. You start off building the upper business case as one or more orchestrations, do all the hard integration work and get it into production. It works so well that another branch in the business wants what they feel is “basically the same thing”. Except, it’s not the same thing. Your solution can do one process for one specific input. You now need to redesign your original solution to incorporate the new requirements. You may be tempted to build some workarounds so that it sort of works too for a second process. Then, the organization decides to use a different DMS. Now you have to rebuild all processes that connect to the old DMS.

 

 

Using EZBus, you would approach this problem differently. EZBus lets you 'chop up' the problem into much smaller, manageable pieces and strongly focus on reuse. So you’d start out looking at which possible separate endpoints (chunks) you’d need in order to interface with all the involved back end systems. For each endpoint (next chunk) you want to scope the functionality such that it can be used generically. Consider functional scopes such as "receive webform", "register customer", "register order" or "send email".  When you have sufficiently granular endpoints you just 'stitch' these chunks together again in an EZBus configuration, that then makes up your runtime EZBus process. 

For the next process, you look at which endpoints you already have, and go from there. Sometimes all you need is to copy an old EZBus configuration and turn it into a new one where you do less steps. Sometimes you need to add steps.

 

Configure steps

Sometimes you need exactly the same steps but you just need to perform a (slightly-) different mapping. Say you need to save customer information from a different webform by some new supplier. That different webform will probably have all data you need, but that data may be structured or named differently. You already built your generic way to talk to your CRM application, so all you need to do is map the incoming data differently. The rest of the endpoint’s behavior (which is specific to the CRM package, not to the incoming data!) stays the same, even better; none of the remaining components you previously configured in your process needs any change. This means you now only have to think about problems specific to your business case at hand and not about (re-)building, (re-)testing, (re-)deploying and all the rest. You don't have to take running processes offline to upgrade etc. etc. Imagine how much more flexible you can react to business requirements and still reduce overall development cost!


 

 

Sample UC 2 
Sample UC 3 
 
Sample UC 1 

Use Case 2 

 

Consider this scenario:

 

Your organization has multiple branches. Some of those branches have their own IT staff and they develop their own automated business processes. They may connect to some of your organization’s shared applications, like SAP. They may use some databases that are local to the branch and they may have chosen to build interfaces with some SaaS applications in the Cloud, for instance a CRM product like SalesForce. You are very successful, because you have very many effective automated business processes, so all your talented staff have accurate and current information at their disposal. As time passes, your organization grows, the number of branches grows and you get more and more automated business processes.

 

  It gets harder and harder to update and expand your automated business processes, because all those processes weren’t developed using a central (ESB) strategy. Every branch has built its own interfaces and now you have a multitude of connections that do essentially the same but need to be supported separately. It gets more and more difficult to support the landscape because of the ‘spaghetti’ of connections between all the applications, both on premises or in the cloud. Every change to your processes takes longer and longer because of the impact on so many subsystems.

 

 

 

 

 

 

 

 

Using EZBus this scenario wouldn’t play out this way. First of all, you would first look at which connections to what application you would need to meet the requirements of all branches. Then EZBus would help you create those processes in such a way that new requirements can be easily built as an extension of the old one, reusing the parts (essentially untouched, so no need for rigorous regression testing) of the process that don’t need to change. New branches which have processes with similar requirements now have a catalog at their disposal of already successfully running EZBus processes, so their first idea will not be to reinvent the wheel, but instead, to reuse. They may have requirements that are not offered, but often it makes sense to reuse a process that covers 90% of the requirements, than build one that covers 99% percent, for ten times the cost.

 

 All your connections are managed by BizTalk so there’s a single place to support those connections, and you can integrate this with your (perhaps already in place) operations management system. On top of that, EZBus offers a Monitoring Client that allows you to monitor your processes on a functional level. Your branches can just load this tool safely through the web and see their processes.


 

Sample UC 2 
Sample UC 3 
 
Sample UC 1 

Use Case 3 

 

Consider the following scenario:

 

You are a growing organization that needs a way to organize automated business processes. You have a number of applications on premises and you need to have interfaces with services in the Cloud as well. But you don’t have the IT staff to support a full ESB implementation. With EZBus it’s possible to host the complete installation in the Cloud. You don’t have to worry about supporting all the software that’s needed to make those EZBus processes run. You can design, build and test your EZBus processes on premises and deploy the production processes in the Cloud! 

  

 Because it makes full use of BizTalk Server, EZBus is fully compatible with Microsoft's Integration stack, both on premises and in the Cloud! You can choose to run EZBus in the Cloud, or you can connect EZBus applications to services living in the Cloud using Windows Azure. Whichever strategy you choose works with EZBus!

Sample UC 2 
Sample UC 3 
 
Support 

Support 

EZBus customers have access to support from consultants with long experience in the field.
They know ESB, SOA, WCF, webservices, C#, .NET, XML, XSD, XPATH, XSLT, BizTalk, SQL.. you name it.
They will always try to help you find a satisfying solution for the business-problem at hand you are trying to solve. 
Whether you need to know how to implement a specific pattern in EZBus, require general help on development with e.g. XML or XPath for your mappings or something changed in your environment that broke a crucial process; we care about you getting your business done with EZBus and will 'get our hands dirty' assisting you! 

EZBus licenses also include 'vouchers' when you experience 'Support Incidents'. 
These 'vouchers' give you high priority access to support* when you need it most.

 

 

 

(*support on location can still be subject to travel-cost, housing etc. when on premises presence is required, depending on geological location)

Wiki 
FAQ 
 
Support 

Wiki 

EZBus comes with a comprehensive wiki-site that gives users architectural and technical information on the entire EZBus-suite, ranging from its auto-discovery landscape, its components and all its tooling. 
You can find advice, guides, instruction videos and best practices on EZBus solutions.

EZBus - wiki

In addition, licensed users get access to all sections and the full technical reference of the EZBus api that easily lets you build the most advanced endpoints.

Wiki 
FAQ 
 
Support 

Frequently asked questions 

  • Q:

We already use BizTalk and have several components in production, can we still start using EZBus?

  • A:

Yes, in most cases you can install EZBus into your existing environment and start using EZBus without breaking your existing logic.

 
  • Q:

What versions of Microsoft BizTalk are supported?

  • A:

Currently we support BizTalk 2006r2 to the recently released version 2013.
Future versions will be supported as soon as possible.

 
  • Q:

We would like to switch to EZBus, but have created many complicated mappings that cost us a great deal of time, can we reuse them?

  • A:

Yes, in almost all cases we can execute your old mappings dynamically within EZBus. Many times actually even faster than native!

 
  • Q:

We use source control and collaboration tools suchs as Team Foundation, SVN or similar. Can we still use EZBus?

  • A:

Yes, all artefacts that are created with the EZBus-tools can be stored into any of the VisualStudio compatible source control solutions.

 
  • Q:

We are only a small organisation without a large IT-staff, can we still use and afford EZBus?

  • A:

Yes, as EZBus is aimed at simplifying development and reducing development, administrative and maintenance costs, any organisation can benefit from EZBus. Consider starting with a 'Standard'-license. When demand grows you can always add more or switch to 'Enterprise'. You can also consider using EZBus as a SaaS-solution!

 
Wiki 
FAQ 
 
Contact 

Contact 

If you have any comments or questions regarding EZBus or would like to receive a product brochure, please feel free to contact us.
We are happy to explain the product's possibilities to you and discuss if EZBus would be a valid and sensible choice for your organisation.

 

Your message has been delivered.
Thank you for taking the time to contact us.
We will contact you as soon as possible.
Organisation *
Mr./Mrs Mr.*
Mrs.
Firstname or initials *
Surname *
Email *
Question or comment *

 

Visiting address (please make an appointment);

iTrajectum B.V. - EZBus sales offices at

Color Business Center - Utrecht
Papendorpseweg 99
3528 BJ  UTRECHT
THE NETHERLANDS

 

Alternatively we can be reached by:

 

email on: info@ezbus.nl, info@ezbus.net or ezbus@itrajectum.nl

phone during office hours (CET) on: +31306662517 (landline) or +31625004670 (mobile)
 
traditional mail:
EZBus by iTrajectum
Utrechtseweg 47g
3544 NA  UTRECHT
THE NETHERLANDS 

 

Disclaimer 
 
 
Contact 

Disclaimer 

EZBus® or iTrajectum® make no representations or warranties with respect to this publication, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. EZBus® or iTrajectum® reserve the right to make changes to any and all parts of this publication at any time, without any obligation to notify any person or entity of such changes.

 

Terms & Conditions

Dutch Fenit terms and conditions as deposited in 2003 apply. 
Click here to download

 

Trademarks

EZBus®, iTrajectum® and their logos are registered trademarks of iTrajectum B.V.
Other product and company names mentioned in this document may be the trademarks or registered trademarks of their respective owners.

 

Copyright

© 2013 EZBus. All rights reserved. EZBus, iTrajectum, the EZBus logo and the iTrajectum logo are registered trademarks or trademarks of iTrajectum B.V. within the Benelux and/or other countries. All other names and brands may be claimed as the property of their respective owners.
Pricing and specifications subject to change without notice.

 

No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.

Disclaimer