Jetspeed 2
  1. Jetspeed 2
  2. JS2-786

Tool for conversion preferences from database no-principal preferences to defaults preferences in psml pages

    Details

      Description

      With jetspeed 2.0 version all preferences was per entity. But all preferences become per user with release of jetspeed 2.1.
      But people with Jetspeed 2.0 have important use case: admin configures portlets on public portal pages for all users (include guests).
      So, people with Jetspeed 2.0 can't migrate to 2.1 version (and later versions).

      edit-defaults custom portlet mode (https://issues.apache.org/jira/browse/JS2-634) can solve this problem. But people with Jetspeed 2.0 can't use edit-defaults portlet mode, because edit-defaults custom portlet mode stores preferences directly in psml pages, and there is no conversion tool to convert no-principal preferences from database to psml pages.

      So, there is need for conversion tool that moves no-principal preferences from db directly to psml pages.

      This is the only way to migrate to Jetspeed 2.1.3 for company that uses important use case described above.

        Activity

        Hide
        Vitaly Baranovsky added a comment -

        Woonsan says (http://issues.apache.org/jira/browse/JS2-634) he will not implement utility (
        >By the way, I will not try implementing the migration tool for some reason.
        >Vitaly, if you still want a migration tool which might be contributed by someone, would you create another issue for the tool? Thanks.
        )

        David, can I ask you, what is the plan for conversion utility?

        Show
        Vitaly Baranovsky added a comment - Woonsan says ( http://issues.apache.org/jira/browse/JS2-634 ) he will not implement utility ( >By the way, I will not try implementing the migration tool for some reason. >Vitaly, if you still want a migration tool which might be contributed by someone, would you create another issue for the tool? Thanks. ) David, can I ask you, what is the plan for conversion utility?
        Hide
        Vitaly Baranovsky added a comment -

        David, so can you answer, what is your plans for conversion utility?

        It is very important for our projects. Please, help me.

        Show
        Vitaly Baranovsky added a comment - David, so can you answer, what is your plans for conversion utility? It is very important for our projects. Please, help me.
        Hide
        David Sean Taylor added a comment -

        I will try to get it into 2.1.3

        Show
        David Sean Taylor added a comment - I will try to get it into 2.1.3
        Hide
        Vitaly Baranovsky added a comment - - edited

        Thanks!

        It is only the way to migrate portal to 2.1.3 version from portals with Jetspeed 2.0 if admin configures public pages for users.

        Show
        Vitaly Baranovsky added a comment - - edited Thanks! It is only the way to migrate portal to 2.1.3 version from portals with Jetspeed 2.0 if admin configures public pages for users.
        Hide
        David Sean Taylor added a comment -

        Addressing preferences performance with:

        1. indexes: see prefs-schema.xml. With tests of 10,000 prefs, this sped up retrieval 700%
        2. preload feature: see prefs.xml, ability to preload prefs into cache by Portlet App or by entities (all or none)

        I did not write a preferences converter. I tried to contact the reporter of this issue, but did not receive a reply from him.
        I assume that this bug is either resolved or no longer an issue

        Show
        David Sean Taylor added a comment - Addressing preferences performance with: 1. indexes: see prefs-schema.xml. With tests of 10,000 prefs, this sped up retrieval 700% 2. preload feature: see prefs.xml, ability to preload prefs into cache by Portlet App or by entities (all or none) I did not write a preferences converter. I tried to contact the reporter of this issue, but did not receive a reply from him. I assume that this bug is either resolved or no longer an issue
        Hide
        Vitaly Baranovsky added a comment -

        David, I've tested your changes to database schema. Speed up of loading preferences is 8 times! And it is a good result!

        I've made one test. One of my pages loaded 469 seconds before index optimization, and 57 seconds after index optimization. But it is still big time. All psml of our portal was preloaded more than 6 hours before optimization, and about 1 hour after optimization.

        And there is one big problem! Jetspeed 2.1.3 uses prefs per user. But Jetspeed 2.0 used prefs per entity. So, we can't use Jetspeed 2.1.3, because we have use cases, when admin users configures public pages. So, we need edit-defaults custom portlet mode.

        But we have big portal, created with edit mode with Jetspeed 2.0. So, we still need converter to convert our Jetspeed 2.0 per entity db preferences to defaults psml preferences.

        And, I think, all Jetspeed 2.0 users that use this use case has such problem too.

        So, can you create such converter? I will reopen this issue as its creator...

        P.S.: Sorry I'm not answering before, I was in vacation...

        Show
        Vitaly Baranovsky added a comment - David, I've tested your changes to database schema. Speed up of loading preferences is 8 times! And it is a good result! I've made one test. One of my pages loaded 469 seconds before index optimization, and 57 seconds after index optimization. But it is still big time. All psml of our portal was preloaded more than 6 hours before optimization, and about 1 hour after optimization. And there is one big problem! Jetspeed 2.1.3 uses prefs per user. But Jetspeed 2.0 used prefs per entity. So, we can't use Jetspeed 2.1.3, because we have use cases, when admin users configures public pages. So, we need edit-defaults custom portlet mode. But we have big portal, created with edit mode with Jetspeed 2.0. So, we still need converter to convert our Jetspeed 2.0 per entity db preferences to defaults psml preferences. And, I think, all Jetspeed 2.0 users that use this use case has such problem too. So, can you create such converter? I will reopen this issue as its creator... P.S.: Sorry I'm not answering before, I was in vacation...
        Hide
        David Sean Taylor added a comment -

        Converter written and provided.

        Show
        David Sean Taylor added a comment - Converter written and provided.

          People

          • Assignee:
            David Sean Taylor
            Reporter:
            Vitaly Baranovsky
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development