|
Home > Archive > WebSphere Portal Server > October 2005 > Does ReleaseBuilder (wpsV5.1) work for wps config management? Is anyone using it?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Does ReleaseBuilder (wpsV5.1) work for wps config management? Is anyone using it?
|
|
|
| I am looking for a way to promote changes to portal structure. I am on Windows 2003 using wps5.1. I know you can use XmlAccess to capture structure. However, ReleaseBuilder (wps\bin\ReleaseBuilder.bat) offers to compare two XmlAccess files and yield xml o
f just the differences. I tried it on a simple portal change and it was fine. But when I run it against a bigger portal I get Exception in thread "main" java.lang.IllegalStateException: Exporting unresolved page at com.ibm.wps.command.xml.factory.Composit
ionItemFactory$1.getReferencedIDs(CompositionItemFactory.java:74) at com.ibm.wps.command.xml.ItemFactory.sortByReference(ItemFactory.java :149) .....
The source xml files look fine and came from two healthy but differently structured portals.
I have enabled tracing, but that just points to a problem when iterating over content-nodes - trace is not fine enough to say which node.
Basically, I just need to know whether to persist with ReleaseBuilder. Is anyone using it?
| |
| George Daswani 2005-10-24, 6:13 pm |
| If you haven't done so, you might want to upgrade to 5.1.0.1 - it has a
couple of release builder fixes..
We've been playing around with release builder (5.1.0.1) and we ran into a
bug, one of the diffs it created did not want to apply, xmlaccess threw
errors (DB INSERT errors and etc), your mileage might vary. We've submitted
a PMR - still haven't received a fix from IBM.
I'm hoping IBM is working on improving release builder, as it makes portal
deployment alot easier (compared to the manual export Admin Pages, Content
Topology, Portlets and etc method).
G
<chris.smyth@defence.gov.au> wrote in message
news:1667470879.1129266172557.JavaMail.wassrvr@ltsgwas007.sby.ibm.com...
>I am looking for a way to promote changes to portal structure. I am on
>Windows 2003 using wps5.1. I know you can use XmlAccess to capture
>structure. However, ReleaseBuilder (wps\bin\ReleaseBuilder.bat) offers to
>compare two XmlAccess files and yield xml of just the differences. I tried
>it on a simple portal change and it was fine. But when I run it against a
>bigger portal I get Exception in thread "main"
>java.lang.IllegalStateException: Exporting unresolved page at
>com.ibm.wps.command.xml.factory.CompositionItemFactory$1.getReferencedIDs(CompositionItemFactory.java:74)
>at com.ibm.wps.command.xml.ItemFactory.sortByReference(ItemFactory.java
>:149) .....
>
> The source xml files look fine and came from two healthy but differently
> structured portals.
>
> I have enabled tracing, but that just points to a problem when iterating
> over content-nodes - trace is not fine enough to say which node.
> Basically, I just need to know whether to persist with ReleaseBuilder. Is
> anyone using it?
| |
|
| Thanks George. I'll look at upgrading. I was pretty disappointed at the poor diagnosic from ReleaseBuilder. When I decompiled the offending class, it looked like a UID could have been placed in the Exception text, which would have narrowed down the hunt f
or the offending content-node.
I have the xmlAccess file 'chunks' (skins, themes, web-apps, content-nodes) method to fall back on. But I agree ReleaseBuilder looks to be a very useful utility if it works reliably.
Chris
> If you haven't done so, you might want to upgrade to
> 5.1.0.1 - it has a
> couple of release builder fixes..
>
> We've been playing around with release builder
> (5.1.0.1) and we ran into a
> bug, one of the diffs it created did not want to
> apply, xmlaccess threw
> errors (DB INSERT errors and etc), your mileage might
> vary. We've submitted
> a PMR - still haven't received a fix from IBM.
>
> I'm hoping IBM is working on improving release
> builder, as it makes portal
> deployment alot easier (compared to the manual export
> Admin Pages, Content
> Topology, Portlets and etc method).
>
> G
>
> <chris.smyth@defence.gov.au> wrote in message
> news:1667470879.1129266172557.JavaMail.wassrvr@ltsgwas
> 007.sby.ibm.com...
> structure. I am on
> XmlAccess to capture
> (wps\bin\ReleaseBuilder.bat) offers to
> the differences. I tried
> when I run it against a
> unresolved page at
> y$1.getReferencedIDs(CompositionItemFactory.java:74)
> com.ibm.wps.command.xml.ItemFactory.sortByReference(It
> emFactory.java
> healthy but differently
> problem when iterating
> say which node.
> with ReleaseBuilder. Is
>
>
| |
| George Daswani 2005-10-24, 6:13 pm |
| Chris,
How do you manage your user's customizations on your production server
when exporting via file chunks? (pre release builder).
G
<chris.smyth@defence.gov.au> wrote in message
news:683758990.1129268772957.JavaMail.wassrvr@ltsgwas007.sby.ibm.com...
> Thanks George. I'll look at upgrading. I was pretty disappointed at the
> poor diagnosic from ReleaseBuilder. When I decompiled the offending class,
> it looked like a UID could have been placed in the Exception text, which
> would have narrowed down the hunt for the offending content-node.
>
> I have the xmlAccess file 'chunks' (skins, themes, web-apps,
> content-nodes) method to fall back on. But I agree ReleaseBuilder looks to
> be a very useful utility if it works reliably.
>
> Chris
>
>
>
| |
|
| George
We haven't really got that far yet - our portal is only at concept demonstration stage. I am trying to set up our configuration management procedures (scripted in Maven/Ant) before we go to Production. I guess I expected that user customisation would be e
nvironment-specific, and as long as UIDs were preserved, the customisation would be unaffected by xmlAccess imports.
Chris
| |
| George Daswani 2005-10-24, 6:13 pm |
| Hello Chris,
How are you exporting pages, one at a time? or the content topology
"wps.My Portal" w/ export-descendants=true during every release?
The problem I see with export descendants = true is that it exports user
page customizations (if the config is coming from staging -> production)..
It's going to clobber production user customization.
Doing it one page at a time without descendant export is quite tedious,
complex, and error prone IMHO - this is why I wish Release Builder is
working properly 
G
<chris.smyth@defence.gov.au> wrote in message
news:1563809336.1129271098122.JavaMail.wassrvr@ltsgwas007.sby.ibm.com...
> George
>
> We haven't really got that far yet - our portal is only at concept
> demonstration stage. I am trying to set up our configuration management
> procedures (scripted in Maven/Ant) before we go to Production. I guess I
> expected that user customisation would be environment-specific, and as
> long as UIDs were preserved, the customisation would be unaffected by
> xmlAccess imports.
>
> Chris
| |
|
| For ReleaseBuilder approach I am using ExportRelease.xml which has attribure export-release="true" and so does not include any private resources.
For 'chunks' approach, I use Export.xml, but then edit down the XML.
I need to do some page customisation and look at the effects on the exported xml before I can say anything more useful on customisation, I'm afraid.
I need to
> Hello Chris,
>
> How are you exporting pages, one at a time? or
> ? or the content topology
> "wps.My Portal" w/ export-descendants=true during
> every release?
>
> The problem I see with export descendants = true is
> that it exports user
> page customizations (if the config is coming from
> staging -> production)..
> It's going to clobber production user customization.
>
> Doing it one page at a time without descendant export
> is quite tedious,
> complex, and error prone IMHO - this is why I wish
> Release Builder is
> working properly
>
> G
>
>
> <chris.smyth@defence.gov.au> wrote in message
> news:1563809336.1129271098122.JavaMail.wassrvr@ltsgwas
> 007.sby.ibm.com...
> only at concept
> configuration management
> Production. I guess I
> environment-specific, and as
> would be unaffected by
>
>
| |
| George Daswani 2005-10-24, 6:14 pm |
| Chris,
We've found a reproducable way to trigger a bug in ReleaseBuilder.
Basically here's what we did
1) uninstall/unregister the portlet (should remove itself from all pages
automatically)
2) Re-install the portlet, then re-add it to the same pages it was
automatically removed from
3) Export new config
4) Create diff between old config, and new config
5) Run diff on other server
When the diff is ran via xmlaccess - xmlaccess fails to update the page that
used to contain the removed / then re-added portlet..
<status element="[portletinstance _5_0846KJRD9D0UH5CC_CH]"
result="failed">
<message
id="EJPXA0043E">com.ibm.wps.command.xml.XmlCommandException: EJPXA0043E: An
error occurred while creating or updating the resource. [portletinstance
_5_0846KJRD9D0UH5CC_CH]</message>
<message id="EJPDB0001E">com.ibm.wps.util.DataBackendException:
EJPDB0001E: Error occurred during database access. Last SQL statement is
[INSERT INTO PORT_INST (OID, CREATED, MODIFIED, PORT_DESC_OID, SCOPE_OID,
WSC_INST_HANDLE, WSP_IS_PROVIDED, WSP_PROD_OFF_INST, TYPE) VALUES (?, ?, ?,
?, ?, ?, ?, ?, ?)].</message>
<message>SQL Exception: INSERT on table 'PORT_INST' caused a
violation of foreign key constraint 'FK300A' for key (301). The statement
has been rolled back.</message>
</status>
We are re-opening our PMR, hopefully you'll have better luck than us.. For
such a simple operation (which should be well tested), releasebuilder is
quite buggy.
George
<chris.smyth@defence.gov.au> wrote in message
news:2030949815.1129274903042.JavaMail.wassrvr@ltsgwas007.sby.ibm.com...
> For ReleaseBuilder approach I am using ExportRelease.xml which has
> attribure export-release="true" and so does not include any private
> resources.
>
> For 'chunks' approach, I use Export.xml, but then edit down the XML.
>
> I need to do some page customisation and look at the effects on the
> exported xml before I can say anything more useful on customisation, I'm
> afraid.
>
> I need to
>
>
>
| |
| George Daswani 2005-10-24, 6:14 pm |
| We've figured this out, it had to do with the ordering of web-app deletes
release builder outputs.
The delete command has both the old OBJECT ID, and the unique id ; then
unique id is used as the reference instead of the object id..
So if removed uninstalled portlet A, installed a portlet with the same uid,
then added it to the same previous page, then the xmlaccess release builder
generates errors out..
eq.
<web-app action="update" objectid="SOMENEWOBJECTID"
uid="portlet.someportlet.webmod">
..
</web-app>
<web-app action="delete" objectid="OLDOBJECTID"
uid="portlet.someportlet.webmod"/>
The second one deletes the first one you've just added (even though it has a
different objectid), it's preferring to delete based on uid if both
attributes are listed.
Release builder should have made the "delete" command only reference the
objectid (no uid).
eq.
<web-app action="delete" objectid="oldobjectid"/>
or
reordered the xmlaccess output so that the deletes are before the adds.
G
|
|
|
|
|