AMIGO Upgrade Program Introduction for BMC TrueSight Server Automation (TSSA) environments

Manage Support IDs

Use checkboxes to 'Remove support IDs/Users' or 'Allow to create Cases'
Support IDs for BMC Customer Support Site Guest User
Profiles Which Include    Back to All Support IDs
 

Knowledge Article

AMIGO Upgrade Program Introduction for BMC TrueSight Server Automation (TSSA) environments
AMIGO Upgrade Program Introduction for BMC TrueSight Server Automation (TSSA - formerly BSA) environments
TrueSight Server Automation
TrueSight Server Automation
All TSSA version starting 8.9.x
TrueSight Server Automation
TrueSight Server Automation
All TSSA version starting 8.9.x
TrueSight Server Automation
TrueSight Server Automation
All TSSA version starting 8.9.x

AMIGO Upgrade Program Introduction

The BMC Assisted Migration Offering, or AMIGO, is a program designed to assist our customers in planning and preparing for product upgrades from an older, to a newer supported version.  By engaging with BMC Technical Support Analysts, you will be provided with materials containing guidelines and best practices to aid in compiling your own upgrade plan.  An upgrade expert will then review your plan, and offer advice and suggestions to ensure success through proper planning.

The AMIGO program consists of two below phases :
1. Starter Phase  -In the Starter Phase, an AMIGO Starter case is opened. Reference material will be provided and a call with a Technical Support Analyst will take place to discuss the details of your upgrade, and address any questions you may have. The AMIGO Starter case will be closed, and the next step will be for you to prepare a documented upgrade plan. 

2.  Review Phase - In the Review Phase, an AMIGO Review case is opened preferably two weeks prior to a set upgrade date. A call will be scheduled with an upgrade expert to review your detailed plan, providing feedback and recommendations, along with answers to any outstanding questions.  As needed, a follow up discussion with a Technical Support Analyst may take place for feedback after the upgrade is performed.

Note : Each phase is initiated by opening a support case, and ends when the case is closed.
 

To assist with the Starter Phase, please complete the following Upgrade Checklist/Questionnaire and include the requested information when opening the Starter Ticket.
 

TSSA AMIGO Upgrade Checklist for BMC TrueSight Server Automation (TSSA - formerly BSA)

1)      Provide Current TSSA Environment Information to BMC Customer Support for analysis:
 
a)       Complete TSSA Environment Information can be captured by exporting Appserver Details from the TSSA Console and providing the exported results file to Customer Support for analysis. 
This single file will provide the following information and much more about the customer’s TSSA environment:
  •    Number and Type of TSSA Appserver Instances (JOB, CONFIG, NSH PROXY and ALL)
  •    TSSA Appserver Version/Build Information
  •    Information about the hosts where TSSA Appserver Instances are installed and running (Number of hosts, OS Vendor, OS Version, Number of Appservers per host etc)
  •    TSSA Database Vendor and Version
The Appserver Details export file is generated as follows from the TSSA Console:

Configuration -> Infrastructure Management -> Export Detail Report
 
b)      Is this TSSA environment part of a BMC Cloud LifeCycle Management(CLM) environment? If so, consideration needs to be given when upgrading the TSSA component to ensure compatibility with CLM is maintained. Provide CLM version information so support can confirm whether TSSA/CLM compatibility would be maintained or whether a CLM upgrade will also be required..
c)      Is the TrueSight Automation Console (TSAC) product installed and referencing this TSSA environment in its TSSA Connector?
d)      Is this TSSA environment integrated with any other BMC Products? E.g BL2ATRIUM, Remedy, Atrium Orchestrator etc. If so, provide integration details.
e)      If the TSSA Application Server from where the TSSA upgrade will be launched is a Linux Server, will an X Windows System be available to display the TSSA UPI UI?
f)      Is the TSSA environment hosted on Physical or Virtual Servers?
 
 
2)      Is TrueSight Smart Reporting for Server (TSSA-DW and TSSR Platform) installed in this environment?
 
If so, consideration needs to be given when upgrading TSSA to ensure compatibility with TSSR-SA (TSSA-DW and TSSR Platform) is maintained.
A corresponding TSSA-DW and TSSR Platform upgrade is typically required to maintain compatibility and it is usually recommended that TSSA-DW and TSSR Platform be upgraded before TSSA .

See the following Compatibility Matrix pages:

TSSR-SA 21.3: https://docs.bmc.com/docs/tssrsa213/compatibility-matrix-1025553414.html
TSSR-SA 21.02: https://docs.bmc.com/docs/tssrsa2102/compatibility-matrix-975419265.html
TSSR-SA 22.2: https://docs.bmc.com/docs/smartreportingserverautomation/222/compatibility-matrix-1085488024.html
 
3)      To what version of TSSA will the environment be upgraded? (i.e. what is the Target Version)
 
4)      TSSA Environment History
a)      How long has this TSSA Environment been in existence?
b)      What is the upgrade history of the TSSA Environment? Some of this information can be captured by running the attached mig_task_output_oracle.sql or mig_task_output_sqlserver .sql script on the bladelogic schema/db and providing the generated output file.
c)      Does the TSSA Cleanup job run frequently and successfully in this Environment? This information can be captured by running the attached deletetasks_oracle.sql or deletetasks_sqlserver.sql script on the bladelogic schema/db and providing the generated output file.
d)  Capture the size of your bladelogic schema/db by running the attached bl_tbl_size_oracle.sql or bl_tbl_size_sqlserver.sql script on the bladelogic schema/db and providing the generated output file. 
 
5)      Is this a Production environment?
a)      If so, does a DEV/LAB/Test environment also exist?
b)      Is the DEV/LAB/Test environment using a copy of the Prod DB? When was it last refreshed with a copy of the Prod DB?
c)      What are the upgrade plans for the DEV/LAB/Test environment(s)?
d)      Review the Testing the upgrade in a duplicated environment section of the TSSA documentation
 
6)      TSSA RSCD Target Information:
a)      How many TSSA RSCD Agents currently exist in the environment?
b)      What is the approximate breakdown of RSCD Targets by OS?
c)      What is the approximate breakdown of RSCD Targets by current agent version?
d)      What is the timeline for upgrading the RSCD Agents after the TSSA Appserver/DB/Console upgrade?
e)      Will the RSCD Agents be upgraded manually or silently?
f)       Have any of the RSCD Agents been installed with the –local switch? (if so, usually the TSSA FileServer)
 
 
7)      TSSA Client/Console Information:
a)      Number of hosts running the TSSA Server Automation Consoles? (RCP console - thick client for TSSA)
b)      Will the TSSA Server Automation Consoles be upgraded manually or silently?
c)      Number of hosts running standalone NSH clients?
d)      Number of hosts running TSSA Repeaters?

 
8)      Verify the versions and platforms are supported for this upgrade by reviewing the System Requirements page of the Target Release 

          a)  TSSA 20.02: https://docs.bmc.com/docs/tssa2002/supported-platforms-910749868.html
          b)  TSSA 21.02: https://docs.bmc.com/docs/tssa2102/supported-platforms-975413192.html
          c)  TSSA 21.3: https://docs.bmc.com/docs/serverautomation/213/supported-platforms-1013436199.html
          d)  TSSA 22.2: https://docs.bmc.com/docs/serverautomation/222/supported-platforms-1094964887.html


9)      Review the TSSA upgrade documentation for the Target Version e.g.

          a)  TSSA 20.02: https://docs.bmc.com/docs/tssa2002/upgrading-911445959.html
          b)  TSSA 21.02: https://docs.bmc.com/docs/tssa2102/upgrading-975414557.html
          c)  TSSA 21.3: https://docs.bmc.com/docs/serverautomation/213/upgrading-1013437634.html
          d)  TSSA 22.2: https://docs.bmc.com/docs/serverautomation/222/upgrading-1094958119.html

 
10)   Are the TSSA Provisioning Management components installed in this environment?

          If so, review the steps in the TSSA doc of your Target Release for “Upgrading the Provisioning System” e.g.

          a)  TSSA 20.02: https://docs.bmc.com/docs/tssa2002/upgrading-the-provisioning-system-910751200.html
          b)  TSSA 21.02: https://docs.bmc.com/docs/tssa2102/upgrading-the-provisioning-system-975414639.html
          c)  TSSA 21.3: https://docs.bmc.com/docs/serverautomation/213/upgrading-the-provisioning-system-1013437718.html
          d) TSSA 22.2: https://docs.bmc.com/docs/serverautomation/222/upgrading-the-provisioning-system-1094958201.html
 
 
11)   Provide an initial Upgrade Plan document to TSSA Customer Support for review and feedback.

The TSSA doc now contains an Upgrade Walkthrough (formerly known as Cheat Sheat) which can be used as a starting point to producing an Upgrade Plan document:

12)   What is the proposed timeline for the TSSA Upgrade?
a)      Start date of proposed upgrade
b)      Length of outage window
c)      Have the necessary resources been informed of the upgrade timeline in case their assistance is required? (e.g. DBAs, LDAP/AD Admins, Network Admins)
 
13)   What is the back out plan in the event that there are unexpected issues?
 
14)   What is the test schedule in the upgraded TSSA environment?
 
Attachment(s):
BSAAMIGOScripts.zip