toro-channels installation without ALM?
Mark Roedel
I've installed the toro channels and portlets following the
instructions in the toro-channels wiki, and everything's up and
running.
However, that process also forces the portal into ALM with the
Academus theme, which means I give up the snazzy new ajax features.
Can I just follow the instructions for converting to DLM in the
uPortal wiki at http://www.ja-sig.org/wiki/display/UPM/02+DLM+Administration+Guide
or are there other considerations that'd make that a bad idea?
bill.stickers
On Aug 8, 3:41 pm, Mark Roedel <MarkRoe...@letu.edu> wrote:
> Working with a fresh install of uPortal 2.6...
>
> I've installed the toro channels and portlets following the
> instructions in the toro-channels wiki, and everything's up and
> running.
>
> However, that process also forces the portal into ALM with the
> Academus theme, which means I give up the snazzy new ajax features.
> Can I just follow the instructions for converting to DLM in the
> uPortal wiki athttp://www.ja-sig.org/wiki/display/UPM/02+DLM+Administration+Guide
> or are there other considerations that'd make that a bad idea?
i spent part of the afternoon trying convert to dlm using those
instructions. so far i haven't been able to get it to work. in
portal.log i see this error:
ERROR [DLM Fragment Activator] dlm.FragmentActivator.[] Aug/08
16:43:00 -
------ Problem occurred activating Guests------
Anomaly occurred while loading layout for fragment 'Guests'. The
fragment will not be available for inclusion into user layouts.
java.lang.RuntimeException: Anomaly occurred while loading layout for
fragment 'Guests'. The fragment will not be available for inclusion
into user layouts.
at
org.jasig.portal.layout.dlm.FragmentActivator.loadLayout(FragmentActivator.java:
323)
at
org.jasig.portal.layout.dlm.FragmentActivator.activateFragments(FragmentActivator.java:
107)
at org.jasig.portal.layout.dlm.RDBMDistributedLayoutStore
$1.run(RDBMDistributedLayoutStore.java:200)
Caused by: java.lang.NullPointerException
at
org.jasig.portal.layout.dlm.RDBMDistributedLayoutStore.getStructure(RDBMDistributedLayoutStore.java:
1639)
at
org.jasig.portal.layout.simple.RDBMUserLayoutStore.createLayout(RDBMUserLayoutStore.java:
484)
at
org.jasig.portal.layout.simple.RDBMUserLayoutStore.createLayout(RDBMUserLayoutStore.java:
493)
at
org.jasig.portal.layout.simple.RDBMUserLayoutStore.createLayout(RDBMUserLayoutStore.java:
493)
at
org.jasig.portal.layout.simple.RDBMUserLayoutStore.createLayout(RDBMUserLayoutStore.java:
493)
at
org.jasig.portal.layout.simple.RDBMUserLayoutStore.getUserLayout(RDBMUserLayoutStore.java:
1833)
at
org.jasig.portal.layout.dlm.RDBMDistributedLayoutStore._safeGetUserLayout(RDBMDistributedLayoutStore.java:
530)
at
org.jasig.portal.layout.dlm.RDBMDistributedLayoutStore.getFragmentLayout(RDBMDistributedLayoutStore.java:
608)
at
org.jasig.portal.layout.dlm.FragmentActivator.loadLayout(FragmentActivator.java:
314)
... 2 more
Roedel, Mark
Thinking through the installation process, I'm wondering if it's even
possible to do what I'm asking. The 'ant db' invokes dbloader to
completely replace the portal database, so in it's current state it's
missing the dlm layout owners and fragment data that are predefined in
the uPortal 2.6.0 release.
I wonder how hard it'd be to re-engineer the installation process so it
can be applied in a more piecemeal fashion -- leave the dbloader stuff
in place for those who want to do a wholesale replacement of their
existing portal database, but also provide an as-automated-as-possible
way of making just the db changes needed to run the calendar channel,
for example.
--
Mark Roedel
Senior Programmer / Analyst
LeTourneau University
Nick Bolton
One of our deployers has done this with some success. After doing the
ant db from toro-channels, you can re-init the db by running uPortal's
native ant db. This should initialize all the default layouts to use
dlm, but does remove any toro channels that have been published.
You'll have to re-publish any channels/portlets you're interested in
using. Basically, all the uPortal native tables are reset. Try that
and let us know how it turns out.
Going forward, we are in the process of reorganizing toro into
individual installable modules (see
http://www.ja-sig.org/issues/browse/TORO-6). This will include being
able to deploy any of the toro modules onto an already deployed
instance of uPortal.
Regards
Nick Bolton