How to Install a New Version of Weave

Owned by Lucy Minato (Deactivated)
Last updated: 24 Oct, 2022 by Shaun Forbes
5 min read

If you already have a version of Weave running, you can upgrade it to the latest version released, or you can perform a completely new installation. This page covers how to perform a new installation. 

Step-by-step guide

  1. Download the Installer file as directed by the new release email from the Weave Support System or from the Latest Downloads page. 

  2. The Installer file is a .jar file so it needs Java to run. If you don't have Java installed but have a previous version of Weave installed, you can use the Java executable that is installed with that Weave (e.g. c:\weave\jre\bin\java.exe).
     
  3. It is recommended that you install the new Weave release into a new folder so you can still have your current version running. You can then remove/rename the previous installation once you are satisfied that the new installation is ready. The steps below give you an example of how this would be done in a Windows environment. 

    Current Weave folders = c:\weave
    New Weave folders = c:\weave-2.6
    Weave downloaded file = c:\downloads\weave-installer-2.6.0.jar
     

      • On a Windows Command Line, run:
        cd c:\weave\jre\bin
        java -jar c:\downloads\weave-installer-2.6.0.jar c:\weave-2.6

        The last parameter in the line directly above (c:\weave-2.6) is optional, if given this will be set the default folder into which Weave will be installed, if not given the default location will be c:\weave. You also get a chance to change this during the installation process.
         
  4. Welcome: Running the Installer .jar file will open up the Weave installation wizard. Click Next on the initial screen.


     
  5. License Agreements: Click on “I accept the terms of the license agreement” to accept the license agreement and click Next. 


     

  6. Target Path: Select an installation path and click Next. The default path is C:\weave as per Step 3. 



  7. Click OK in the resulting window to create the Weave directory, then click Next.


     
  8. Installation Packages: You can select the components to install. Choose the Extensions that you wish to have access to, and click Next.



    From Weave 2.6.4, some items that were previously optional to install have been included as part of the Main Components item so don't need to be individually selected. This includes the Google, Zip'n'Ship and Spatial Upload items. Also two new extensions have been added - System Metrics and Online Help.

     
  9. User Data: Specify the port numbers for Weave to connect with. Please make sure that these ports are not already in use by other applications. Click Next.


     
  10. If needed, you can configure telnet access to Weave’s OSGi console, and click Next.


     
  11. The following screen shows the service settings for Weave. Click Next to proceed.


     
  12. In the following screen, configure the proxy settings if applicable, and click Next.


     
  13. The Weave installation will now begin.


     
  14. When the installation is complete, click on Next to proceed.



  15. Once the installation is finished you can chose to generate an automatic installation script with all your settings for future use by clicking the button. Else click Done to exit the wizard. 


     
  16. To complete the installation process, you have to carry out a few minor steps as described below.

  17. Copy your existing configuration XML files to the new installation (e.g. c:\weave\platform\workspace\config).

  18. Copy other configuration files that need to be carried over from your old installation to the new one (e.g. C:\weave\platform\workspace\reports, C:\weave\platform\workspace\icons, C:\weave\platform\workspace\logging.properties, C:\weave\platform\workspace\config.xml, C:\weave\platform\workspace\users.properties, etc.).
     
  19. If you have installed particular JDBC drivers for your existing Weave, copy them into the new installation (c:\weave\platform\workspace\jdbc).
     
  20. If you have had functions written specifically for your environment, you'll need to copy the customised bundles (binary files) to the new installation (C:\weave\platform\plugins). Also copy the config.ini from your existing installation as this file lists the bundles to start when Weave starts up (or edit the new config.ini file to include your custom bundles). 
     
  21. Once you have copied all the appropriate files to your new installation folders you can start Weave in one of two ways - if the Weave instance is to be used as a development server for creating and testing changes to configuration files then it's best to start Weave from the startup.cmd file, however if this Weave instance is intended to run all the time, or in a production/UAT fashion, then it's usually better to start it as a service.
    1. Start Weave manually by running c:\weave-2.6\startup.cmd.
    2. Start Weave automatically by running c:\weave-2.6\service\bat\installService.bat as the Administrator. Then either use the Windows control panel services applet to start the new service or run c:\weave-2.6\service\bat\startService.bat
      1. The configuration file for running the service is at c:\weave-2.6\service\config\wrapper.conf. It contains settings that you may want to update to suit your local environment, i.e. the user that will run the service, the amount of memory to use, etc.
      2. Also if you start Weave using startup.cmd then switch to using the service, if the service is not run as the same user that ran startup.cmd you may have files created that are no longer readable/writable by the user that is running the service so you may need to fix permissions.

  22. In the Weave client, click the About button as this will give you the software version, confirm that is corresponds with the version you've upgraded to (or check the c:\weave-2.6\version.txt file).


The same process should be followed to start the installation process when installing any additional components that come with their own installer, e.g. the editing extensions, the interoperability extensions or the report designer


For: