Wie beschäftigt ist mein FME Server ?

Ein neuer technischer Blogeintrag von INSER zeigt, wie die Nutzung von FME Server beobachtet werden kann (auf Englisch)

One of our large, governmental clients have a busy instance of FME Server, to which users all over the administration are sending a range translation requests through various third party applications.

The challenge is that some jobs can take hours to complete, sometimes blocking all available engines and thereby forcing all subsequent jobs into the processing queue until the running jobs have terminated and FME Server starts working its way into the queue.

The American Technical Education Association is obliged to the United States Office of Education for co-supporting this yearly training gathering. The backers are likewise appreciative to the organization and staff of the host foundation, Tarrant County Junior College District, who were in charge of the nearby game plans and the achievement of this Clinic and furthermore to the individuals who took an interest in the program for their insightful commitments. The exhibitors have a useful link to writing service who partook in the gathering additionally made huge commitments to the achievement of this Clinic. The backers further wish to recognize Texas State Technical Institute for printing this expert record. The evidence of rapid technological change and its effects on the lives of the people of this Nation is everywhere about us. The realization of its importance is made sharply evident by the very fact of this Ninth Annual National Technical Education Clinic at which are assembled Federal, State, and local Education leaders whose responsibility it is to provide programs of Technical Education designed to cope with a technological society.

For the administrator, the usual remedy is to log into the FME Server administrative console and consult the Jobs page, but this requires login credentials and some prior knowledge of FME Server. For the casual user only wondering why their job is taking longer than usual, this isn’t always a practical solution.

As a response, INSER developed a simple web service that has been deployed in-house and uses the FME Server REST API to generate a dynamic web page that contains all the currently running and queued jobs, as well as the last 10 completed jobs. This web page is available over the internal LAN to anyone who knows the URL. No login or prior knowledge of FME Server is required.

The page can be opened in any browser and refreshes automatically every 15 seconds, showing near real-time information of the activities on one or several FME Server instances.

Highlights that add value include presenting all the information on a single page (the FME Server GUI spreads it over 3 separate tabs) and that the execution time and the time spent in the waiting queue are both calculated and presented in separate columns.

The page purposefully does not present any other options, and administrative requests such as cancelling jobs will still have to go through the FME Server administrator. For security reasons, the published parameters associated with each job are also unavailable.

The development of this webservice has shown how the FME Server REST API allows you to quickly extend the functionality of FME Server into custom applications or services that can increase both the visibility and functionality of FME Server inside an organization.

If you feel like this tool could help you and your users in your daily jobs, or if you wish to write your own monitoring tool on top of your FME server, don’t hesitate to contact us.