Solutions to easily avoidable errors deploying Websphere Portal 6.1 on z/OS

WSDN1A1

[wplc-create-ear-impl] appname

---

  wimwmm

[wplc-create-ear-impl] node.name

---

  WSDN1

[wplc-create-ear-impl] systemApp

---

  true

[wplc-create-ear-impl] cell.name

---

  WSD

[wplc-create-ear-impl] *_*_*_*_*_*_*_*_*_*_*_*_*_*_*_

[wplc-create-ear-impl] [05/17/10 11:04:43.113 EDT] WKSP0500

[wplc-create-ear-impl]ADMA6008IAppNotification:task=InstallApplication, taskStatus=InProgress,subtask=, subtaskStatus=, properties={appname=wimwmm}, message=ADMA5016I: Installation of wimwmm started.

[wplc-create-ear-impl] ADMA6008IAppNotification:task=InstallApplication, taskStatus=InProgress, subtask=SystemAppsConfigureTask, subtaskStatus=Failed, properties={appname=wimwmm}, message=ADMA5006E: An error occurred configuring wimwmm in WebSphere Application Server repository: com.ibm.websphere.management.exception.AdminException: ADMA5026E: No valid target is specified in ObjectName WebSphere:cell=WSD,node=WSDN1,server=WSDN1A1 for module

WebSphere:cell=WSD,node=WSDN1,server=WSDN1A1.

[wplc-create-ear-impl]com.ibm.websphere.management.exception.AdminException: ADMA5026E: No valid target is specified in ObjectName

  WebSphere:cell=WSD,node=WSDN1,server=WSDN1A1 for module WebSphere:cell=WSD,node=WSDN1,server=WSDN1A1.

[wplc-create-ear-impl]

ADMA6008IAppNotification:task=InstallApplication, taskStatus=InProgress, subtask=Cleanup, subtaskStatus=Completed, properties={appname=wimwmm}, message=ADMA5011I: The cleanup of the temp directory for application wimwmm is complete.

[wplc-create-ear-impl] ADMA6008IAppNotification:task=InstallApplication, taskStatus=Failed, subtask=, subtaskStatus=, properties={appname=wimwmm}, message=ADMA5014E: The installation of application wimwmm failed.

[wplc-create-ear-impl] App Management object name = WebSphere:name=AppManagement,process=dmgr,platform=proxy,node=WSDDM,version=7.0.0.9,type=AppManagement,mbeanIdentifier=AppManagement,cell=WSD,spec=1.0

[wplc-create-ear-impl] Error removing listener:  javax.management.ListenerNotFoundException

[wplc-create-ear] null

   [wsadmin] WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode.

   [wsadmin]   ''

   [wsadmin] WASX7017E: Exception received while running file "/ao/was/WSD/WSDN1/AppServer/profiles/default/ConfigEngine/config/work /was/curJaclScript.jacl"; exception information:com.ibm.ws.scripting.ScriptingException: WASX7444E: Invalid parameter value "" for  parameter "config id" on command "showAttribute"

[wplc-create-ear] /ao/was/WSD/WSDN1/Portal/installer/wp.config/config/includes/wp.security_cfg.xml:129: Java returned: 105 

BUILD FAILED

/ao/was/WSD/WSDN1/Portal/installer/wp.config/config/includes/wp.security_cfg.xml:129: /ao/was/WSD/WSDN1/Portal/installer/wp.config/config/includes/wp.security_cfg.xml:129: Java returned: 105

CAUSE

This is observed with  the missing target if "Automatic Synchronization" is turned off in the nodeagent. WebSphere Portal's basic configuration does a server creation and then it maps all the apps to the server, but if the node was not synchronized then it fails

RESOLUTION
 From the WebSphere Admin Console:

System  administration -> Node agents -> nodeagent -> File synchronization service.

Make certain "Automatic synchronization" is checked..  With this turned on you should recycle the whole cell, synchronize all nodeagents and perform the installation again.The EJPSBCA job creates resources and makes changes to the

Portal server instance that are required when it is being started up to perform further configuration tasks, such as xmlAccess.  This is also needed to  deploy portlets and perform configuration changes through an access bean which connects to the JMX interface on the DM. Changes for Portal will  be written to the Deployment Manager and come in to effect on the Appserver node first when it is being synchronized.
Having the auto-sync box checked  is not a special requirement, it is the default when configuring WebSphere. 

 

Problem 4: EJPSBCA script fails during cfg-jcr-resources

with a return code 3072

EJBPSCA job excerpts

initialize-nodes:

     [echo] Calling JCRInitializer for file:

/PortalServer/V6R1/Portal/base/wp.sitem.cmd/config/nodes/publishrule.nodes

Target finished: initialize-nodes

Target finished: action-initialize-nodes-wp.sitem.cmd

Target finished: initialize-all-nodes

Target finished: cfg-jcr-resources

BUILD FAILED

/PortalServer/V6R1/Portal/jcr/prereq.jcr/config/includes/jcr_cfg.xml:79: The following error occurred while executing this line:

/PortalServer/V6R1/Portal/jcr/prereq.jcr/config/includes/jcr_cfg.xml:2647: The following error occurred while executing this line:

/PortalServer/V6R1/Portal/base/wp.sitem.cmd/config/includes/wp.sitem.cmd_cfg.xml:189: The following error occurred while executing this line:

/PortalServer/V6R1/Portal/jcr/prereq.jcr/config/includes/jcr_cfg.xml:2781: Java returned: 1

Total time: 18 minutes 50 seconds

---

Excerpts from the servant  logs

BossLog: { 0001} 2009/07/06 11:31:49.439 01 SYSTEM=SYLE SERVER=WPTPS1

PID=0X050000C1 TID=0X000000A1 0X133F5858  c=./bbgrjtr.cpp  at line:+955 ... com.ibm.icm.jcr.nodetype.ConstraintViolationException: The mandatory property: icm:language is not present for the Node named: ibmpersonalization:AttributeBasedAdmin.  The Node Type:ibmpersonalization:AttributeBasedAdmin requires this property be set for nodes of Node Type: icm:category.com.ibm.icm.jcr.nodetype.ConstraintViolationException: The mandatory property: icm:language is not present for the Node named:ibmpersonalization:AttributeBasedAdmin.  The Node Type:ibmpersonalization:AttributeBasedAdmin requires this property be set for nodes of Node Type: icm:category.

  at com.ibm.icm.jcr.NodeImpl.save(NodeImpl.java:3364)

  at com.ibm.icm.jcr.NodeImpl.save(NodeImpl.java:3292)

  at com.ibm.icm.jcr.NodeImpl.save(NodeImpl.java:3292)

  at com.ibm.icm.jcr.NodeImpl.save(NodeImpl.java:3292)

  at com.ibm.icm.jcr.NodeImpl.save(NodeImpl.java:2952)

  at com.ibm.icm.jcr.NodeImpl.save(NodeImpl.java:2892)

  at com.ibm.icm.jcr.serialization.handler.SysViewContentHandler.endDocument(SysViewContentHandler.java:243)

  at org.apache.xerces.parsers.AbstractSAXParser.endDocument(UnknownSource

< TRUNCATED>

CAUSE:

  The wrong version of Derby  database is in use. It appears  that the version  of the  Derby  database was not automatically updated.

RESOLUTION

You may need to manually update the   Derby version associated with the Portal server

 From OMVS

1. Change the working directory to the directory that contains the Derby fix.

 cd /usr/lpp/zWebSphere/V6R1/derby/fixes/10.1/<derby_build_number

derby_build_number would be 10.1.3.2.639536 or later

2. Run the script referencing the  appropriate WAS_HOME variable.
updateDerby.sh < WAS_HOME >                    For example:   updateDerby.sh /WebSphere/V6R1M0/AppServer

 This is  reported  in APAR PK66013   See  the following  link for more information.  http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg21305388

Problem 5: EJPSBCA script fails during enable-security-wizard job fails during SOAP connection

EJBPSCA job excerpts

com.ibm.websphere.management.exception.ConnectorException: ADMC0016E: The system cannot create a SOAP connector to connect to host

xxx.xxx.xxx.xx.com at port 30013.at com.ibm.websphere.management.AdminClientFactory.createAdminClient(AdminClientFactory.java:531)

  at com.ibm.wkplc.was.registry.AdminConfigRegistry.createAdminClient(AdminConfigRegistry.java:211)

Caused by:

com.ibm.websphere.management.exception.ConnectorNotAvailableException:

[SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket: javax.net.ssl.SSLException:java.lang.RuntimeException: Unexpected error:

java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty;

targetException=java.lang.IllegalArgumentException: Error opening socket: javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error:java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty] at com.ibm.ws.management.connector.soap.SOAPConnectorClient.reconnect(SOAPConnectorClient.java:392) at

com.ibm.ws.management.connector.soap.SOAPConnectorClient.(SOAPConnectorClient.java:211)  ... 21 more

Caused by: [SOAPException: faultCode=SOAP-ENV:Client; msg=Error openingsocket: javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error:

java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty; targetException=java.lang.IllegalArgumentException: Error opening socket:

javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty] at

org.apache.soap.transport.http.SOAPHTTPConnection.send(SOAPHTTPConnection.java:426)  at org.apache.soap.rpc.Call.invoke(Call.java:267)  at com.ibm.ws.management.connector.soap.SOAPConnectorClient$4.run(SOAPConnectorClient.java:364)at

com.ibm.ws.security.util.AccessController.doPrivileged(AccessController:java:118)  at com.ibm.ws.management.connector.soap.SOAPConnectorClient.reconnect(SOAPConnectorClient.java:349)

 Also review the various FFDC logs entries at the time of the errors   and you may see  entries  similar  to the following below

java.io.IOException: R_datalib (IRRSDL00) error: profile for ring not found (8, 8, 84)

at com.ibm.crypto.provider.RACFInputStream.a(Unknown Source)

at com.ibm.crypto.provider.RACFInputStream.(Unknown Source)

at com.ibm.crypto.provider.safkeyring.a.getInputStream(Unknown Source)

at java.net.URL.openStream(URL.java:1013)

at com.ibm.ws.ssl.config.WSKeyStore.openKeyStore(WSKeyStore.java:1124)

at com.ibm.ws.ssl.config.WSKeyStore$1.run(WSKeyStore.java:769)

com.ibm.ws.security.util.AccessController.doPrivileged(AccessControlleR

Atcom.ibm.ws.ssl.config.WSKeyStore.do_getKeyStore(WSKeyStore.java:595)

at com.ibm.ws.ssl.config.WSKeyStore.getKeyStore(WSKeyStore.java:874)

com.ibm.ws.ssl.config.KeyStoreManager.getKeyStore(KeyStoreManager.java:

com.ibm.ws.ssl.provider.AbstractJSSEProvider.getKeyTrustManagers(AbstractJSSEProvider.java:336)

com.ibm.ws.ssl.provider.AbstractJSSEProvider.getSSLContext(AbstractJSSEProvider.java:191)

com.ibm.ws.ssl.provider.AbstractJSSEProvider.getSSLSocketFactory(AbstractJSSEProvider.java:813)

com.ibm.websphere.ssl.JSSEHelper.getSSLSocketFactory(JSSEHelper.java:603com.ibm.websphere.ssl.protocol.SSLSocketFactory.(SSLSocketFactor

 

CAUSE

    The initial error indicates that the mentioned user in the log cannot find  the appropriate keyring. However the root of the problem is usually that  servant  region is running under the wrong user id

 RESOLUTION:

 Make sure the  servant region is running under correct  user  (not IBMUSER )

Here is a sample set of command to view and set the appropriate  user. For Started  task. Change the  user and servant region names to match your  environment.

To view the STARTED task:

RLIST STARTED WSACRA.WSSR00BS STDATA

To set the STARTED task to WSASRU for WSACRA.WSSR00BS

RDEFINE STARTED WSACRA.WSSR00BS STDATA(USER(WSASRU) GROUP(WSCFG) TRACE(YES))SETROPTS RACLIST(STARTED) GENERIC(STARTED) REFRESH

Problem 6:

Large Portlet Application deployment errors 

CAUSE

This error usually happens when  very large portlets  are  being deployed .  The default 10M  protocol_http_large_data_inbound_buffer  size   is not enough . This  also  happens when a large  file is being imported during  other activities. This is not unique to  the  z/OS.

RESOLUTION

In order to handle large EAR files, make sure that the HTTP buffers for   the administration server  or  the deployment manager and node agents are set to larger numbers:

Gradually increase the protocol_http_large_data_inbound_buffer and, optionally, protocol_http_large_data_response_buffer

Restart the deployment  manager and or Administration server and rerun the appropriate task or job .

Environment >  Manage Websphere Variables> new

- protocol_http_large_data_inbound_buffer = 20485700 (or some other large number)

Relevant links

http://www-01.ibm.com/support/docview.wss?uid=swg1PK57911

If running in 64 bit mode, also see  http://www-01.ibm.com/support/docview.wss?rs=404&uid=swg1PK37706