How do I apply a deFacto update to the server (V4)?

Home > FAQ > How do I apply a deFacto update to the server (V4)?

To apply an update to a server do the following:
  1. Unzip the zip file.
  2. Copy all folders contained in the unzipped folder to the server folder normally contained in the Program Files folder. (i.e. "Callisto Server" or "Performance Management Server")
  3. If the update includes NT_Service folders:
    • Stop the CallistoService
    • Copy the contents of the appropriate NT_Service_xxxxx folder into the NT_Servicefolder.
    • Start the CallistoService
  4. Open the Web_Service folder and copy the dll files from the appropriate folder into the bin folder.
  5. If the update includes AS_Security folder.
    • Open the SQL Server Management Studio and connect to Analysis Services.
    • Open the Assemblies folder in the tree.
    • Delete CallistoService.
    • Right click Assemblies and select New Assembly
    • Select "CallistoSecurity.dll" with the button next to the File name entry.
    • Select Permissions - "External Access"
    • Select Impersonation - "Use a specific Windows user name and password"
    • Enter Username and Password.
    • Click OK.
  6. If the update includes BusinessRuleLibrary folder.
    • Open the Modeler.
    • On the "Select Application" dialog box during logon click "Server Setup"
    • Click "Save" on the "Server" tab to update the "Minimum Server Version" which will force all users to update to the latest Excel client.
    • Select "Business Rule Library" tab
    • Click "Update Business Rule Library" to update the master Business Rule Library.
    • After updating the master Business Rule Library, open each Application and Deploy to update the Application Business Rules from the master Business Rule Library.
  7. If the update includes Clients folder, all users will need to download the latest Excel client and Administrators will need to download the latest Modeler.
 

Notes, comments, and suggestion

For server updates, we have not ever required a server reboot. Don't want to say never, but I can't think of any updates to the server software that would require a server reboot. With server updates there are a small number of scenarios they should be aware of:

  • Most updates consist of just copying in new files on the server. While these updates can be performed while the application is in use, this is not a good practice. It is best to pick a time when the application will not be in use for a short period of time. After the update, it is also a good practice to open the Modeler, Update Server Settings for the latest required Client version, and Deploy the application.
  • Sometimes an update will require changes to the structure of the database, and it is always recommended to insure you have a current database backup prior to applying these updates. Structural changes to the database take place automatically by the software the next time you logon to the Application in the Modeler. Check the Release Notes for comments on the need for a database backup prior to applying an update.
  • When an update includes the NT_Service, the NT Service named CallistoService must be stopped prior to applying the update and restart the service after applying the update. Check the Release Notes for any changes to the NT_Service.
  • In relatively rare circumstances, the Analysis Services Security Assembly requires an update. To do this as part of an update requires manual work within the SQL Services Management Studio on the Analysis Services server, and no users will have access while the update is underway. Normally this level of update is also supplied as a full server install, so that the update can be done as an uninstall of the server and reinstall.
Updated:

Other Articles

and 14 more ...