Steps for this task
Note: Ensure that you have Enabled Server Target support for J2EE projects and that you set the target server as Integration Server v5.1. Without properly setting one of these target servers the panels listed in the following steps night not appear. Furthermore, after enabling or changing the target server you might need to close and re-open any currently open Deployment Descriptor Editors for these changes to be reflected in the given Deployment Descriptor Editor. Note that Pushdown support is only available when the server target is Integration Server v5.1.
Set the interactionSpecClassName attribute to the appropriate fully-qualified J2EE Connector Architecture (JCA) InteractionSpec class name. For example, the class name for use with CICS ECI is com.ibm.connector2.cics.ECIInteractionSpec.
CMPDeploy <ejb.jar | application.ear> <-dir directory> <-overwrite> <-verbose>
If you do not specify -dir the tool outputs its files into a package-based directory structure rooted at the current directory.
If you do not specify -overwrite the tool will abort the process with a warning message if the UserDefinedPushDownMethodsImpl class already exists.
If you do not specify the -verbose option the tool does not display tracing messages, but only displays a message at the end of the process specifying either what was emitted or else what problems were encountered.
This command accepts either an EAR or JAR file, and generates the UserDefinedPushDownMethods interface, and skeleton Java source code for the bean's UserDefinedPushDownMethodsImpl class. For example, if the EJB JAR contains a procedural CMP bean called Account, then CMPDeploy Account.jar emits a generic AccountUserDefinedPushDownMethods interface, and a backend specific AccountUserDefinedPushDownMethodsImpl.java class that implements the interface.
For a non-CCI based CMP/A bean (one that does NOT use JCA connectors, such as one with a backEndType of EJB, JAX-RPC, WSIF, or Custom), you must install the WebSphere Procedural Resource Adapter provided with WebSphere Business Integration Server Foundation Version 5.1, and specify a binding to it. To do this, you need to install the WebSphere/AppServer/installableApps/cmpaAdapter.rar file.
Note: Such beans are inherently non-transactional, and should be marked with a transaction policy of NotSupported, unless your UserDefinedPushDownMethodsImpl code (or code called from it) registers with JTA. For non-transactional CMP/A beans, you must use Compensation to enable transaction rollback functionality.