An alternate option for installing business integration applications uses the serviceDeploy command. This command prepares an EAR file from a JAR or zip file that contains service components. For example consider an application "sampleOrderBPELApp", the orderProcess business process (service component) is packaged in a JAR file called sampleOrderBPELApp.jar. The syntax for the command is as follows:
serviceDeploy sampleOrderBPELApp.jar -keep
The service components are taken from the JAR file and an installable EAR file named sampleOrderBPELApp.ear is generated. The EAR file is then deployed to the application server. The -keep option saves the temporary files generated during deployment, which may be useful for troubleshooting. There is another command-line option, -noJ2EEdeploy, which skips the deployment of the application to the application server. You should consider this option if you need to only generate the EAR file and do not wish to deploy the application immediately.
serviceDeploy sampleOrderBPELApp.jar -keep
The service components are taken from the JAR file and an installable EAR file named sampleOrderBPELApp.ear is generated. The EAR file is then deployed to the application server. The -keep option saves the temporary files generated during deployment, which may be useful for troubleshooting. There is another command-line option, -noJ2EEdeploy, which skips the deployment of the application to the application server. You should consider this option if you need to only generate the EAR file and do not wish to deploy the application immediately.
No comments:
Post a Comment