Regular updates, new versions and fixes are an integral part of our product strategy. In this article you will learn what preparations have to be made, how to update the software and what else you should know about it.
Information about software updates
From mid-2018, we will actively inform our customers‘ contacts about each released software version of ScriptRunner. To keep the list of your contacts up to date, you can fill out this form to register new contacts and, if necessary, have former colleagues or employees removed from the mailing list.
The information about a new software version regularly contains the build number of the software as well as information about new features, fixes and special features. It is sent by e-mail to the list of contact persons and also contains a link to download the software.
Preparations for the update
Before you start the update, you should make some preparations to ensure a quick recovery of your system in case of doubt.
Take a snapshot of the ScriptRunner Host VM
- To save the configuration, exit the „AppSphere ScriptRunner Service“ and save the directory Drive:\programdata\AppSphere\… . Before terminating the service, check whether PowerShell processes of running actions on the host are still active by checking exe processes in Task Manager.
- Back up the folder of your Script Library if you have changed the default settings. You can view your settings in the Admin App under the main menu „Settings“ and „Script Library“.
- To restore, make sure you have access to the installation files of the installed version.
- If changes to the Web App configuration files URI.JS under Drive:\programs files(x86)\AppSphere\ScriptRunnerWebApps\AdminApp or \DelegateApp, please save these configuration files as well.
- Download the new software version, copy it to the ScriptRunner host and unpack the ZIP file.
Before you start
Please make sure that you have made the preparations as described above.
- Log in to the ScriptRunner Host with the rights to install the software.
- End all PowerShell processes on the host, including PowerShell sessions that are not controlled by ScriptRunner.
- Check that the ScriptRunner service is running.
- Make sure that the operation of the ScriptRunner Host VM is not interrupted by automatic or manual restarts during the update.
Performing the update
Only use the ScriptRunner setup files to perform the update. These ensure that all configuration information is retained and, if necessary, converted during setup.
Important note: Each ScriptRunner setup first removes the old binaries in Drive:\programs files(x86)\AppSphere\… completely. The configuration files under Drive:\programdata\AppSphere\… remain complete.
Both the update of the ScriptRunner service and an update of the ScriptRunner Web Apps must always be performed. Otherwise the proper interaction of Web Frontend and ScriptRunner Backend can be disturbed and the compatibility of functions cannot be guaranteed.
- First, update the ScriptRunner service. The settings from the previous installation are adopted and should not be changed.
- Check the newly installed AppSphere ScriptRunner Service. This must have started.
- If errors occur during installation, check the uninstall and setup logs in Drive:\Program Files (x86)\AppSphere\ScriptRunnerService.
- Then run the setup for the Web Apps with the „Deploy to IIS“ option. During installation, the setup checks whether the ScriptRunner Web Service is available under the specified URI (http, https).
- If you use individually modified configuration files URI.JS, rename the installed URI.JS and copy your individually modified URI.JS from the backup to the corresponding directory.
- Open the Admin and the Delegate Web App in the web browser from a workstation.
- If errors occur during installation, check the uninstall and setup logs in Drive:\Program Files (x86)\AppSphere\ScriptRunnerWebApps
- Optional: Run the setup of the Team Apps on the ScriptRunner host.
If you are using the ScriptRunner ISE PlugIn on clients, run the Team App Setup and select the option ISE Plugin.
What you can do after the update
After the update, we recommend checking the ScriptRunner Host installation in the directories and setup logs, checking the basic settings on the host using the PowerShell ScriptRunnerSettings module, and performing and checking some selected actions.
You can then view the version used in both web apps via the „About“ page on the backend and on the frontend.
If the update has been installed correctly and is functional, you can then save the new version. They can create a snapshot of the ScriptRunner VM as well as save the complete directory Drive:\programdata\AppSphere\…..
Restore the previous installation
To restore a previous installation, you need either a snapshot of the ScriptRunner VM or a completely backed up directory Drive:\programdata\AppSphere\…
When restoring using Snapshot, please follow the best practices for each virtualization platform. Information on this can be found on the websites of the manufacturers.
When restoring with a saved configuration, the following steps are necessary:
- Uninstall ScriptRunner completely.
- Copy the saved directory Drive:\programdata\AppSphere\… completely to the system.
- Start the corresponding ScriptRunner Service Setup of the previous installation and execute it.
- Check and configure the necessary host settings with the PowerShell ScriptRunnerSettings module.
- Run ScriptRunner Web Apps Setup.
For technical questions regarding your version, please contact firstname.lastname@example.org.
[Automatically translated with www.DeepL.com/Translator]
Letzte Artikel von Merle Siegmon (Alle anzeigen)
- PowerShell Script Header and Parameters for Use in ScriptRunner (English) - 4. Dezember 2018
- PowerShell parameters and their graphical representation in ScriptRunner (English) - 4. Dezember 2018
- ScriptRunner Tip: Software Update [EN] - 28. Mai 2018