What is the recommended process for migrating mainframe monitoring from Managed to SaaS?

[derick_hewetson]

Hi,

I am busy with a migration from Managed to SaaS. As part of this, I need to migrate the mainframe monitoring.

I haven't come across any documentation highlighting the process required to switch the monitoring communication endpoints. Has anyone done this yet?

Regards,

Derick

[rastislav_danis]

Mainframe (zremote) uses env ActiveGate to send data, so for me it seems reconfig of AG should be enough.

[derick_hewetson]

Thanks, Ratislav.

I was thinking along the same lines, as the mainframe components all point to the zRemote ActiveGate, so switching that (using the same IP etc) should be enough.

[Peter_Youssef · Accepted solution]

Hello @derick_hewetson 

• As per Dynatrace the AG migration recommended approach is "Concurrent deployment of new ActiveGates on the new hardware".

Meanwhile using the AG reconfiguration method you will ensure: 

• Less downtime and bandwidth (don't need to download and run any installers).
• Re-use existing infrastructure.
• Avoid re-deploying extension packages.

On the other hand these are the Cons due to AG Reconfigurations:

• Error-prone due to manual configuration modification.
• Possible monitoring gaps without failover for OneAgent.
• Requires environment token rotation.

For the ease of switching communications you can proceed with the AG Reconfigurations.

The recommended approach will help you testing ActiveGate setup before decommissioning existing setup, cut is done on the agent time so it's least downtime from the time factor perspective and the required action: Re-apply any customizations made to custom.properties and launcheruserconfig.conf.

BR, 

Peter

[derick_hewetson]

Thanks, Peter.

If I understand your comments correctly, you are agreeing that the only changes required are at the ActiveGate level, not on the mainframe itself.

To switch the ActiveGate configuration, would an uninstall of Managed ActiveGate software, followed by an installation of the SaaS ActiveGate software introduce any issues, besides a monitoring gap during the process?

Regards,

Derick

[Peter_Youssef]

Thanks @derick_hewetson for your valuable inputs. 

• In case you will proceed with the new AG Reconfiguration > the applied changes will be on the AG itself to make the AG pointing to the new SaaS environment.
• The best practice to migrate the OA is to : Remote bulk migration with remote configuration management.
• What you will change the remote communication configurations through the UI to enforce OA sending the data to the new AG connected that's connected to the SaaS environment.

• You have option to change the OA communications through oneagentctl locally on each host but it's time and effort consuming you that's why it's recommended to use the remote configurations.

Wishing you interesting migration experience, keep us posted 👨‍💻

BR, 

Peter

[derick_hewetson]

Thanks, @peter , I wasn't aware that the OneAgent on the mainframe supported remote bulk configuration. I'll check that out.

[Peter_Youssef]

Almost welcome @derick_hewetson , all the best.

[Peter_Youssef]

Hi @derick_hewetson 

Regarding the second point: 

• Reconfiguration won't require uninstallation and re- installation as what we are accomplishing is connecting the current AG to a new Cluster instead of the managed it will be connected to SaaS.

Regarding AG re-installation on the same HW these are the below cons:

• Downtime when running an installer.
• Re-apply any customization made to custom.properties and launcheruserconfig.conf.
• Possible monitoring gaps without failover for OneAgent.

The good thing about Re-installation approach:

• Re-use existing infrastructure
• Re-use automation tools if exist.

Hoping this adds value.

KR,

Peter.