Comparison between Adapter and Plug-in
This section is useful for users that have previously used the TIBCO ActiveMatrix® Adapter for Files for Unix/Win to help understand differences in the plug-in where supported features have overlap with adapter.
| Feature | TIBCO ActiveMatrix® Adapter for Files for Unix/Win | TIBCO ActiveMatrix BusinessWorks™ Plug-in for Files for Unix and Windows |
|---|---|---|
| Services Provided |
Publication service and Subscription service |
The plug-in is a replacement of the File Adapter and AE Palette available in TIBCO ActiveMatrix BusinessWorks™. The file parser activity is equivalent to File Adapters Publication service with an Adapter Subscriber activity. The file serializer activity is equivalent to File Adapters Subscription Service with Publish to Adapter activity. |
| Lifecycle for Reading File | Publication Adapter Service supports both Once-Only and Repeating | File Parser Activity only supports Repeating. |
| Support for sFTP transfer | Supported | Not Supported. If sFTP is required by using BW6, then use ActiveMatrix BusinessWorks™ Plug-in for sFTP. |
| Transport Type | JMS and RV | The plug-in is native to TIBCO BusinessWorks and no longer requires messaging. |
| Error Directory in Publication Service |
When the transfer mode is Simple File Transfer, this field is mandatory. When the transfer mode is Record Transfer, this field is not mandatory. When specified, an XML file containing the name of the input file and the error details is created in directory. |
Since the plug-in is native to TIBCO BusinessWorks, the Error Directory is no longer applicable. If the corresponding error scenario occurs in plug-in, the details will be shown in console or log. |
| Add timestamp to filename | Default format is in 12 hr | Default format is in 24hr. |
| Checkpoint Restart | Optional | Default |
| Mbusiness Document | Supported | Not Supported |
| Message Format | The File Adapter is developed using Adapter SDK libraries and outputs the message using a Schema | The plug-in is native to TIBCO BusinessWorks and outputs the message as XML based on a XSD. |
| Input Buffer Max Size | Configurable | Default to 32KB |
| Support for Load Balancing | Configurable | It is supported by default when Post Processing is Move to or Delete. |
| TRA Properties | TRA properties are maintained in TIBCO Administrator and-or adfilesagent.tra file | TRA properties are not applicable in plug-in. |
| TRA Property : adfiles.PublishEmptyField | Configurable and default ON | Default is add NULL for empty fields. |
| TRA Property : adfiles.NullNumberFieldAsZero | Configurable and default ON | Default is add 0 for empty fields. |
| TRA Property : adfiles.quotedField | Configurable and default ON | Default is if field is enclosed with double quotes, delimiter is considered as actual character. |
| TRA Property : adfiles.matchFieldCountAndRecordLength | Configurable and default OFF | Default is if Input line maps with schema and a warning message is displayed as extra fields, then the input line has been discarded in Output XML. |
| Base Record | Supported | Not Supported |
| Container Record | Supported | Not Supported |
| Business Document | Supported | Not Supported |
| Position from header | Position from header is configurable for child records such as Begin or End. | No such field is displayed in the Files for Unix and Windows Resource Configuration of the plug-in and the default value is Begin. |
| WIP creation mode - Close file on RV message, JMS message, business document lot end | Supported | Not supported as transport (RV, JMS) is removed in plug-in. |
| WIP creation mode - One message per file | Supported | Not supported in plug-in. Instead plug-in supports WIP creation mode - One Job per file |
| File name selection | Supported | Not supported as SFT transfer mode is not supported in plug-in. |
| Message time out (minutes) field | Supported | Not supported as transport (RV, JMS) is removed in plug-in. |
| Closing Subscriber field | Supported | Not supported as transport (RV, JMS) is removed in plug-in. |
| Promote / Demote child records | Supported | Not Supported. |
|
TRA property : adfiles.toggleChildRecordsOrdering |
Configurable and default is OFF | The Toggle Child Records Ordering field is provided in Advanced tab of the File Serializer activity, under Processing section. |
|
TRA property : adfiles.subscriber.ignoreEmptyRecord |
Configurable and default is ON | Default is OFF. Empty records are written to output file |
| TRA property : adfiles.io.sub.flusheverymsg | Configurable and default is OFF | Default is OFF for WIP creation mode, as Close is ON for Timer and Default is ON for One Job per file. |
| TRA property : adfiles.io.sub.disableWipMoveOnShutdown | Configurable and default is OFF |
Default is ON so that whenever a running process is stopped in between, WIP file will not be moved to output directory. It will remain in working directory. The above behavior will not work if stop appnode command is used in bwadmin utility. It will only work if stop application command is used in bwadmin. |