Why and when to perform this task
After a CMP bean and an application have been developed into an .ear file, you are ready to deploy this application in the WebSphere environment. We recommend that you provide the stored procedure invocation and input/output record management logic in a separate document so the deployer knows how to inject the code into the UserDefinedPushDownMethodsImpl class. Or, you can put the information in the method description under the Deployment Descriptor.
There are two ways to deploy the beans:
CMPDeploy ejb.jar|application.ear -dir directory -overwrite -verbose
Where:
-dir is an optional parameter; when specified, the files are output to this package-based directory structure, rooted at the specified directory
-overwrite is an optional parameter. When specified, any existing file is overwritten; otherwise, CMPDeploy ends with a message if the beanUserDefinedPushDownMethodsImpl class already exists
-verbose is an optional parameter. When specified, full trace messages display; otherwise, one information message displays at the end of the trace. For example: CMPDeploy BankAccountBean.jar