Any issues with installing Python to run 3d party interface exportsimports along side Infor Lawson s

vlaniauskas

In order to accommodate 3d party interface exportsimports to Infor Lawson, we are contemplating installing Python so that
we can run Python scripts along side Infor Lawson software. Are there any problems or issues or complications in doing so? I cannot find any mention in Knowledge Base or Infor Community forums. Thanks in advance for your advice! 

unknown

Should be no problem. We do not have Python, but we have a number of interfaces installed that are 'outside' of Lawson. That is, Lawson has no knowledge of their existence. Scripts are written with careful attention to them being unaware of Lawson and its internals. Things like folder locations have to explicitly written out the 'long' way. Also, careful coordination between outside scripts/interfaces and Lawson processing is necessary. We either use staggered timing, with testing to assure that an incoming interface is done before the Lawson scheduled job starts, or, we use manually-triggered operation for both the 'outside' interface and the 'internal' Lawson job.



it's an old consultant's trick to create interface jobs that are technically 'outside' of Lawson, but are run by a COBOL program. This 'internal - external' mashup is a consultant's dream, a job setup that's so complicated that it creates a revenue stream for maintenance. I am assuming you wouldn't want that kind of abomination. Just keep it clean and simple, and all will be fine.