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.
Related
I am trying to deploy a simple standalone war file in liferay tomcat version. It is neither a portlet nor theme. How can I configure the war file to be deployed as a standalone war in liferay tomcat.
I am getting following error
16:45:51,175 ERROR [localhost-startStop-1][HotDeployImpl:211]
com.liferay.portal.kernel.deploy.hot.HotDeployException: Error
registering portlets for travelinsurancetravelinsurance
So, I simply want to skip this registration as a portlet and access in by the url. Is this possible?
What did you try so far? Just deployed to tomcat webapps directory? That should work. Make sure your plugin does not have any Liferay-recognized deployment descriptor, then everything should work and any complaints by Liferay can be ignored. Don't go through Liferay's deploy directory if you're not deploying a Liferay component.
I have created some theme in Liferay. Then I exported it as a *.war file. My next step was to install it on liferay server and then run. But this theme doesn't work, it is unavailable. Do you know why?
Aditional information ... same I did with some portlets and it works. Thank you.
I am getting stuck while creating a new plugin project in liferay, eclipse get stuck everytime and console displaying only [ivy:resolve] message
It appears that the Ivy resolve process inside of the Liferay Plugins SDK is failing when it tries to create a new process.
Go into your Liferay Plugins SDK folder and open the ivy-settings.xml file. Notice that it points to some online repositories. It seems that your system is having trouble connecting to those remote repositories. See the log messages about the failing certificates (when its trying to connect to the https:// server of jboss repository ).
Maybe will be any special configuration required for connecting to those repositories, proxy...
Try from here
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.
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.