JR47663: STANDALONE WEBSPHERE ADAPTER INSTALLATION INSTRUCTIONS ARE INCORRECT AND CAN CAUSE DEPLOYMENT FAILURES.

APAR status

• Closed as documentation error.

Error description

• Standalone WebSphere Adapter installation instructions are
  incorrect and can cause deployment failures.
  
  There is a limitation when using standalone adapters, that the
  jar files are required for use on the deployment manager when
  installing an application. This is because the data bindings for
  an application's SCA adapter bindings are generated at install
  time.
  
  When this task fails you may still see the application EAR
  successfully installed although the logs may show an error for
  the data binding task like:
  J2CBinding    E
  J2CGenerateDataBindingTask.generateDataBinding():
  Cannot load databinding generator:
  com.ibm.j2ca.jdbc.emd.databinding.JDBCDataBindingGenerator
  
  If this task fails then the adapter bindings would not be able
  function at runtime. Then you might see error when processing
  messages with the binding like this:
  ResourceException thrown in J2CMethodBindingImpl.invoke() javax.
  resource.ResourceException: Illegle arguement: the value of
  input Record is null, please provide a not null and valid input
  Record.
  
  Or
  java.lang.ClassNotFoundException:
  com.ibm.xmlns.prod.websphere.j2ca.jdbc.
  MyObjectbg.MyObjectBGDataBinding
  at java.lang.Class.forNameImpl(Native Method)
  at java.lang.Class.forName(Class.java:174)
  at com.ibm.ws.sca.binding.j2c.handler.J2CImportHandler$1.run
  (J2CImportHandler.java:261)
  at java.security.AccessController.doPrivileged
  (AccessController.java:277)
  at
  com.ibm.ws.sca.binding.j2c.handler.J2CImportHandler.newInstance
  (J2CImportHandler.java:259)
  
  
  WAS does not provide a method for installing a RAR file to the
  Deployment manager. While the rar file only needs to be
  available to the deployment manager during related application
  installation, it is not documented in the deployment or
  standalone adapter install instructions.
  http://pic.dhe.ibm.com/infocenter/dmndhelp/v8r5m0/topic/com.ibm.
  wsadapters.jca.jdbc.doc/env/shared/tsha_cluster_node_jndi.html
  or
  http://pic.dhe.ibm.com/infocenter/dmndhelp/v8r5m0/topic/com.ibm.
  wsadapters.jca.jdbc.doc/env/shared/tsha_installrar.html
  
  This page is a bit confusing:
  http://pic.dhe.ibm.com/infocenter/dmndhelp/v8r5m0/topic/com.ibm.
  wbpm.admin.doc/topics/rcfglibadapters.html#rcfglibadapters__stan
  dalone
  
  The documentation needs to state the steps of installing the
  rar on each node in the desired cluster or server. Then the rar
  file needs to be copied to the deployment manager's
  installedConnectors directory from the other node's
  installedConnectors directory.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Business Process Manager Advanced Users     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Standalone WebSphere Adapter            *
  *                      installation instructions are           *
  *                      incorrect and can cause deployment      *
  *                      failures.                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Following steps should be used when install the stand along
  adapter:
  If you install an EAR package in a network deployment
  environment that has dependencies on a stand-alone adapter,
  ensure that the adapter can be accessed on the deployment
  manager server by completing the following steps:
  1. Locate the BPM_Install_root/lib/ext folder for the
  installed deployment manager server.
  2. Extract all the content contained in the stand-alone
  adapter RAR package to that folder.
  3. Restart the deployment manager server to make the server
  class loader clear the cache, and index the newly added
  classes and schemas.
  4. Install the application to the target server using the
  administrative console or administrative scripts.
  5. After you have installed the application to the target
  server or cluster, remove all the content you extracted from
  the stand-alone adapter RAR package into thelib/ext folder, to
  avoid duplicated entry issues at run time.
  

Problem conclusion

• With the updated process. The standalone adapter can be
  successfully installed on server.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels