WebSphere Issues

06/01/2012

Export URL Mappings in WebSphere Portal using xmlaccess

Filed under: Scripts, WebSphere Portal — Ishtiaque @ 7:15 am

1. Following samples shows to export url mapping inside base portal:

script1.xml:

<?xml version=”1.0″ encoding=”UTF-8″?>
<request type=”export” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance&#8221; xsi:noNamespaceSchemaLocation=”PortalConfig_1.4.xsd”>
<portal action=”locate”>
<url-mapping-context action=”export” objectid=”*” />
</portal>
</request>

Script2.xml

Following script will export page2 which is nested inside page1 urlmpping:

<?xml version=”1.0″ encoding=”UTF-8″?>
<request type=”export” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance&#8221; build=”wp6014_010_01″ version=”6.0.1.4″ xsi:noNamespaceSchemaLocation=”PortalConfig_6.0.1_2.xsd”>
<portal action=”locate”>
<url-mapping-context action=”locate” label=”page1urlmappingcontext”>
<url-mapping-context action=”export” label=”page2urlmappingcontext” />
</url-mapping-context>
</portal>
</request>

xmlaccess -in exporturlmapping.xml -user wpsadmin -password wpsadmin -url http://localhost:10038/wps/config -out script1_out.xml

2. Following scripts shows to export urlmapping inside a virtual portal:

Script3.xml

<?xml version=”1.0″ encoding=”UTF-8″?>
<request type=”export xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance&#8221; build=”wp6014_010_01″ version=”6.0.1.4″ xsi:noNamespaceSchemaLocation=”PortalConfig_6.0.1_2.xsd”>
<portal action=”locate”>
<url-mapping-context action=”export” label=”vp1″ />
</portal>
</request>

Script4.xml

Following script will export page2 which is nested inside page1 urlmpping under a virtual poratl:

<?xml version=”1.0″ encoding=”UTF-8″?>
<request type=”export xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance&#8221; build=”wp6014_010_01″ version=”6.0.1.4″ xsi:noNamespaceSchemaLocation=”PortalConfig_6.0.1_2.xsd”>
<portal action=”locate”>

<url-mapping-context action=”locate” label=”vp1″>
<url-mapping-context action=”locate” label=”page1urlmappingcontext”>
<url-mapping-context action=”export” label=”page2urlmappingcontext” />
</url-mapping-context>
</portal>
</request>

xmlaccess -in exportscript3.xml -user wpsadmin -password wpsadmin -url http://localhost:10038/wps/config/vp1 -out script3_out.xml

Note: By default all the child urlmapping contexts if exist would be exported along with parent.

Rerferences:

https://www-304.ibm.com/support/docview.wss?uid=swg21267262

04/01/2012

cluster-setup taks failed with error code EJPCA3004E: ERROR: /CacheInstance:strategy/ not there in WebSphere Portal V6.0

Filed under: WAS, WCM, WebSphere Portal — Ishtiaque @ 2:09 am

If Dmgr and nodes are running on version 6.0.2.17 or higher, then adding new member into cluster will fail during the WPSconfig cluster-setup task due to WAS version 6.0.2.17 introduced changes to the scoping behavior of the application server. Portal scripts previously looked at the server scope for certain resources. This results in failures during WPSconfig cluster-setup for both the primary and the secondary node.

This issue was resolved by following steps:

1. Downgrading WAS version onto Dmgr and all nodes by uninstall WAS fixpack which was installed after fresh installation.

2. Install the portal fix PK38907 and PK68347 onto the new member.

3. Run WPSconfig cluster-setup task.

References:

http://www-01.ibm.com/support/docview.wss?uid=swg24015073

https://www-304.ibm.com/support/docview.wss?uid=swg1PK68347

http://groups.google.com/group/ibm.software.websphere.portal-server/browse_thread/thread/56c61658a417ddf3

Blog at WordPress.com.