从Liferay Portal EE 6.1.20迁移到Liferay Portal CE 6.1.1 [英] Migrate from Liferay Portal EE 6.1.20 to Liferay Portal CE 6.1.1

查看:101
本文介绍了从Liferay Portal EE 6.1.20迁移到Liferay Portal CE 6.1.1的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我想从Liferay Portal EE 6.1.20 GA2(使用试用版在本地开发)迁移到Liferay Portal CE 6.1.1 GA2(客户端要求已更改).

I would like to migrate from Liferay Portal EE 6.1.20 GA2 (developed locally with trial version) to Liferay Portal CE 6.1.1 GA2 (client requirement changed).

是否可以使用相同的数据库(可能进行某些降级过程)和配置,开发的Portlet,数据等?很多信息都存储在db中(组织层次结构,用户,角色,站点和页面模板等),并且很难通过export-imports进行手动迁移.

Is it possible to use the same db (with some downgrade process possibly) and configurations, developed portlets, data etc.? A lot of information is stored in db (organizations hierarchy, users, roles, site and page templates, etc) and it is hard to migrate it manually with exports-imports etc.

尝试使用相同的数据库会引发以下异常:

Trying to use the same db throws the following exception:

java.lang.IllegalStateException: Attempting to deploy an older Liferay Portal version. Current build version is 6120 and attempting to deploy version 6101.

在EE数据库的release_表中手动将liferay门户的构建版本从6120更改为6101是否安全?

Is it safe to manually change liferay portal's build version in the EE database's release_ table from 6120 to 6101?

推荐答案

最后,按照我的问题中的描述实施了它,并且看起来工作正常.

Finally, implemented it as described in my question and seems to work fine.

我使用了与Liferay EE 6.1.20安装相同的数据库,并在EE数据库的release_表中手动将liferay门户的构建版本从6120更改为6101. 我将Liferay CE 6.1.1捆绑软件与tomcat一起使用,并从EE捆绑软件中复制了webapps文件夹中所有已部署的插件(主题,portlet,hook等)的数据文件夹(包括文档库文件等),所有配置文件(门户) -ext.properties等).

I used the same db as Liferay EE 6.1.20 installation and manually changed liferay portal's build version in the EE database's release_ table from 6120 to 6101. I used the Liferay CE 6.1.1 bundle with tomcat and I copied from the EE bundle the data folder (with document library files, etc) all my deployed plugins (themes, portlets, hooks etc) in webapps folder, all configuration files (portal-ext.properties, etc.).

我现在只在日志中抛出关于市场插件版本的异常,但是对于用户而言似乎并不显眼且不可见,并且一旦市场功能正常运行,就可以了.

I now only throws in the logs an exception about the marketplace plugin version but it seems unobtrusive and invisible to the user and event the marketplace feature works fine.

这篇关于从Liferay Portal EE 6.1.20迁移到Liferay Portal CE 6.1.1的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆