Skip to main content
Solved

logging FME Server job status at begin and end to Oracle Non spatial table

annette2
Contributor
Forum|alt.badge.img+10

I have written an FME workbench hosted on FME Server that will be called by the Informatica application.

The Informatica team want a logging mechanism via an Oracle non spatial table.

 

The columns in the table are

workbench_id (published parameter filled by Informatica job call)

workbench_name (fixed value - e.g Clipper_Perf_POC)

run status (1 = run started, 2 = run success, 3 = run failed)

 

They want to insert a log message at the start and a second log message at the end of a workbench..

 

What is the most elegant way to do this - start up and shutdown scripts, fmeserverjobsubmitter (aka workspace runner)? Is it worth adding the fme server job id to the table...the workbench_id parameter filled by Informatica is not very informative for further investigation within FME Server.

Any tips would be appreciated.

 

Best answer by takashi

Hi @annette2, I would adopt an approach using the FMEServerJobSubmitter.

To the first workspace, add a process to insert the Job ID (and "workbench_id" if necessary) and the "run started" status to the logging table at first.

Then, create another workspace which contains a FMEServerJobSubmitter (Wait for Job Complete: Yes) to run the first workspace. To the second workspace, add a process to update the status of the record to "run success" or "run failed" according to result of the translation run by the FMEServerJobSubmitter.

I'm not sure whether it's elegant but I think the implementation is easier and also the maintainability is better than using Startup/Shutdown Python Script, in most cases.

View original
Did this help you find an answer to your question?

2 replies

takashi
Evangelist
  • takashiEvangelist
  • Best Answer
  • February 6, 2018

Hi @annette2, I would adopt an approach using the FMEServerJobSubmitter.

To the first workspace, add a process to insert the Job ID (and "workbench_id" if necessary) and the "run started" status to the logging table at first.

Then, create another workspace which contains a FMEServerJobSubmitter (Wait for Job Complete: Yes) to run the first workspace. To the second workspace, add a process to update the status of the record to "run success" or "run failed" according to result of the translation run by the FMEServerJobSubmitter.

I'm not sure whether it's elegant but I think the implementation is easier and also the maintainability is better than using Startup/Shutdown Python Script, in most cases.

annette2
Contributor
Forum|alt.badge.img+10
  • annette2Contributor
  • Author
  • Contributor
  • February 12, 2018
takashi wrote:

Hi @annette2, I would adopt an approach using the FMEServerJobSubmitter.

To the first workspace, add a process to insert the Job ID (and "workbench_id" if necessary) and the "run started" status to the logging table at first.

Then, create another workspace which contains a FMEServerJobSubmitter (Wait for Job Complete: Yes) to run the first workspace. To the second workspace, add a process to update the status of the record to "run success" or "run failed" according to result of the translation run by the FMEServerJobSubmitter.

I'm not sure whether it's elegant but I think the implementation is easier and also the maintainability is better than using Startup/Shutdown Python Script, in most cases.

Many thanks Takashi. I am going to try this out this week

 

 

Reply


Helpful Members This Week

Community Stats

31,504
Posts
119,425
Replies
39,122
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.