This section describes everything that a developer of UltraESB has to know in the development phase of the integration solution implementation. This section assumes the IDE that you are familiar with being setup and ready to be used in the development process as described in the Setting up the IDE section.
All the configurations are mainly done at the ultra-dynamic.xml file which resides in the ULTRA_HOME/conf directory, a spring configuration file additionally supporting the UltraESB schema. So you may use any text editor if you are familiar with the configurations for development, but using an configured IDE helps you develop faster and enables you to test and fix issues pretty fast in the development phase.
An integration solution in UltraESB is mainly defined in the ultra-dynamic.xml spring configuration file, apart from the transports and the other deployment related configurations such as clustering, caching etc... which are configured with the ultra-root.xml spring configuration.
 | Multiple configuration files are supported Even though the ultra-dynamic.xml file has been used through out the documentation to place dynamic configuration fragments, the file name and place can be changed and it is possible to have more than one configuration files with proxy services, endpoints and sequences etc. Refer to the Configuration and Administration for more information on structuring the configuration files. |
The development of the integration solution with UltraESB must start with a proxy service, which is the only entry point for the external messages into the UltraESB. Once you have the entry point configured, you may define the exit point/s for the messages that are coming in through the proxy service entry point. Finally the rest is connecting these two points with your mediation logic. So in effect the development process can be broken down to 3 steps as follows.
- Entry point configuration with the Proxy Service Configuration
- Exit point configuration with the Endpoint/Destination Configuration
- Wiring the above 2 points with the Sequence and Mediation Development
In addition to that, the solution might require new transport configurations too and you may refer to the Configuration and Administration for enabling/configuring transports for the UltraESB.
Once you have the solution implemented with these 3 steps, you can Test and Debug the solution.
Labels