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 connector project, you must have already selected business objects to add to the adapter project. For more information on the values needed to complete the wizard fields, see the Reference section of this guide.

About this task

To generate business objects and artifacts for your connector 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 Deploy connector with module check box.
  3. Select the default setting, Use discovered connection properties. If you want to use the WebSphere 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.
    Figure 1. Generate Artifacts window
    This image is described in the surrounding text.
  4. In the Generate Artifacts window, type the value for each of the required activation specification properties. Activation specification properties hold the inbound event processing configuration information for a message endpoint. Required fields are marked with an asterisk (*).
    1. From the Delivery type list, select the delivery type for the endpoint. By default, ORDERED is selected.
    2. In the Poll period field, type the time in milliseconds between polls for events. By default, the value of this property is 2000.
    3. In the Poll quantity field, type the maximum number of events to be collected during each poll. By default, the value of this property is 10.
    4. In the Retry interval field, type the time in milliseconds between connection attempts in case of enterprise information system connection failure.
    5. In the Retry limit field, type the number of times the adapter attempts to establish an inbound connection.
    6. To stop the adapter when an error is encountered during polling, select the Stop polling on error check box.
    7. To disable once-and-only-once delivery, clear the Assured once delivery check box By default, this property is selected.
    8. To filter event files that have a timestamp, select the Filter future events check box.
    9. In the Event type filter field, type the business object types that the adapter should publish.
  5. In the Generate Artifacts window, type a value for each of the required Flat Files properties. These are activation specification properties that are specific to the adapter. Required fields are marked with an asterisk (*).
    1. In the EventDirectory field, type the repository path name where the event files are stored. The event directory must be created on your local directory or the wizard will not be able to find inbound events.
    2. To enable archiving, select the Archiving processed check box
    3. If archiving is enabled, then In the Archive directory field, type the path name where processed event files are archived.
    4. In the FailedArchiveExt field, type the file extension used to archive unsuccessful business objects. By default, the value of this property is fail.
    5. In the OriginalArchiveExt field, type the file extension used to archive the original event file. By default, the value of this property is original.
    6. In the SuccessArchiveExt, type the file extension used to archive all successful business objects. By default, the value of this property is success.
    7. In the EventFileMask field, type the value of the file mask used while the adapter polls the event directory. By default, the value of this property is "*.*".
    8. To pass an unprocessed event file to the endpoint as a reference, select the FilePassByReference check box.
    9. To send the value of the SplitCriteria property to the endpoint along with the contents of the business object, select the IncludeEndBODelimiter check box.
    10. To manually the event persistence database, clear the EPCreateTable check box. By default, the value of this property is true.
    11. In the DataSourceJNDIName field, type the JNDI name of the data source created on WebSphere Process Server. This property is used by event persistence to obtain the JDBC database connection.
    12. In the EventTableName field, type the name of the table used by the adapter for event persistence.
    13. In the DatabaseSchemaName field, type the schema name of the database used for event persistence.
    14. In the DatabaseUserName field, type the user name used by event persistence to obtain the JDBC database connection from the data source.
    15. In the DatabasePassword field, type the password used by event persistence to obtain the JDBC database connection from the data source.
    16. In the SortEventFiles field, type a value that determines the sorting order of polled event files.
    17. In the SplitCriteria field, a value to split event files based on either size or a delimiter.
    18. In the SplittingFunctionClassName field, type the name of the class used to split files based on either size or a delimiter.
    19. In the EventContentType field, type the mime type of the event file.
    20. In the FileContentEncoding field, type the encoding used for the content of the event file.
    21. In the DefaultObjectName field, type the namespace of the wrapper business graph used during inbound processing.
  6. In the Generate Artifacts window, 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.
  7. Click Finish.

Result

The FlatFileInboundInterface.wsdl and FlatFileInboundInterface.export artifacts, and the 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 WebSphere Integration Developer assembly editor to generate reference bindings.
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)