The key steps to perform an upgrade of ActiveControl are summarised below:
| Step | Activity | Other Information |
|---|---|---|
| 01 | Provision of ActiveControl Software + Software Links | To request the latest version of ActiveControl, please email your Basis Technologies’ Customer Success Manager, or assigned Delivery consultant. |
| 02 | Delivery of License Key by Basis Technologies | Once you have received the software, you will also need a License Key. You can request this via the Basis Technologies Support Team, by providing the following information in a support ticket raised via the Support Portal : 1) Customer name 2) Domain Controller System ID 3) Domain Controller Installation Number. 4) ActiveControl version. |
| 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 ActiveControl 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 Upgrade | |
| 08a | Development DC: Apply Transports – Domain Controller | Nb: this cannot be done via ActiveControl. |
| 08b | Development DC: Apply Transports – Satellite Systems | Nb: this cannot be done via ActiveControl. Also note, you may wish to only update certain satellite system path for testing, or even use a Sandbox path for initial testing. Note that as of ActiveControl 9.00, different transports need to be deployed in Dev Satellite Systems versus non-Dev Satellite Systems. |
| 09 | Deploy latest Web Platform docker image to Dev/Test server | |
| 10 | Install new License Key | The first person logging into ActiveControl after the Upgrade will need to upload the new License Key |
| 11 | Development DC: Test ActiveControl Upgrade | |
| 12 | Training (if required, depending on process changes) | |
| 13 | Communicate Change Freeze | |
| 14 | Production DC: Perform ActiveControl Upgrade | |
| 14a | Production DC: Take Backup of Config and Data | Refer to online FAQ for process |
| 14b | Production DC: Switch off any existing Import Schedules via ActiveControl. | After doing this step, check via SM37 that the import jobs are not still running (they will all be called TE_SCHED* |
| 14c | Production DC: Switch off Notification Jobs | You can delete the existing job via SAP GUI (SM37). The program is /BTI/TE_RNOTIFICATION_ENGINE. |
| 14d | Production DC: Apply Transports – Domain Controller | Nb: this cannot be done via ActiveControl itself. |
| 14e | Production DC: Apply Transports – Satellite Systems | Nb: this cannot be done via ActiveControl itself. |
| 14f | Production DC: Deploy latest Web Platform docker image to Production server. | |
| 14g | Install new License Key | The first person logging into ActiveControl after the Upgrade will need to upload the new License Key |
| 14h | Production DC: Perform Roles Updates | If you took copies of the out-of-the-box ActiveControl roles during original implementation, you need to overwrite those roles with the latest ActiveControl roles |
| 14i | Production DC: Configure all new functionality required | Refer to Release Notes for configuration steps |
| 14j | Production DC: Switch on Notification Jobs | Reschedule program /BTI/TE_RNOTIFICATION_ENGINE via SM36, using your existing variant. |
| 14k | Production DC: Switch on Import Schedules | Switch on the Import Schedules via ActiveControl. Check in SM37 that they are released after doing so. |
| 15 | Production DC: Initial validation of the Upgraded system | |
| 16 | Production DC: Perform Archiving (if appropriate) | Refer to online FAQ for more details on the process |
| 17 | Communicate End of Change Freeze |
Post your comment on this topic.