Search Engine: Elastic

Article ID: 3347, created on Nov 30, 2007, last review on Sep 29, 2014

  • Applies to:
  • H-Sphere

Automatic import from KB #3347


  • Login to CP server as cpanel user.
  • If a package contains templates, prepare your custom template directory according to steps 1-3 of Template Customization.
  • Install the package using the Package Installer tool. Use the --help option for the syntax:

    java --package=/path/to/package/file [--upgrade] [--check-only] [--force]    


    • --package=/path/to/package/file

    Specifies the path to the built package. H-Sphere package is a Java archive file (JAR) with .hsp extension.


    Makes utility not install the package but only perform a check routine if the package can be installed.

    • (HS 2.4.3+) [--upgrade]

    Use this option if you upgrade the package already installed on your H-Sphere. With this option, you can easily upgrade the package without uninstallation of the older package and restarting H-Sphere after the uninstallation.


    Forces the package installation even if conflicts were detected. For example, if you are installing two packages that use exactly the same file, install the first one without, and the second one with the --force option. The first instance of the file will be replaced with the second. Use this option only if you are sure this won't damage other packages.

  • Check whether all H-Sphere package components have been successfully installed.
  • Restart H-Sphere.

If something goes wrong during or after the installation, you can uninstall the package. The files installed with the package will be copied to the ~cpanel/shiva/packages/PackageName directory, where PackageName is the name of the package without its version and build number. For example, after installation of the MyPackage-1.0.1-2.hsp package its files will be stored in the ~cpanel/shiva/packages/MyPackage directory.

f213b9fa8759d57bee5d547445806fe7 3ef1f5f998c0dc182718a7fe4376f875

Email subscription for changes to this article
Save as PDF