Differences between EBI 2.6 and EBI 3
EXTOL Business Integrator (EBI) gives users a single, middleware platform that enables them to integrate data and applications without coding. EBI is a apply-to-many tool that allows users to build maps, business rules, processes, event triggers, and manage exceptions and alerts.
Object Comparisons - See the EBI 2.6 -> EBI 3 differences between Rulesets, Endpoints, Database Bindings
All objects are now housed within Projects.
Keep Projects separated by trading partner and document type to help you find what you need faster when changes need to be made. A project can be viewed as an EDI trading partner or base objects for an ERP such as SAP, JDEdwards, or BPCS.
By using Projects trading partner is made easier and much more efficient. We see the efficiency when we use the EXTOL EDI Project Wizard. With EBI 3 we are able to compartmentalize our related objects, users will be able to identify dependencies. This reduces the risk of changing unrelated objects and saves users time while testing a solution.
Multiple users can work on a single Project by downloading their own copy of a Project from an SVN repository, then synchronizing their changes with the source Project.
Users can share resources as well, eliminating duplication of similar work. For example, many EBI 2.x users probably have duplicate schemas for databases, EDI, flatfiles and etc. These type of duplications can be removed.
With multiple users working on a single Project, keeping track of changes is vital. Using SVN from within the EBI Studio allows users to easily see a log of changes made to each object and who made them. With the history log, objects can be reverted back to a previous state, which makes experimental changes safer.
This version control also allows you to manage changes when they occur. If two team members make different changes to the same section of a resource, the SVN allows a side-by-side comparison with the differences highlighted and provides tools to make consolidation easy.
The development, test, and production environments are completely separated. The Studio allows users to test scenarios on their own Local Test Server without touching anything on the remote production and test servers.
Once a solution has been successfully completed, it can be pushed from the Studio to a remote test server, then to a remote production server. All Servers can be accessed from the Studio, but the Studio can be used to develop independently without being connected to an outside server.
Using a single interface, administrators can control which users can push their solutions to the remote servers. JDEdwards users can think of this process as a CNC related step. In EBI we will be deploying projects, just as a CNC task would be to build/deploy packages.
The Ruleset editor has been given a facelift with these additional features:•The Properties view provides a centralized panel to view data for individual Rules and entire Rulesets. Users can modify a Rule and its conditions, add comments on a Rule, or change the Ruleset's Runtime properties from this panel. Users can even view Schema node properties (such as field length) from within a Ruleset with this view.
•The new layout capitalizes on use of widescreen monitors, giving users easier access to more editing options on a single screen.
•Condition values are displayed in-line with the Rule they affect, so users can determine with a glance how a Rule affects data.
•Node icons give users at-a-glance data type identification.
•Users can copy and paste Rules from one Ruleset to another.