Troubleshoot VMM

Verify adapter library deployment

cd wp_profile/ConfigEngine 
ConfigEngine.sh verify-SNPortletsVMM-setup \
                -DWasPassword=mypassword \
                -DPortalAdminPwd=mypassword \
                -DWasUserid=wasadmin \
                -DPortalUserid=wpsadmin

If the libs are deployed successfully, stdout shows:

[wsadmin] AdapterClassVerification --> Success - Adapter Class Found.

If VMM libs are not deployed successfully, stdout shows:

[wsadmin] AdapterClassVerification --> Failed - Adapter class could not be found. Verify VMM Adapter jars are added at correct path.
[wsadmin] AdapterClassVerification --> Failed - ClassNotFoundException - Verify the path for com.ibm.ws.wim.adapter.connections.jar is correct.

If the VMM adapter configuration is successful, stdout shows:

[wsadmin] AdapterClassVerification --> Success - Adapter Class Found.
[wsadmin] PortalLoginVerification --> Success - Correct credentials found for DSX Admin and login done in Portal.
[wsadmin] HTTPSAuthCallVerification --> Success - HTTPS Call using DSX Admin credentials returned 200 status code.
[wsadmin] SonataCallVerification --> Success - DSX API HTTPS Call using DSX Admin credentials returned 200 status code.

If there is a configuration failure, stdout shows:

[wsadmin] AdapterClassVerification --> Failed - Adapter class could not be found. Verify VMM Adapter jars are added at correct path.
[wsadmin] AdapterClassVerification --> Failed - ClassNotFoundException - Verify the path for com.ibm.ws.wim.adapter.connections.jar is correct.
[wsadmin] PortalLoginVerification --> Failed - Verify the DSX Admin credentials in Security and J2CAlias REP.
[wsadmin] PortalLoginVerification --> Failed - Unable to find J2CAuthAlias REP property. Make sure it is defined.
[wsadmin] PortalLoginVerification --> Failed - Could not initialize WSMappingCallbackHandlerFactory. This is usually because of a problem with the node agent process.
[wsadmin] HTTPSAuthCallVerification --> Failed - 403 exception encountered while making Authenticated call. Verify that correct DSX Admin is defined.
[wsadmin] HTTPSAuthCallVerification --> Failed - 401 exception encountered while making Authenticated call. Verify that DSX Admin is defined.
[wsadmin] HTTPSAuthCallVerification --> Failed - SSL HANDSHAKE FAILURE : Please import Connection Server SSL certificate in Portal's local trust store - NodeDefaultSSLSettings.
[wsadmin] HTTPSAuthCallVerification --> Failed - Error : Error occurred while executing the Get request to Connections Server.
[wsadmin] HTTPSAuthCallVerification --> Failed - Error : Error occurred while reading document.
[wsadmin] SonataCallVerification --> Success - DSX API HTTPS Call using DSX Admin credentials returned 200 status code.
[wsadmin] SonataCallVerification --> Failed - Exception encountered while making Sonata call. Verify same user is used as DSX Admin on Connections as on Portal and the SSL certificate of Portal is installed on Connections Server.
[wsadmin] SonataCallVerification --> Failed - 401 exception encountered while making Sonata call due to empty or invalid credentials.
[wsadmin] SonataCallVerification --> Failed - 403 exception encountered while making Sonata call. Verify that correct DSX Admin is defined.
[wsadmin] SonataCallVerification --> Failed - Cannot read service document. Attempting retry.

Checkpoints

If, for example, community groups are not displaying on the Portal server, check the timeout settings on the Portal and Connections servers to verify they are compatible.

1. From the WAS console, go to...
   Security | Global Security | Authentication | LTPA

   ...and record the value of the timeout setting.

2. On the Portal server edit either...
   DMGR_PROFILE/config/cells/cell/sonata.services.xml (Clustered)
   WP_PROFILE/config/cells/cell/sonata.services.xml (Stand-alone)

   ...and set...

   <attribute key="CookieTimeout" value="60" />

   ...to a value that is 80 - 90% of the value set for the LTPA timeout setting.

3. On the Connections server edit either...
   PROFILE_HOME/config/cells/cell/LotusConnections-config/LotusConnections-config.xml (stand-alone)
   DMGR_PROFILE/config/cells/cell/LotusConnections-config/LotusConnections-config.xml (clustered)

   ...and set...

   <customAuthenticator name="DefaultAuthenticator"> 
       <attribute key="CookieTimeout" value="24" /> 
   </customAuthenticator>

   Set CookieTimeout to the same value set in sonata.services.xml on the Portal service.

4. Restart the Connections and Portal servers.

5. Verify the Connections server can resolve the Portal server's host name using either...
   • DNS setting
   • Adding entry in /etc/hosts file on the Connections server. Windows location is C:\Windows\System32\drivers

6. Delete the Portal SSL certificate imported on the Connections server earlier, and import a new one.

Parent topic:
Configure the Connections repository for VMM