Portal Deployments and Version Control
We have developers at different locations who are going to be collaborating on a demo deployment of Sun Portal Server 7 update 1. We would appreciate any recommendations from the community for sharing and versioning (subversion) the demo Portal configuration that we are working on (display profiles, desktops, containers, users, etc.)? In other words, which folders and files need to be shared in order to reproduce a Portal deployment on a clean install?
We are all Sun Portal newbies and in the process of reading the docs. After a quick glance it appears like this isn't a topic that's covered in the docs; my apologies if is it.
[648 byte] By [
lewen7er9a] at [2007-11-27 11:00:11]
# 1
My colleague has come up with the following list:
"Based on what I've read and files I see changing as I make modifications to the samples, only ...
* PortalServer-DataDir/portals/portal-ID/desktop
* PortalServer-DataDir/portals/portal-ID/war
* PortalServer-DataDir/portals/portal-ID/config
* PortalServer-DataDir/portals/portal-ID/web-src
... should be put in source control. Of course the war directory is portlet war files. Guess we need source control for each portlet."
Can this be confirmed by those with more experience? Or are people simply scripting the configuration and managing the script under source control?
# 2
Versioning:
From our portal deployment, instead of messing with the data itself, we created scripts that actually provisioned the portal server, and then versioned those scripts. This not only allowed a quick, reproducible enviroment, but also gave us the option to rebuild machines quickly.
I would also be aware that just dumping files into various portal directories may not correctly update all the appropriate locations (display profile, user store, etc).
Our script follows this process:
1) Moves static files around (index.html to docroot, static images to docroot, etc).
2) Set jdbc connections using asadmin create-connection-pool, etc.
3) Provisions access manager using xml files and amconfig -s XMLFILE. This builds the necessary orgs, groups, roles, base users, etc.
4) Configures the roles and orgs within portal. using psadmin set-attribute this script sets the desktopType, default channel, Priority, and the display profile xml.
5) Finally, I deploy the portlets into the proper org (we actually use global) by running psadmin deploy-portlet.
Easier said then done, but this will get portal up and running correctly and is easily reproducible.
I would love to see what some of the portal experts at sun have to say about such methods (or are they just building portals from scratch in a one-off format).
Just
