During upgrade liferay due to some exception my liferay upgrade stops. Please check the link for the details of log file http://kl1p.com/up_6_0_6_1. I have done specific changes that we have to do in portal-ext.properties too. Not sure what we have to put for "upgrade.processes = XXX".
The following is what the portal.properties contain for 6.1:
upgrade.processes=\
com.liferay.portal.upgrade.UpgradeProcess_5_0_0,\
com.liferay.portal.upgrade.UpgradeProcess_5_1_0,\
com.liferay.portal.upgrade.UpgradeProcess_5_1_2,\
com.liferay.portal.upgrade.UpgradeProcess_5_2_0,\
com.liferay.portal.upgrade.UpgradeProcess_5_2_1,\
com.liferay.portal.upgrade.UpgradeProcess_5_2_2,\
com.liferay.portal.upgrade.UpgradeProcess_5_2_3,\
com.liferay.portal.upgrade.UpgradeProcess_6_0_0,\
com.liferay.portal.upgrade.UpgradeProcess_6_0_1,\
com.liferay.portal.upgrade.UpgradeProcess_6_0_2,\
com.liferay.portal.upgrade.UpgradeProcess_6_0_3,\
com.liferay.portal.upgrade.UpgradeProcess_6_0_5,\
com.liferay.portal.upgrade.UpgradeProcess_6_0_6,\
com.liferay.portal.upgrade.UpgradeProcess_6_1_0
com.liferay.portal.upgrade.UpgradeProcess_6_1_0 this is fine.
So you don't need to set anything in your portal-ext.properties for this field for upgrading to 6.1.
As for the errors they are usual as you mentioned as there are a lot of changes int the Doc library portlet and Image portlet from 6.0 to 6.1.
Related
i am using liferay framwork, some message showing "Not updating Demo *** because version 6.2.5 is newer than version 6.2.0.1" when try do deploy.plz help me.how to fix and update version?
You just have to add this line: module-version=6.2.0.5 under module-incremental-version=1 in liferay-plugin-package.properties file. And it will work. That thing bothered me for a long time too, so I looked into the source code and now it works like a charm. You can experiment with module-version number. Example liferay-plugin-package.properties:
name=Demo
module-group-id=liferay
module-incremental-version=1
module-version=6.2.0.5
tags=
short-description=
long-description=
change-log=
page-url=http://www.liferay.com
author=Liferay, Inc.
licenses=LGPL
liferay-versions=6.2.0+
portal-dependency-jars=\
groovy.jar,\
asm.jar,\
antlr3-runtime.jar,\
antlr2.jar,\
antlr3.jar
My guess:
If you are getting this error while deploying a plugin to liferay server, check in your liferay-plugin-package.properties if there is a liferay version specified which is required by the portlet.
Update the version and if you are still getting the error, remove the portlet from webapps and redeploy again.
I am trying to deploy Liferay 6.1 on WAS 7.0.
Though I have deployed it successfully with context path as "lportal", while accessing it I facing following issues
class not found
com.liferay.portal.kernel.servlet.filters.invoker.invokerfilter
exception
Which was resolved somehow by restarting the server.
Currently, I have portlet.jar, portal-service.jar, mysql.jar and hsql.jar in global path i.e
IBM/WebSphere/AppServer/lib/ext folder
Dockbar portlet is not loading up and showing only processing icon
Has anyone tried this and access liferay from WAS successfully?
Any help is appriciated.
I need to make an upgrade of Liferay, as mentioned above(5.2->6.0) So far, as my research (1,2,3) shows I need to:
Make backups of the Database and file system of plugins (especially portal*.properties).
Overwrite dependency jars
Deploy new .war
Set permission algorithm to 5 in the properties (as L-5.2 uses it, however L-6.0 uses 6)
Start application,
see if the DB updates correctly
see if the portal is working correctly
Clean up user-specific permissions
Convert legacy permission algorithm to 6 in the control Panel
Migrate a custom theme.
Upgrade EXT to EXT Plugin(p. 398)
It's fairly understandable, but I stumbled upon this thread(Missing FileEntryForm class). Are there any more changes of this kind?
Also, is there something else I'm missing?
Thanks :)
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.
Im new with liferay have a problem with portlet deployment using the plugins sdk,
Platform:
liferay-portal-tomcat-5.5-5.1.2,
liferay-plugins-sdk-5.2.2,
windows vista.
Problem:
I have successfully created a sample portlet with ant and deployed it into the hot-deploy folder. It is automatically picked up by the server but the console messages say that the portlet has been copied successfully and never registers it.. and i cant find it in the add application drop-down menu.. pls your help will be very appreciated.
I don't know if anything important changed in these versions, but you say you're using Liferay 5.1.2 with the plugin environment 5.2.2 - try with matching versions - at least on the second digit.
also, make sure that all required files are available - among them are WEB-INF/web.xml, WEB-INF/portlet.xml.
Create a new sample portlet with "create.bat" in the plugin SDK's portlet folder and deploy this - it should succeed. Then make sure that all config files from the new one are present in your current one.
How did you create your current portlet? What did you do/change?