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
- To create a new business integration module, use the following
procedure.
- In the Generate Artifacts window, next
to the Module name field, click New.
- In the Integration Project window, select
the default setting, Create a module project, and click Next.
- In the New Module window, type the module
name in the Module Name field.
- Under Module Location, select the Use Default check
box.
- Click Finish.
- In the Generate Artifacts window, select the Deploy
connector with module check box.
- 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
- 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 (*).
- From the Delivery type list, select the
delivery type for the endpoint. By default, ORDERED is selected.
- In the Poll period field, type the time
in milliseconds between polls for events. By default, the value
of this property is 2000.
- 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.
- In the Retry interval field, type the
time in milliseconds between connection attempts in case of enterprise information
system connection failure.
- In the Retry limit field, type the number
of times the adapter attempts to establish an inbound connection.
- To stop the adapter when an error is encountered during polling,
select the Stop polling on error check box.
- To disable once-and-only-once delivery, clear the Assured
once delivery check box By default, this property is
selected.
- To filter event files that have a timestamp, select the Filter
future events check box.
- In the Event type filter field, type
the business object types that the adapter should publish.
- 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 (*).
- 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.
- To enable archiving, select the Archiving processed check
box
- If archiving is enabled, then In the Archive directory field,
type the path name where processed event files are archived.
- In the FailedArchiveExt field, type the
file extension used to archive unsuccessful business objects. By
default, the value of this property is fail.
- In the OriginalArchiveExt field, type
the file extension used to archive the original event file. By
default, the value of this property is original.
- In the SuccessArchiveExt, type the file
extension used to archive all successful business objects. By default,
the value of this property is success.
- 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 "*.*".
- To pass an unprocessed event file to the endpoint as a reference,
select the FilePassByReference check box.
- To send the value of the SplitCriteria property to the endpoint
along with the contents of the business object, select the IncludeEndBODelimiter check
box.
- To manually the event persistence database, clear the EPCreateTable check
box. By default, the value of this property is true.
- 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.
- In the EventTableName field, type the
name of the table used by the adapter for event persistence.
- In the DatabaseSchemaName field, type
the schema name of the database used for event persistence.
- In the DatabaseUserName field, type the
user name used by event persistence to obtain the JDBC database connection
from the data source.
- In the DatabasePassword field, type the
password used by event persistence to obtain the JDBC database connection
from the data source.
- In the SortEventFiles field, type a value
that determines the sorting order of polled event files.
- In the SplitCriteria field, a value to
split event files based on either size or a delimiter.
- In the SplittingFunctionClassName field,
type the name of the class used to split files based on either size or a delimiter.
- In the EventContentType field, type the
mime type of the event file.
- In the FileContentEncoding field, type
the encoding used for the content of the event file.
- In the DefaultObjectName field, type
the namespace of the wrapper business graph used during inbound processing.
- In the Generate Artifacts window, type the
value for each of the resource adapter properties. Required fields are marked
with an asterisk (*).
- 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.
- 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.
- In the Log file name field, type the
full path of the log file.
- 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.
- 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.
- In the Trace file name field, type the
full path of the trace file.
- 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.
- 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.