Your SlideShare is downloading. ×
0
Achieving Continuous Integration with  Tibco BusinessWorks <ul><li>Vijay Narayanan </li></ul><ul><li>http:// softwarereuse...
Technologies Involved <ul><li>Tibco BusinessWorks </li></ul><ul><li>Apache Ant </li></ul><ul><li>Apache Axis & XML Beans <...
Your team’s passion for quality code, defect detection, and prevention
Act I - Using simple, effective test tools <ul><li>Used command line tools for smoke testing deployments on a development ...
Act II - Automated Tests  <ul><li>Used Apache Axis2 & XML Beans to generate web service stub classes and run each test cas...
Act III - Cruising with Continuous Integrations <ul><li>Found on the web a Apache Ant script for deploying and starting Bu...
Continuous Integration High Level Steps
Some Sample Screenshots
JUnit Results Summary Email
CruiseControl Dashboard
3 Key Benefits <ul><li>Confidence  that your processes work as expected prior to your client discovering broken code/funct...
But the biggest benefit...
Is a charged up team ready to change, improve, and support the code base on a  continuous  basis!
Upcoming SlideShare
Loading in...5
×

Achieving Continuous Integration With Tibco BW

5,312

Published on

Presentation on achieving continuous integration with SOA/BPM suite.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
5,312
On Slideshare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
129
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Transcript of "Achieving Continuous Integration With Tibco BW"

  1. 1. Achieving Continuous Integration with Tibco BusinessWorks <ul><li>Vijay Narayanan </li></ul><ul><li>http:// softwarereuse.wordpress.com / </li></ul>
  2. 2. Technologies Involved <ul><li>Tibco BusinessWorks </li></ul><ul><li>Apache Ant </li></ul><ul><li>Apache Axis & XML Beans </li></ul><ul><li>JUnit </li></ul><ul><li>Subversion for source code control </li></ul><ul><li>CruiseControl for Java </li></ul>
  3. 3. Your team’s passion for quality code, defect detection, and prevention
  4. 4. Act I - Using simple, effective test tools <ul><li>Used command line tools for smoke testing deployments on a development environment via XML message payloads </li></ul><ul><li>It was super easy to run and very effective in testing web services against BusinessWorks - We usually ran it after deploying our BusinessWorks engine on the Server </li></ul>
  5. 5. Act II - Automated Tests <ul><li>Used Apache Axis2 & XML Beans to generate web service stub classes and run each test case as a JUnit test case </li></ul><ul><li>Created generic ant scripts for compiling JUnit tests and reporting test results using JUnitReport </li></ul><ul><li>Ran our full battery of test cases as an automated Ant script daily. This was a manual event… </li></ul>
  6. 6. Act III - Cruising with Continuous Integrations <ul><li>Found on the web a Apache Ant script for deploying and starting BusinessWorks engine on windows Tibco Administrator </li></ul><ul><li>Integrated CruiseControl with Subversion to build and deploy our ‘latest’ processes and JUnit to run our automated tests on a continuous basis </li></ul>
  7. 7. Continuous Integration High Level Steps
  8. 8. Some Sample Screenshots
  9. 9. JUnit Results Summary Email
  10. 10. CruiseControl Dashboard
  11. 11. 3 Key Benefits <ul><li>Confidence that your processes work as expected prior to your client discovering broken code/functionality </li></ul><ul><li>Agility – Upgraded to newer version of Tibco iProcess within a week </li></ul><ul><li>Defect detection and prevention - discovered and fixed 600+ defects before deploying to server environment! </li></ul>
  12. 12. But the biggest benefit...
  13. 13. Is a charged up team ready to change, improve, and support the code base on a continuous basis!
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×