The key steps to perform an Upgrade are detailed in separate Upgrade Plan documentation.
They are summarised as follows:
| Step | Activity | Other Information |
| 01 | Provision of ActiveControl Software + Software Links | To request the later version, please email your Basis Technologies Account Manager |
| 02 | Delivery of License Key by Basis Technologies | Once you have got the software, you can email Support (support@basistechnologies.com to request a license key. You will need to provide the following information: 1) Customer name 2) Domain Controller System ID 3) Domain Controller Installation Number. To make things easier, please include a screenshot of the License screen from the Windows GUI (via Help>License Key dropdown option) |
| 03 | Verify if existing MDR/Diffuser Customer | If you are an existing MDR/Diffuser customer, please ensure you inform Basis Technologies – as upgrading to the latest version of ActiveControl can have detrimental impact on MDR/Diffuser if not carefully planned. |
| 04 | Delivery of Health Check by Basis Technologies | |
| 05 | Review of current user exits and enhancements, and impacts of upgrade | Please review table /BTI/TE_EXITC in the Domain Controller. If you have any non-sample User Exits defined in this table, please copy the contents of the Function Module code from SE37 and email it to Support. |
| 06 | Review of current TE roles usage – and impacts of new ActiveControl version on existing roles | Refer to Roles Matrix that should have been provided to you with the new ActiveControl software. |
| 07 | Development DC: Take Backup of AC Config and AC Data in Dev DC | Refer to online FAQ for process |
| 08 | Development DC: Perform ActiveControl 7.1 Upgrade | |
| 08a | Development DC: Apply Transports – Domain Controller | Nb: this cannot be done via Transport Expresso |
| 08b | Development DC: Apply Transports – Satellite Systems | Nb: this cannot be done via Transport Expresso. Also note, you may wish to only update certain satellite system path for testing, or even use a Sandbox path for initial testing. |
| 09 | Development DC: Test ActiveControl 7.1 Upgrade | |
| 10 | Training (if required, depending on process changes) | |
| 11 | Communicate Change Freeze | |
| 12 | Production DC: Perform AC 7.1 Upgrade | |
| 12a | Production DC: Take Backup of Config and Data | Refer to online FAQ for process |
| 12b | Production DC: Switch off any existing Import Schedules | This is done via the Windows GUI, via the Advanced Import toolbar to remove the existing Schedule, or via Configuration screen (on the Import Options tab within the Target). After doing this step, check via SM37 that the import jobs are not still running (they will all be called TE_SCHED* |
| 12c | Production DC: Switch off Notification Jobs | You can delete the existing job via SAP GUI (SM37). The program is /BTI/TE_RNOTIFICATION_ENGINE. |
| 12d | Production DC: Apply Transports – Domain Controller | Nb: this cannot be done via Transport Expresso |
| 12e | Production DC: Apply Transports – Satellite Systems | Nb: this cannot be done via Transport Expresso |
| 12f | Production DC: Deploy new ActiveControl Windows GUI | |
| 12g | Production DC: Perform Roles Updates | If you took copies of the out-of-the-box Transport Expresso roles during original implementation, you need to overwrite those roles with the latest ActiveControl roles |
| 12h | Production DC: Configure all new functionality required | Refer to Release Notes for configuration steps |
| 12i | Production DC: Switch on Notification Jobs | Reschedule program /BTI/TE_RNOTIFICATION_ENGINE via SM36, using your existing variant. |
| 12j | Production DC: Switch on Import Schedules | Switch on the Import Schedules via the Windows GUI. Check in SM37 that they are released after doing so. |
| 13 | Production DC: Initial validation of the Upgraded system | |
| 14 | Production DC: Perform Archiving (if appropriate) | Refer to online FAQ for process |
| 15 | Communicate End of Change Freeze |
Post your comment on this topic.