| Exercise 4.2 | Building Updates Notification System |
| Data | Building footprints (Esri Shapefile) |
| Overall Goal | Real-time updates to databases |
| Demonstrates | Running a workspace in response to a notification |
| Start Workspace | None |
| End Workspace | C:\FMEData2018\Workspaces\ServerAuthoring\RealTime-Ex2-Complete.fmw |
As a technical analyst in the GIS department, you have realized the overhead associated with pushing manual updates to your corporate database. Having read up about notifications in FME Server, you think that it should be possible to set up a system that automates this process.
So far you have set up a system for added file notifications to be registered by FME Server. Now you must create a workspace to process these and publish it to FME Server. The workspace must then be triggered by a notification topic.
| Miss Vector says... |
| This exercise continues where Exercise 1 left off. You must have completed Exercise 1 to carry out this exercise. |
1) Create Workspace
Start FME Workbench and begin with an empty workspace. Simply add a Creator and Logger transformer:
This will give us a workspace to run in response to new files; albeit one that doesn’t do much yet. We're just creating this to check that we can get the setup to work.
2) Save and Publish Workspace
Save the workspace and publish it to FME Server. We only need it to be run (not do anything special) so register it only with the Job Submitter service.
3) Create Subscription
Return to the FME Server web interface and navigate to the Notifications page. Click on the Subscriptions tab and click New to create a new Subscription.
Call the subscription "Process Building Updates". Subscribe to the topic ShapeIncomingFile:
Now set the protocol to FME Workspace and select the workspace uploaded in the previous step:
Click OK to create the subscription. This will cause the workspace to run every time an incoming Shape dataset triggers the ShapeIncomingFile topic.
4) Test Subscription
Back in Windows Explorer, zip up the update002.shp/.dbf/.shx/.prj files. Then back in FME Server, test the subscription by uploading the update002.zip file.
NB: Since we set the Directory Watch to watch only for new files, the Shapefile uploaded should be a different one - or at least have a different name - to the first.
This time, instead of monitoring the topic (although it will appear there again), check the Jobs page. You should see that the workspace has been run in response to the new file:
This proves that the workspace has run.
| CONGRATULATIONS |
By completing this exercise you have learned how to:
|