Can I make the URL part of the a Http Client Connect a replacement variable?
I am not sure what do you mean by replacement variable. What i understand is whether we can replace the URL during execution. Yes, you can by using extensible variables. You need to check the available extensions during your build.
Not during execution. But using a Set Properties object. I would like to set the URL for the HTTP Client Connector from a value of a previous HTTP Call.
No, you cannot use replacement variables in the URL part (host name). You can only use replacement variables in the operation of a connector.
That's a huge limitation!
Boomi's license model is based on connectors. So if would Boomi allow to use dynamic URL's, you could use 1 http client connector for multiple systems. So that's the reason
We just started with Boomi so forgive me to bring up this older thread.
We make a distinction between dev, test, acceptance and production where we would like to use the same process for all these environments and use a set of url's, usernames, client secrets etc. per environment. If the http client url is static, should we use a condition in the flow (if dev use client 1, if prod use client 2 ?) or is there a better way to support this ?
The extension and environment functionality are what you need. It will allow you to use separate credentials, variables etc per environment. And you use the same connection for all environments. There's no need to maintain separate processes per environment (dev, test, prod). Keep in mind that you need test connectors for each non-production environment as well. See Environment management for more details.
Thank you Sjaak for the quick reply.
I've skimmed the environment management page you referred to. Dynamic properties for user credentials etc are clear, what is missing is how we can influence the domain the http client will connect to. Our product runs on salesforce and each environment has it's own domain name. (we do have separate test and prod licenses + atoms)
Again thanks for looking into this.
You need to "extend" the connection settings in your process and then deploy the process to test and production. When you open up the environment extension page, you can enter values such as URL's etc for the endpoint you want to connect to. Keep in mind that you only need to extend the FQDN (=fully qualified domain name) of the end point. The resource part, like "/rest/v1/customers/12345" is part of the operation.
Super, that's what i was looking for.
Here are a few screenshots
1. Create HTTP client connection (shared by all environments)
2. Extend connection settings for each process and deploy the process
3. Set extension values for your environment (Atom management)
Retrieving data ...