Achieving Continuous Integration With Tibco BW

  • 4,762 views
Uploaded on

Presentation on achieving continuous integration with SOA/BPM suite.

Presentation on achieving continuous integration with SOA/BPM suite.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
4,762
On Slideshare
0
From Embeds
0
Number of Embeds
6

Actions

Shares
Downloads
118
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

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