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 a module.

Before you begin

To generate business objects and artifacts for your adapter project, you must have already selected business objects to add to the adapter project.

About this task

To generate business objects and artifacts for your adapter project, you must first create a new business integration module. Business integration modules contain all of the business processes that you will need for your business integration project. You will later deploy this module on the server.

To generate artifacts with the enterprise service discovery wizard, use the following procedure.

How to perform this task

  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 the module name 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 the default setting, Use discovered connection properties to set properties at this time. If you want to use the WebSphere Process Server or WebSphere Enterprise Service Bus administrative console to configure the adapter and you do not want the import or export to contain the resource adapter's runtime properties, select Use connection properties specified on server.
    Note: The adapter only supports the Use discovered connection properties option.
  3. Optional: 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 of the directory the adapter will use to write output files during outbound processing. 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 of the directory used by the adapter during create, append, and overwrite operations to first write output files to during outbound processing. After the file is written to the staging directory, the file is renamed and copied to the output directory.
      Note: 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.
      Figure 1. Generate Artifacts window
      Specify the properties for the artifacts that will be generated in your workspace in the Generate Artifacts window.
  4. Type the value for each of the resource adapter properties. Required fields are marked with an asterisk (*).
    1. In the Adapter ID field, type the identification of the adapter deployment instance.
      Important: If you are using more than one instance of an adapter, the value of this property must be unique.
    2. In the Log file size field, type 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 the full path of the log file.
    4. In the Log files field, type 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 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 the full path of the trace file.
    7. In the Trace files field, enter 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 no value is specified it will be set to 1.
      Figure 2. Lower section of the Generate Artifacts window
      Specify the properties for the artifacts that will be generated in your workspace in the Generate Artifacts window.
  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.

What to do next

Use the enterprise service discovery wizard to configure the adapter for inbound processing.
Related concepts
Required folders
Introduction
Related reference
Adapter configuration properties

Terms of use |


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