WebSphere Issues

24/08/2011

Migrating from WPv6.1.5 to WPv7

Filed under: WebSphere Portal — Ishtiaque @ 1:32 pm

1. manageprofiles -create -defaultPorts -enableAdminSecurity false -profileName wp_profile7 -profilePath C:/IBM/WebSphere7/wp_profile7 -templatePath C:/IBM/WebSphere7/AppServer/profileTemplates/default -nodeName DefaultNode -cellName DefaultNode -hostName host -isDefault -omitAction samplesInstallAndConfig defaultAppDeployAndConfig

2. WASPreUpgrade C:/IBM/WebSphere7/waspreupgradebk C:/IBM/WebSphere/AppServer -oldProfile wp_profile

3. WASPostUpgrade C:/IBM/WebSphere7/waspreupgradebk -profileName wp_profile7 -oldProfile wp_profile -username wpsadmin  -password wpsadmin -includeApps true -backupConfig false

4. In admin guide it’s suggested to change WPv7 ports after the upgradeConfigEnigne task but as both portal servers are listening on same ports so it may update WPv6.1 configenigne tool. That’s why it’s suggested to do either remote migration or change the ports before running the upgradeConfigEngine task.

In my environment I guess it updated the WPv6.1 configenigne tool because it was not able to run successfully and it was pointing to WPv7 installation location during run time.
5. upgradeConfigEngine wp_profile7 -conntype SOAP -hostname host -port 16040 -user wpsadmin -password wpsadmin

References:

https://www-304.ibm.com/support/docview.wss?uid=swg27021370&aid=1

23/08/2011

Change WebSphere Portal ports

Filed under: WAS, WebSphere Portal — Ishtiaque @ 1:10 pm

Run the following commands:

1. ConfigEngine.bat list-server-ports -DWasPassword=password OR

ConfigEngine.bat list-server-ports-by-name -DServerName=server1 -DwasPassword=password

2. ConfigEngine.bat modify-ports-by-startport -DModifyPortsServer=servername -DStartPort=starting port number OR

ConfigEngine.bat modify-ports-by-portsfile -DModifyPortsServer=servername -DPortsFile=full path to ports file

Here are the contents of sample ports file:

BOOTSTRAP_ADDRESS=10031
SOAP_CONNECTOR_ADDRESS=10033
SAS_SSL_SERVERAUTH_LISTENER_ADDRESS=10032
CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS=10025
CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS=10036
WC_adminhost=10027
WC_defaulthost=33344
DCS_UNICAST_ADDRESS=10029
WC_adminhost_secure=10039
WC_defaulthost_secure=10035
SIB_ENDPOINT_ADDRESS=10026
SIB_ENDPOINT_SECURE_ADDRESS=10037
SIB_MQ_ENDPOINT_ADDRESS=10030
SIB_MQ_ENDPOINT_SECURE_ADDRESS=10028
ORB_LISTENER_ADDRESS=10034

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

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

11/08/2011

Verify your WebSphere portal installation contains WCM

Filed under: WCM, WebSphere Portal — Ishtiaque @ 12:58 pm

There are 2 versions of Portal. One is Content and the other is Server. The “Server” version does not contain WCM.

You can check in your C:IBMWebSpherewp_profilePortalServerwps.properties, whether you have installed the server version which does not contain WCM.

Following is Server installation which does not contains WCM:
WPFamilyName=server
WPInstallType=full

Following is Content installation which does contain WCM:

WPFamilyName=content
WPInstallType=full

References:

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

02/08/2011

Configure WebSphere Portal with Active Directory over SSL as Federated Repository

Filed under: Active Directory, WebSphere Portal — Ishtiaque @ 12:46 pm

1. Update the following parameteres in the template file wp_profile_root/ConfigEngine/config/helpers/wp_security_federated.properties
federated.ldap.id=fedAD1
federated.ldap.host=ad.ibm.com
federated.ldap.port=636
federated.ldap.bindDN=cn=wpsadmin,cn=users,dc=ibm,dc=com
federated.ldap.bindPassword=wpsadmin
federated.ldap.ldapServerType=AD2003
federated.ldap.baseDN=dc=ibm,dc=com
federated.ldap.sslEnabled=true
federated.ldap.sslConfiguration=NodeDefaultSSLSettings

Run the following command to update parent property file wkplc.properties and validate the connection to LDAP:
-> ConfigEngine validate-federated-ldap -DparentProperties=C:IBMWebSpherewp_profileConfigEngineconfighelperswp_add_federated_ad.properties -DSaveParentProperties=true -DWasPassword=wpsadmin -DPortalAdminPwd=wpsadmin

2. Run the following command to add a federated ldap and then restart WebSphere_Portal server:
-> ConfigEngine.bat wp-create-ldap -DWasPassword=wpsadmin

3. Check that all defined attributes are available in the configured LDAP user registry.Run the following task :
NOTE: After running the following task, check the ConfigEngine/log/ConfigTrace.log file for missing attributes in portal. Then proceed to the following steps.
-> ConfigEngine wp-validate-federated-ldap-attribute-config -DWasPassword=password

4. Run the following task : The task will create “availableAttributes.html” file in wp_profile_root/ConfigEngine/log dir.
-> ConfigEngine.bat wp-query-attribute-config -DWasPassword=password

5. Enter a value for one of the following sets of parameters in the wkplc.properties file found under the VMM Federated repository properties heading to correct any issues found in the config trace file:
federated.ldap.attributes.nonSupported
federated.ldap.attributes.nonSupported.delete
federated.ldap.attributes.mapping.ldapName
federated.ldap.attributes.mapping.portalName
federated.ldap.attributes.mapping.entityTypes

Run the following task to update the LDAP user registry configuration and then restart WebSphere_Portal:
-> ConfigEngine.bat wp-update-federated-ldap-attribute-config -DWasPassword=wpsadmin

6. 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

Run the following command to update Group and PersonAccount entity types and then restart WebSphere_Portal:
-> ConfigEngine wp-update-entitytypes -DWasPassword=wpsadmin

7. Update the following parameters in the property file wkplc.properties:
newAdminId=
newAdminPw=
newAdminGroupId=

Change WAS admin Id by running the command and then restart WebSphere_Portal:
-> ConfigEngine.bat wp-change-was-admin-user -DWasPassword=wpsadmin -Dskip.ldap.validation=true

Change Portal admin Id by running the command and then restart WebSphere_Portal:
-> configEngine.bat wp-change-portal-admin-user -DWasPassword=wpsadmin -Dskip.ldap.validation=true

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

Run the following command to create realm:
-> ConfigEngine.bat wp-create-realm -DWasPassword=password

9. To update the default parents per entity type and realm
realmName=IDSRealm1
realm.personAccountParent=cn=users,dc=us,dc=ibm,dc=com
realm.groupParent=cn=groups,cn=groups,dc=us,dc=ibm,dc=com
realm.orgContainerParent=dc=us,dc=ibm,dc=com

To update the default parents per entity type and realm.Run the following task and then restart WebSphere_Portal
-> ConfigEngine.bat wp-modify-realm-defaultparents -DWasPassword=password

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

http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1/topic/com.ibm.wp.ent.doc_v615/install/win_add_ldap_ureg_ssl.html

Change from Standalone to Federated repository

Filed under: Active Directory, TDS, WebSphere Portal — Ishtiaque @ 12:10 pm

1. Update the following properties in the file  wp_profile_root/ConfigEngine/properties/wkplc.properties under the heading VMM Federated LDAP Properties:

federated.ldap.id=fedAD1
federated.ldap.host=ad.mycompany.com
federated.ldap.port=636
federated.ldap.bindDN=cn=wpsadmin,cn=users,dc=mycompany,dc=com
federated.ldap.bindPassword=wpsadmin
federated.ldap.ldapServerType=AD2003
federated.ldap.baseDN=dc=mycompany,dc=com
federated.ldap.sslEnabled=true
federated.ldap.sslConfiguration=NodeDefaultSSLSettings

2. Update the following required parameters in the wkplc.properties file under VMM Federated repository properties:

federated.primaryAdminId=cn=wpsadmin,cn=users,dc=mycompany,dc=com
federated.realm=realm1
federated.serverId=cn=wpsadmin,cn=users,dc=mycompany,dc=com
federated.serverPassword=wpsadmin

3. Run the following command and then restart WebSphere_Portal server.

ConfigEngine wp-modify-federated-security -DWasPassword=wpsadmin -Dskip.ldap.validation=true

References:

-> http://publib.boulder.ibm.com/infocenter/wpexpdoc/v6r1/index.jsp?topic=/com.ibm.wp.exp.doc_v615/security/win_mod_fed_sec.html
-> http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Changing_from_a_standalone_repository_to_a_federated_repository_on_Windows_wp7

Create a free website or blog at WordPress.com.