Scenario 3: Deploy requests to multiple deployment areas

This scenario demonstrates how to deploy Dimensions CM requests to modify the Qlarius web application.

This scenario is similar to Scenario 2: Deploy requests to a single deployment area. The main difference is that multiple requests are deployed in a specific sequence to multiple deployment areas.

Note: To run this scenario, first set up the environment, as described in Prerequisites.

Scenario overview

  • The release manager raises an enhancement request.

  • The development team lead primes two child tasks from the request and delegates them to separate developers.

  • The developers modify items, deliver the modifications and relate them to the tasks, build the tasks, and capture the build outputs in Dimensions CM.

  • The team lead promotes and deploys the request and tasks in a specific sequence to the SIT stage and deployment areas, and then promotes them to the QA stage.

  • The QA manager deploys the request and tasks to the QA deployment areas in the same sequence and then promotes them to the PRE-PROD stage.

  • The release manager deploys the request and tasks to the PRE-PROD deployment areas in the same sequence, and then promotes and deploys them to the LIVE stage and production environments.

Back to top

Scenario information

The following stream is used: QLARIUS:JAVA_BRANCHA_STR

  • There is a separation of duties between the employees at the following stage transitions:

    • SIT to QA

    • QA to PRE-PROD

  • A build is only required at the DEV stage.

  • Deployment is to multiple areas at each stage. The following deployment areas are used:

    Stage Deployment area Deploy by Default enabled on area? Server type
    Location

    DEV

    LCL_DEV_JBRNCHA_AREA01 Yes RDBMS London
    LCL_DEV_JBRNCHA_AREA03 Yes Web application London
    SIT LCL_SIT_JBRNCHA_AREA01 Yes RDBMS London
    LCL_SIT_JBRNCHA_AREA03 Yes Web application London
    QA LCL_QA_JBRNCHA_AREA01 No RDBMS London
    LCL_QA_JBRNCHA_AREA03 No Web application London
    PRE‑PROD LCL_PP_JBRNCHA_AREA01 No RDBMS London
    LCL_PP_JBRNCHA_AREA03 No Web application London
    LIVE LCL_LIVE_JBRNCHA_AREA01 No RDBMS London
    LCL_LIVE_JBRNCHA_AREA03 No Web application London
    LCL_LIVE_JBRNCHA_AREA04 No RDBMS New York
    LCL_LIVE_JBRNCHA_AREA05 No Web application New York

The deployment sequence to these areas is important as the database schema must be updated before the web application code that uses it:

  • During deployment to the RDBMS areas post deployment scripts run to remotely shutdown the application servers and execute the SQL script that has been deployed to update the database schema. The update to the database is more likely to go wrong and is harder to fix than the file movement. Therefore the database is updated first so that if anything goes wrong there is less work to restore.

  • After deployment to the RDBMS server has been completed successfully, deployment continues to the web application server area. The scripts in the web application server area then re-start the servers.

  • Only content relevant to the specific areas is deployed, for example, the Linux RDBMS server area receives the SQL script files and the Linux web application server area receives the Jar files.

For a list of the promotion and deployment privileges required by the users, see Scenario privileges.

Back to top

Scenario prerequisites

On your local machine, create work areas for the users Dinesh and Dawn, for example:

  • C:\streams\JAVA_BRANCHA_STR\dinesh

  • C:\streams\JAVA_BRANCHA_STR\dawn

Back to top

Run this scenario

The following table describes the tasks performed in this scenario.

Action Procedure

The release manager raises an enhancement request.

Changes are required to the Qlarius web application. Rita, the release manager, raises an enhancement request to manage the change.

  1. Log in to the Dimensions CM web client as Rita.

  2. Switch to the following stream: QLARIUS:JAVA_BRANCHA_STR.

  3. In the Requests tab, in the toolbar, click New and select CR. The New Request dialog box opens.

  4. In the Title field, enter Implement support for Qlarius iPhone app.

  5. In the Detailed Description field, enter a description.

  6. In the Attributes tab, from the Severity/Priority list, select a value.

  7. Click Submit and then Close.

The new Dimensions CM request is added to Rita’s request inbox with the following ID: QLARIUS_CR_n.

By default the request is at the DEV stage when it is raised.

The release manager delegates the request to the team lead.

Rita delegates the request to the development team lead, Ted, whose team is responsible for maintaining Qlarius.

  1. Select the request, and in the toolbar click Delegate. The Delegate wizard opens.

  2. Check that the Capability option is set to Secondary.

  3. From the Role to Delegate list, select IMPLEMENTOR, and click Next.

  4. In the Candidate Users Authorized for Role Assignment list, select Ted, and click Add.

The wizard closes automatically. Dimensions CM sends an email to Ted notifying him that a request has been added to his Request inbox.

The release manager actions the request to its next state.

Rita actions the request to its next state, UNDER WORK.

  1. Select the request, and in the toolbar select Action. The Action wizard opens.

  2. Check that the To Next State field is set to UNDER WORK.

  3. Click Finish and then OK. The request is removed from Rita’s request inbox.

  4. Log out of the web client.

The development team lead primes two child tasks from the request.

Ted reads the email, views the request in his Request inbox, and does some design work to see what parts of the application are affected. He primes two child tasks from the request.

  1. Log in to the web client as Ted.

  2. Switch to the following stream: QLARIUS:JAVA_BRANCHA_STR

  3. In the Requests tab, select the Request inbox.

  4. Select the request that was raised by Rita. In the toolbar, click Prime, and select Task. The Prime Request dialog box opens.

  5. Change the default title to Implement support for Qlarius iPhone app (Java).

  6. Click Submit and then Close.

    The new child task is added to Ted’s request inbox with the following ID: QLARIUS_TASK_n.

    By default the child task is at the DEV stage when it is raised.

  1. To create a second child task, repeat steps 4 to 6 and change the title to Implement support for Qlarius iPhone app (sql).

The development team lead delegates the tasks to separate developers.

Ted delegates the first child task that he primed, Implement support for Qlarius iPhone app (Java), to Dinesh, and the second child task, Implement support for Qlarius iPhone app (sql), to Dawn. Both are developers in his team.

  1. Select the first child task that Ted primed, and in the toolbar click Delegate. The Delegate wizard opens.

  2. Check that the Capability option is set to Secondary.

  3. From the Role to Delegate list, select IMPLEMENTOR, and click Next.

  4. In the Candidate Users Authorized for Role Assignment list, select Dinesh, and click Add.

    The wizard closes automatically. Dimensions CM sends an email to Dinesh notifying him that a task has been added to his Request inbox.

  5. Repeat steps 1 to 4 for the second child task, and select Dawn as the candidate user.

The development team lead actions the tasks to their next state.

Ted actions the tasks to their next state, UNDER WORK.

  1. Select both child tasks, and in the toolbar select Action. The Action Multiple Requests dialog box opens.

  2. Click Finish. The tasks are removed from Ted’s request inbox.

  3. Log out of the web client.

The first developer updates their work area from the stream.

Dinesh reads the email and checks his Request inbox. He does some research, identifies the item that needs to be modified, Autoquote.java, and updates his work area.

  1. Log in to the web client as Dinesh.

  2. Switch to the following stream: QLARIUS:JAVA_BRANCHA_STR.

  3. Change Dinesh’s work area to the one that you created earlier in Scenario prerequisites.

  4. In the Items tab, in the Dirs tab of the navigation pane, expand Qlarius Underwriter > qlarius and select interfaces.

  5. In the toolbar, click Update. The Update from Stream wizard opens.

  6. Click Next.

  7. Click Finish and then Close. Dinesh’s work area is updated.

The developer modifies the item.

In Dinesh’s local work area, edit Autoquote.javalocated in this folder: Qlarius Underwriter\qlarius\interfaces.

For the purpose of this scenario, make a minor edit, for example, add a comment to the top of the item.

The developer delivers the item and relates it to the task.

Dinesh delivers the modified item to Dimensions CM and relates it to the task that is delegated to him.

  1. In the Items tab, in the toolbar, click Deliver. The Deliver to Stream wizard opens.

  2. Check that the Modifications option is selected.

  3. Click Next.

  4. Verify that AutoQuote.java is selected, and click Next.

  5. In the Relate to Request(s) field, click Select. The Select Request wizard opens.

  6. From the Product Name list, select QLARIUS.

  7. From the Type Name list, select TASK. Click Next.

  8. Select the child task that is delegated to Dinesh and click Finish.

  1. In the Deliver to Stream wizard click Finish and then Close.

The developer verifies that the item was automatically deployed to the DEV areas.

The Deploy by Default option is enabled for the DEV area, so when Dinesh delivered the item, it was automatically deployed. He checks that the item was successfully deployed.

  1. Select the Deployment tab.

  2. To view information only for the current stream, do the following:

    1. In the navigation pane, click the filter button in the top right corner.

    2. Select Show Current Stream.

  3. Select the History tab, and in the navigation pane select the DEV stage node.

  4. In the content pane, verify that the AutoQuote.java was successfully deployed to both DEV deployment areas (there is a separate entry for each area):

    • LCL_DEV_JBRNCHA_AREA01

    • LCL_DEV_JBRNCHA_AREA03

The Event Result column should display Succeeded.

The developer builds the task and captures the outputs.

Dinesh builds the child task in the DEV web application deployment area and captures the build outputs in Dimensions CM against the task that is delegated to him.

  1. In the Requests tab, select the Request inbox.

  2. Select the child task, click Build in the toolbar, and select Build. The Run Build wizard opens.

  3. In the Build Configuration field, accept the default configuration.

  4. From the Build Stage list, select DEV.

  5. From the Build Area list, select LCL_DEV_JBRNCHA_AREA03. Click Next.

  6. Select the option Check in build outputs automatically. This checks the build outputs into Dimensions CM.

  7. To specify the request that the build outputs will be related to when they are checked into Dimensions CM, in the Specify the Request(s) field, click Select. The Select Request wizard opens.

  8. Specify the following details:

    1. From the Product Name list, select QLARIUS.

    2. From the Type Name list, select TASK, and click Next.

    3. Select the child task that is delegated to Dinesh, and click Finish.

  9. In the Run Build wizard, click Next.

  10. Accept the default build option selections (none) and click Next.

  11. Accept the default target selection options.

  12. In the target list, select Jar Files. Click Next.

  13. Review the summary of the build command, and click Finish.

  14. (Optional) To monitor the progress of the build, click the Job <ID number> link.

  15. Click Close.

The developer verifies that the build was successful and that the outputs were captured in Dimensions CM and deployed.

Dinesh verifies that the build was successful and that the outputs were captured in Dimensions CM against the task and deployed to the DEV web application deployment area.

  1. To verify that the build was successful, in the Deployment view select the History tab.

  2. In the navigation pane expand the DEV stage node and select LCL_DEV_JBRNCHA_AREA03.

  1. In the content pane, verify that the Event Result column displays Succeeded for the following objects:

    • Autoquote.jar (the event type is Collect)

    • QLARIUS:JAVA_BRANCHA_STR (the event type is Build)

  2. Open Autoquote.jar, make a note of the item revision, and click Cancel.

  3. To verify that the build outputs were captured in Dimensions CM against the task, in the Requests tab select the Request inbox, and open the task. The Open Request dialog box opens.

  4. Select the Relationships tab, and from the Related object class list, select Items. A list of all the build outputs that were captured in Dimensions CM against the task is displayed.

  1. Click Cancel.

  2. To browse the DEV web application deployment area, in the My Current Project view expand Deployment Areas > DEV Stage > LCL_DEV_JBRNCHA_AREA03

  3. Select the Qlarius Underwriter folder.

  4. In the content pane, verify that latest revision of AutoQuote.jar was deployed.

The developer delegates the task to the team lead for peer review.

Dinesh delegates the task to Ted for peer review.

  1. In the Requests tab, select the Request inbox.

  2. Select the child task, and in the toolbar click Delegate. The Delegate wizard opens.

  3. Check that the Capability option is set to Secondary.

  4. From the Role to Delegate list, select REVIEWER and click Next.

  5. In the Candidate Users Authorized for Role Assignment list, select Ted and click Add.

The wizard closes automatically. Dimensions CM sends an email to Ted notifying him that a task has been added to his Request inbox.

The developer actions the task to its next state.

Dinesh actions the task that is delegated to him to its next state, PEER REVIEW.

  1. Select the child task, and in the toolbar select Action. The Action wizard opens.

  2. In the New State section, check that the To Next State field is set to PEER REVIEW. Click Next.

  3. In the Actual Completed Date field, enter a date.

  4. In the Actual Development Effort (hours) field, enter a number.

  5. Click Finish. The task is removed from Dinesh’s request inbox.

  6. Log out of the web client.

Log in to the web client as Dawn and perform the following actions:

  1. Switch to the stream QLARIUS:JAVA_BRANCHA_STR.

  2. Set the work area for Dawn.

  3. Update Dawn’s local work area from the stream.

  4. Edit the item qlarius.sql located in Qlarius Underwriter\qlarius\sql.

    Note: Dawn builds and tests the sql file locally.

  5. Deliver the modified item back to the stream and relate it to the task that was delegated to Dawn. Make a note of the latest item revision.

  6. In the Deployment view, verify that qlarius.sql was deployed successfully to the LCL_DEV_JBRNCHA_AREA01 deployment area.

  7. In the My Current Project view, browse the DEV RDBMS deployment area and verify that the latest revision of qlarius.sql was deployed to LCL_DEV_JBRNCHA_AREA01 > Qlarius Underwriter > qlarius > sql.

  8. Delegate the task to Ted for peer review.

  9. Action the task to PEER REVIEW.

  10. Log out of the web client.

The team lead does a peer review and actions the tasks to their final state.

Ted has read his emails, seen the tasks in his Request inbox, done a peer review of the items that Dinesh and Dawn modified, and is satisfied with the changes that they made. He actions the tasks to their final state, CLOSED.

  1. Log in to the web client as Ted.

  2. In the Requests tab, select the Request inbox. Select both child tasks, and in the toolbar click Action. The Action wizard opens.

  3. Click Finish.

The child tasks are removed from Ted’s Request inbox.

The team lead promotes and deploys the request and tasks to the SIT stage and RDBMS server area.

To perform system integration testing, Ted promotes and deploys the request and the child tasks to the SIT stage and deployment areas in the following order:

  1. RDBMS server area

  2. Web application server area

The Deploy by Default option is enabled for the SIT areas. A build is not required at the SIT stage, so the team lead uses an area filter to only deploy the items that are required for testing at SIT (the executables).

  1. Select the parent request, and in the toolbar click Promote. The Promote wizard opens.

  2. Check that the Promote Child Requests option is selected. This promotes the child task with its parent request.

  3. In the Next stage field, check that SIT is selected. Click Next.

  4. To deploy immediately, check that the option Perform Deployments is set to As Soon As Possible.

  5. In the Areas for Deployment field, select the SIT LCL_SIT_JBRNCHA_AREA01 deployment area (the RDBMS server). Click Next.

    Note: If both areas are selected, clear SIT LCL_SIT_JBRNCHA_AREA03.

  6. Review the summary of the promotion and deployment activity and command, and click Finish.

The team lead verifies that promotion and deployment operations were successful.

Ted verifies that promotion and deployment operations were successful and that the sqlemail file was deployed to the SIT RDBMS deployment area.

  1. Select the Deployment view, and check that only the current stream is displayed.

  2. Select the History tab, and in the navigation pane select the SIT stage node.

  3. In the content pane, verify that the request was promoted successfully from DEV to SIT.

  4. In the navigation pane, expand the SIT stage node and select the LCL_SIT_JBRNCHA_AREA01 deployment area.

  5. In the content pane, verify that the request and child tasks were deployed successfully to the SIT RDBMS deployment area.

  6. To browse the SIT RDBMS deployment area, in the My Current Project view expand Deployment Areas > SIT Stage > LCL_SIT_JBRNCHA_AREA01.

  7. Expand Qlarius Underwriter > qlarius > sql.

  8. In the content pane, verify that the latest revision of qlarius.sql was deployed.

The team lead deploys the request and tasks to the SIT web application server area.

Deployment to the RDBMS server area has been completed successfully, so Ted now deploys the request and tasks to the SIT web application server area.

  1. In the Deployment view, select the Pending tab, and in the navigation pane select the SIT stage node.

  2. In the content pane, from the Show list, select Requests.

  3. In the content pane, select the request, and in the toolbar click Deploy. The Deploy wizard opens.

  4. Check that the Deploy Child Requests option is selected.

  5. In the Next stage field, check that SIT is selected. Click Next.

  6. To deploy immediately, check that the Perform Deployments option is set to As Soon As Possible.

  1. In the Areas for Deployment field, check that the LCL_SIT_JBRNCHA_AREA03 deployment area (the SIT web application server) is selected. Click Next.

  2. Review the summary of the deployment activity and command, and click Finish..

The team lead verifies that promotion and deployment operations were successful.

Ted verifies that promotion and deployment operations were successful and that the .jar file was deployed to the SIT web application deployment area.

  1. Select the History tab.

  2. In the navigation pane, select the LCL_SIT_JBRNCHA_AREA03 deployment area.

  3. In the content pane, verify that the request and child tasks were deployed successfully to the SIT web application deployment area.

  4. To browse the SIT web application deployment area, in the My Current Project view expand Deployment Areas > SIT Stage > LCL_SIT_JBRNCHA_AREA03.

  5. Select the Qlarius Underwriter folder.

  6. In the content pane, verify that the latest revision of AutoQuote.jar was deployed.

Ted performs system integration testing.

The team lead promotes the request and tasks to the QA stage.

System integration testing has been completed successfully so Ted promotes the request and tasks to the QA stage. Because Deploy by Default is not enabled, the request and task cannot be automatically deployed to the QA deployment area.

  1. In the Requests tab, in the Request inbox, select the request, and in the toolbar click Promote. The Promote wizard opens.

  2. Check that the Promote Child Requests option is selected.

  3. In the Next stage field, check that QA is selected. Click Next.

  4. Because Deploy by Default is not enabled, no deploy options are available. Click Next.

  5. Review the summary of the promotion activity and command, and click Finish.

  6. Dimensions CM sends an email to the QA manager, Tao, notifying her that a promotion has been performed.

  7. In the Deployment view, select the History tab, and in the navigation pane select the QA stage node.

  8. In the content pane, verify that the request was promoted successfully from SIT to QA.

The team lead actions the request to its next state.

Ted actions the request to its next lifecycle state, IN TEST, so that QA can test the application.

  1. In the History tab, select the request, and in the toolbar click Action. The Action wizard opens.

  2. In the New State section check that the To Next State field is set to IN TEST. Click Next.

  3. In the Details of Solution Given field, enter a solution. Click Finish.

    Note: The task is removed from Ted’s request inbox.

  4. Log out of the web client.

The QA manager deploys the request and tasks to the QA deployment areas.

Tao reads the email, checks her Request inbox, and deploys the request and tasks to the QA deployment areas in the same sequence:

  1. RDBMS server area

  2. Web application server area

A build is not required at the QA stage, so the QA manager uses an area filter to only deploy the items that are required for testing at QA (the executables).

  1. Log in to the web client as Tao.

  2. Switch to the following stream: QLARIUS:JAVA_BRANCHA_STR.

  3. Select the Deployment view, and check that only the current stream is displayed.

  4. Select the Pending tab.

  5. In the navigation pane, expand the QA stage node and select the LCL_QA_JBRNCHA_AREA01 deployment area (the RDBMS server).

  6. In the content pane, from the Show list, select Requests.

  7. Select the request, and in the toolbar click Deploy. The Deploy wizard opens.

  8. Check that the option Deploy Child Requests is selected.

  9. Check that the Deploy Stage is set to QA. Click Next.

  10. To deploy the request and child tasks immediately, check that the option Perform Deployments is set to As Soon As Possible.

  11. In the Areas for Deployment field, check that the LCL_QA_JBRNCHA_AREA01 deployment area (the RDBMS server) is selected. Click Next.

  12. Review the summary of the deployment activity and command, and click Finish.

  13. Select the History tab.

  14. In the content pane, verify that the request and child tasks were successfully deployed to the QA area LCL_QA_JBRNCHA_AREA01.

Repeat the steps for the QA web application server area: LCL_QA_JBRNCHA_AREA03.

The QA team performs their tests.

The QA manager actions the request to its final lifecycle state.

QA testing has been completed successfully, so Tao closes the enhancement request.

  1. In the History tab, select the request, and in the toolbar click Action. The Action wizard opens.

  2. Check that the To Next State field is set to CLOSED.

  3. Click Finish and then OK.

Note: The request is removed from Tao’s request inbox.

The QA manager promotes the request and tasks to the PRE-PROD stage.

Tao promotes the request and tasks to the PRE-PROD stage. Deploy by Default is not enabled, so the request and tasks cannot be automatically deployed to the PRE-PROD deployment area.

  1. In the History tab, select the request, and in the toolbar click Promote. The Promote wizard opens.

  2. Check that the Promote Child Requests option is selected.

  3. In the Next stage field, check that PRE-PROD is selected. Click Next.

    Because Deploy by Default is not enabled, no deploy options are available. Click Next.

  4. Review the summary of the promotion activity and command, and click Finish.

    Dimensions CM sends an email to the release manager, Rita, notifying her that a promotion has been performed.

  5. In the navigation pane, select the PRE-PROD stage node.

  6. In the content pane, verify that the request was promoted successfully from QA to PRE-PROD.

  7. Log out of the web client.

The release manager deploys the request and tasks to the PRE- PROD deployment areas.

Rita, the release manager, reads the email and checks the Pending tab for the PRE- PROD stage on the Deployment view. Rita sees that the request and tasks are ready to be deployed to PRE-PROD. The deployment sequence is the same as in the previous stages. A build is not required at the PRE-PROD stage, so the release manager uses an area filter to only deploy the items that are required at PRE-PROD (the executables).

  1. Log in to the web client as Rita.

  2. Select the Deployment view and check that only the current stream is displayed.

  3. Select the Pending tab, in the navigation pane expand the PRE-PROD stage node, and select the LCL_PP_JBRNCHA_AREA01 deployment area (the RDBMS server).

  4. In the content pane, from the Show list, select Requests.

  5. Select the request, and in the toolbar click Deploy. The Deploy wizard opens.

  6. Check that the Deploy Child Requests option is selected.

  7. Check that the Deploy Stage is set to PRE-PROD. Click Next.

  8. To deploy the request and child tasks immediately, check that the Perform Deployments option is set to As Soon As Possible.

  9. In the Areas for Deployment field, check that the LCL_PP_JBRNCHA_AREA01 deployment area (the RDBMS server) is selected. Click Next.

  10. Review the summary of the deployment activity and command, and click Finish.

  11. Select the History tab.

  12. In the content pane, verify that the request and child tasks were successfully deployed to the PRE-PROD LCL_PP_JBRNCHA_AREA01 deployment area.

  13. Repeat steps 3 to 14 for the PRE-PROD web application server area: LCL_PP_JBRNCHA_AREA03.

The release team performs their tests.

The release manager promotes the request and tasks to the LIVE stage.

Testing has been completed so Rita promotes the request and tasks to the LIVE stage. Deploy by Default is not enabled for the LIVE deployment area.

  1. In the History tab, select the request, and in the toolbar click Promote. The Promote wizard opens.

  2. Check that the Promote Child Requests option is selected.

  3. In the Next stage field, check that LIVE is selected. Click Next.

  4. Rita has the privilege to deploy at the same time as the promotion but chooses not to. Do not select any deployment areas. Click Next.

  5. Review the summary of the promotion activity and command, and click Finish.

In the navigation pane, select the LIVE stage node.

In the content pane, verify that the request was promoted successfully from PRE- PROD to LIVE.

The request and tasks are now ready to be deployed to the company’s live production environments in London and New York. Deployment normally takes place during the regular maintenance period when the areas are offline.

Rita does the following:

  • Schedules the deployment to the New York production environment at midnight local time.

  • Manually deploys to the London production environment at midnight local time. London is ahead of New York so if there is a problem with the deployment she has time to fix it.

Note: Rita deploys to the LIVE deployment areas in the same sequence as in the previous stages.

The release manager schedules a deployment to the live production environment in New York.

Rita schedules the deployment of the request and tasks to the live production environment in New York at midnight local time.

  1. In the navigation pane, expand the LIVE stage node and select the RDBMS deployment area in New York: LCL_LIVE_JBRNCHA_AREA04.

  2. In the Pending tab, select the request, and in the toolbar click Deploy. The Deploy wizard opens.

  3. Check that the option Deploy Child Requests is selected.

  4. Check that the Deploy stage is set to LIVE. Click Next.

  5. To schedule the deployment, select the option At Specified Time.

  6. Click the Calendar button.

  7. Select today’s date at midnight.

    Tip: To test this scenario, schedule the deployment to run soon, for example, in 15 minutes.

  8. In the Areas for Deployment field, verify that the LCL_LIVE_JBRNCHA_AREA04 deployment area is selected. Click Next.

  9. Review the summary of the deployment activity and command, including the date and time, and click Finish.

  10. In the Queue tab, verify that the request and tasks are queued and waiting to be deployed.

  11. Repeat steps 1 to 12 for the web application deployment area in New York, LCL_LIVE_JBRNCHA_AREA05.

    You must schedule the deployment a few minutes later than the deployment to the RDBMS area.

The release manager deploys the request and the tasks to the LIVE RDBMS deployment area in London.

Let’s assume that it is now midnight in London and the local live production environments are offline. Rita checks to see what requests are ready to be deployed to the LIVE stage. She uses an area filter to only deploy the executables.

  1. In the navigation pane, in the LIVE stage node, select the RDBMS deployment area in London: LCL_LIVE_JBRNCHA_AREA01.

  2. In the Pending tab, select the request, and in the toolbar click Deploy. The Deploy wizard opens.

  3. Check that the Deploy Child Requests option is selected.

  4. Check that the Deploy Stage is set to LIVE. Click Next.

  5. To deploy the request and child task immediately, check that the Perform Deployments option is set to As Soon As Possible.

  6. In the Areas for Deployment field, check that the LCL_LIVE_JBRNCHA_AREA01 deployment area is selected. Click Next.

  7. Review the summary of the deployment activity and command, including the date and time, and click Finish.

The release manager verifies that deployment to the RDBMS area was successful.

Rita verifies that deployment operation was successful and that the sql file was deployed to the LIVE RDBMS deployment area in London.

  1. Select the History tab.

  2. In the content pane, verify that the request and tasks were successfully deployed to the LIVE area.

  3. To browse the LIVE deployment area, in the My Current Project view expand Deployment Areas > LIVE Stage > LCL_LIVE_JBRNCHA_AREA01.

  4. Expand Qlarius Underwriter > qlarius > sql.

  5. In the content pane, verify that the latest revision of qlarius.sq was deployed.

The release manager deploys the request and tasks to the LIVE web application deployment area in London.

The deployment to the RDBMS area was successful, so Rita can now deploy the request and tasks to the LIVE web application deployment area in London.

  1. In the Deployment view, in the LIVE stage node in the navigation pane, select the web application deployment area in London: LCL_LIVE_JBRNCHA_AREA03.

  2. In the Pending tab, select the request, and in the toolbar click Deploy. The Deploy wizard opens.

  3. Check that the option Deploy Child Requests is selected.

  4. Check that the Deploy stage is set to LIVE. Click Next.

  5. To deploy the request and child task immediately, check that the Perform Deployments option is set to As Soon As Possible.

  6. In the Areas for Deployment field, check that the LCL_LIVE_JBRNCHA_AREA03 deployment area is selected. Click Next.

  7. Review the summary of the deployment activity and command, including the date and time, and click Finish.

The release manager verifies that deployment to the web application area was successful.

Rita verifies that deployment operation was successful and that the jar file was deployed to the LIVE RDBMS deployment area in London.

  1. Select the History tab.

  2. In the content pane, verify that the request and tasks were successfully deployed to the LIVE area.

  3. To browse the LIVE deployment area, in the My Current Project view expand Deployment Areas > LIVE Stage > LCL_LIVE_JBRNCHA_AREA03.

  4. Select the folder Qlarius Underwriter.

  5. In the content pane, verify that the latest revision of AutoQuote.jar was deployed.

Rita emails the New York office to advise them that a deployment has been scheduled for midnight local time and that the deployment in London was successful. Rita goes to sleep and in the morning verifies that the deployment to the production environment in New York was successful. The enhancement to the Qlarius web application is now live across all production environments.
End of scenario

Back to top

Scenario privileges

The following tables list the promotion and deployment privileges required by each user in the scenario.

Promotion privilege Privilege owner Required at these stages

REQUEST_PROMOTE_NEXTSTAGE ITEM_PROMOTE_NEXTSTAGE

Team lead DEV
SIT
QA Manager QA
Release Manager PRE-PROD
Deployment privilege Privilege owner Required for these areas
The DEV area is a Deploy by Default area, and no deployment privileges are required.
REQUEST_DEPLOY ITEM_DEPLOY Team Lead LCL_SIT_JBRNCHA_AREA01
LCL_SIT_JBRNCHA_AREA03
QA Manager LCL_QA_JBRNCHA_AREA01
LCL_QA_JBRNCHA_AREA03

Release Manager

LCL_PP_JBRNCHA_AREA01
LCL_PP_JBRNCHA_AREA03
LCL_LIVE_JBRNCHA_AREA01
LCL_LIVE_JBRNCHA_AREA03
LCL_LIVE_JBRNCHA_AREA04
LCL_LIVE_JBRNCHA_AREA05

Back to top