Hello (FME) world,
I’d like to identify all URLs called by all FME workspaces in FME Flow - as we are migrating servers and I need to ensure these are whitelisted.
Is there a ~quick and ~easy way to do this?
Thanks!
+60- Celebrity
- 3704 replies
Using the Text File reader to read all workspaces and then a StringSearcher to use a regular expression that searches for url's seems to be a quick solution but that would also find url's in annotations, so maybe not completely what you're looking for.
+63- Celebrity
- 1632 replies
Using the Text File reader to read all workspaces and then a StringSearcher to use a regular expression that searches for url's seems to be a quick solution but that would also find url's in annotations, so maybe not completely what you're looking for.
It may also have the URLs FME encoded, or double slashed etc, so bare that in mind!
If you’re just working for URLs in HTTPCallers, you could use the owrkspace reader and filter out the parameter in the transformer that contains the URL
+60- Celebrity
- 3704 replies
Using the Text File reader to read all workspaces and then a StringSearcher to use a regular expression that searches for url's seems to be a quick solution but that would also find url's in annotations, so maybe not completely what you're looking for.
It may also have the URLs FME encoded, or double slashed etc, so bare that in mind!
If you’re just working for URLs in HTTPCallers, you could use the owrkspace reader and filter out the parameter in the transformer that contains the URL
Don't forget OpenAPICaller and FeatureReader (for WFS/WMS), but theoretically every file-based reader can use a url for the input dataset.