I am working on an upgrade to SA 17 and I used the deployment wizard to build an msi file to deploy to my customer's 4 servers. What I don't understand is how to apply the activation keys without having to go to each server and use the dblic utility to apply the licenses. Is there an easier way?
asked 04 Mar '16, 13:55
The documentation you refer to above describes silent installs of the full product. The documentation on silent installs won't help you with upgrading a deployment wizard MSI install.
The install built by the deployment wizard does not need a registration key to run. If your installer includes the server (dbsrv17.exe and/or dbeng17.exe) it will be governed by the license you created when you installed SQL Anywhere. The deployment wizard will include the file dbsrv17.lic when dbsrv17.exe is include (and/or dbeng17.lic when dbeng17.exe is included) in the deployment installer. So the deployment installer is essentially using the registration key you supplied when you originally installed SQL Anywhere.
If for some reason you need to change the license on the servers to which you've already deployed, then you will need to run the dblic.exe utility on each machine. (No doubt there are ways to automate that process.)
If you need to upgrade the version of SQL Anywhere on your servers using the deployment wizard, you will need to create an Upgrade MSI. The catch with creating an Upgrade MSI is that you need to have available your original deployment wizard generated MSI. This is so that the Upgrade MSI can generated components with the original MSI's component GUIDs.
Here is how you would go about doing the above:
The above command will upgrade the image on your servers to build 1384 and will continue to use the existing dbsrv17.lic file as the license. You will not need to provide a registration key.
answered 07 Mar '16, 16:15
Found it on document xchange. http://dcx.sap.com/index.html#sqla170/en/html/8168a3fa6ce21014a346e584d7ae12a7.html
answered 04 Mar '16, 16:10