PFI as a migration tool and interface?

PFI is a solution for interfaces, and can be used for a conversion from non-Lawson. But is absolutely not the way to go, unless you're reimplementing with different structures and want to mass-convert the data (and even then I'd question PFI as the right tool)

. Lawson provides upgrade programs for 8 to 9 apps. Their is no need for PFI in this scenario (maybe you should hire me to do the upgrade...)

Thanks for the information.  Hopefully in time I will have some input into decisions of who gets hired.  For now all I can do is pass on the information and where I got it. 

Could you elaborate a little on the use of PFI as an interface between systems?  I know that it is capable of interfacing between systems but is it the catch-all, best solution any time we want to interface?  Does Lawson not provide easier/better tools for interfacing?

Here's an example of how PFI is very useful in our daily routines:

1. I created an ScanFileClient (daemon) that checks for the presence of a file (with extension of.ctx) in $LAWDIR/IN
directory. This daemon called INSUR2LAWSON will sleep and wakes up every 5 minutes to check if a file
with an extension of .ctx is present in the given directory. This file is coming from our insurer.
2. If a file is present, the daemon will trigger a new workunit and calls a processflow which I name
INSURE2LAWSON which is same name as the daemon.
3. within the flow I will use a Datastage node to validate the file sent by the insurer and create a new import file
that I can upload to the benefit application. If there errors then I will sent an email to the insurer.
If no error then the flow proceeds to submitting a Lawson job that upload the import file.
4. Send an email to Lawson users that the file and job was successfully uploaded.

note: I always make sure that saving files to archives as my first step within the flow.

Very interesting.  Thank you. 

Do you know if process flow has limitation on how big the file can be?? Because some of the files that we need to process is pretty big. I tried to using process flow to query the employee table and it stop around 6000 records.

Is the data stage node same as the TX Adpater?? Where can I find information on installing the TX adapter?? Does it come with PFI??

Thanks!!

Becky

Posted By Becky on 02/06/2009 04:05 PM
Do you know if process flow has limitation on how big the file can be?? Because some of the files that we need to process is pretty big. I tried to using process flow to query the employee table and it stop around 6000 records.

What are you using for the query -- Data/DME ?
There should be no limitation on table size, however depending on what you're doing, you might be chewing up memory, as each call creates JavaScript variables.  Also, two other things that can negatively affect it are 1) turning on the 'Debug' checkbox, and 2) running on the desktop vs. running on the server.

Posted By Becky on 02/06/2009 04:05 PM
Is the data stage node same as the TX Adapter??

Yes, it used to be called Mercator as well

Posted By Becky on 02/06/2009 04:05 PM
Where can I find information on installing the TX adapter??

The install guide is on the Lawson support site product download page for ProcessFlow Integrator

Posted By Becky on 02/06/2009 04:05 PM
Does it come with PFI??

Yes

Elizb;
1. you SHOULD hire John to do your upgrade for you. We utilized John's knowledge, made our upgrade process MUCH faster!

2. the Partners telling your boss to use PFI to do program/data upgrades have no idea what they are talking about. They are trying to sell you additional services. Lawson, provide upgrade programs that worked just fine for us. Would you buy tires when you buy a new car, when the new car comes with new tires? No

3. PFI, is GREAT for system integration. We have 20 interfaces to various system into / out of Lawson that utilizes PFI. Some examples
a. we integrate with an Oracle based on-line system for nightly batch load.This is file based.
b. we export data from Lawson, including PGP encryption.
c. we use process flow to facilitate loading of image files associated w/ our automated Procure to Pay process.

The other benefit of using PFI is its "relatively low" learning curve and its "outside" of Core Lawson. i.e. you don't have to write custom COBOL to do data import. COBOL (and shell scripting for that matter) is great, but, its a more specialized skill.

There is ONE caviet with PFI. Process Flow itself, is not scaleable. i.e. you can't split it out like WebSphere.

Use PFI for Interfaces, it will leave you with more time for fun.

MTFF-

I would hire John in a heart-beat if I had that kind of power. We employ 8000 people with layers and layers of administration. I have been here 8 months. No one listens to me... yet. Next time.

So what nodes are you using to do this integration? TX Activity and Lawson Adapter?

I am going to the Process Flow Integrator class (PF part II) at CUE. I am hoping that will help.

One of our process decrypts PGP encrypted files, then does an importdb, then, call a Lawson job. We also get a success/failure email notification. This is a scheduled PF (Scheduled via the Lawson job scheduler, you can also use PF's scheduler)

The nodes used are
File Access (verify files are present in a designate file folder)
decrypt and run importdb(SysCommand),
use WebRun to call the Lawson Job.

We also have more complex integration that utilizes IBM's MQ Series, that woks well.

There are a few good articles on Process Flow in the Lawson Guru Letter archives that may help you.

if you are in the MidAtlanatic region, there is a User Group Meeting on 3/20. If you need info for the User Group, let me know!

We upgraded our ProcessFlow Professional to PFI right after migrating to LSF9. We had never implemented PF Pro in version 8.

I can’t tell you how easy this product is to use. We have already rolled out an ‘e-Pedigree’ process developed with PFI and Design Studio. Every time a PO is received, a Work Order is released or a BL122 is run data is automatically extracted, formatted, and FTP’d to an outsourced e-Pedigree solution provider. We even use it to base64 encode PDF files of scanned documents and include them as a field in the text file transmissions. The provider decodes the file back to PDF.

We have just barely scratched the surface of PFI’s capability…

I am in the SouthWest User group. WEST!?!? Nowhere is Mississippi classified as West except with Lawson.

I believe I have read everything on PF on the Lawson Guru site. A great site!! Those PF articles you mentioned are on my list to go back and re-read.

I have been working on a termination flow for about 5 months and it keeps getting more and more encompassing the more I get done. It continues to be a great learning experience. I plan to try my hand at "talking" to other systems over the next few weeks.

Thank you both for the input. Look for future questions as this adventure continues.