Setting deployment and runtime properties for outbound processing, WebSphere Adapter for FTP

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 > Configure the adapter for outbound processing
Setting deployment and runtime properties

Specify deployment and runtime properties that the external service wizard uses to connect to the FTP server.

Before you can set the properties in this section, you must have created your adapter module. It must appear in IBM Integration Designer below the adapter project. For more information about creating the adapter project, see Starting the external service wizard.

To set deployment and runtime properties, follow this procedure. For more information about the properties in this topic, see Managed (J2C) connection factory properties.

Procedure

In the Select the Processing Direction window, select Outbound and click Next.
The Specify the Security and Configuration Properties window appears. In the Deploy connector project field, specify whether to include the adapter files in the module. Choose one of the following options:

With module for use by single application
With the adapter files embedded in the module, you can deploy module to any application server. Use an embedded adapter when you have a single module using the adapter or when multiple modules need to run different versions of the adapter. By using an embedded adapter, you can upgrade the adapter in a single module without the risk of destabilizing other modules by changing their adapter version.
On server for use by multiple applications
If you do not include the adapter files in a module, install them as a stand-alone adapter on each application server where you want to run the module. Use a stand-alone adapter when multiple modules can use the same version of the adapter and you want to administer the adapter in a central location. A stand-alone adapter can also reduce the resources required by running a single adapter instance for multiple modules.

Define the following FTP system connection information for your module. See Managed (J2C) connection factory properties.

Host name - Specifies the host name of the FTP server.
Directory - Specifies the output directory on the FTP server. If the value of the Directory field is set to <HOME_DIR>, the adapter performs the outbound operations in the users home directory.
Verify output directory access permission - Specifies if the access permissions for the output directory must be verified before performing the outbound operation.
Protocol - Specifies the protocol used to connect to the FTP server. Following are the protocols that can be specified:

FTP - File Transfer Protocol
FTP over SSL - File Transfer Protocol over Secure Socket Layer
FTP over TLS - File Transfer Protocol over Transport Layer Security
SFTP - Secure shell File Transfer Protocol

Port number - Specifies the port number of the FTP server.

Figure 1. Specify the Security and Configuration Properties window

Click Advanced to specify additional properties, service properties, data format options, properties that control working with a second FTP server, bidi formatting, a staging directory, logging and tracing, secure connection, and sequence file selection. See Managed (J2C) connection factory properties.
Specify the required security credentials in the Service Properties area:

To use a J2C authentication alias, select the Using an existing JAAS alias (recommended) field, and specify the name of the alias in the J2C Authentication Data Entry field.
You can specify an existing authentication alias or create one at any time before deploying the module. The name is case-sensitive and includes the node name.
To use managed connection properties, select the Using security properties from managed connection factory field, and type the values in the User name and Password fields.
User name - Specifies the name of the user who has privileges to connect to the FTP server and perform FTP operations. See User name property (userName).
Password - Specifies the password of the user who has privileges to connect to the FTP server and perform FTP operations. See Password property (password)
To administer the user name and password from other mechanism, select Other.

If you have multiple instances of the adapter, expand Logging and tracing and set Adapter ID to a value that is unique for this instance. For more information about this property, see Adapter ID (AdapterID).
Optional: In the Service properties section of the window, specify a Java™ Authentication and Authorization Services (JAAS) alias for the adapter to use at run time. The specified alias is the authentication alias that you set up on the FTP server. The name is case-sensitive. For information about authentication alias, see Create an authentication alias.
In the Data format options field, select one of the following:

Use default data binding 'FTPFileBaseDataBinding' for all operations
A non-configured data binding for all the operations used in the service.
Use a data binding configuration for all operations
A configured data binding for all the operations used in the service.
Specify a data binding for each operation
No default binding is specified. You can select a specific data binding for each operation used in the service.

Select the Change the logging properties for the wizard check box if you want to specify the log file output location or define the level of logging for this module. For information about logging levels, see Configure logging and tracing.

Results
The external service wizard now has the information to connect to the FTP server.

What to do next
If you have selected the Data format options as Use default data binding 'FTPFileBaseDataBinding' for all operations or Specify a data binding for each operation, click Next to continue to work in the wizard to select a data type for the module and to name the operation associated with the data type.
If you have selected the Data format options as Use a data binding configuration for all operations, proceed to Configure data binding and data handler.

Configure the module for outbound processing

Next topic: Selecting a data type and operation name

Related concepts:

User authentication