WebSphere Portal 7. Export url mappings with XMLAccess

If you have to move url mappings between your prod and test WebSphere Portal environments, then you can do it like the following. If you have virtual portal then export you url mapping:

<request build="wp7002_132_01" type="export" version="7.0.0.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PortalConfig_7.0.0_2.xsd">
<portal action="locate">

<url-mapping-context action="locate" label="virtual_portal_name">
<url-mapping-context action="export" label="mapping1" />
</url-mapping-context>
</portal>
</request>





Command for export:
xmlaccess -in exportscript.xml -user wpsadmin -password wpsadmin -url http://localhost:10039/wps/config/virtual_portal_name -out script_out.xml




Use the same command for importing that file or use portal admin console to import the xml file.

WebSphere Portal 7. Remote portlet update through Xmlaccess.

In the previous post we setup the xmlaccess for running on Windows.
Now I'll show how to update the existing portlet through the xmlaccess on the remote host.

WebSphere Portal. Run XmlAccess on remote hosts.

If you want to automate the configuration and deployment task on WebSphere Portal, eventually, you will use XmlAccess.

IBM provides ant task called XmlAccess. My goal is to achieve the invokation of configuration tasks on remote machine from my machine. I use Windows 7 and ant 1.8.4 . Remote installations of WebSphere Portal use Linux.