Identifying Oracle Service Bus Project Versions

Identifying Oracle Service Bus Project Versions


“Look around, get acquainted, see how we do things.” It’s time for another 2 Minute Tech Tip! The 2 minute clock starts now! When working in service bus projects you often run into the problem of identifying which version of a service bus project is deployed on your service bus environment. But there exists a simple solution. In the Java space, version information and meta information can be provided in a text file called “manifest.” Every Java library contains a manifest file. This file contains properties like vendor, title, specification version, and some other stuff. This mechanism can also be applied to service bus projects. The only thing you need is a source code management system like Git, and a build framework like Maven. Maven provides plugins, like the resource plugin with the filtering option and the build number plugin. With these two plugins you are able to create a manifest file. The resource plug-in creates the manifest file based on the information provided in your pom.xml, like group ID, artifact ID or version. The build number plug-in allows you to retrieve the unique ID for your commits in your Git repository. This commit ID can also be incorporated in the manifest file. With this you have everything in place to identify which version of your service bus project is deployed on your environment. The only thing to consider is, service bus only allows XML files. So when you create a manifest file you have to include it in XML text. And then you are able to deploy this file to your service bus environment. Service bus console can then be used to display this information in this file by simply clicking on the manifest file deployed with your service bus project. What did you think of that tip? “Nothing short of a miracle!” We want your opinion! Thanks for watching and stay tuned!