IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > FTP > Configure the module for deployment

Road map for configuring the module

Before you use WebSphere Adapter for FTP in a runtime environment, configure the module. Understanding this task at a high level helps you perform the steps that are needed to accomplish the task.

You configure the module for WebSphere Adapter for FTP by using IBM Integration Designer. The following figure illustrates the flow of the configuration task, and the steps that follow the figure describe this task at a high level only. For the details about how to perform each of these steps, see the topics following this road map.

Figure 1. Road map for configuring the module

Configure the module

This task consists of the following steps, which are described at a high level.

These steps assume that you are using user-defined business objects that require data transformation. If using generic business objects, which do not require data transformation, some of the following steps are ignored.

For example, you need not select a data binding and a data handler.

1. Create an authentication alias to access the FTP server. Perform this step using the administrative console on the server.

2. Create a module in IBM Integration Designer.

   You create business objects in the module.

3. Define the business objects that will be used by the project.

4. Use the Adapter patterns wizard to create simple services. See Create a simple service with the adapter pattern wizard.

5. Create a project, which is used to organize the files associated with the adapter using the external service wizard in IBM Integration Designer.
6. Build business services by running the external service wizard from IBM Integration Designer, and then perform the following steps:

   1. Specify the following deployment and runtime properties:
      • Connection properties
      • Security properties
      • Deployment options
      • Function selector - Inbound only

   2. Select a data type and name the operation associated with this data type. For each operation, specify the following:

      • The operation kind.

        For example, Create, Append, and Exists.

      • Specify if the operation is pass through or user defined.

   3. Select the data binding. Each data type has an equivalent data binding used to read the fields in a business object and fill the corresponding fields in a file.

   4. Select the data handler that performs the conversions between a business object and a native format.

   5. Specify interaction specification property values and generate artifacts. The output from running the external service wizard is saved to a business integration module, which contains the business object or objects, and the import or export file.

If you are performing the step 4, do not follow the other steps following it and exit.

If you are not performing the step 4, continue to follow the steps from 5 immediately after the step 3.

Configure the module for deployment

Related tasks:

Configure the module for deployment

Deploying the module for production