Gain Competitive Advantage with Rapid Integration to your Customers’ Environment

Add a broad spectrum of connectivity to hundreds of data sources, along with robust data transformation services and data workflow logic to your software systems with Enterprise Enabler, the full spectrum data integration technology that is 100% .NET-based. Package the full capability of Enterprise Enabler!

Flexibility

No need to worry about using the integration tools du jour at each customer’s site, but rather provide connectivity to those environments as a part of your offering.

Harvest Enterprise Enabler’s capabilities in a way that best fits your application roadmaps, and in a way that is most appropriate for your end-user community.

Benefits

• Moves data anywhere at any frequency
• Provides a flexible and extensive framework for robust functionality
• Reuses the .Net language features to customize applications
• Extends and evolves with and for the users
• Reuses AppComms (connectivity), functions, transformations, processes, nodes, etc.
• Supports any standard but does not require standards

SOA:

• No application server required.
• Zero coding necessary to expose or consume web services.
• Complies with SOAP, but does not require SOAP for all or any components.
• Provides web services using multiple sources
• Functions as a web services client

E-Commerce:

• Easily handles connection to ERP, CRM, Data Stores and Files
• Sends information via various protocols SOAP, FTP, HTTP, etc
• Handles the interchange between hierarchical and relational data

Technical OEM Models

Stone Bond allows you to leverage EE’s capabilities in 3 ways, as follows.

Loosely-Coupled Model

Whatever platform, language, and communication protocol your products use, you can package Enterprise Enabler as a tool that you (or your customer) can use to quickly integrate your software or SAAS to whatever systems, data sources, or middleware that is in place at your customer, and also build the data flow logic that indicates when you want the data to be moved, who you want notified, and how you want error conditions handled. 

Using Enterprise Enabler’s intuitive Graphical User Interface, implementers will build reusable metadata that reflects the specific requirements of your software. On site or remotely, you can make clean, rapid, secure connectivity to your customers’ systems.  Once implemented, you can use the one-click deployment to the run-time server. Where appropriate, you can use Enterprise Enabler’s remote monitoring to troubleshoot the integration.

With this loosely-coupled model, no change is required to your product. All the responsibility for integration is absorbed by Enterprise Enabler.

Tightly-Coupled Model

A tightly-coupled OEM model puts all the control in the hands of your product developers, particularly for .NET based applications. The functionality of the process, transformation, and data access layers is available via web services and .NET objects. That means that EE will be embedded in your application as opposed to being a separate executable. In most cases, you would want to build the customer-specific integration (metadata) using Enterprise Enabler’s GUI, and at run time you would access the metadata instructions for integration from your application, where the run-time functionality is embedded. In some cases, such as for BI applications, you may want to give your end users the ability to define where they want the data to come from and how to map it. In that case, you can provide subsets of EE- Studio embedded in your application.

Enterprise Enabler Extension Model

Enterprise Enabler is effectively an extensible composite application development platform that does not require that all components be web services. EE can be used as the overall orchestration and controller that initiates your new or existing components based on the logical workflow you design using EE Studio.  You can incorporate any of the pre-built nodes in your application by dragging, dropping, and filling in a few blanks. The environment extends and customizes to your needs as you build and incorporate your own nodes. Embedded .Net compilers are accessible from within the environment, so you can add snippets of code as needed. Continuous design time validation in a single environment for design, test and deployment ensures a most efficient development environment. Of course, the integration with customer information then becomes an inherent capability of your application.

This model is a good one for companies that have a .NET based product, or that want to stage forward into one. Your current modules can initially be initiated from the environment with surrounding control logic, and newly architected .NET components or web services can be incorporated as they become available.