Import and Export Processors
You can write your own import and export processors to handle the identification selection, validation and cleansing of data between your own application database and the intermediate staging database tables.
Refer to the following for more information:
Develop an import or export processor
Connect your import or export processor to the transaction document processing framework
NB: The need for import and export processors is predicated on your transaction document processing solution using intermediate "staging" database tables as the target for inbound transformation maps and/or the source for outbound transformation maps. This solution insulates your application from the interfaces that the transaction document processing solution opens to the outside world. However, the use of "staging database tables may not be necessary in all cases. If your transformation maps write and/or read directly to or from your application database, then you may have no need to implement import and export processors.
Develop an import or export processor
Your import and export processors must be implemented as LANSA RDMLX components (re-useable parts) that will reside and execute in the same LANSA system and partition as LANSA Composer.
For general considerations about integrating your custom LANSA code with your LANSA Composer solution refer to:
Appendix E. Using LANSA Composer with LANSA Applications
You must use DXXBASIMP as the ancestor of your import processor component and DXXBASEXP as the ancestor of your export processor component.
Before you begin development, you must prepare your development environment. You will need a correctly licensed and configured Visual LANSA development environment at the level defined in Install LANSA Composer.
- Development of your custom import and export processors must be performed in a partition that is enabled for full RDMLX.
- You must import the LANSA Composer development package into the partition in which you will develop your import and export processors. This provides the DXXBASIMP and DXXBASEXP ancestor classes that you will need to compile your processors
The LANSA Composer development package can be found in the folder DEV\Import on your LANSA Composer software DVD.
Connect your import or export processor to the transaction document processing framework
When you have built your import or export processor and deployed it to the LANSA Composer server environment, you must connect it to the transaction document processing framework so that LANSA Composer knows for which type of transactions it should invoke your processor(s).
This is done by specifying the name of the import or export processor in the appropriate data interchange attribute field of the Transformation Map(s) that process the transaction type to which it applies.
For more information, refer to Transformation Map Data Interchange Attributes.