2009-08-06 08:04 PM
Starting ops-Mgr 3.8 it was decided not to bundle active perl.
" We currently bundle a version of ActivePerl for Windows (5.8.4 built in 2004). We
have not heard of any customers using it or asking for it to be updated.
Since most customers install a version of perl on windows servers, we need not
This was the reason for not including it.
Its removal is mentioned in the release notes.
2009-08-07 08:42 AM
Thanks for your reply. I guess am I part of the silent minority. It did everything I needed it for me to do.
You might not have heard of customers using it because we took it as part of the integrated service provided with DFM.
Are all Perl runtimes on Windows qualified with OM or are there some restrictions?
On a slightly different topic, but refers to embedded runtimes, thank you for finally updating the JRE embedded with the NMC with OM 3.8 / NMC 2.3 to 1.6.0. Erroneous time plots within the NMC for previous releases were problematic when performing troubleshooting.
2009-08-07 10:58 AM
OM by itself does not use Perl for anything, although you could use it run alarm scripts and script plugins, so AFAIK no Perl distribution needs to be qualified to work with it. If your scripts work with whatever Perl distribution you use (ActiveState and Strawberry are two commonly used ones), you should be good to go.
2009-08-10 07:23 AM
Agreed about Perl still being available if you upgrade directly.
Traditionally when OM gets upgraded it usually conincides with a DFM server hardware refresh, and because OM performs so many functions the prefered approach is to install the latest version on a new server and then copy the last database backup to the new server and perform a restore.
This way we can roll back quickly if there is a problem.