The potential and promise of service-oriented architecture (SOA) can be
realized by designing, developing, and deploying well-designed, flexible,
extensible, and scalable Web services, Web applications, and portlets.
Reusable enterprise class Web services encapsulate business logic and drive
business processes. A variety of clients consume these Web services without
worrying about specific implementation technologies. The user interface,
which is responsible for driving dynamic user experience, is most often Web
based. These user interfaces serve the needs of several audiences and invoke
the enterprise Web services on an as-needed basis. With Web services, the
usage patterns tend to ramp up much more quickly, and the concurrent loads
tend to be much higher than traditional applications or services. To
successfully make the transition to an SOA, the Web services need ... (more)
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 managea... (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)
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)
In my first article (WLDJ, Vol. 3, issue 6), I provided an overview of BPM
specifications in this area. I described the order change example and the
steps needed to create the business process in WebLogic Integration.
In this article, you will see how to create a process application. We can
call this application orderChange. In this application we need to create a
new process called orderChange.jpd. To start the process, we need to add a
ClientRequest received. Next we will add the Web service validate. We will be
looking in detail at the steps to create this business process in W... (more)