Client Side Component Installation
This part of document will explain installation procedure for client side components for Vin & Sprit Fidaware, ESCON, Finance, Produktguiden and EDIMAN integrations. Assuming that the current client side environment at V&S remains the same, the details regarding system are not explained.
Note – Naming conventions
Naming convention followed for Broker ofas is as follows
For new deliveries, upgrades
VNS<Interface name OR location>_Date<yyyymmdd>_<port>.ofa
For cases solved
VNS<case number>_Date<yyyymmdd>_<port>.ofa
<port> indicates on which Broker port the ofa should be imported.
This convention will be followed for all the deliveries now on.
Delivery Contents
1. COM DLLs
2. Ofa – for changed Broker side components
3. Sample configuration files for reference
4. SQL Scripts for CAPS tables, GUID table, update trigger for data sent date
1. WMS (FIDAWARE, ESCON)
The delivery contains the client side components tested for SP13 upgrade of BaanERP 5.0c and the components redesigned for recovery process.
Installation Procedure
1. Copy the COM dlls from the delivery into a folder on Broker server machine (Suggestion, create a VNSCOMDLLs folder to copy the COM Dlls). List of COM DLLs is as follows
a. B50cVNSwheszPlanningDataForFW.dll
b. B50cVNSwhinhInboundOrders.dll
c. B50cVNSwhinhListOutboundOrders.dll
d. B50cVNSwhinhOutboundOrdersforESCON.dll
e. B50cVNSwhinhReceipts.dll
f. B50cVNSwhinhUpdateOutboundAdvice.dll
g. B50cVNSwhwmdItems.dll
2. Un-register the old COM DLLs (delivered for UpdateOutboundAdvice)
3. Register the new COM dlls
4. Restart the Broker server
5. Import ofa VNSWMS_20031010_7250.ofa on port 7250
6. Import ofa VNSWMS_20031010_7251.ofa on port 7251
7. Run the SQL scripts from folder SQLScripts on VNS_DATABASE, there are two scripts delivered –
i. CAPSDB.sql – for creating CAPS tables on the SQL server. The CAPS interface will use the MS SQL server as intermediate database for integration
ii. trUpdateData_received.sql – trigger for changing the data when data sent from Fidaware to Baan is changed. This is provided as a workaround as date updated from Broker was not correct.
iii. Upload_GUID_table.sql – Upload_GUID_table is modified to add one more field for CAPS id, the old table will be dropped and new one will be created with this script
8. Check the configuration files against the files provided in the sample configuration files in the delivery. Points to be noted
a. DSN for CAPS is pointing to MS SQL instead of Oracle
b. TimeOut tags are present for all the interfaces as in the sample configuration files – initial value for timeout is set to 60000ms (10min), on timeout this will be updated automatically by Broker to maximum (180000) 30 minutes.
9. Periodic processes for upload data for all streams and download data for all streams are updated with appropriate calls and are renamed to ppUploadAllStreamsNew, ppDownloadAllStreamsNew. Instead of old periodic processes these new ones should be used (can also be renamed to same name as earlier)
10. The tasks called from Launch application are also updated, Launch can be used with the new components
Note – new version of Launch will be delivered soon but the present version is also
With this installation procedure gets over