Hi Dojo,
Every month a new DataMiner, IDP and SRM package is released. Accordingly, I schedule a maintenance window so that I can install these packages all at once.
The problem that I have is that after installation of each package, the DataMiner software starts up. Since this can easily take 15 minutes, it's for me very time consuming when I have also other packages to install.
Is it possible that Skyline can provide packages that just stops the DataMiner software when it's running and that the person who's installing the package needs to start the software manually afterwards?
I think some caution is needed as now you have a restart after every package, so you can validate that after the installation of this 1 package, your system still works as expected. If you want to install 3 packages on your system and start it up after installing those 3 packages, you might have a harder time finding the root cause of any errors that present themselves during or after the startup of your system.
Hi Baptiste, a valid concern. In my case I’m upgrading the staging environment step by step. Once everything is validated, I would like to upgrade the production environment with just 1 restart.
Hi Jens,
This is currently not supported. The upgrade packages you mention always include a start action at the end.
The only alternative, for the more advanced users, would be to alter the upgrade package manually (at your own risk since this would no longer be validated and supported by Skyline) and remove the 'Start' action from the 'UpdateContent.txt'. More info here: Actions that can be performed during an upgrade operation | DataMiner Docs
Bert
Since DM10.0.11, there is the possibility to use Application Packages, these do not require a restart of DM.
The SRM and IDP packages however do not come in this type of package.
Hi Jens,
According to the DataMiner help, this option is already present in both Cube and SLTaskbarUtility. I have not tested it though.
This option is to automatically start DataMiner when Windows starts. DataMiner will start anyhow after the upgrade package is executed. So, this option is not useful for the use case of Jens his question…
I’ll update the documentation to make this more clear
Nice proposal
We could do this via Update Center and let the user decide what to update on the system.