Generating artifacts

Use the enterprise service discovery wizard to generate artifacts for use with your adapter project. When you generate artifacts, you are adding instructions to the metadata that you extracted from the enterprise information file system. This process also bundles everything together to create an assembled adapter application, also known as an SCA module.

  1. To create a new business integration module, use the following procedure.
    1. In the Generate Artifacts window, next to the Module name field, click New.
    2. In the Integration Project window, select the default setting, Create a module project, and click Next.
    3. In the New Module window, type "FlatFileOutboundModule" in the Module Name field.
    4. Under Module Location, select the Use Default check box.
    5. Click Finish.
  2. In the Generate Artifacts window, select Use discovered connection properties.
    Figure 1. Generate Artifacts window
    This image is described in the surrounding text.
  3. In the Generate Artifacts window, type the values for the managed connection factory properties. These properties are used by the adapter to create outbound connections to the enterprise information system file repository.
    1. In the Output Directory field, type the path C:\flatfiledir\outputdir. This directory must be created on your file system for this value to work. This value tells the adapter where it will write output files during outbound processing.
    2. In the Staging Directory field, type the path C:\flatfiledir\stagingdir. This directory must be created on your file system for this value to work. This value tells the adapter where it will create, append, and overwrite operations during outbound processing.
      Note: This step is not required in an actual implementation, but included in this tutorial for educational purposes.
  4. Specify the following remaining values as follows:
    Figure 2. Lower half of the Generate Artifacts window
    This image is described in the surrounding text.
    1. In the Adapter ID field, retain the default.
    2. In the Log file size field, type 100000. This indicates the size for each log file in kilobytes. If no value is specified, the file will have no maximum size.
    3. In the Log file name field, type c:\logs as the full path of the log file.
    4. In the Log files field, type 10 for the maximum number of log files to use after the log file has reached its maximum size. When a log file reaches its maximum size it will start using another log file. If no value is specified it will be set to 1.
    5. In the Trace file size field, type 100000 for the size for each trace file in kilobytes. If no value is specified, the file will have no maximum size.
    6. In the Trace file name field, type c:\trace as the full path of the trace file.
    7. In the Trace files field, enter 10 for the maximum number of trace files to use after the log file has reached its maximum size. When a trace file reaches its maximum size it will start using another log file. If a value is not specified it will be set to 1.
  5. Click Finish.

Result

The FlatFileOutboundInterface.wsdl, FlatFileOutboundInterface.import artifacts, FlatFileBG, FlatFile, UnstructuredContent, CustomerWrapperBG, CustomerWrapper, and Customer business objects are generated. The application business objects specified by the user are updated with application-specific information for data transformation and saved in the business object location.

Terms of use |


(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)