The outbound service outputs a file that has been processed to the file system.
To create the outbound service using the adapter pattern wizard, follow these steps:
The following artifacts are created.
Artifact | Name | Description |
---|---|---|
Import | SeparateCustomerOut | The import lets your service use the WebSphere Adapter for Flat Files to output files. |
Business objects | CreateResponse, UnstructuredContent | CreateResponse, which will be used in creating the output of the application, uses the Customer business object as its input. The UnstructuredContent business object can be used for generic input types. |
Business objects for fault handling | DuplicateRecordFault, MissingDataFault, PrimaryKeyPairType, RecordNotFoundFault, WBIFault | These business objects can be used to handle exceptions. When a business exception is thrown, the adapter throws a fault exception and passes the fault information to the calling component. If you wish to use this information, you will need to create a fault selector configuration file. |
Interface | SeparateCustomerOut | This interface contains the operation that can be invoked. |
Operation | create | This operation creates the files in the output directory. |
For our particular application, we will only be using a one-way inbound request and do not require fault handling. In the following steps, we will remove the faults from the import binding and the interface.