Known Issues: WebSphere Process Server and Enterprise Service Bus for z/OS V7.0

Content

This document is split into two sections, the first section lists installation and configuration issues and the second section lists runtime issues.

Installation and Configuration Issues:

• Problem: The CEI configuration fails. You cannot configure the CEI component on an Network Deployment cell either manually or using the deployment environment tool. When you attempt to configure the CEI component from the administration console, the following error is seen:
  
  
  CEIIN0751E The command found an existing Event Service DB2 data source, which is not compatible with the DB2ZOS database. To create the Event Service DB2ZOS data source, run the command again with the overrideDataSource parameter set to true.
  
  
  Solution: Download and SMP/E install usermod AN62573 for WebSphere Process Server or AN62574 for WebSphere Enterprise Service Bus before configuring WebSphere Process Server or WebSphere Enterprise Service Bus for z/OS V7.0.
  
  
• Problem: When DB2 for z/OS is the database, the generated createTable_governancerepository.sql script contains a superfluous period, which causes execution of the DDL to fail.
  
  
  The DDL to create the governance database tables contains an extra period (".") in the DDL on the CREATE UNIQUE INDEX @SCHEMA@.w_obj_subj_idx statement. The extra period is between "w_obj_subj_index" and "(obj_id...":
  
  
  CREATE UNIQUE INDEX @SCHEMA@.w_obj_subj_idx
  ON @SCHEMA@.w_obj_subj_index.(obj_id, obj_typ_cd, version_from,
  version_to, partition_id);
  
  
  This issue causes the execution of the DDL to fail with SQLCODE = -104, SQLSTATE = 42601, error tokens = (;<IDENTIFIER>
  
  
  Solution: Manually edit the DDL to remove the period before executing the DDL.
  Note: The file is an ASCII file. With the period removed, the above DDL looks like:
  
  
  CREATE UNIQUE INDEX @SCHEMA@.w_obj_subj_idx
  ON @SCHEMA@.w_obj_subj_index(obj_id, obj_typ_cd, version_from,
  version_to, partition_id);
  
  
  If the createDB.sh script is being used, the default location for the DDL being executed is <WAS_HOME>/util/dbUtils/WBI_CommonDB_DB2-zOS-x-CommonDB/
  createTable_governancerepository.sql (where "x" is the DB2 Version 8 or 9).
  
  
• Problem: There is an invalid combination of Provider and Driver Type on the Business Process Choreographer ME data source.
  
  
  The data source "Business Process Choreographer ME data source" is generated with a Java™ database connectivity (JDBC) Provider of "DB2 Universal JDBC Driver Provider (XA)" and a driver type of "2", which is an invalid combination.
  
  
  This situation can be verified in the administration console by navigating to Data sources > Business Process Choreographer ME data source and verifying the values for "Provider" and "Database name". There is also an exception thrown in the servant job log:
  BossLog: { 0225} 2009/12/01 16:36:48.745 02 SYSTEM=MVP1 CELL=S05CELL1 NODE=NODE1 CLUSTER=WCLS05Z1 SERVER=WZS05Z1  PID=0X0001031E TID=0X00000051 0X74BFC24C  c=./bbgrjtr.cpp  at line:+886 ... BBOO0220E: J2CA0009E: An exception occurred while trying to instantiate the ManagedConnectionFactory class com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl used by resource jdbc/com.ibm.ws.sib/Node1MVSP1.server1-BPC.S05Cell1Base.Bus : java.lang.reflect.InvocationTargetException                                                    
  
  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.ejs.j2c.J2CUtilityClass.createMCFEntry(J2CUtilityClass.java:581)                                                        
  at com.ibm.ejs.j2c.ConnectionFactoryBuilderServerImpl.createMCFandPM(ConnectionFactoryBuilderServerImpl.java:564)                  
  at com.ibm.ejs.j2c.ConnectionFactoryBuilderServerImpl.processObjectInstance(ConnectionFactoryBuilderServerImpl.java:938)          
  at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(ConnectionFactoryBuilderImpl.java:627)                          
  at javax.naming.spi.NamingManager.getObjectInstanceByFactoryInReference(NamingManager.java:485)                                    
  at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:350)                                                        
  at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers.java:927)                                            
  at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:730)                                              
  at com.ibm.ws.naming.jndicos.CNContextImpl.cacheLookup(CNContextImpl.java:4023)                                                    
  at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1772)                                                      
  at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1749)                                                      
  at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1500)                                                      
  at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:637)                                                          
  at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:165)                                                                  
  at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)                                                       at javax.naming.InitialContext.lookup(InitialContext.java:455)                                                              at com.ibm.ws.sib.msgstore.persistence.impl.WASDatasourceWrapper.getDataSource(WASDatasourceWrapper.java:632)              
  at com.ibm.ws.sib.msgstore.persistence.impl.WASDatasourceWrapper.<init>(WASDatasourceWrapper.java:169)                      
  at com.ibm.ws.sib.msgstore.persistence.impl.DatasourceController.<init>(DatasourceController.java:133)                      
  at com.ibm.ws.sib.msgstore.persistence.impl.PersistentMessageStoreImpl.initialize(PersistentMessageStoreImpl.java:167)      
  at com.ibm.ws.sib.msgstore.persistence.PersistenceFactory.getPersistentMessageStore(PersistenceFactory.java:68)            
  at com.ibm.ws.sib.msgstore.impl.MessageStoreImpl.start(MessageStoreImpl.java:1517)                                          
  at com.ibm.ws.sib.admin.impl.JsMessagingEngineImpl.start(JsMessagingEngineImpl.java:609)                                    
  at com.ibm.ws.sib.admin.impl.HAManagerMessagingEngineImpl.activate(HAManagerMessagingEngineImpl.java:995)                  
  at com.ibm.ws.sib.admin.impl.JsActivationThread.run(JsActivationThread.java:92)                                            
  Caused by: javax.resource.ResourceException: DB2ZOS_TYPE2_ERROR                                                              
  at com.ibm.ws.rsadapter.spi.InternalDB2UniversalDataStoreHelper.setProperties(InternalDB2UniversalDataStoreHelper.java:295)
  at com.ibm.ws.rsadapter.spi.WSRdbDataSource.<init>(WSRdbDataSource.java:1271)                                              
  at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.setDataSourceProperties(WSManagedConnectionFactoryImpl.java:2600)
  ... 29 more                                                                                                                 . com.ibm.ejs.j2c.ConnectionFactoryBuilderServerImpl              
  
  
  This problem affects Process Choreographer messaging functions.
  
  
  Solution: Change the "Business Process Choreographer ME data source" in one of two ways:
• Change the data source to be a type 4.
1. Navigate to Data sources > Business Process Choreographer ME data source and change "Driver type" to type 4. Note: The "Server name" and "Port number" also need to be set for the type 4 driver to work.
2. Save your changes.
3. Restart the server.
• Delete the data source and recreate it with the correct JDBC driver.
1. Navigate to Data sources > Business Process Choreographer ME data source.
2. Record the value of "JNDI name".
3. Navigate to Data sources. Select Business Process Choreographer ME data source and click Delete.
4. Save your changes.
5. Navigate to Data sources and select a scope of server. Click New.
6. Enter a "Date source name" of "Business Process Choreographer ME data source". In the "JNDI name" field, enter the value which you saved in step 2.
7. Choose Select an existing JDBC provider and select DB2 Universal JDBC Driver Provider.
8. Set "Driver type" to "2"; set "Database name" the database location name of your DB2 subsystem.
9. Click Next on the "Setup security aliases" panel.
10. Click Finish.
11. Navigate to Data sources > Business Process Choreographer ME data source > Custom properties > fullyMaterializeLobData and change the value from "true" to "false".
12. Navigate to Data sources > Business Process Choreographer ME data source > Custom properties > retrieveMessagesFromServerOnGetMessage and change the value from "true" to "false".
13. Save your changes.
14. Restart the server.


• Problem: If you are using the createDB.sh script to create DB2 for z/OS tables, the default setting for use of SET CURRENT SQLID has changed from true to false. This change can cause problems with the Relationship component if the appropriate GRANTs are not issued.
  
  
  There are two options on createDB.sh -UseSqlid and +UseSqlid, which instruct the script to not make use of SET CURRENT SQLID or to make use of SET CURRENT SQLID respectively. The default setting in previous versions was +UseSqlid, which in response to customer feedback, has been changed to -UseSqlid.
  
  
  The plan is to eventually remove the setting of the currentSQLID custom property on all WBI data sources. Unfortunately, this property is still required on WBI_DataSource. This, combined with the changed default for UseSqlid in the createDB.sh script, results in the Relationship Service producing SQL errors similar to the following:
  [IBM/DB2][T2zos/2.11.67]T2zosStatement.readExecuteImmediate:nativeExecuteImmediate:867:DB2 engine SQL error, SQLCODE = -551, SQLSTATE = 42501, error tokens = S4CELL;CREATE TABLE;S4CELLDB  
  
  
  This error means that the schema S4CELL does not have the privilege to create tables on database S4CELLDB, because the database owner is the user identity used to run the createDB.sh script. In previous versions, a SET CURRENT SQLID = S4CELL issued by the createDB.sh script would have made S4CELL the owner of the database and this error would not occur.
  
  
  Solution: The permissions, which need to be assigned to prevent this error, are:
• GRANT DBADM ON DATABASE S4CELLDB TO S4CELL;
• GRANT USE OF STOGROUP S4DBSTO TO S4CELL;
Alternatively, run the createDB.sh script with the +UseSqlid option explicitly specified.


• Problem: The DDL to create the Common Event Infrastructure (CEI) database tables does not contain the parameters in a database design file created by the DbDesignGenerator.sh script. For example, the database name in cr_db.ddl is hard-coded as "event".
  
  
  The DDL for the CEI tables might be generated by the augment of a stand-alone server, for which the database design file might be referenced using the "wbidbDesign" response file parameter. The DDL is generated into the /<WAS_HOME>/profiles/default/dbscripts/CEI directory. This DDL is generated with none of the customizations that were specified to the DbDesignGenerator.sh script when the database design file was created.
  - cd_db-ddl contains a hard-coded database name:"CREATE DATABASE event CCSID UNICODE;".
  - cr_db_catalog.dll contains a hard-coded database name: "CREATE DATABASE eventcat CCSID UNICODE;".
  - cr_tbl.ddl and cr_tbl_catalog.ddl contain an incorrect schema name in the "SET CURRENT SCHEMA" statement. In addition, the DDL does not contain schema qualifiers on tables and so on
  - cr_ts.ddl and cr_ts_catalog.ddl define tables into hard-coded database names (see above).
  - catalogSeed.ddl contains SQL which is not qualified with the schema name.
  
  
  Solution: Use the createDB.sh script to generate the DDL. If the createDB.sh script is run with the following options, the DDL is generated (but not run) into the cdbtmp/ceidb.sql file, where cdbtmp is the work directory created in the directory from which createDB.sh is run.
  
  
  ./createDB.sh -All +DBCEI -RunSQL
  
  
• Problem: The Business Space data source configuration is incomplete.
  If Business Space is configured manually on a Network Deployment cell, the Business Space application console does not display. This situation does not happen on stand-alone servers or Network Deployment cells that are configured using the Deployment Environment tool.
  On launching the Business Space application console the following error is returned:
  
  
  BMWMB0039E: Fail to load page. The error message is: TypeError - this.getNavigationRootNode(_178) is null. Please contact Lotus Mashups administrator.
  
  
  In the Deployment Manager joblog there are the following errors:
  CWMFN4005E: The datasource was found but a database exception occurred. Possible causes are the database was down, database connectivity was lost, network error, incorrect or insufficient credentials to connect to the database.com.ibm.db2.jcc.b.SqlException: DB2 SQL error: SQLCODE: -725, SQLSTATE: 42721, SQLERRMC: CURRENT SCHEMA;DSN810PP
  
  
  Implications if issue is not addressed
  Unable to launch Business Space.
  
  
  Solution: Complete the following steps in the administration console:
1. Delete the mashupDS data source.
2. Create a new mashupDS data source using the desired DB2 Universal JDBC Driver Provider.
3. Stop and restart the cluster.

• Problem: SCA Messages are not being processed from destinations due to missing listeners in the Adjunct (CRA). Messages are successfully written to SCA destinations but time outs occur due to the missing listeners. Asynchronous test scenarios using the native container fail with the following error:
  [11/12/09 13:47:59:125 GMT] 00000057 CommonBridge  E   BBOJ0117I: JAVA THREAD STACK TRACEBACK FOR THREAD WebSphere:ORB.thread.pool t=009bed90:
  Thread Hang Recovery--thread could not be encouraged to complete
  Traceback for thread WebSphere:ORB.thread.pool t=009bed90:
  java.lang.Object.wait(Native Method)
  java.lang.Object.wait(Object.java:167)
  com.ibm.ws.sib.jfapchannel.impl.ExchangeReceiveListener.waitToComplete(ExchangeReceiveListener.java:227)
  com.ibm.ws.sib.jfapchannel.impl.ConversationImpl.exchange(ConversationImpl.java:985)
  com.ibm.ws.sib.comms.common.JFAPCommunicator.jfapExchange(JFAPCommunicator.java:382)
  com.ibm.ws.sib.comms.client.ConsumerSessionProxy.performReceive(ConsumerSessionProxy.java:913)
  com.ibm.ws.sib.comms.client.ConsumerSessionProxy._receiveWithWait(ConsumerSessionProxy.java:824)
  com.ibm.ws.sib.comms.client.ConsumerSessionProxy.receiveWithWait(ConsumerSessionProxy.java:732)
  com.ibm.ws.sib.ra.impl.SibRaConsumerSession.receiveWithWait(SibRaConsumerSession.java:218)
  com.ibm.ws.sca.internal.async.sib.SIBAsyncHandler.receiveMessage(SIBAsyncHandler.java:894)
  com.ibm.ws.sca.internal.async.sib.SIBAsyncHandler.receiveResponse(SIBAsyncHandler.java:340)
  com.ibm.ws.sca.internal.async.handler.AsyncSourceHandler.processMessage(AsyncSourceHandler.java:406)
  com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessage(MessageDispatcherImpl.java:1671)
  com.ibm.ws.sca.internal.message.impl.ManagedMessageImpl.process(ManagedMessageImpl.java:837)
  com.ibm.ws.sca.uow.handler.UOWNativeWASStrategyImpl.transactionLocalActivitySessionFalse(UOWNativeWASStrategyImpl.java:1152)
  com.ibm.ws.sca.uow.handler.UOWNativeWASStrategyImpl.deliverAsyncAtCall(UOWNativeWASStrategyImpl.java:85)
  com.ibm.ws.sca.uow.handler.DeliverAsyncAtUOWNativeHandler.processMessage(DeliverAsyncAtUOWNativeHandler.java:72)
  com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessage(MessageDispatcherImpl.java:1671)
  com.ibm.ws.sca.internal.proxy.impl.ProxyInvocationHandlerImpl.invokeResponse(ProxyInvocationHandlerImpl.java:1223)
  com.ibm.ws.sca.internal.proxy.impl.ProxyInvocationHandlerImpl.invoke(ProxyInvocationHandlerImpl.java:732)
  $Proxy62.invokeResponse(Unknown Source)
  
  
  Solution: Download and apply the fixes from this link.
  
  
• Problem: SCA Asynchronous Callback scenarios fail due to a missing callback token. The Event Sequencing, Store and Forward, and Recovery functions result in the following error:
  FFDC Exception:java.lang.IllegalArgumentException
  SourceId:com.ibm.wsspi.sca.container.ComponentMetaDataManager.beginContext
  ProbeId:001 Reporter:com.ibm.ws.classloader.CompoundClassLoader@6a8d6a8d
  java.lang.IllegalArgumentException: Current thread's InvocationToken (to
  handle callbacks) cannot be obtained.
  at
  com.ibm.wsspi.sca.container.ComponentMetaDataManager.beginContext(ComponentMetaDataManager.java:92)
  at com.ibm.wsspi.sca.container.ComponentMetaDataManager.beginContext(ComponentMetaDataManager.java:56)
  at com.ibm.wbiservers.storeandfwd.messaging.CompQAsyncCallbackImpl.processMessage(CompQAsyncCallbackImpl.java:412)
  at com.ibm.wbiservers.storeandfwd.messaging.CompQAsyncCallbackImpl.consumeMessages(CompQAsyncCallbackImpl.java:280)
  at com.ibm.ws.sib.processor.impl.AsynchConsumer.processMsgs(AsynchConsumer.java:113)
  at com.ibm.ws.sib.processor.impl.JSLocalConsumerPoint.processAttachedMsgs(JSLocalConsumerPoint.java:2511)
  at com.ibm.ws.sib.processor.impl.JSLocalConsumerPoint.runAsynchConsumer(JSLocalConsumerPoint.java:3286)
  at com.ibm.ws.sib.processor.impl.JSLocalConsumerPoint$AsynchThread.run(JSLocalConsumerPoint.java:3581)
  at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1550)
  
  
  Solution: Download and apply the fixes from this link.
  
  
• Problem: When you log into Business Space, you might see a "Topic not found" message in the Welcome to Business Space space or you might see the message when you click the Help link in the banner or in the widget menus.
  
  
  Solution: To resolve the problem, you will need to add the absolute path to the help for each node in the cell. Complete the following steps:
1. Stop all servers or clusters.
2. Change the directory to the directory that contains the redirection file for the help:
   For a standalone server:
   <WAS_Profile>/installedApps/<Cell_name>/BusinessSpaceHelpEAR_<nodename>_<servername>.ear/BusinessSpaceHelp.war/WEB-INF/eclipse/configuration/
   For Network Deployment:
   <WAS_Profile>/installedApps/<Cell_name>/BusinessSpaceHelpEAR_<DeploymentEnvironmentTargetname>.ear/BusinessSpaceHelp.war/WEB-INF/eclipse/configuration/
3. Edit the ASCII file links.properties and add the following line:
   second = <WAS_Profile>/config/BusinessSpace/help/bspace_help.link
   
   The file will look like this example:
   
   first = config/BusinessSpace/help/bspace_help.link
   second = /WebSphere/V7S04Z1/AppServer/profiles/default/config/BusinessSpace/help/bspace_help.link
   
   Note: If you want a common redirection file, add a line for each profile hosted on z/OS. You can then copy the file to the other profiles.
4. Change the directory to the help system cache:
   For a stand-alone server:
   <WAS_Profile>/temp/<nodename>/<servername>/BusinessSpaceHelpEAR_<nodename>_<servername>/BusinessSpaceHelp.war/eclipse/configuration
   
   For Network Deployment:<WAS_Profile>/temp/<nodename>/<DeploymentEnvironmentTargetname>/BusinessSpaceHelpEAR_<DeploymentEnvironmentTargetname>/BusinessSpaceHelp.war/eclipse/configuration
5. Delete the links.properties file and all directories starting with name 'org.eclipse'.
   For example:
   rm links.properties
   rm -rf org.eclipse.*  
6. Start the server or cluster.
   
   
• Problem: The Business Space System Health Widget displays unreliable status information.
  The information displayed should reflect the same as information in the administration console. However, in some circumstances, it does not. Some components with their status started in the administration console displays on the System Health Widget as stopped.
  
  Solution: Do not rely upon the information displayed on the Business Space System Health Widget. Use the administration console instead.