Unlike previous versions of Social Office, Social Office 2.0 is available as an application that can be installed on Liferay Portal 6.1. Liferay applications, or apps, are packages of Liferay plugins that are grouped together with descriptions, version information, and other metadata. You can identify downloaded Liferay apps by their
.lpkg file extensions. They’re available from Liferay Marketplace at http://www.liferay.com/marketplace. Prior to version 2.0, Social Office was provided as an independent product that was based on, but separate from, Liferay Portal.
To install Social Office manually, you just need to deploy the Social Office
.lpkg file to your Liferay installation. If you’re installing Social Office CE, you can install it just like any other app from Liferay Marketplace. Remember that there are two ways to access Liferay Marketplace: from http://www.liferay.com/marketplace or from the Marketplace section of your Liferay instance’s Control Panel. If you purchase Social Office EE, you need to deploy the license order id that you’ll receive before you can install Social Office.
To find Social Office EE on Liferay Marketplace, click on the EE Marketplace link and look for the Social Office EE app. Once you’ve found it, click on it to view some details about the app. If you’d like to install Social Office EE, you can either purchase the app or you can obtain a free 30-day trial.
Whichever option you choose, you’ll be prompted to select a purchase type. If you’d like to obtain the free 30-day trial, you’ll need to agree to the End User License Agreement and Terms of Service before you can click Free to obtain the trial license.
Once you’ve obtained a Social Office EE license (trial or otherwise), you should deploy the license to your Liferay instance. To do so, first click on License Manager at the bottom of the Server Administration section of the Control Panel. Then enter your order id into the field provided, click Query, and select Social Office EE. Now you’re able to install Social Office EE! Note: If you already downloaded Social Office EE and attempted to install it before deploying your order id license, you’ll need to restart your Liferay server after deploying the license in order for Social Office EE to deploy.
The Social Office
.lpkg file is hot-deployable and includes the following Liferay plugins. The plugins listed in italics belong only to either the CE or EE versions of Social Office.
After deploying Social Office, we recommend that you restart your application server. Restarting may not be necessary in all cases but it can help you avoid potential caching problems. For example, sending and accepting connection invitations among Social Office users might not work without a server restart. For additional information, see the section below on installation peculiarities for specific application servers. If you want to avoid restarting, you should at least re-index Liferay’s search indexes and database cache. These options are available from the Server Administration section of Liferay’s Control Panel.
Installation Peculiarities for Specific Apps Servers
After installing Social Office on Glassfish, you need to restart the server before Social Office will be fully deployed. If you don’t restart, Glassfish doesn’t recognize the so-hook and the hook won’t be available. Once you’ve restarted the server, the so-hook deployment completes as expected.
For JBoss, you have to restart the server in order to see the Dashboard link. If you don’t restart the server, the Dashboard link won’t appear although you can find other content added by Social Office if you use the Go To → My Public/My Private Pages menu. To fix this issue, simply restart your server.
Uninstalling Social Office
If you’d like to uninstall Social Office, you can do so from the Purchased page of the control panel, under the Marketplace heading. However, after you’ve uninstalled Social Office from Marketplace, you need to manually revert the friendly URL of the Welcome page.
Otherwise, the portal will always be looking for the
/so/login page which no longer exists since the hook is gone. This will produce a number of errors in the log and once you log out, you won’t be able to log in again.