Versioning of Web services in JBoss Fuse

Solution Verified - Updated -

Environment

  • Red Hat JBoss Fuse
    • 6.x

Issue

  • We want to know the best solution/strategy for versioning of Web services hosted in FUSE fabric server from a Governance stand point!
  • Can you please provide some references on how to version Web services from a Governance ?

Resolution

  • All web services deployed in Fuse 6.1 in a fabric are configured into the fabric registry and so appear in the API console; so you can browse your WADL / WSDL and so forth.

  • We also have a (tech preview) Gateway which can provide discovery and load balancing between web services, which you can find in this link.

  • While API versioning is a huge and complex topic with lots of approaches; the gateway does support a simple approach to versioning or lets you expose explicitly versioned URIs:
    http://fabric8.io/gitbook/gateway.html#versioning-rolling-upgrades.

  • The idea being to run a local gateway on each machine; then for all the containers on that machine to use the same fabric version; so that it sees a consistent set of back end services for that version. Then you can support multiple versions easily by different machines working on different fabric versions.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments