TWIN Broker components redesign – Solution TWIN20030725
This document will describe the changes in the Broker side components for TWIN and will guide for implementation of new components.
Scope
The TWIN Broker side component structure has been changed to take out the iBaan OpenWorld Gatway component from the scripts and use the COM DLL instead. There is no change in the functional design of the interface
How the new components work
- In the new design the there will be no change in the invocation of the TWIN process. As earlier the file/files will be put into the D:DataVNSFinanceTWINInputFiles folder.
- The User will start the process, using Launch, or a periodic process if running will pick up these files at subsequent run.
- The message handler will poll the new files and will create a temporary TWIN file with the data in the TempFiles folder. This is a new folder and will have to be created in location D:DataVNSFinanceTWINInputFilesTempFiles.
- The file being processed will be moved to OldFiles folder, on error, the file will be stored wo ErrorFiles folder with name TWIN appended by timestamp.
- The message handler will call the file processing Broker script. Within the script the file contents will be parsed and business objects for TWIN will be created using the COM DLL – B50cVNStfgldTransactionsTwin.dll. Broker will give a call to BOI on BaanERP and will wait for response.
- All the errors (infrastructure / parsing / Functional) will be notified via e-mail and will be logged to database, Broker event viewer. Broker event viewer must be configured to view the logged events. Events will be logged as Transactions
- User will have to make correction to ASCII files if needed and reprocess the file. In case of timeout errors the default timeout will be increased automatically and will be saved to configuration file. A new tag (<TimeOut>) has been added to configuration file for this.
- The event logs can be viewed through Launch. Successful events will be notified via e-mail with batch numbers created and also will be logged.
Installation Procedure
Pre-condition
Following products should be installed
1. iBaan OpenWorld Adapter installed and configured on both client and Baan ERP server side
2. The error handler dll for iBaan OpenWorld BaanErrorHandler.dll must be registered and error handling classes should be in classpath
3. iBaan OpenWorld Broker version 3.0.1 must be installed
4. MDAC 2.5 or above installed
5. The configuration file for integrationVNSFinanceConfig.XML VNSFinanceParameterFile.xml, for integration should be present in the folder for the Broker for Sweden instance
6. The new timeout tag should be added to all the interfaces as shown below. Appropriate minimum timeout should be set for the interface
7. The COM DLL – B50cVNStfgldTransactionsTwin.dll should be installed and registered on the Broker server machine
<Interface>
<InterfaceName>TWIN</InterfaceName>
<Company>950</Company>
<BusComponentName>cn=VNS-FWR-Henri, o=baan.com</BusComponentName>
<TimeOut>600000</TimeOut>
<Email>ssonone@baan.com</Email>
<ErrorFile>c:\Twin.txt</ErrorFile>
</Interface>
Post Condition
After installation, of ofa the following script should be run to get the configuration and parameter data.
“VNSFinanceGlobalObjectsConfigurationParametersgetFinanceConfigParams”,
“VNSFinanceGlobalObjectsParameterFilegetFinanceParameters”
This has to be done from the Broker Designer for now. This is required for the scripts to read the configuration data.
New/Modified Components
Sr. No. |
Component |
1. |
“VNSFinanceCommonModelgvEnableLogging” |
2. |
“VNSFinanceCommonModelKernel32” |
3. |
“VNSFinanceCommonModelrowLogEventToDB” |
4. |
“VNSFinanceGlobalObjectsConfigurationParametersConfigurationParameters” |
5. |
“VNSFinanceGlobalObjectsConfigurationParametersgetFinanceConfigParams” |
6. |
“VNSFinanceGlobalObjectsConfigurationParametersgvFinanceConfig” |
7. |
“VNSFinanceGlobalObjectsConfigurationParametersInterface” |
8. |
“VNSFinanceGlobalObjectsConfigurationParametersObject” |
9. |
“VNSFinanceGlobalObjectsConfigurationParameterssetConfigParams” |
10. |
“VNSFinanceGlobalObjectsConfigurationParameterst_Interface” |
11. |
“VNSFinanceGlobalObjectsParameterFilegetFinanceParameters” |
12. |
“VNSFinanceGlobalObjectsParameterFilegvFinanceParameters” |
13. |
“VNSFinanceGlobalObjectsParameterFileInterface” |
14. |
“VNSFinanceGlobalObjectsParameterFileParameterFile” |
15. |
“VNSFinanceGlobalObjectsParameterFileInterfaces” |
16. |
“VNSFinanceGlobalObjectsParameterFilet_Interface” |
17. |
“VNSFinanceTransferObjectsSwedenTwinToBaanCreateForTwinfileObj” |
18. |
“VNSFinanceTransferObjectsSwedenTwinToBaanCreateForTwinmsgHdlTwin” |
19. |
“VNSFinanceTransferObjectsSwedenTwinToBaanCreateForTwinrowTwin” |
20. |
“VNSFinanceTransferObjectsSwedenTwinToBaanCreateForTwintabTwin” |
21. |
“VNSFinanceTransferObjectsSwedenTwinToBaanCreateForTwinscrProcessTwinTrans” |
22. |
VNSFinanceConfig.xml |
23. |
B50cVNStfgldTransactionsTwin.dll |
Change for user
There is no change in the operation of the interface from users perspective. For Launch, the same interface can be used. But for Launch event viewer, user will not be able to see the error in XML document; instead the error will be shown as plain text.