Version 2


    Ted has built a new purchase order web service that he wants to deploy into production.  This new web service consists of a WSDL file and numerous XML Schema files.  Ted creates and stores the WSDL and Schemas in a source code repository.  He also creates a Maven project to build his web service.  When run, the Maven build results in a WAR that includes the WSDL, Schemas, and runtime implementation of his web service.  Once the web service is complete, it must be released into production.


    System Narrative:

    System Path 1 -

    Ted runs a Maven release build, which results in Maven uploading the WAR to the S-RAMP repository.  The upload triggers a Governance Workflow to start.  The Governance Workflow will request approval for the new web service to be deployed to the Test environment.  Once approval is given, UAT can be completed.  Once UAT is completed, the test team will approve the service, at which point the Governance Workflow will deploy the service into production.  During all of this, Ted can use the UI to see the status of the service.


    System Path 2 -

    Same as above, except UAT fails.  In this case, Ted must fix some bugs and produce a new version of the web service WAR.  He does this and once again runs the Maven Release build.  Maven will upload a new version of the WAR, updating the WAR in the s-ramp repository (along with all artifacts found in the WAR).  The workflow will once again guide the lifecycle of the WAR through approvals until it reaches production.





    Related Scenarios:

    S-RAMP Scenario: Upload single or ZIP file manually

    S-RAMP Scenario: Update files manually

    S-RAMP Scenario: View version history