FAQ

What Mechanisms are used by ModelBus for exchanging data?

ModeBus uses plain Web Service technology for transmitting data and events. This is done by using a particular interaction pattern which realizes essentially a call-by-reference semantic, which relies on unique identifiers (based on URIs) and a repository. The data integration is achieved by using Model-Driven Techniques, i.e. metamodels, models, transformation.

How is data linked coming from different sources (tools)?

This is done by storing relevant trace information in the ModelBus Repository. The trace information (e.g. who, when, why) can be created either automatically (e.g. by a transformation engine) or manually (e.g. by a trace editor or a modeling tool). The trace information is based on references.

What are features of the ModelBus Repository?

ModelBus comes with an inbuilt Model Repository. ModelBus Repository is an efficient storage space which can be used for models as well as for plain artifacts. This repository implements a standard repository interfaces and can be characterized with the following feature list:
•    Consistent management of models and other artifacts
•    Notifications
•    Support of arbitrary metamodels (and migration of these over time)
•    Model-driven and rule-based access rights management
•    Standard SCM functionality (e.g. versioning, branching, tagging, …) is supported
•    Accessibly via standard Web Service technology
•    (Meta-) Model dependency management
•    Model fragment support
•    Locking on model element level

What is the effort needed to connect a tool to ModelBus?

This is very much dependent on the tool that has to be connected and its interface. First of all you need to know if you want to make the tools functionality available as a service to other tools or if you want to use the tools editor and share its data or both. Typically a two-layer approach can be taken. First layer deals with the tool specifics (e.g. definition of a tool metamodel, tool plugin) and the second layer deals with the data integration (model transformation from tool metamodel to other metamodels). You may contact the ModelBus Team in order to get support and help for integrating a tool. However, the overhead compared to an file based EMF import export is two lines of code.

Is it possible to use my favorite BPEL engine to orchestrate my development process?

At this point ModelBus orchestrations can be run with ActiveBPEL only. One of the major improvements in ModelBus 2.0 will be its general compatibility with other web services. Hence, it should work with any orchestration engine you would like to use. The current implementation of ModelBus 2.0 has already been proven to work with Intalio (Apache ODE).

I want to use JMI instead of EMF. Is this possible?

Currently not, but the architecture is sufficiently flexible to accommodate different code generators for various platform and technology combinations. If there is sufficient demand, it is likely that we will provide a JMI adapter generator in the future.

I want to use ModelBus in a .NET environment. Is this possible?

Yes. Currently, this still involves some manual work. However, there will be automatic code generation for .NET in ModelBus 2.0.

Do I have to generate specific EMF model code in order to use ModelBus?

No.

What can be expected as new major features of ModelBus in near future?

ModelBus is comprehensive software which helps you to solve your integration problems. However, there are a couple of features we are targeting on and which are demanded to make ModelBus even more effective. The following list includes a selection of upcoming features:
•    Incremental support
•    WEBDAV
•    Server Plugin Extension Points (based on eclipse plugin mechanisms)
•    Enhancements in Eclipse Team Provider
•    Atomic Commit
Do not hesitate to contact the ModelBus Team, if you like to have additional features realized or to suggest certain priorities on them.

Is it possible to integrate my already existing web services into ModelBus?

Yes, there are a number of different ways to achieve this:

1. Wrap the service with a ModelBus adapter to make it aware of models.
2. Integrate calls to your service via service orchestrations.
3. If you simply intend to share data, you should implement the ModelBus repository interface.

Is it possible to use multiple, technically different model repositories simultaneously?

Yes, if these repositories implement the ModelBus repository interface. Please note, that different kinds of repository interfaces with different functionality are available.

Is it possible for me to access a model with transparent conversion of type (if conversion is possible)?

Yes, this is possible. If a type conversion is available, a model will be automatically converted for a service invocation.

I want to be notified if something happened in the ModelBus. Is this possible, and how can I access the information?

Every action on the ModelBus can be tracked by listening to specific ModelBus events.

What is the granularity of access control?

Access control is provided on the model and service level.

I use PHP for development, can I use ModelBus?

Yes, you can.

Is there a workspace concept in ModelBus?

Yes, there is! It is a hierarchically organized set of directories containing relevant artifacts such as models and transformations.

Is it possible to find out all referenced models?

Yes, referenced models are available in the “workspace” implicitly.

If you are not satisfied with the answers listed above or have further questions not yet mentioned here at all, please feel free to contact us at info [at] modelbus [dot] org or visit the contact section.