Jive provides an installer that deploys the Jive for SharePoint Windows Solution
Package (.wsp) to your Windows SharePoint Server. This installation requires assistance from
a Professional Services engineer.
Use the installer script to automatically deploy the .wsp solution
file onto your SharePoint server. The script is available as an attached file from
the Release Notes.
Use the same script to upgrade, install, or uninstall Jive for SharePoint.
Note: This installation requires assistance from a Professional Services
Before you install, note the following prerequisites.
- The installer script can only be used with SharePoint 2010 and 2007 when
installed in the default directory.
- In case of fatal error, after the source of the problem has been
resolved, the solution must be retracted/deleted manually by the
administrator before attempting to redeploy automatically.
- The SharePoint Administration and SharePoint Timer services must be
started to enable deployment automation, which standard in
If you are upgrading, perform an IISRESET before running the installer script
in order to have IIS release some locks on the Jive DLLs.
Save the .bat file to the same directory as the
To install, uninstall, or get help for the installWSP.bat,
type the appropriate command at a command line:
Note: When you run the install script on an individual SharePoint farm, you need
to run it on only one web server only (not on all of them). Never run the
script on the Application Server. When you run the install script on a
multiple SharePoint farm, you need to run the script on one web server in
|To do this
||Type this command
|Upgrade the current Jive for SharePoint.
|Uninstall the current Jive for SharePoint.
|Install Jive for SharePoint for the first time when you
don't have an existing installation.
|Provide help when typed at a command line.
Because some of the calls wait for SharePoint to process, the batch makes
several pauses, waiting for SharePoint to complete each stage. You can use
the solution management screen of the Central Administration website to
monitor when a step is completed. For example, it's waiting for the Old site
feature to be retracted, new site feature to be installed, and the new site
feature to be deployed.
Note: If the retry fails indefinitely, the deploy
procedure should be stopped manually by pressing CTRL+C. You can then
investigate why the script can't perform the operation.