IBM Support

Making the business object name optional for FixedWidth DataBindings in inbound and outbound scenarios of the Adapter for Flat Files

Troubleshooting


Problem

The inclusion of the business object name followed by business data in the file should be made optional so that you can include it when it suits your business needs. Note that: * When using data transformation for FixedWidth DataBindings in an outbound scenario, the output file that is created always includes the business object name along with business data. * When using data transformation for FixedWidth DataBindings in an inbound scenario, the input file being polled is expected to contain the business object name followed by business data.

Resolving The Problem

The attached document (technote.doc) explains how to use sample data binding to make the business object name optional in the file. The zip file (sampleDataBindings.zip) contains modified FixedWidth data bindings source files. These files are taken from samples that come with the full WebSphere Process Server installation in the following path:


<WPS Installed Location>/Samples/CustomEISDataBinding/src.

SampleDataBindings.ziptechnote.doc

[{"Product":{"code":"SSMKUK","label":"WebSphere Adapters Family"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Adapter for FlatFiles","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"6.0.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
15 June 2018

UID

swg21256263

Page Feedback