Migrate from Liferay Portal EE 6.1.20 to Liferay Portal CE 6.1.1












1














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).



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.


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










share|improve this question





























    1














    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).



    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.


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










    share|improve this question



























      1












      1








      1







      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).



      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.


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










      share|improve this question















      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).



      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.


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







      migration liferay liferay-6






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jul 31 '13 at 12:28

























      asked Jul 31 '13 at 10:02









      Maria Ioannidou

      1,17611135




      1,17611135
























          2 Answers
          2






          active

          oldest

          votes


















          1














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



          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.






          share|improve this answer





























            0














            In my case, I had the connection to database written in context.xml inside tomcat/conf folder.
            Make sure you check the connection and it is pointing to the right database. and also deleting release_ table helped me.






            share|improve this answer





















              Your Answer






              StackExchange.ifUsing("editor", function () {
              StackExchange.using("externalEditor", function () {
              StackExchange.using("snippets", function () {
              StackExchange.snippets.init();
              });
              });
              }, "code-snippets");

              StackExchange.ready(function() {
              var channelOptions = {
              tags: "".split(" "),
              id: "1"
              };
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function() {
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled) {
              StackExchange.using("snippets", function() {
              createEditor();
              });
              }
              else {
              createEditor();
              }
              });

              function createEditor() {
              StackExchange.prepareEditor({
              heartbeatType: 'answer',
              autoActivateHeartbeat: false,
              convertImagesToLinks: true,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: 10,
              bindNavPrevention: true,
              postfix: "",
              imageUploader: {
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              },
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              });


              }
              });














              draft saved

              draft discarded


















              StackExchange.ready(
              function () {
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f17967379%2fmigrate-from-liferay-portal-ee-6-1-20-to-liferay-portal-ce-6-1-1%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              1














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



              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.






              share|improve this answer


























                1














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



                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.






                share|improve this answer
























                  1












                  1








                  1






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



                  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.






                  share|improve this answer












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



                  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.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Aug 2 '13 at 11:08









                  Maria Ioannidou

                  1,17611135




                  1,17611135

























                      0














                      In my case, I had the connection to database written in context.xml inside tomcat/conf folder.
                      Make sure you check the connection and it is pointing to the right database. and also deleting release_ table helped me.






                      share|improve this answer


























                        0














                        In my case, I had the connection to database written in context.xml inside tomcat/conf folder.
                        Make sure you check the connection and it is pointing to the right database. and also deleting release_ table helped me.






                        share|improve this answer
























                          0












                          0








                          0






                          In my case, I had the connection to database written in context.xml inside tomcat/conf folder.
                          Make sure you check the connection and it is pointing to the right database. and also deleting release_ table helped me.






                          share|improve this answer












                          In my case, I had the connection to database written in context.xml inside tomcat/conf folder.
                          Make sure you check the connection and it is pointing to the right database. and also deleting release_ table helped me.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Nov 12 at 18:47









                          Vineela Thonupunuri

                          5010




                          5010






























                              draft saved

                              draft discarded




















































                              Thanks for contributing an answer to Stack Overflow!


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid



                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.


                              To learn more, see our tips on writing great answers.





                              Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                              Please pay close attention to the following guidance:


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid



                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.


                              To learn more, see our tips on writing great answers.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function () {
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f17967379%2fmigrate-from-liferay-portal-ee-6-1-20-to-liferay-portal-ce-6-1-1%23new-answer', 'question_page');
                              }
                              );

                              Post as a guest















                              Required, but never shown





















































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown

































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown







                              Popular posts from this blog

                              Bressuire

                              Vorschmack

                              Quarantine