How can I know the release of a running liferay? Is there any file to check somewhere?
I tried to check dome of the readme files but didn"t find anything
Goto Control Panel -> Server Administration, there the version will be displayed:
Another option is to check (grep) $LIFERAY_HOME/logs/liferay.yyyy-mm-dd.log which reports the version number during startup:
08:49:06,691 INFO [fileinstall-C:/liferay70/osgi/marketplace][BundleStartStopLogger:35] STARTED Liferay CE Foundation_7.0.7 [174]
If you didn't change the http.header.version.verbosity=full
the liferay version it is being shown on the response headers.
Below is the info about this property, from portal.properties on liferay sources.
#
# Set the level of verbosity to use for the Liferay-Portal field in the HTTP
# header response. Valid values are "full", which gives all of the version
# information (e.g. Liferay Portal Community Edition 6.1.0 CE etc.),
# "partial", which gives only the name portion (e.g. Liferay Portal
# Community Edition), or the default release name (e.g. "Liferay Portal
# Community Edition" or "Liferay Portal Enterprise Edition"), which prevents
# the Portal from adding the Liferay-Portal field in the HTTP header
# response. The default release name must match the Portal edition being
# used.
#
http.header.version.verbosity=full
Hope this helps
Related
I tried to copy the content DB from Prod to Dev server for the first time in my SP 2016 environment. Both the environments build versions are same (16.0.4705.1000). However in the prod under "Manage Patch Status" I see one extra Feature Pack 2 patch (16.0.4588.1001).
https://support.microsoft.com/en-us/help/4011127/descriptionofthesecurityupdateforsharepointserver2016september12-2017
Now when I am doing Mount-SPContentDatabase, I get the following error.
Mount-SPContentDatabase : An extension defined in the database is not registered with the farm.
In the ULS I see the following information. It says the project server database extensions are missing.
Following are my questions,
Is this because I have installed Feature Pack 2(link above) in Prod which has security updates for Project server? We don't have project server enabled in either of the environments.
Can I install the Feature Pack 2 in Dev now even though it has higher security update already installed? Isn't the later patch includes everything that was released in the previous patches?
This is just for my understanding. In the manage patch status why does the Install Status for feature pack 2 shows as "Superseded" even though I have other later patches?
Tried Restore-SPsite as well but getting error "The extension set does not match."
Had the same problem during the migration from 2016 -> 2019.
My solution:
Register the missing extension https://techcommunity.microsoft.com/t5/sharepoint-support-blog/upgrading-a-content-db-from-sharepoint-2016-to-sharepoint-2019/ba-p/1374209 (look at the bottom of the post)
remount the contentDB
Required code to perform the registration in step 1:
Check extensions in old farm
$contentservice=[Microsoft.sharepoint.Administration.SPwebservice]::ContentService
$contentservice.RegisteredDatabaseExtensionTypes >> SP2016Farm_registered_Extn.txt
Check extensions in new farm
$contentservice=[Microsoft.sharepoint.Administration.SPwebservice]::ContentService
$contentservice.RegisteredDatabaseExtensionTypes >>SP2019Farm_registered_Extn.txt
Register missing extension in new farm
$svc = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.Office.Project.Server.Database.Extension") | FL
$svc.RegisteredDatabaseExtensionTypes.EnsureAdded([Microsoft.Office.Project.Server.Database.Extension.ProjectDatabaseExtension])
$svc.Update($true)
In my case i did the steps below before i have registered the missing extension, but i think/hope there is no need to do that.
Powershell: Enable-ProjectServerLicense (Trail License)
Check running Sharepoint CA > ProjectServer Service
Check/create Sharepoint CA > ProjectServer Application
I'm trying to use Liferays webservices (viewable at /api/jsonws), but my Liferay installation is not starting any of this services. I'm running Liferay 6.1.3 on JBoss 7.2. This problem occures on three different servers. Same Liferay & JBoss setup on all 3. Only difference is that one of those servers had Liferay 6.2 running briefly. 6.2 allowed access to all webservices from /api/jsonws. Sadly I cannot switch back to 6.2 for several reasons.
Got a log entry stating that no service is configured.
16:36:03,291 DEBUG [ServerService Thread Pool -- 268][JSONWebServiceConfigurator:221] Configure JSON web service actions
16:36:03,299 DEBUG [ServerService Thread Pool -- 268][JSONWebServiceConfigurator:236] Configured 0 actions in 7 ms
Same liferay on a local tomcat works pretty fine and starts all webservices. So my question is if there is any kind of global on/off switch or if I have to set any special settings? I'm running out of ideas right now ...
Thanks in advance and regards, Sebastian
It may be worth checking portal-ext.properties file in your server.
There is a setting to turn JSON web services on/off. I guess it may be set as "false" in your case.
#
# Set this property to true to enable JSON web services. Note that setting
# this to false will cause portlets that make JSON web service calls from
# working.
#
json.web.service.enabled=true
I am working with Liferay 6.0 on JBoss 5.1.1, Windows 8 is the OS. On server startup I always get the following error explaining the auto deploy directory can't be found:
ERROR [AutoDeployDir:90] Directory F:\liferay-portal-ee-6.0\deploy could not be created
This makes sense because I don't have an F: drive. However, I'm unable to configure it in the portal-ext.properties file as explained here. When I log into the Liferay control panel, and look under Portal Administration -> Portal Properties, I can see that the value I put in ext.properties is indeed displayed as the value for auto.deploy.deploy.dir. However, when the server starts up, it is using F:\liferay-portal-ee-6.0\deploy as the auto deploy directory and logging the error above. I have debugged the GlobalStartupAction class which initializes Liferay's auto deploy and I can see that it's calling PrefsPropsUtil.getString(String, String) to retrieve the value for the auto deploy directory and it's passing the value I set in portal-ext.properties as the second argument, according to the PrefsPropsUtil Java doc the second argument is a default value. When I dig down into the PrefsPropsUtil.getString call I can see that it's using an instance of PortalPreferencesLocalServiceImpl to retrieve a list of properties by companyId, ownerId and ownerType which are set to 0, 0 and 1 respectively. Since the PortalPreferencesLocalServiceImpl is "local" I'm assuming it's not going to a different machine to retrieve values. I've done extensive directory and file searching for references to auto.deploy.deploy.dir and values like F:\liferay-portal-ee-6.0 and I'm unable to fine where this property is getting set. Where is this value coming from and why isn't my override being used?
Since you are using Liferay 6.0, go to Control Panel-> Plugins Installation -> Install More Portlets -> Configuration.
In the configuration tab, you may see the Deploy directory set to be F:\liferay-portal-ee-6.0\deploy
This may be because either someone has modified the value from the control panel or you are using database dump from some other existing Liferay installation.
You can use auto.deploy.dest.dir property in portal-ext.properties to set auto deploy path.
i.e
auto.deploy.dest.dir=C:/../../autodeploy
HTH
I downloaded liferay 6.1 with bundled tomcat from the website and i am currently trying to add a new repository in the documents and media portlet, using the process described in here.
Although the integration succeeds, in the repository list, the newly created cmis repository (alfresco) displays the following warning: "an unexpected error occured while connecting to the repository". Nothing on the catalina.out and the liferay logs though. Then when i try to create a subfolder, i get the following exception: in apache chemistry CmisRuntimeException: Length Required.
I checked with wireshark and, in fact the POST request from liferay to alfresco misses the content-length indeed. How can i enable it ? has anyone had similar issues ?
Any help will be much appreciated.
Best regards
Portal Settings - Authentication - Use screen name.
Nickname and password for account creating repository should be same as for alfresco.
Add parameters to portal-ext.properties
session.store.password=true and company.security.auth.type=screenName
Create repository. Use URL path /alfresco/service/cmis (not /alfresco/cmisatom). Live repository ID blank.
Read more at
Mounting Multiple CMIS Repositories on Liferay 6.1 and CMIS Repository.
Liferay migration from one server to another help required. Can anyone share there steps for migration of Liferay portal 5.2.3 from one server to another. I am using Windows + Tomcat + MySql.
I have uploaded whole tomcat folder to the new windows machine and imported the database too with the corresponding change to the configuration file like Database details.
But after starting the tomcat server it is showing some error like "Unable to load repository http://plugins.liferay.com". Any idea why I am getting this error ?
These are the steps that I have followed and able to migrate the Liferay successfully:
Take the backup of Liferay files and database from first windows machine.
Install the same version of Liferay (Say Liferay 5.2.3) on second windows machine.
Shut down Liferay.
Import the database on new system.
Add portal-ext.properties with relevant entries. (e.g Datbase Name, User Name , Pasword etc)
Add \liferay-portal-5.2.3\data\document_library files from old machine.
Start the tomcat. It will automtically do the rest.
NOTE: In the above method I have not deployed Theme and custom plugins etc, you have to deploy Theme and custom plugins also that are used on old system.
Lifery is trying to connect to plugin repository to find whether there are updates for plugins.
Does your new machine have internet conectivity?
Also you have options to ignore that message or configure liferay not to check for updates.
For later put in portal-ext.properties
plugin.repositories.trusted=
plugin.repositories.untrusted=
UPDATE:
If behind proxy create (if not existent) system-ext.properties (beside portal-ext.properties) and add
com.liferay.util.Http.proxy.host=proxy_host
com.liferay.util.Http.proxy.port=proxy_port
Change proxy_host and proxy_port with your values.
Also remove from portal-ext.properties if you want liferay to check repositories
plugin.repositories.trusted=
plugin.repositories.untrusted=