The title is self explanatory. I need to upload or create dozens of database connections and I found cumbersome to upload only once of them at a time.
How can I do that? May I share a folder with them?
Page 1 / 1
Its not documented in the REST API but there is the /fmerest/v3/namedconnections/connections/ endpoint.
Its pretty straight forward to figure out from using dev tools to capture your request in the UI then using that to programatically formulate requests to FME, for example:
{"type":"Actian Ingres","parameters"::{"name":"HOST","value":"1"},{"name":"PORT","value":"II7"},{"name":"DATASET","value":"1"},{"name":"USER_NAME","value":"1"},{"name":"PASSWORD","value":"1"},{"name":"SPECIFY_JDBC_CONN_GROUP","value":"NO"},{"name":"CONNECTION_STRING","value":"<Unused>"},{"name":"MASK_CONNECTION_STRING","value":"<Unused>"},{"name":"CONNECTION_PROPERTIES","value":"<Unused>"}],"name":"test","category":"DATABASE"}
Or create a simple workspace, with a single reader for every connection (I think I would only attach an Inspector to every reader, just to mae sure it works first), and upload that workspace. Then when uploading, make sure you check all the connections. Luckily that’s easy, just toggle the box before ‘Connections’.
Or create a simple workspace, with a single reader for every connection (I think I would only attach an Inspector to every reader, just to mae sure it works first), and upload that workspace. Then when uploading, make sure you check all the connections. Luckily that’s easy, just toggle the box before ‘Connections’.
This is actually a nice way to be able to test your connections too. A workspace which contains important connections can be run on a schedule. If a connection gets out of date you know about it and can do something about it.
)