Troubleshooting
Problem
Running the serviceDeploy tool as a stand-alone application and without using WebSphere Integration Developer does not generate Java source code files for some artifacts, such as custom mediations or mappings (interfaces and business objects).
Symptom
The information contained in this document has been moved to developerWorks Answers located here. This technote will be archived in 60 days. Please bookmark the new location.
A new Enterprise Archive (EAR) is generated by the serviceDeploy tool, but the packaged application is missing the compiled Java™ classes for any type of custom Java code implementations. This scenario might result in a runtime exception (for example ClassNotFoundException).
Cause
The problem is a limitation in WebSphere Process Server V6.0, 6.1, 6.1.2, 6.2, and 7.0. WebSphere Integration Developer provides a plug-in that generates the necessary Java source code files for artifacts, such as custom mediations. However, that plug-in is not available to the serviceDeploy tool, and, therefore, some files are not generated.
Resolving The Problem
Depending on the approach you use to compile and package your WebSphere Process Server and WebSphere Enterprise Service Bus applications, you can resolve the problem in one of the following ways:
- You use WebSphere Integration Developer to package and export your application.
Because WebSphere Integration Developer provides the necessary code-generating plug-in, all of the Java source files that are needed for custom artifacts are available to generate the Java code and compile it. The following technote explains how to export your application so that it can be compiled using the serviceDeploy tool as a stand-alone application and explains the differences in WPS V7.0 run-time deployment for the serviceDeploy tool:
Derived files not generated when serviceDeploy is used in WebSphere Process Server
- You use the serviceDeploy tool as a stand-alone application.
This approach is usually used when the service deployment and application packaging is automated, for example, when using Ant as the build engine. If you check out your project from a Source Control System (the workspace is copied and packaged in a .zip file for the serviceDeploy tool to use), make sure that all artifacts are available to the tool, including custom artifacts (for example, for custom mediations, make sure that all .smap files are available) and the by the plug-in already generated Java source code files. In the case of a custom mediation, the following files must be available (if the default path in the workspace was not changed):
yourModule/gen/src/sca/component/mediation/java/*.java
yourModule/gen/src/sca/component/mediation/java/*.smap
By default, the serviceDeploy tool compiles all Java source code files, and the resulting EAR file contains the missing resources:
yourModuleJAR/sca/component/mediation/java/*.class
Related Information
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21384239