There are lots of folks out there developing applications on top of Oracle SOA Suite, and those applications are becoming more critical. I believe we have reached the time when it is necessary to start adopting some more industrial-strength development, testing, deployment and delivery processes for SOA applications.
In this series of posts, I am going to discuss development lifecycle issues and present a method to use modern tools and techniques in a SOA development environment.
Let’s get started:
- SOA Development and Delivery
- Version Control
- What is wrong with how we are doing it now? -or- Why do we need to change?
- A first look at Robot
- Writing a Robot Remote Library
- Setting up a Maven Repository Manager (Binary Repository) with Artifactory
- Doing more with the WebLogic Maven Plugin (Robot, Selenium and Sonar too)
- SOA Maven support added in 12c
- Creating SOA Applications using Maven
- Running SCA Tests from Maven
- Adding a Human Task to our SOA Maven build (talks about using MDS)
- more to come…
You may also be interested in:
- Introducing SOA into your environment
- What BPM adds to SOA
- Choosing between BPMN and BPEL
- Canonical data, abstract WSDLs, MDS
- Purging data (and see this whitepaper)
- Tuning Database
- Our series on Continuous Integration
- Our sample custom worklist
- Starting SOA with a Node Manager
- An introduction to Human Workflow in 11g
- Using the TaskQueryService from .Net
- Using the database as your policy store
Stay tuned. Please feel free to leave a comment if you have a suggested topic.
Pingback: Version Control | RedStack
Pingback: SOA Version Control by Mark Nelson | SOA Community Blog
Pingback: A Roadmap for SOA Development and Delivery | RedStack