ADMN0034E: SocketTimeoutException -- Solution

Rapid Deploy deployments timing out when deploying large web apps, with the following error:

Caused by:ADMN0034E: The service is unable to obtain a valid administrative client to connect process "nodeagent" from process "dmgr", because of exception:ConnectorException: java.net.SocketTimeoutException: Async

Solution:

Perform the following steps to prepare the WebSphere Application Server Deployment Manager:

1. Use the following URL to launch the network deployment administrative console:http://dmgr_hostname:9060/ibm/console, where dmgr_hostname is the fully qualified host name for the WebSphere Application Server Network Deployment.
2. Log into the deployment manager administrative console.
3. Increase the HTTP connection timeouts for the deployment manager.
   Note: See HTTP transport channel custom properties for additional information.
   1. Click System Administration > Deployment Manager > Web container transport chains.
   2. Increase the timeout values. For the WCInboundAdmin and WCInboundAdminSecureentries listed in the web container transport chains section, complete the following steps to increase the timeout values:
      1. Click HTTP Inbound Channel.
      2. Change the Read timeout value to 0.
      3. Change the Write timeout value to 0.
      4. Save the configuration changes.
4. Change the timeout request period for the Java Management Extensions (JMX) connector.
   1. Click System administration > Deployment Manager > Administration Services > JMX connectors > SOAPConnector > Custom Properties.
   2. Select the requestTimeout property, and increase the value from 600 to 6000.
   3. Save the configuration changes.
5. Update the maximum Java heap size used by the deployment manager:
   1. Update the heap size in the following two locations:
      • Click System administration > Deployment manager > Java and Process Management > Process Definition > Control > Java Virtual Machine.
      • Click System administration > Deployment manager > Java and Process Management > Process Definition > Servant > Java Virtual Machine.
   2. Set the jvm max size to 1024
   3. Click OK and then save your changes.
6. Change the timeout request period for the Simple Object Access Protocol (SOAP) client. Open a UNIX System Services (USS) command prompt. Edit the soap.client.props file, located in theDmgr_profile/properties directory:
   Change the line to: com.ibm.SOAP.requestTimeout=0.
   Note: If you are instructed to open a properties file, please note that the files are ascii files and should be open using the appropriate tool.
7. Stop and restart the deployment manager:

Just spent the morning trying to find .nifregistry after a failed WAS 8 deployment..

Important Note to self: Starting Websphere Application Server 8 nifregistry is no more available. Instead one can use .was.installlocations.registry file located at the same location of .nifregistry as mentioned in the above table.

Setting up RSA keys for Putty to Local Machine

From Server home directory create a directory .shh/environment

chmod -R 700 .ssh 

Run: ssh-keygen -t rsa

When asked enter a name and leave passpharse empty

cp public key authorized_keys (if it doesn't already exist, if it does cat and append it >> )

Copy the private key back to your desktop.

Open Keygen and select Conversions/import Key , and save private key

Open Putty and load your session, select SSH - Auth and browse to your new private key location my.ppk 

Under connections select data and enter the user name for the server and then save the session.

Now when you login in it will automatically connect for you ....

Error: Main WebSphere Portal fixup task failed' during install

While scripting a Portal 6.1.5 to run on an existing WAS 7 Application server I came accross this error.

Problem

IBM® WebSphere® Portal v6 install fails with "Error: Main WebSphere Portal fixup task failed." The complete error is shown below.

Cause

Output of wpsinstalllog.txt:

MultiPlatform.install, com.ibm.wps.install.ExecutePortalArchiveInstaller$ArchiveLocalizerUpdate$PortalLocalizerProgressListener, msg2, Progress = aborted: Error: Main WebSphere Portal fixup task failed

When attempting to install WebSphere Portal 6.1.0.1 into an existing WebSphere Application Server (WAS) 7.0, the Portal installer gets about 5 minutes into the install and fails with WASX7017E and "CWPMC0006E: IPC_CONNECTOR_ADDRESS not found" errors.

Symptom

Installation fails.

LocalizeTraceArchive5.txt contains the following error message:

[wsadmin] WASX7017E: Exception received while running file ".../wp_profile/ConfigEngine/config/work/was/modifyPortsWithFile.jacl"; exception information: com.ibm.websphere.management.cmdframework.CommandException: CWPMC0006E: The endpoint with name 'IPC_CONNECTOR_ADDRESS' is not found.

Cause

This error happens when the Portal installer tries to use the wrong CD or part.

During installation, a default backup WAS profile configured for Portal 6.1.0.1 is copied from the CDs or install directories. CD 5 contains a WAS 6.1 profile, while CD 5-A contains a WAS 7.0 profile. WAS 7.0 profiles have a new port that does not exist in WAS 6.1 profiles: the IPC_CONNECTOR_ADDRESS port.

The CWPMC0006E error message means that the installation is failing because it is looking for a WAS 7.0 port that does not exist in a WAS 6.1 profile; that is, it is looking for the files found in CD 5-A but getting the files found in CD 5.

Resolving the problem

If you are installing Portal with the default WAS 6.1, or installing to an existing WAS 6.1, the installer will require CD 5 (C1U32ML), which contains a profile for installations to WAS 6.1. If you are installing to an existing WAS 7.0, the installer will need to use CD 5-A (C1U36ML), which contains a WAS 7.0 profile.

Reference

Portal Security Error

Had an issue this morning re-enabling security on Portal where Portal appears to start successfully but when you try and access WebSphere Portal via the browser, you receive a "404 Error Initialization of one or more services failed" error.

The SystemOut.log showed the following errors:

Caused by: com.ibm.wps.um.exceptions.impl.PumaSystemExceptionImpl: com.ibm.wps.util.DataBackendException: EJPSG0015E: Data Backend Problem com.ibm.websphere.wim.security.authz.AccessException: CWWIM2008E The principal 'AnonymousUser' is not authorized to perform the operation

'GET PersonAccount' on 'uid=wpsadmin,o=defaultWIMFileBasedRealm'

[datetime] 00000015 PortalCollect E com.ibm.hrl.portlets.WsPse.PortalCollectionsService PortalCollectionsService EJPJO0119E: Failed to initialize portal collections services. java.lang.NoClassDefFoundError: com.ibm.wps.ac.impl.AccessControlDataManagement (initialization failure)

...............

Cause

Administrative security is disabled, but I had just enabled security on the Deployment Manager and used it to login via the admin console, with a little more digging around I noticed that in this particular scenario, the deployment manager did not sync with the node correctly and therefore didn't update the sercirty.xml file at cell level.

Resolving the problem

Enabled security in the security.xml and doubled checked the dmgr security.xml and restarted everything, and all worked and I was now able to login to Portal again as normal.

Has WCM been Installed??

Portal comes in many different version, so it important to check that you are installing the correct version: Express, Base, Enable and Extend . Some of them include WCM and some of them not, as a friend of mine found out the hard way, after spending some time getting his install working on AIX he couldn't find any of the WCM components.

There is two ways to check that Portal was install correctly with WCM installed.

1- Use the command:

$WPS_HOME/bin/WPVersionInfo.sh and check the Portal version and the installed capabilities, including WCM.

http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1/topic/com.ibm.wp.exp.doc_v6101/reference/wp_history.html

2- Open the file $WPS_HOME/wps.properties, if your Portal installation has WCM you will have a line like this one:

WPFamilyName=content

If you Portal installation doesn’t have WCM you will find a line like this:

WPFamilyName=server

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

Cloning an IBM WebSphere Portal V7 installation

Useful when automating WebSphere Portal 7 installations.

Summary: Learn how to clone an installation of IBM WebSphere Portal version 7.0 that has been configured for specific deployment needs. This white paper is intended for portal administrators who want to build a standardized installation of WebSphere Portal within their organization and use it as a template from which to mass-produce additional pre-installed and pre-configured portals.

Link - Developer works