Application versioning has always been a challenge for the developer
community. With the introduction of Web services, this issue becomes even
more difficult as developers are dealing with a more distributed set of
components that aren't necessarily under their control.
A robust versioning strategy is needed to support multiple versions of Web
services in development. This can allow for upgrades and improvements to be
made to a Web service, while continuously supporting previously released
versions. The right versioning strategy can maximize code reuse and provide a
more manageable approach to the naming, deployment, and maintenance of your
Web services.
The issue of versioning is a complicated one, and this article does not
attempt to answer every question surrounding the versioning of XML and Web
services. However, there are some key approaches and design practice... (more)
In the first article I gave an overview of BPM and covered the specifications
in this area. I described the order change example and the steps needed to
create the business process in WLI. In the second article we saw how to
create a process application, specifically how to create the application
orderChange. In this application I created a new process called
orderChange.jpd. To start the process I added a ClientRequest received. Next
we added the Web service validate config.
In the third article I added a decision point to handle the result from
validate config Web service. The... (more)
When processes are modeled well and don't change, existing IT systems work
well. However, real business changes all the time and processes are becoming
more complex especially as the Internet is able to easily link internal and
external systems.
Business process management (BPM) can help in managing this complex and ever
changing process. The concept of manipulating data, which IT systems do
efficiently today, can be extended to business processes. Businesses can use
BPM systems, using workflow-type techniques, to control existing
applications, Web services, and human processes ... (more)
In Part 1 (Vol. 3, issue 6) of this series I gave you an overview of business
process management (BPM) and covered the specifications in this area. I
described the order change example and the steps needed to create the
business process in WebLogic Integration. In Part 2 (Vol. 3, issue 7), we
created a process application - orderChange. In this application we created a
new process called orderChange.jpd. To start the process we added a
ClientRequest received. Then we added the Web service validate config.
This month we will add a decision point to handle the result from validate ... (more)
In the first article in this series (Vol. 3, issue 6), I gave you an overview
of business process management (BPM) and covered the specifications in this
area. I described the order change example and the steps needed to create the
business process in WebLogic Integration (WLI). In the second article I
looked at how to create a process application (orderChange). In this
application I created a new process called orderChange.jpd. To start the
process we added a ClientRequest received. Next we added the Web service
validate config.
In the third article I added a decision point to ... (more)