Here you will find description of the elements which can be managed via xmlaccess. "http://publib.boulder.ibm.com/infocenter/wpdoc/v6r0/topic/com.ibm.wp.ent.doc/wps/adxmlabt.html" After a few days working with jboss portal i still missing xsd or dtd for confgiuration files. What the exported configuration going to look like - do we really want to export many different configuration files (object.xml, instances.xml, jboss-portlet.xml and so on)? I like "all-in-one-file" solution for export/import. When portlet is deployed, it can be still configured with multiple files. Admins also need some way to trace import/export failures or warnings. Separate responce file (can be configured with jboss app server logging) (might be olso one responce file per import/export activity) can be used to achieve this - i am not happy with the current console logging. It would be cool to perform import/export via the admin portlet. Each content node can get an "export" button that exports configuration of the selected portal node, child objects (pages, windows) and objects the node depends on (portlet instances, layout). As portal role-based administration evolves, kind of configuration changes log is required - we need to know "who-what-when" changes portal configuration. p.s.: lets define some sticky name for xml import interface. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973473#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...