When developing mediation service applications, you may need to work with resources such as JSP files, JAR files, Web projects, Java™ projects, and J2EE projects. This topic provides information to help you set up your projects and resources so that they can be successfully built and deployed to WebSphere® Enterprise Server or WebSphere Process Server.
Best Practices: If you need to develop Java applications or import JAR files that will be used by a custom mediation primitive, you should create a Java project for the code and add a dependency on the Java project to the mediation module that will be using the Java code.
The Java properties of the business integration library or mediation module should not be altered because this may cause problems in deployment code generation. As a result, we do not recommend that you develop complex Java applications or import JAR files into a library or mediation module in order to use them. Also, when generating Java implementations for Java components in a mediation module assembly diagram, the generated Java implementations should be used as a launch point to call other Java classes.
Note that the Business Integration view only shows Java implementations and interfaces that are used in an assembly diagram. They are listed under the mediation module that uses them. If you need to work with Java projects you can switch to work in the Java perspective.
Switching to the Java perspective
Open the Java perspective by following these steps:
In the Java perspective, the two opened perspectives are shown at the top right corner of the Workbench window, you can switch to the Business Integration perspective by clicking the Business Integration perspective button, as shown in this image:
Best Practices: If you plan to use imports and exports in mediation module assembly diagrams, it is a good practice to put the business objects and interfaces that are used by the import and exports into a library so that they can be shared. Then, add a dependency on the library to all of the modules that use these common resources. Avoid copying the same business objects and interfaces into different modules to use them.
If you need to use a WSDL file in a module, copy it to the module. Optionally, copy the WSDL file to a library and, in the module, set a dependency on the library so that you can use the library's resources. If you tried to drag a WSDL file from another type of project, for example a Web project, an error message will prompt you to copy the WSDL to the module or library.
You should avoid modifying module dependencies outside of the dependency editor.
When you add a dependency on a library, Java project, or J2EE project, changes are made to the module's properties. That is, the module's properties are changed, as follows:
Use the dependency editor to manage project dependencies for your mediation modules and libraries instead of editing their properties. There are important Java assumptions set in the properties of mediation modules and libraries, so you should not modify the Java properties, for example, to change their source and output folders.