Managing requests

The main unit of deployment in BMC Release Process Management is a request. A request represents the deployment of the components of an application into an environment. A request describes the work to be done in the deployment process, such as putting an application in an environment, adding attributes, and packaging and deploying the software. A request is composed of steps, which can be manual (for example, “Check logs for errors”) or automated (for example, “Deploy package”) using one of the automation modules.

You can assign requests and steps to users and schedule requests on the calendar. Requests have a duration, a planned date, and a due date. They follow a series of states and transitions from planned to complete.

Through the BMC Release Process Management model, each step in the request can determine which servers and components are affected during execution. It can also draw on properties assigned to those components. Properties store settings and values that are important to the execution of requests. By putting values such as classpath in properties, you can ensure that the same value is mapped to each request that works with those components in those environments.

You can execute requests as part of a project, or as part of an application plan process or release plan.

You can characterize steps as part of a task, such as “predeployment checks,” and also by phase or runtime phase, such as “night before work.” You can complete steps in series, where each one must be complete before starting the next, or in parallel, where execution proceeds asynchronously to reflect dependencies in the work. There are also “anytime” steps, which can be completed anytime during the request but must be complete to complete the request (for example, “update documentation”).

You can create a request in several ways, including from existing request templates. Request templates are particularly useful when you know that some steps will be repeated in several requests. Instead of constructing the steps over and over, you can take the request that has a complete set of information and steps and create a request template.

When the request has a complete set of information, you can perform the release. You must change the request status from Created state to Planned. When the Planned request reaches its scheduled time, the Coordinator or Deployer can start the request execution. For more information about user permissions for managing the requests, see Administering users, roles, and access permissions.

To create a request

You can create a request in three possible ways. They are as follows:

• Create a request from the request header
• Create a request from a request template (first create a request template and then create a request from the template)
• Import a request

To create a request template

BMC Release Process Management allows you to create request templates from existing requests and use the template more than once if you require it. This is to save time to create requests over and over again.

1. Click the Requests tab. The requests list open.
2. Click open a request for which you want to create a template.
3. Click the Create Template button on the right.
4. In the small dialog box that appears, type in a name of a template.
5. Click Create Template.

To create a request from a request header

1. Click the Requests tab at the top, and then on the Requests page, click the Create Request tab on the right pane.
2. Enter the required data in the various fields under Core Attributes.
3. From the Plan list, select the plan for your request.
4. From the Stage list, select the plan stage for your request.
5. Click the Show link next to Extended Attributes and enter the required attributes, if any. These include the following: Projects, Package Contents, Wiki, and Assets.
6. Under Scheduling and Estimation, select the estimated time from the list in the Estimate field.
7. In the empty space in the Planned Start field, click once.
8. In the monthly calendar, select the start date. Then select the start time from the at field next to the Planned Start field.
9. In the empty space in the Due by field, click once.
10. In the monthly calendar, select the due date. then select the due by date from the at field next to the Due by field.

11. Click Create Request. The request is created and the Request page opens. You can see the request ID at the top left corner.
    You can add steps to the request. For more information about adding steps, see To add steps to a request.

     

To create a request from a request header using the request template

You may choose an existing template and use it to create a request

1. Click the Requests tab.
2. Click the Create Requests button at the right.
3. Under Core Attributes type in a name for your request.in the name field.
4. Click Choose Template on the right. The requests template page appears.
5. Click the Create Request button next to your required template.
6. In the new dialog box that appears, from the Select environment list, select the required environment for the request.
7. From the Plan list, select the plan for your request.
8. From the Stage list, select the plan stage for your request.
9. Click Create Request.

You can add steps to the request. For more information about adding steps, see To add steps to a request.

To create a request from a request template

You may have created one or more template and now you need to create a request from one of those templates.

1. On Environment > Metadata > Manage Request Templates, from the Request Templates list, select the template that you want to use.
2. Click New Request from Template at the right of the appropriate request template.
3. In the new dialog box that appears, from the Select environment list, select the required environment for the request.
4. From the Plan list, select the plan for your request.
5. From the Stage list, select the plan stage for your request.
6. Click Create Request.
   A new request is created and the request details are displayed.

You can add steps to the request. For more information about adding steps, see To add steps to a request.

To create a request for a plan

After you have created a plan and edited plan details, you must create requests.

1. From the Stages tab for a plan, click Create Request.
2. On the Request page, create a request from scratch, or choose a template by clicking Choose Template on the right.
   (Click the image to expand it)
   
3. Click Create Request.
4. In the dialog box, select an environment from the Select Environment list, and click Create Request.
5. Click the expand link to see the request details.
6. (Optional) If you need to modify the request, click Modify Request details, and then modify the details in the Edit Request dialog box.

To export a request

You can import a request to the system. But, for that you need to export a request and save it in .xml, .pdf, and .html format on your local machine.

1. Click the Requests tab.
2. When the request list appears, click the appropriate request.
   The request details open.
3. From the right pane, select the export format option:
   • Export as XML
     
   • Export as PDF
   • Export as HTML
     
     

To import a request

You can import a request which you have stored as a XML file. BMC Release Process Management supports importing a file from your local machine in XML format. You can rename this request if you want.

1. Click the Requests tab.
2. Click the Import Request link on the right.
3. In the Import dialog box that appears, select the required XML file from your local machine.
4. Click Create Request.

To modify a request

1. From the Requests page, click open the request that you need to modify.
2. When the request opens, click expand.
   The request details open.
3. Click Modify Request Details.
   The Edit Request dialog box opens
4. Make the necessary changes to the request details.
5. Click Update.

To change notifications options

Notification options indicate the list of participants who are supposed to receive the notifications for requests, changes in the request status, and so on.

For with BMC Release Process Management version 4.3.01.04 and earlier:

1. On the Requests tab, click the appropriate request.
2. On the request page open, click expand.
3. Click the Change Notifications Options. The Notifications Options for Request dialog box opens.
4. Select the notifications options for the request (see the attached figure).
5. From the Users list, select the users that you want to set the email notifications for.
6. From the Groups list, select the user groups that you want to set the email notifications for.
7. In the Other Email Ids field, enter additional emails to send the request notifications.
8. Click Update.
   (Click the image to expand it)
   

Starting with BMC Release Process Management version 4.3.01.05 and later:

1. On the Requests tab, click the appropriate request.
2. On the request page open, click expand.
3. Click the Change Notifications Options. The Notifications Options for Request dialog box opens.
   

4. From the Request Events list, select event request notification options.

   Note

   For the selected request events, the request Owner and Requestor always receive event notifications.

5. Select Notify Step Owner(s), if you want to send the request event notifications to all step owners.

6. From the Step Events list, select step notification options.

   Note

   For the selected step events, the step Owner always receives event notifications.

7. Select Notify all Step Owners from Request about changes to send the step event notifications for all the request steps to all step owners.

8. Select Notify Request's Owner/Requestor about changes to send the step event notifications for all the request steps to the request Owner and Requestor.

9. In Additional Participants, select additional notification recipient options:
   
   • From the Notify on Request events list, select options to send notifications for the request events.

   • From the Notify on Step events list, select options to to send notifications for the step events.

   • From the Users list, select additional users to receive event notifications.
     Only users that have access to the application associated with the request are available in the Users list.

   • From the Groups list, select the user groups to receive event notifications.
     Only groups that have access to the application associated with the request are available in the Users list.
   • In the Other Email Ids field, enter additional emails for the event notifications.
10. In Groups notification behavior:
    • Select Group email only to send notifications only to the specified group email.
    • Select Group email + Member email(s) to send notifications to the specified group email and every group user personal email.
11. Click Update.
    
    

To edit component versions

There may be change of plans and so you may need to change the component versions associated with the request.

1. On the Requests tab, click the appropriate request.
2. On the request page open, click expand.
3. Click the Edit Component Versions link.
   Edit Component Versions opens. 
    
   (Click the image to expand it)
   
4. In Edit Component Versions, the check box for the environment that is default with the component, appears disabled. If you want to see the other environments, select the check box for the environment under View other environments for this application.
5. From the Proposed testdev drop down, select the required version.
6. Click Submit.

In a plan run, you can clone requests and execute requests in sequence or in parallel. For more information, see Managing plan runs.

Related topic

Managing steps