Troubleshooting
Problem
Language data binding generator such as CICS adapter does not generate binding classes when the deployment is through the servicedeploy command.
Symptom
The CICS adapter does not generate the necessary binding classes when the project is deployed with the servicedeploy command, resulting in errors similar to the following:
[4/12/12 14:04:42:591 CEST] 00000072 EIS Z
com.ibm.ws.sca.binding.j2c.deploy.J2CGenerateDataBindingTask
com.ibm.ws.sca.binding.j2c.deploy.J2CGenerateDataBindingTask#1482
Exception: commonj.connector.metadata.MetadataException: Could not load
the databinding generator, invalid generator specified on the
dataBindingType:
com.ibm.databinding.writer.databinding.LanguageDataBindingGenerator
This applies to the language data binding generators so this includes CICS, IMS, and possibly Flatfile, FTP, and MQ.
Cause
This is a permanent limitation of WebSphere Integration Developer V7.0 (WID) for the language data binding generators such as the CICS adapter, and the issue has been addressed in V7.5.
Resolving The Problem
The way to work around this limitation is to move the generated adapter binding classes from the gen/src directory to the root directory (so they will still be on the classpath and can be found), and mark them as "Not derived" by right-clicking the file and unchecking "Derived" from its Properties editor.
It is necessary to check in the binding classes into the version control system. Also, to prevent these classes from getting generated in gen/src every time, it is necessary to "clear" the binding data format in the Properties of the Import as shown in the image below. This way it will not generate the binding classes anymore.
There is no need to regenerate the binding classes if there is no change in the binding data. If changes are made, regenerate the binding classes and move the classes out of gen/src again.
This issue is fixed in BPM 7.5 and following releases.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21595166