I wan't to migrate my Liferay 6.1 from filesystem to Alfresco.
When I introduce these parameters in portal-ext.properties:
dl.store.impl=com.liferay.portlet.documentlibrary.store.CMISStore
dl.store.cmis.credentials.username=admin
dl.store.cmis.credentials.password=admin
dl.store.cmis.repository.url=http://localhost:9080/alfresco/service/api/cmis
dl.store.cmis.system.root.dir=Liferay Home
The option CMIS in Administration panel-Migration dissapear.
If I select FileSystem, the console shows me this error
Exception in thread "liferay/convert_process-1" java.lang.NoClassDefFoundError: Could not initialize class com.liferay.portlet.documentlibrary.store.CMISStore$SessionHolder
at com.liferay.portlet.documentlibrary.store.CMISStore.<init>(CMISStore.java:64)
at sun.reflect.GeneratedConstructorAccessor111.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at com.liferay.portlet.documentlibrary.store.StoreFactory.getInstance(StoreFactory.java:87)
at com.liferay.portal.convert.ConvertDocumentLibrary.doConvert(ConvertDocumentLibrary.java:91)
at com.liferay.portal.convert.ConvertProcess.convert(ConvertProcess.java:44)
at com.liferay.portal.convert.messaging.ConvertProcessMessageListener.doReceive(ConvertProcessMessageListener.java:47)
at com.liferay.portal.convert.messaging.ConvertProcessMessageListener.receive(ConvertProcessMessageListener.java:32)
at com.liferay.portal.kernel.messaging.InvokerMessageListener.receive(InvokerMessageListener.java:63)
at com.liferay.portal.kernel.messaging.SerialDestination$1.run(SerialDestination.java:110)
at com.liferay.portal.kernel.concurrent.ThreadPoolExecutor$WorkerTask._runTask(ThreadPoolExecutor.java:671)
at com.liferay.portal.kernel.concurrent.ThreadPoolExecutor$WorkerTask.run(ThreadPoolExecutor.java:582)
Any Ideas?
Many thanks in advance
You probably have all of your documents in a filesystem repository (or the default repository).
For migration you'll have to run Liferay with a setting that has all documents, e.g. before you change your portal-ext.properties to CMIS.
What you can and should do is to configure the access credentials to your CMIS installation, but don't update the dl.store.impl yet.
Now go to the Migration form in Server Administration (can't remember exactly, I have no admin access to Liferay currently), you can select CMIS as the target that you migrate to. Once migration has been done, shut down, change the value for dl.store.impl and start up. Make sure that nobody uploads new documents during the migration process.
Related
I'm running into a strange behavior with my liferay 6.2 (build 6210). I was trying to install the latest fixpack portal-84 and cannot start my server since. Since I reverted all fixpacks etc. and still the startup doesn't work I doubt the update is the reason. I get the following message Permission conversion to algorithm 6 has not been completed. Up until this point the startup looks normal. Strange thing is my database schema was never used for anything else than liferay 6.2.
10:42:13,566 ERROR [localhost-startStop-1][MainServlet:212] java.lang.IllegalStateException: Permission conversion to algorithm 6 has not been completed. Please complete the conversion prior to starting the portal. The conversion process is available in portal versions starting with 5203 and prior to 6200.
java.lang.IllegalStateException: Permission conversion to algorithm 6 has not been completed. Please complete the conversion prior to starting the portal. The conversion process is available in portal versions starting with 5203 and prior to 6200.
at com.liferay.portal.tools.DBUpgrader._checkPermissionAlgorithm(DBUpgrader.java:297)
at com.liferay.portal.tools.DBUpgrader.upgrade(DBUpgrader.java:135)
at com.liferay.portal.events.StartupAction.doRun(StartupAction.java:181)
at com.liferay.portal.ee.license.StartupAction.doRun(Unknown Source)
at com.liferay.portal.events.StartupAction.run(StartupAction.java:74)
at com.liferay.portal.servlet.MainServlet.processStartupEvents(MainServlet.java:1245)
at com.liferay.portal.servlet.MainServlet.init(MainServlet.java:209)
at javax.servlet.GenericServlet.init(GenericServlet.java:160)
at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1280)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1193)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1088)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5176)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5460)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:656)
at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1635)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Stopping the server due to unexpected startup errors
Is assume that something is wrong within my database (although I have no idea how that happened). When I start liferay with the embedded memory DB the startup works. There are only some other messages in the log because there are lucene files in filesystem without entries in memory db. select * from RELEASE_; states the correct version portal 6210 and my configured database connection is correct as well (tried with jndi resource in tomcat and with conenction information in portal-ext.properties). But maybe there is some other location where a version is saved and is vital to portal startup.
Did anyone ever had this behavior or is this a completely special case that is (more or less) exclusive to me?
Thanks ans regards. Sebastian
The upgrade script checks if the ResourceCode table is empty. It was used prior to Liferay 6, Liferay 6 upgrade scripts usually remove all data from it or the whole table whatsoever.
To overcome this issue I did all the steps according to this tutorial from Liferay. The only difference to your situation is that I'm using Liferay CE.
Very general question here:
I have Liferay 6.1.1 ga2 set up on my Oracle WebLogic 12c.
It works fine on my local, but when I deploy it onto our development server, I lose all write permissions.
E.g., changing the theme/color scheme, creating web content, pages, and saving changes to most things
I try to import LARs however it is saying it is not permitted
I'm not seeing any errors in the logs, and the control panel messages are even telling me my content was created or change successfully (besides the LARs0, but everything stays the same.
Any reason(s) why my changes aren't showing up? I'll surely give a bounty if I can get pointed in the right direction here
Given your description, I'd recommend checking OS issues, like write access to various folders, like temporary folders etc.. I guess that Liferay has proper permissions to the whole database (it's rare to have incomplete access) and can write to all tables. And you're operating on a portal-wide admin account, right?
Unrelated to LAR import, changes will not show up if you have workflow enabled - then you'd find the changes in the list of tasks that need approval.
As staging has quite an obvious UI in 6.1, I assume you don't have staging activated, otherwise you just need to publish. In order to see new portlets, make sure that the "Edit Controls" checkbox in your dockbar is checked. This has bitten me more than once.
if you're running a cluster, make sure that you have set it up correctly, e.g. that you don't see cached content on your node.
Can you confirm that you can see the options to change on the UI, just that your changes aren't persisted?
Also, please note that Weblogic 12c is not on the "supported Appservers" list for Liferay 6.1, it's there for Liferay 6.2 only (probably due to release date). This doesn't mean that it shouldn't run, just that it's not tested for your version. Further, there's a GA3 release for 6.3 already, so you might want to check if it's a problem that's fixed in GA3.
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.
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=