Promoting the Serena Service Manager Snapshots

To promote the Service Manager snapshots:

  1. Log in to SBM Application Repository using the following URL:
    http://serverName:port/mashupmgr
  2. Select the Process App Snapshots tab.
  3. Click All and then select to filter on Serena Service Manager.
  4. Promote the snapshots (in no particular order) by performing the following steps:
    1. Select the snapshot and then click Promote. The Summary of the Promote dialog box is displayed.
    2. Choose the Destination Environment by selecting the Destination box.
    3. In the Entities section, choose which entities to import. It is recommended that you import all of them, but it is not mandatory.
      Tip: You should only promote the SSM - Integrations process app if you are using Serena Asset Manager or the Asset Discovery Adapter.
      The following tables describe which options must be selected for each snapshot and which are optional.
      Table 1. Promotion Options
      Type Notes
      Projects Mandatory.
      Notifications Optional, but suggested. Not importing notifications means that no notifications will be available until you create them.
      Notification Rules Optional, but suggested. Not importing notification rules means that notifications will not be sent within the workflow until you add new notification rules.
      Reports Mandatory.
      Auxiliary Table Data Depends on the process app. See the following table for more information.
      Transition Group Restrictions Mandatory.
      User Field Selections Mandatory.
      Mailboxes Optional.
      E-mail Templates Mandatory.
      Table 2. Auxiliary Table Data
      Process App Notes
      SSM - Change Management No auxiliary tables or data.
      SSM - Configuration Management System
      • CI Categories, CI Sub-Categories, CI Sub-Category Types: Recommended, but not required. If you do not import the table data, you must populate the tables with data before using Service Manager.
      • Model Numbers, Relationships, Software Platforms: Not required. Note that these tables do not contain data and selecting them to import will have no effect.
      • Relationship Types: Strongly recommended. If not, you must add relationship types before you can create relationships between CIs.
      • Vendors: Mandatory.
      SSM - Incident Management
      • Resolution Codes: Not required.
      • Symptom Codes: Not required.
      SSM - Integrations
      • CI Events: Mandatory.
      SSM - Problem Management
      • Workarounds: Not required. Note that these tables do not contain data and selecting them to import will have no effect.
      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.
    4. If no mappings are needed in the Mapping dialog box, click Done.
    5. Click Promote to finish the operation.
    6. Repeat this process for each snapshot in the solution.
Tip: If you also have Request Center, modify the multi-table report, "Requests Center - My Requests," under the Service Request solution tab to include the Incident Management table. This allows users to see incidents that they have submitted in Request Center.