Building WebSphere Portal 7 Cluster Environment with two horizontal portal nodes ( Installation and configuration of WP7, TDS v6.2, DB2 v9.7 , IBM HTTP Server v7)


Simply followed WP v7 Cluster guide (Link provided in references section) published by IBM L2 team, but there are few deviations/additions like below as per my requirements

  1. Portal DB transfer :: I have transferred all schemas to single database instance (Where as in IBM Cluster Guide,  explains transferring it to different database instances)
  2. DMGR profile creation :: As 64-bit operating systems doesn't support the profile management tool wizard , had to execute commands (Where as in IBM Cluster Guide, uses the wizard to create the DMGR profile)
  3. WAS ND installation for DMGR :: I have used the WAS ND deployed as part of the portal install (Where as in IBM Cluster Guide, remote installation of WAS ND is explained)
  4. Adding the Federated LDAP repositories :: Used WAS console to add the federated LDAP (Where as in IBM Cluster Guide, explains commands to create the repository)
  5. DB2 Installation and configuration for the websphere Portal 
  6. TDS installation and configuration for Websphere Portal

     Divided into multiple articles
  1. Websphere Portal Database Transfer (DB2)
  2. Clustering : Create DMGR Profile and Agument
  3. Clustering : Federate and cluster the primary node
  4. Configuring security : Configure the Portal Cluster with Federated LDAP Repositories
  5. Configuring security : Issues faced while configure Federated LDAP Repositories
  6. Adding horizontal portal node-part1: Install portal with binary only & Registering Profile Templates
  7. Adding horizontal portal node-part2: Create wp profile using pmt (profile management tool)
  8. Adding horizontal portal node-part3: Add node to DMGR and Update cluster members
  9.  
  10. DB2 v9.7 Installation
  11. DB2 v9.7 database creation
  12. DB2 v9.7 Augmenting/configuring for the WebSphere Portal
  13. DB2 v9.7 Applying Fixpack
  14. DB2 v9.7 Issues faced during db transfer
  15.  
  16. TDS v6.2 Installation
  17. TDS v6.2 Directory Server Instance Creation
  18. TDS v6.2 Configuring for the WebSphere Portal
  19. TDS v6.2 Installing IDSWebApp (web admin tool) on the Websphere
  20.  
  21. IHS v7 Installation
  22. IHS v7 Plugin generation for the WebSphere

Appendix
  1. Adding the Federated Repository from the WAS ISC Console
  2. Uninstalling WebSphere Portal 7

References


Posted by Siva R Vaka 0 comments
Labels: ,

Adding horizontal portal node-part2: Create wp profile using pmt (profile management tool)



1. On the WebSphere Portal additional node, launch the Profile Management Tool C:\IBM\WP7\AppServer\bin\ProfileManagement\pmt.bat

2. On the Welcome screen, click the 'Launch Profile Management Tool' button






 NOTE: Do NOT use the same node name as your primary node. You will be unable to add this node to the DMGR cell if the node names are identical.

3. IMPORTANT: Check the box for 'Federate this node later'. If you federate the node now, the Portal cluster member will be unusable

4. On the Security Certificate screen, choose the default one to create new certificates. Click Next


Accepted the default values

Review and create the profile



NOTE: A WebSphere_Portal server will NOT be created during the profile creation. The WebSphere_Portal server will be created after the node is added to the existing cluster
Posted by Siva R Vaka 0 comments
Labels: ,

Adding horizontal portal node-part1: Install portal with binary only & Registering Profile Templates


1. Install websphere portal using binary install option


./install.sh -W defaults.isBinaryInstall=true
Install.bat -W defaults.isBinaryInstall=true

NOTE: The flag defaults.isBinaryInstall=true tells the installer to not create a Portal profile. Instead, we will use the Profile Management Tool to create a Portal profile and federate it to the Deployment Manager later in this guide.






























2. As part of the above it doesn’t create any profile (wp_proflie directory ).


3. Create a directory called profileTemplates within the <PortalServer root> directory i.e. C:\IBM\WP7\PortalServer\profileTemplates


4. Copy <PortalServer root>/profileTemplates/profileTemplates.zip from the Primary Portal node to the newly created <PortalServer root>/profileTemplates directory on the additional node.


5. Unzip the profileTemplates.zip file into the <PortalServer root>/profileTemplates directory on the additional node.


6. From the <PortalServer root>/profileTemplates directory, execute the following command:


./installProfileTemplates.sh <AppServer root>
installPortalTemplates.bat C:\IBM\WP7\AppServer


C:\IBM\WP7\PortalServer\profileTemplates>installPortalTemplates.bat C:\IBM\WP7\AppServer
"checking availability of setupCmdLine.bat"
"registering the profileTemplates in C:\IBM\WP7\AppServer"
WSVR0615W: The user.install.root system property is not set. Some product classes might not be found.
Buildfile: installPortalTemplates.ant
unifyPaths:installPortalTemplates:
[echo] Using Portal home directory: C:\IBM\WP7\PortalServer
[echo] Using WAS home directory: C:\IBM\WP7\AppServer
[copy] Copying 2 files to C:\IBM\WP7\PortalServer\profileTemplates\default.portal
[copy] Copying 2 files to C:\IBM\WP7\PortalServer\profileTemplates\managed.portal
[copy] Copying 2 files to C:\IBM\WP7\AppServer\bin\ProfileManagement\plugins
[echo] fixing up file C:\IBM\WP7\PortalServer/profileTemplates/default.portal/templateMetadata.xml
[echo] fixing up file C:\IBM\WP7\PortalServer/profileTemplates/managed.portal/templateMetadata.xml
[echo] fixing up file C:\IBM\WP7\PortalServer/profileTemplates/managed.portal.augment/templateMetadata.xml

[echo] fixing up file C:\IBM\WP7\PortalServer/profileTemplates/management.portal.augment/templateMetadata.xml

BUILD SUCCESSFUL
Total time: 6 seconds

C:\IBM\WP7\PortalServer\profileTemplates>
Posted by Siva R Vaka 0 comments
Labels: ,

Adding horizontal portal node-part3: Add node to DMGR and Update cluster members


1. Make sure the Deployment Manager is started and the time on the Deployment Manager server and the time on the additional Portal node server are no more than 5 minutes apart. 

2. In the next step, we will be federating the profile to the DMGR cell. 

From the <wp_profile root>/bin directory, execute the following command:
./addNode.sh <dmgr_hostname> <dmgr soap port> -username <dmgr admin ID> -password <dmgr user password>

addNode.bat sivapc.sivavaka.com 8879 -username wpsadmin -password wpsadmin

C:\IBM\WP7\wp_profile\bin>addNode.bat sivapc.sivavaka.com 8879 -username wpsadmin -password wpsadmin

During this step
a. Adds the signer alias "CN=sivapc.sivavaka.com,ou=root" to local keystore "ClientDefaultTrustStore"
b. Adds the signer alias "default" to local keystore "ClientDefaultTrustStore"
c. Adds the signer alias "datapower" to local keystore "ClientDefaultTrustStore"
d. Federate Node "svakaNode01" with DMGR at sivapc.sivavaka.com:8879
e. Create node agent configuration for node svakaNode1
f. Adds node svakaNode01 to cell
g. sync between node and cell
h config and initialize the node agent

ADMU0300I: The node svakaNode01 was successfully added to the SivaPCCell01

3 Edit the wkplc.properties file in the <wp_profile root>/ConfigEngine/properties directory and ensure all of the following properties are set:

WasUserId=<DMGR admin user ID>
WasPassword=<DMGR admin password>
PortalAdminPwd=<password>
WasRemoteHostName=<fully qualified hostname of DMGR>
WasSoapPort=<soap port for DMGR; default is 8879>
ServerName=WebSphere_Portal_2
PrimaryNode=false
ClusterName=PortalCluster

Following are the values set
WasUserid=uid=wpsadmin,cn=users,dc=sivavaka,dc=com
WasPassword=wpsadmin   
PortalAdminPwd=wpsadmin
WasRemoteHostName=svaka.sivavaka.com
WasSoapPort=8879
ServerName=WebSphere_Portal_2
PrimaryNode=false
ClusterName=PortalCluster

NOTE: For additional nodes, ServerName can be any value you want. This server will be created by the cluster-setup script.
NOTE: Ensure ClusterName matches the value of the existing cluster.


4. Edit the wkplc_dbdomain.properties file in the <wp_profile root>/ConfigEngine/properties directory and ensure that the database password values are all set correctly.


NOTE: These file should be pre-populated with your database information from running the 'enable-profiles' script on the primary node earlier.

5. Edit the wkplc_dbtype.properties file in the <wp_profile root>/ConfigEngine/properties directory and ensure that the <dbType>.DbLibrary value is valid for this system.

db2.DbLibrary=C:/IBM/WP7/AppServer/db2drivers/db2jcc4.jar;C:/IBM/WP7/AppServer/db2drivers/db2jcc_license_cu.jar

NOTE: These file should be pre-populated with your database information from running the 'enable-profiles' script on the primary node earlier.


6. Ensure the NodeAgent is started on this node by running the following command from the <wp_profile>/bin directory:


./startNode.sh


7. Executing the following ConfigEngine script to create a second WebSphere_Portal cluster member:

./ConfigEngine.sh cluster-node-config-cluster-setup-additional -DWasPassword=password

NOTE: This will automatically create a secondary cluster member to your existing cluster based on whatever value you set for ServerName.

During this step

  1. Creates the database variables by domain, creates jdbc providers for db domains
  2. Adds the csuster member (This step will take time to expand all ear files on new node i.e. svakaNode01)
  3. Update the dynacache instances
  4. Update or creates the JVM custom properties for the new node
  5. Update ports
  6. Removes the original server i.e. WebSphere_Portal from second node
  7. Sync with primary node
  8. Dumps all properties for this node (just to make sure all are valid).

8. Execute the following ConfigEngine script to update the Portal Administrative user for the new cluster member with the LDAP administrative user:

./ConfigEngine.sh wp-change-portal-admin-user -DWasPassword=<password> -DnewAdminId=<full distinguished name from ldap> -DnewAdminPw=<ldap ID password> -DnewAdminGroupId=<full distinguished name from ldap>

ConfigEngine.bat wp-change-portal-admin-user -DWasPassword=wpsadmin -DnewAdminId=uid=wpsadmin,cn=users,dc=sivavaka,dc=com -DnewAdminPw=wpsadmin -DnewAdminGroupId=cn=wpsadmins,cn=groups,dc=sivavaka,dc=com


9. To verify that the cluster member was created successfully, log in to the DMGR Administrative Console and browse to:

Servers -> Clusters -> WebSphere Application Server Clusters -> ClusterName -> Cluster Members



10. You can check and validate the ports from ISC console.
11. Restart DMGR, NodeAgent and portal servers
Posted by Siva R Vaka 0 comments
Labels: ,

Websphere Portal Database Transfer to DB2 v9.7


NOTE: Following article gives detail on how to transfer all schemas to single database instance (most of the times each schema is created under different database instance, but as this is not intended for heavy use , just used single db instance for all schemas. It is also simple to create different schemas under different db instance by just giving proper db names for each schema in datasources section below. WP Cluster guide also details on how to create schemas on separate databases using command line approach )

WebSphere portal database transfer can be done either using the Portal Configuration Wizard or using configengine tasks.

Database Transfer using portal config wizard

Open the portal config wizard from C:\IBM\WebSphere\wp_profile\PortalServer\wizard\configwizard.bat, this wizard will walk you through all required configuration to transfer the db (most of the screens are self-explanatory). 


Optionally you can update the following files to pre-populate information by config wizard.

1. Edit the wkplc_dbtype.properties file and make the following changes:

db2.DbLibrary=C:/IBM/DB2/java/db2jcc4.jar;C:/IBM/DB2/java/db2jcc_license_cu.jar
db2.JdbcProviderName=wpdbJDBC_db2


2. Edit the wkplc_dbdomain.properties file and make the following changes:

feedback.DbType=db2
feedback.DbName=wps7db
feedback.DbSchema=FEEDBACK
feedback.DataSourceName=wpdbDS_db2
feedback.DbUrl=jdbc:db2://mydbserver.ibm.com:50000/wps7db:returnAlias=0;
feedback.DbUser=db2admin
feedback.DbPassword=Passw0rd
feedback.DbRuntimeUser=db2admin
feedback.DbRuntimePassword=Passw0rd

likeminds.DbType=db2
likeminds.DbName=wps7db
likeminds.DbSchema=likeminds
likeminds.DataSourceName=wpdbDS_db2
likeminds.DbUrl=jdbc:db2://mydbserver.ibm.com:50000/wps7db:returnAlias=0;
likeminds.DbUser=db2admin
likeminds.DbPassword=Passw0rd
likeminds.DbRuntimeUser=db2admin
likeminds.DbRuntimePassword=Passw0rd

release.DbType=db2
release.DbName=wps7db
release.DbSchema=release
release.DataSourceName=wpdbDS_db2
release.DbUrl=jdbc:db2://mydbserver.ibm.com:50000/wps7db:returnAlias=0;
release.DbUser=db2admin
release.DbPassword=Passw0rd
release.DbRuntimeUser=db2admin
release.DbRuntimePassword=Passw0rd

community.DbType=db2
community.DbName=wps7db
community.DbSchema=community
community.DataSourceName=wpdbDS_db2
community.DbUrl=jdbc:db2://mydbserver.ibm.com:50000/wps7db:returnAlias=0;
community.DbUser=db2admin
community.DbPassword=Passw0rd
community.DbRuntimeUser=db2admin
community.DbRuntimePassword=Passw0rd

customization.DbType=db2
customization.DbName=wps7db
customization.DbSchema=customization
customization.DataSourceName=wpdbDS_db2
customization.DbUrl=jdbc:db2://mydbserver.ibm.com:50000/wps7db:returnAlias=0;
customization.DbUser=db2admin
customization.DbPassword=Passw0rd
customization.DbRuntimeUser=db2admin
customization.DbRuntimePassword=Passw0rd

jcr.DbType=db2
jcr.DbName=wps7db
jcr.DbSchema=jcr
jcr.DataSourceName=wpdbDS_db2
jcr.DbUrl=jdbc:db2://mydbserver.ibm.com:50000/wps7db:returnAlias=0;
jcr.DbUser=db2admin
jcr.DbPassword=Passw0rd
jcr.DbRuntimeUser=db2admin
jcr.DbRuntimePassword=Passw0rd


 Choose the task that you want to perform i.e. " Transfer data to other database"

Provide the WAS admin ID and password

Select the source db (dy default portal uses derby database)
Choose the target database i.e. db2 in my case

Entered the DB version (remaining details are populated from the properties file that entered already)

Provide JDBC provider info for the release database domain if it is not already mentioned in the above properties 


Make sure all properties for the customization database are proper below


Make sure all properties for the community database are proper
Make sure all properties for the JCR database are proper 

Make sure all properties for the Feedback database are proper 
Make sure all properties for the likeminds database are proper 


Following is the consolidate screen for all schemas , validate the details before go further

Click next to start the db transfer.



References
Posted by Siva R Vaka 0 comments
Labels: ,

IBM WebSphere Portal 7 Clustering : Federate and cluster the primary node

Federate and cluster the primary node

  1. Federate Node (add Node)
    1. Make sure Deploymnet Mgr is started and Websphere Portal and server1 are stopped

  1. Execute the following command to add node to DMGR

addNode.bat sivapc.sivavaka.com 8879 -username wasadmin -password wasadmin -includeapps -includebuses

./addNode.sh <dmgr_hostname> <dmgr soap port> -username <dmgr admin ID> -password <dmgr user password> -includeapps -includebuses

NOTE: If the WAS administrator user ID and password for the local node are different than the Deployment Manager administrator user ID and password, add the following parameters to the addNode task:  -localusername local_was_admin_user -localpassword local_was_admin_password

  1. Restart the deployment manager

  1. Create cluster
    1. On the primary node, edit the <wp_profile>/ConfigEngine/properties/wkplc.properties file and ensure all of the following properties are set appropriately for your enviornment

WasUserId=<DMGR admin user ID>
WasPassword=<DMGR admin password>
PortalAdminPwd=<password>
WasRemoteHostName=<fully qualified hostname of DMGR>
WasSoapPort=<soap port for DMGR; default is 8879>
ServerName=WebSphere_Portal
PrimaryNode=true
ClusterName=PortalCluster

  1. Make sure DB userid/passwords are valid in the <wp_profile>/ConfigEngine/properties/wkplc_dbdomain.properties file

  1. Update the deployment manager configuration for the new WebSphere Portal server by executing the following ConfigEngine script:
ConfigEngine.bat cluster-node-config-post-federation -DWasPassword=wasadmin

  1. Create the cluster definition and add the WebSphere_Portal server as a cluster member by executing the following ConfigEngine script:
ConfigEngine.bat cluster-node-config-cluster-setup -DWasPassword=wasadmin

Following tasks get executed during the above task
  1. Created the cluster "PortalCluster"
  2. Hostnames are modified accordingly (Cell, node and port mappings)
  3. WCM caches are adjusted to cluster
  4. Data Replication domain has created
  5. Server dyna cache details are modified (global cache)
  6. Custom JVM properties are added ( like cacheconfig related)
  7. Updated WCM variables (like WCM_HOST , WCM_PORT , WCM_ILWWCM_HOME (to C:/IBM/WP72/WebSphere/PortalServer/wcm/prereq.wcm/wcm))
  8. Created icm property value on cluster
    1. Created documentURI="cells/SivaPCCell01/wp_properties/PortalCluster.icm.properties" (deleted file= "C:/IBM/WebSphere/wp_profile/PortalServer/jcr/lib/com/ibm/icm/PortalCluster.icm.properties")
  9. Enabled app security on cluster
  10. Sync nodes (nodeagent (NODE_AGENT), app servers (websphere_portal, server1), deployment manager (dmgr)).
  11. Started websphere_portal and set the managed node =true

  1. Login to DMGR console and validate the cluster is created properly and websphere_portal is added as member.

  1. Updating JCRSeedBus members
    1. Need to fix the JCRSeedBus because earlier it was pointing to node .



  1. Add new bus member
  1. Select "High availability" in next screen and click next
  2. Select "Data Store" radio button and click next
  3. Click on the JCRSeedBus and configure the db details
  1. Add following details
Datasource :: jdbc/<existing JCR datasource>
Schema :: JCR schema name ( can  get it from wkplc_dbdomain.properties)
Authentication alias : JCR authentication
  1. Click next and no changes to heap sizes and click "finish"
  2. You can remove the old bus member
  1. Restart all (DMGR, Nodeagent, Portal)


References




Posted by Siva R Vaka 0 comments
Labels: ,

IBM WebSphere Portal : Issues faced while configure Federated LDAP Repositories (non-SSL)


Issues faced while configuring the federated repository

  1. Have executed "was-change-admin" without creating the portal user in the LDAP, caused build failure
  2. If you are creating user using some UI (like softerra) and when you select the template , make sure to select the "Internet Organizational Person" (this template has the "uid" as relative distinguished name (RDN) instead of "cn") and for creating the select "group of uniquenames" as template
  3.  Failed while running Configuration Engine task 'wp-change-portal-admin-user'

com.ibm.websphere.management.exception.ConfigServiceException: javax.management.JMRuntimeException: ADMN0022E: Access is denied for the resolve operation on Con
figService MBean because of insufficient or empty credentials.
        at com.ibm.websphere.management.configservice.ConfigServiceProxy.resolve(ConfigServiceProxy.java:477)
        at com.ibm.wkplc.was.registry.AdminConfigRegistry.getExistingRegistry(AdminConfigRegistry.java:104)
        at com.ibm.wkplc.models.compregistry.ResourceWidget.loadRegistryFromWAS(ResourceWidget.java:200)
        at com.ibm.wkplc.models.compregistry.GenerateNodeRegistryXML.cacheWASRegistry(GenerateNodeRegistryXML.java:243)
        at com.ibm.wkplc.models.compregistry.RegistryHelper.getWasRegistry(RegistryHelper.java:132)
        at com.ibm.wps.config.ConfigEngine.loadRegistry(ConfigEngine.java:1250)
        at com.ibm.wps.config.ConfigEngine.process(ConfigEngine.java:707)
        at com.ibm.wps.config.ConfigEngine.main(ConfigEngine.java:247)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
        at java.lang.reflect.Method.invoke(Method.java:600)
        at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:260)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
        at java.lang.reflect.Method.invoke(Method.java:600)
        at com.ibm.wps.config.launch.ConfigEngineLauncher.process(ConfigEngineLauncher.java:269)
        at com.ibm.wps.config.launch.ConfigEngineLauncher.main(ConfigEngineLauncher.java:311)
Caused by: javax.management.JMRuntimeException: ADMN0022E: Access is denied for the resolve operation on ConfigService MBean because of insufficient or empty cr
edentials.
        at com.ibm.ws.management.connector.soap.SOAPConnectorClient.handleAdminFault(SOAPConnectorClient.java:933)
        at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplateOnce(SOAPConnectorClient.java:901)
        at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplate(SOAPConnectorClient.java:667)
        at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplate(SOAPConnectorClient.java:657)
        at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:643)
        at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:465)
        at $Proxy0.invoke(Unknown Source)
        at com.ibm.ws.management.AdminClientImpl.invoke(AdminClientImpl.java:224)
        at com.ibm.websphere.management.configservice.ConfigServiceProxy.resolve(ConfigServiceProxy.java:452)
        ... 18 more
com.ibm.websphere.management.exception.ConfigServiceException: javax.management.JMRuntimeException: ADMN0022E: Access is denied for the resolve operation on Con
figService MBean because of insufficient or empty credentials.
        at com.ibm.websphere.management.configservice.ConfigServiceProxy.resolve(ConfigServiceProxy.java:477)
        at com.ibm.wkplc.was.registry.AdminConfigRegistry.getExistingRegistry(AdminConfigRegistry.java:104)
        at com.ibm.wkplc.models.compregistry.ResourceWidget.loadRegistryFromWAS(ResourceWidget.java:200)
        at com.ibm.wkplc.models.compregistry.GenerateNodeRegistryXML.cacheWASRegistry(GenerateNodeRegistryXML.java:243)
        at com.ibm.wkplc.models.compregistry.RegistryHelper.getWasRegistry(RegistryHelper.java:132)
        at com.ibm.wps.config.ConfigEngine.loadRegistry(ConfigEngine.java:1250)
        at com.ibm.wps.config.ConfigEngine.process(ConfigEngine.java:707)
        at com.ibm.wps.config.ConfigEngine.main(ConfigEngine.java:247)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
        at java.lang.reflect.Method.invoke(Method.java:600)
        at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:260)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
        at java.lang.reflect.Method.invoke(Method.java:600)
        at com.ibm.wps.config.launch.ConfigEngineLauncher.process(ConfigEngineLauncher.java:269)
        at com.ibm.wps.config.launch.ConfigEngineLauncher.main(ConfigEngineLauncher.java:311)
Caused by: javax.management.JMRuntimeException: ADMN0022E: Access is denied for the resolve operation on ConfigService MBean because of insufficient or empty cr
edentials.
        at com.ibm.ws.management.connector.soap.SOAPConnectorClient.handleAdminFault(SOAPConnectorClient.java:933)
        at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplateOnce(SOAPConnectorClient.java:901)
        at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplate(SOAPConnectorClient.java:667)
        at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplate(SOAPConnectorClient.java:657)
        at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:643)
        at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:465)
        at $Proxy0.invoke(Unknown Source)
        at com.ibm.ws.management.AdminClientImpl.invoke(AdminClientImpl.java:224)
        at com.ibm.websphere.management.configservice.ConfigServiceProxy.resolve(ConfigServiceProxy.java:452)
        ... 18 more
Registry could not be loaded from WAS using current connection information.
Please verify your WAS connection properties and retry the operation.  Current input:
WasUserId: uid=wasadmin,cn=users,dc=sivavaka,dc=com
WasPassword: PASSWORD_REMOVED
WasRemoteHostName: sivapc.sivavaka.com
WasSoapPort: 8879
CellName: SivaPCCell01
NodeName: SivaPC
Return Value: -1

From Reference

Scenario #5
Conditions:

    WebSphere Application Server administrative user fails to log into the ISC when using the login attribute.
    WebSphere Application Server administrative user fails to log into the ISC when using the full DN (uid=wasadmin,o=ibm).
    WebSphere Portal administrative user login to WebSphere Portal can fail or succeed in this scenario.
    You are not able to choose different LDAP users for your administrative users that are unique across all of the repositories. You want to use the LDAP username(s) that are in conflict with the file registry user.
Resolution:
NOTE: The following resolution will remove the file registry from the federated repository so that there are no longer duplicate entries found for the user(s). If you setting up a non-production environment and want to keep the file registry, the alternative to the following steps would be to rename the user in the file registry so that the login attribute is unique


  1. When I tried to create a user within the portal I have the following errors

EJPSG0015E: Data Backend Problem com.ibm.websphere.wim.exception.WIMApplicationException: CWWIM4508E Virtual member manager failed to write to the 'C:IBMWP72WebSpherewp_profileconfigcellsSivaPCCell01 ileRegistry.xml' file: 'CWWIM6009E All updates must be performed at the deployment manager and not at a managed node.'.
com.ibm.wps.util.DataBackendException: EJPSG0015E: Data Backend Problem com.ibm.websphere.wim.exception.WIMApplicationException: CWWIM4508E Virtual member manager failed to write to the 'C:IBMWP72WebSpherewp_profileconfigcellsSivaPCCell01 ileRegistry.xml' file: 'CWWIM6009E All updates must be performed at the deployment manager and not at a managed node.'.
EJPSG0015E: Data Backend Problem com.ibm.websphere.wim.exception.WIMApplicationException: CWWIM4508E Virtual member manager failed to write to the 'C:IBMWP72WebSpherewp_profileconfigcellsSivaPCCell01 ileRegistry.xml' file: 'CWWIM6009E All updates must be performed at the deployment manager and not at a managed node.'.
CWWIM4508E Virtual member manager failed to write to the 'C:IBMWP72WebSpherewp_profileconfigcellsSivaPCCell01 ileRegistry.xml' file: 'CWWIM6009E All updates must be performed at the deployment manager and not at a managed node.'.
CWWIM6009E All updates must be performed at the deployment manager and not at a managed node.



To ensure that new users and groups are created in your LDAP. Edit the wkplc.properites file in <wp_profile root>/ConfigEngine/properties and set the
following values (these examples are from my own environment. Ensure you use values that match your LDAP environment):

personAccountParent=cn=users,dc=ibm,dc=com
groupParent=cn=groups,dc=ibm,dc=com
personAccountRdnProperties=uid
groupRdnProperties=cn

Execute the following ConfigEngine script to ensure that new users and groups are created in your LDAP:

./ConfigEngine.sh wp-set-entitytypes -DWasPassword=<password>

ConfigEngine.bat wp-set-entitytypes -DWasPassword=wpsadmin

  1. I have changed the realm name from ISC console to "sivatdsldap" instead "defaultWIMFileBasedRealm"

EJPSG0015E: Data Backend Problem com.ibm.websphere.wim.exception.DefaultParentNotFoundException: CWWIM0516E The default parent for 'PersonAccount' entity type cannot be determined. Verify that the configuration for the 'sivatdsrealm' realm is correct.
com.ibm.wps.util.DataBackendException: EJPSG0015E: Data Backend Problem com.ibm.websphere.wim.exception.DefaultParentNotFoundException: CWWIM0516E The default parent for 'PersonAccount' entity type cannot be determined. Verify that the configuration for the 'sivatdsrealm' realm is correct.
EJPSG0015E: Data Backend Problem com.ibm.websphere.wim.exception.DefaultParentNotFoundException: CWWIM0516E The default parent for 'PersonAccount' entity type cannot be determined. Verify that the configuration for the 'sivatdsrealm' realm is correct.
CWWIM0516E The default parent for 'PersonAccount' entity type cannot be determined. Verify that the configuration for the 'sivatdsrealm' realm is correct.


Posted by Siva R Vaka 0 comments
Labels: ,
Subscribe to: Posts (Atom)