Promoting the Snapshots

Promote the process app snapshots, following the instructions carefully, especially for the Release Package snapshot. For the best results, read through the following sections before beginning the promotion.

When you are ready to promote a snapshot, perform the steps below for each of the snapshots.

  1. Log in to SBM Application Repository using the following URL, where serverName is your server name or IP number and port is your port number. The default port is 8085. http://serverName:port/mashupmgr
  2. In the left navigation pane, select Snapshots.
  3. In the Sources selection box, select Release Control to filter the list. You will see the following snapshots:
    • RLC - Approvals
    • RLC - Environment
    • RLC - Manual Deployment Task (optional)
    • RLC - Release Data
    • RLC - Sample Request (optional)
    • RLC - Task Templates
    • RLC - Release Train
    • RLC - Release Package
    Tip: Although RLC - Manual Deployment Task and RLC - Sample Request are optional, you should promote them if you plan to follow along with the examples used in this documentation.
  4. In the given order, select a snapshot and in its Actions column, click the Promote icon. The Promote Snapshot wizard is displayed.
    • RLC - Task Templates must be promoted before RLC - Release Train. Otherwise, the default project is not set properly for RLC - Deployable Release Train.
    • RLC - Release Train must be promoted before RLC - Release Package. Otherwise, the RLC - Release Package promotion may fail with Aborted status.
  5. In the Destination step, select the environment to which to promote. Click Next.
  6. In the Entities step, choose which entities to import. It is recommended that you import all of them for each snapshot.
    Important: Select the Merge conflicts option if you have already promoted the snapshot to the target environment and you want to preserve changes that you made to the existing application. For example, if you want to keep new user roles that you added to an application, select the Merge conflicts check box to preserve them in the target environment after the promotion. If Merge conflicts is not selected, the existing entities will be deleted in the target environment.

    Click Next.

  7. In the Mappings step, notice that any endpoint mappings point to the IP address of the server onto which you are installing. Click Next.
  8. In the Summary step, review your selections and then click Promote to finish the operation.
  9. Repeat starting with step 4 for each of the snapshots that you want to use.
    Tip: If you aren't sure whether you will use the optional snapshots, promote them and if you decide you don't want to use them later, you can delete them or hide them by removing privileges. If you want to configure the end-to-end solution for proof of task or evaluation, promote them.
  10. After you have promoted each of the snapshots, continue with Generating Views for Deployment Path Reports.
    Note: If you promoted Release Package before Release Train and it aborted, just promote it again after promoting Release Train and it should complete successfully. Make sure it is promoted successfully before continuing to generate the views.

Related Topics

Generating Views for Deployment Path Reports