unfortunately, we just purchased ON so i can't say that i have tinkered with it much,
but these are the things i can identify as having the most value for our organization:
1) it would be nice to be able to centralize administration of user portlets rights,
etc... directly from ON, as opposed to having administrators log into each portal
"instance"
2) CMS control - it would be cool if you could deploy a single (or clustered) CMS
"server" and deploy content links as required to all instances of portal via ON.
this might be a bit bloated, not sure of implications and whether portal could fully
handle it.
3) directly edit / deploy all critical XML's from ON
4) to further extend on Roy's point... if i understood him correctly... it would be
absolutely bitchin if porlet instances or CMS content could be archived remotely and
restored from ON.
5) this has nothing to do with portal directly... but when doing major portlet / portal
code changes, the database purge / data directory remove / rebuild can be a real hassle...
especially in heavy prototype / production enviornments. would it be possible to utilize
ON to at the minimum "reinsert" users and roles upon redeployment... or at the
click of a button in the console ? obviously, permission associations to portlets
can't be restored, as portlets / portal deployment may change, but the ability to
resync users and roles would be a big help. it sure beats having to create sql scripts
manually to reinsert.
these are the things i can think of offhand. maybe some of these things are already
possible. I will throw more things at you once i get ON installed and running... or at
the minimum after i go to the roadshow tomorrow. i would guess we will do our own
install late this week / early next week for our test servers.
thanks
JW
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972400#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...