Java Reference
In-Depth Information
different services that you will need to maintain, version, decommission, and migrate clients
for.
Ideally, your repository product should be standards-based and offer both a visual client
browser and an API that you can use to invoke it programmatically. Repositories are typically
integrated with the developer IDE so that during application development, programmers can
simply browse the list of available services just as they would see classes in a selected pack-
age.
Many of the better enterprise repositories also make available a view for business users, or at
least business analysts who work at the process level. As your SOA matures, and your ser-
vice catalog is built out, you may find that you want to connect your services using executable
business processes. Such business processes will be sewn together using services available in
your repository. So a business analyst using something like BPMN within the IDE or studio
tool will be presented a different view from that of the developer based on LDAP credentials,
and see documentation and high-level details of each service. The analyst can then drag and
drop items from the repository catalog to build the executable process.
Once the process is complete, the analyst can typically make a change to it and immediately
see the impact across schemas and other artifacts participating in the composite service. Fre-
quently, the impact analysis is presented in a graphical interface that shows the interconnec-
ted web of resources. This can be very handy in helping to ensure that your business runs
smoothly.
