Flexibility about the “camel-case” notation in the naming convention.

schemas, namespaces, service names, etc) according to a specific naming convention. There are many features in our product backlog to be added to the tool. The tool has been released publicly in its first stable version. The jar file is executable and can be started either with a double click on it or using the java command line with the –jar option. The tool runs in any operating system hosting a minimum version of Java 8. Baseline TIBCO BusinessWorks processes are part of a “generated” folder (also this folder name is fully customizable from a configuration point of view), in order to emphasize that these processes should never be touched or modified by any developer.The tool works fine even with an empty TIBCO BusinessWorks project template, it’s enough to list only the service types to include in the final project.High level of customization of the input template structure.Services with one or multiple operations.Any combination of front-end, back-end and/or composite services.It’s possible to combine the services that will be part of the TIBCO BusinessWorks project in several ways: schema, TIBCO BusinessWorks sample processes, etc), the more accurate and complete the final TIBCO BusinessWorks project will be. The more complete the provided input resources are (e.g. The tool guarantees that all the generated resources follow the same naming convention and a standard way of working. A template structure to base the TIBCO BusinessWorks project on.The default set of properties can be overridden with specific (custom) properties defined in the input configuration file. This file is validated against an XSD structure, where all the types of the services are defined with the possibility to add specific properties. In order to maximize the flexibility of output generation the tool is driven by two types of configuration sources: Notification services asynchronous services waiting for a final notification.Back-end services to connect the ESB services towards the back-end applications.Composite services mainly meant for orchestration, service composition and routing features.Front-end or Façade services to let external applications communicate with the ESB layer.The tool allows to create different types of ESB services to cover different functionalities: A very simple interface allows the user to specify input configuration files and generate TIBCO BusinessWorks 5.x code. The tool is a Spring Boot application, written in Java. So combining these two ingredients the Serbian and the Dutch team decided to deliver a tool to automate the “boring” part of every development phase: initial BusinessWorks project setup. We have much expertise in the integration area and many of our consultants are experts in the main TIBCO integration software (i.e.

Java code generator