|
Upgrading from VisualCron 4.x to 5.x |
Top Previous Next |
|
In version VisualCron version 5 we have optimized a lot of the code structure in earlier version of VisualCron. However, this it was not possible to be completely compatible with version 4, which means that you will lose some information when upgrading from version 4 to 5. Also, other changes exist that may or not affect you. Below is a list of changes for version 5 and how they might affect you and your Jobs.
Install and location VisualCron 5 will now install by default in %PROGRAMFILES%\VisualCron\. Previously, VisualCron was installed in %PROGRAMFILES%\VisualCron 4\. The installation of VisualCron 5 will not uninstall version 4. Both versions can co-exist.
Service name The service name for VisualCron 5 is VisualCron. For version 4, the service name is VisualCron 4. If you previously used a specific user for version 4 you need to set that user to run the VisualCron service for version 5. That information is not transferred automatically.
API If you are using the API you have to upgrade to the latest version of the API for version 5 in order to connect to version 5. Old version can still connect to VisualCron 4.
Desktop short cut The desktop shortcut is named VisualCron 5.
Task changes SQL Task The connection string is no longer stored in the Task. We wanted to make the actual Connection global and we are now storing the connection in Connections. This means that your old connection string will be missing and that you have to create a Connection and select it in the Task.
FTP/S Task We have removed the direct link to the certificate file and are now storing Client certificates in Certificates. You need to import any existing certificate in Certificates and the select the actual Certificate in the Task.
SFTP Task We have removed the direct link to the certificate file and are now storing Client certificates in Certificates. You need to import any existing certificate in Certificates and the select the actual Certificate in the Task.
Notification changes SQL Notification The connection string is no longer stored in the Notification. We wanted to make the actual Connection global and we are now storing the connection in Connections. This means that your old connection string will be missing and that you have to create a Connection and select it in the Notification.
Installation notes If VisualCron 4 is already installed and VisualCron 5 is installed, the following notes are applicable:
|