WebSphere Issues

26/05/2011

CWWIM4538E occurs on login after configuring for federated repository

Filed under: TDS, WAS, WebSphere Portal — Ishtiaque @ 9:24 pm

This issue is usually arrive when duplicate user names were found between default file based repository and newly configured federated repository such as wpsadmin.

In SystemOut logs following exception is shown while logging to either WAS or WP console:

[5/26/11 12:51:51:171 CDT] 0000002f exception     E com.ibm.ws.wim.ProfileManager loginImpl CWWIM4538E Multiple principals were found for the ‘wpsadmin’ principal name.
[5/26/11 12:51:51:171 CDT] 0000002f exception     E com.ibm.ws.wim.ProfileManager loginImpl
com.ibm.websphere.wim.exception.DuplicateLogonIdException: CWWIM4538E Multiple principals were found for the ‘wpsadmin’ principal name.

 

Follow Scenario-5 in the following technot to resolve the issue:

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

Configure WebSphere Portal 6.x with Tivoli Directory Server 6.x as Federated Repository

Filed under: TDS, WAS, WCM, WebSphere Portal — Ishtiaque @ 9:10 pm

1. Update C:IBMWebSpherewp_profileConfigEngineconfighelperswp_add_federated_ids.properties with following values:
federated.ldap.id=fed1
federated.ldap.host=tdshost.ibm.com
federated.ldap.port=390
federated.ldap.bindDN=cn=root
federated.ldap.bindPassword=password
federated.ldap.ldapServerType=IDS6
federated.ldap.baseDN=dc=ibm,dc=com

2. Run the following command to update parent property file and validate the connection to LDAP:

ConfigEngine validate-federated-ldap -DparentProperties=C:IBMWebSpherewp_profileConfigEngineconfighelperswp_add_federated_ad.properties -DSaveParentProperties=true -DWasPassword=wpsadmin -DPortalAdminPwd=wpsadmin

3. Run the following task to add a federated ldap:
ConfigEngine.bat wp-create-ldap -DWasPassword=wpsadmin

4. Restart WebSphere_Portal

5. Update the values for the following required parameters in the wkplc.properties file
under the VMM supported entity types configuration heading:
personAccountParent=cn=users,dc=ibm,dc=com
groupParent=cn=groups,dc=ibm,dc=com
personAccountRdnProperties=uid
groupRdnProperties=cn

6.  Run the following command to update Group and PersonAccount entity types:
ConfigEngine wp-update-entitytypes -DWasPassword=wpsadmin

7. Restart WebSphere_Portal

8. Change WAS admin Id by running the command:
ConfigEngine.bat wp-change-was-admin-user -DWasPassword=wpsadmin -DnewAdminId=uid=wpsadmin,cn=users,dc=training,dc=ibm,dc=com -DnewAdminPw=wpsadmin -Dskip.ldap.validation=true

9. Restart WebSphere_Portal

10. Update WP admin Id by running the command:

ConfigEngine.bat wp-change-portal-admin-user -DnewAdminId=uid=wpsadmin,cn=users,dc=training,dc=ibm,dc=com -DnewAdminPw=wpsadmin -DnewAdminGroupId=cn=wpsadmins,cn=groups,dc=training,dc=ibm,dc=com -Dskip.ldap.validation=true

11. Restart WebSphere_Portal

12. Enter a value for the following required parameters in the wkplc.properties file under the VMM realm configuration section:
realmName=IDSRealm1
addBaseEntry=dc=us,dc=ibm,dc=com
securityUse=active
delimiter=/

References:

http://www-10.lotus.com/ldd/portalwiki.nsf/dx/MultipleRealms.pdf/$file/MultipleRealms.pdf

http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1/index.jsp?topic=/com.ibm.wp.ent.doc_v615/install/win_add_ldap_ureg.html

25/05/2011

Export and Import theme policies for WP6.x

Filed under: WebSphere Portal — Ishtiaque @ 11:40 am

1. Create an xml file exportThemePolicy.xml and paste either of the following contents in it:

The file specified is the location to where the exported information is written. The following example exports all theme policies.

<?xml version=”1.0″ encoding=”UTF-8″?>
<request xsi:noNamespaceSchemaLocation=”PortalConfig_1.4.xsd”  create-oids=”true” type=”export”  xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”&gt;
<portal action=”locate”>
<policy-node action=”export” label=”WebPage” type=”theme” path=””>
<url>file:///C:/exportedThemePolicies.xml</url>
</policy-node>
</portal>
</request>

The following example exports only the TestThemePolicy theme policy:

<?xml version=”1.0″ encoding=”UTF-8″?>
<request xsi:noNamespaceSchemaLocation=”PortalConfig_1.4.xsd”  create-oids=”true” type=”export”  xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”&gt;
<portal action=”locate”>
<policy-node action=”export” label=”WebPage” type=”theme” path=”TestThemePolicy”>
<url>file:///C:/exportedTestThemePolicy.xml</url>
</policy-node>
</portal>
</request>

2. Run the following command to export the theme policy:

<portal_install_root>binxmlaccess  -url http://localhost:10040/wps/config -user wpsadmin -password wpsadmin -in C:exportThemePolicy.xml –out C:exportThemePolicyOut.xml

3. Create a xml file such as importTestThemePolicy.xml and paste following contents in it to import the exported theme policy:

<?xml version=”1.0″ encoding=”UTF-8″?>
<request xsi:noNamespaceSchemaLocation=”PortalConfig_1.4.xsd” create-oids=”true” type=”update” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”&gt;
<portal action=”locate”>
<policy-node action=”update” label=”WebPage” type=”” path=””>
<url>file:///C:/exportedTestThemePolicy.xml</url>
</policy-node>
</portal>
</request>

4. Run the following command to import the theme policy on target server:

<portal_install_root>binxmlaccess -url http://localhost:10040/wps/config -user wpsadmin -password wpsadmin -in C:importTestThemePolicy.xml –out C:exportThemePolicyResult.xml

References:

http://sivavaka.blogspot.com/2011/02/exporting-theme-policies-in-wp7.html

http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1/index.jsp?topic=/com.ibm.wp.ent.doc_v615/dev/dgn_thempolicy.html

Move a Virtual Portal from staging to production using XMLAccess

Filed under: WebSphere Portal — Ishtiaque @ 11:15 am

1. Create an empty virtual portal by running ConfigEngine task:

http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1/index.jsp?topic=/com.ibm.wp.ent.doc_v615/admin/advpref.html

2. Export the virutal portal config by running the following XMLAccess command:

<portal_install_root>binXmlAccess -user wpsadmin -password wpsadmin -url http://localhost:10040/wps/config/vp -in <portal_install_root>docxml-samplesExport.xml  -out C:ExportOut.xml

3. Perform the following steps before running import task:

3.1 Copy the custom portlet war files inside <portal_install_root>installableApps directory.

3.2 Deploy themes, skins and theme policies on target

3.3 If the source and target repositories are different and are using different ldap suffixes, then review the ACLs in xml file and replace the source users with appropriate users on target in xml file.

3.4 Export/import any personalization rules from source to target if exists

3.5 XML file will automatically create pages, portlet clones & config, ACLs on pages & portlets, credential vaults, portlet wires.

4. Import virtual portal config by running following XMLAccess command:

<portal_install_root>binXmlAccess -user wpsadmin -password wpsadmin -url http://localhost:10040/wps/config/vp -in <portal_install_root>docxml-samplesExport.xml  -out C:ExportOut.xml

References:

http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1/index.jsp?topic=/com.ibm.wp.ent.doc_v615/admin/advpref.html

http://www.ibm.com/developerworks/websphere/library/techarticles/0712_kubik/0712_kubik.html

18/05/2011

Running member fixer task

Filed under: WCM, WebSphere Portal — Ishtiaque @ 3:02 pm

1. Run the following command to create a report of user ids which need to be fixed:

ConfigEngine.bat run-wcm-admin-task-member-fixer -DPortalAdminId=wpsadmin -DPortalAdminPwd=wpsadmin -Dlibrary=myLib -Drealm=myRealm -DnoRealmDn=true

2. Update the property file using sample provided in the file

C:IBMWebSpherewp_profilePortalServerwcmsharedappconfigwcmservicesMemberFixerModule.properties

3. Run the following command to upadate the references:

ConfigEngine.bat run-wcm-admin-task-member-fixer -DPortalAdminId=wpsadmin -DPortalAdminPwd=wpsadmin -Dlibrary=myLib -Drealm=myRealm -DnoRealmDn=true -Dfix=true -DaltDn=update -DmismatchedId=update

11/05/2011

Change WAS/WP admin user ids

Filed under: WAS, WebSphere Portal — Ishtiaque @ 3:40 pm

Plz run the following to change WAS admin user id:

1. ConfigEngine.bat wp-change-was-admin-user -DWasPassword=password -DnewAdminId=uid=wpsadmin,dc=example,dc=com -DnewAdminPw=password -Dskip.ldap.validation=true

2. Restart both server1 and WebSphere_Portal.

3. ConfigEngine.bat wp-change-portal-admin-user -DWasPassword=password -DnewAdminId=uid=wpsadmin,dc=example,dc=com -DnewAdminPw=password -DnewAdminGroupId=cn=wpsadmins,dc=exampels,dc=com -Dskip.ldap.validation=true

4. Restart again both server1 and WebSphere_Portal

10/05/2011

Database transfer fails with ‘duplicate key row’ error

Filed under: WebSphere Portal — Ishtiaque @ 3:56 pm

Plz verify is “SQL_Latin1_General_CP1_CS_AS” is selected for jcrdb and other portal databases. For details plz refer following IBM technotes:

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

Configure WebSphere Portal 6.1.x with SQLServer 2005

Filed under: WebSphere Portal — Ishtiaque @ 3:50 pm

Plz follow the link: http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Steps_to_configure_Portal_v6.1.x_with_SQLServer_2005

05/05/2011

Install Oracle 11g, Error file not found /oracle/product/11.2.0/dbhome_1/oc4j/j2ee/oc4j_applications/applications/em.ear

Filed under: Oracle — Ishtiaque @ 11:30 am

You need to extract both  downloaded zipped files (For windows they are win32_11gR2_database_1of2.zip & win32_11gR2_database_2of2.zip) into the same directory such as C:oracle or /opt/oracle.

For rest of the procedure to install the oracle please follow the link: http://st-curriculum.oracle.com/obe/db/11g/r2/2day_dba/install/install.htm

References:

1. http://forums.oracle.com/forums/thread.jspa?threadID=956641&tstart=0

2. http://st-curriculum.oracle.com/obe/db/11g/r2/2day_dba/install/install.htm

Create a free website or blog at WordPress.com.