genMapper command-line utility

Use the genMapper command-line utility to generate a component that bridges as Service Component Architecture (SCA) reference to a Java interface.

The genMapper command generates a component that bridges an SCA reference to a Java™ interface creating files that you import into IBM® Integration Designer. After importing to IBM Integration Designer, you wire the Web Services Description reference and the Java interface to the generated component.

The input can contain a Java class, a stateless session bean, or a Java interface.

If the input is a Java class, the class can contain only one interface and the interface cannot extend other interfaces.

Syntax

genMapper
-javaOutput java_output_dir
-scdlOutput sca_output_dir
-name java_class_file

Parameters

-javaOutput java_output_dir: Specifies the name of the directory where the system places the generated Java classes.
-scdlOutput sca_output_dir: Specifies the name of the directory where the system places the generated bridge component.
-name java_class_file: Specifies the fully qualified file name that contains the Java class or interface for which the bridge component is generated.

Examples

This example generates a bridge component for the input interface com.ibm.mj.Customer. The system places the generated implementation class to c:\customer\src and the SCA component to directory c:\customer, which do not exist.

genMapper -javaOutput c:\customer\src -scdlOutput c:\customer -name com.ibm.mj.Customer

After the command completes, listing the directory c:\customer shows the following files:

Customermapper.component
Customermapper.wsdl

Listing the directory c:\customer.src shows the following file:

Customermapper.java

Copy the files from both generated directories to the directory of any module that requires the bridge component. You can then either import that bridge component into IBM Integration Designer and wire the reference and interface to the bridge component or use the serviceDeploy command to create an enterprise archive (EAR) file to deploy to the server.