Procedural configuration of connection metadata

Hm. Might be some support training indicated, then; I was pretty specific in the ticket; I even asked if policies were the appropriate feature to do this automatic configuration.

I don't have enough experience with the Designer to make concrete examples; we're still trying to get the thing to run. I can speak with some precision about the idea I want to accomplish.

We have a taxonomy of connections; to databases, external apps (salesforce et. al.) authentication sources and what-not.

My expectation is that a new integration server can be deployed, with reference to some list of configuration objects, and not require that the deploying person (or continuous integration process!) click on web pages to make it happen. They would need to make configuration statements in the deploy descriptor analogous to: 'here's the list of datasources I need to access', and expect that they be available.

I interpret your response as "Yeah, you can do this, it'll be reflected in a list of policies applied to the deploying barfile(s)".

So once we get ACE actually functioning, I'll seek for this pattern. Thanks for your prompt response!

Idea / RFE Review. Thank you Allen for taking the time to raise this enhancement request. The case which you reference discussed the name of the account configuration used by the App Connect Designer ... and yet in the description of this idea there is reference to IIBv10 having the capacity to create and maintain connection metadata (it sounded like you may also have been referring to ODBC.ini configuration with your example?) ... so it wasn't clear to us whether your intentions are now relating specifically to Designer flows or are you still using Toolkit message flows?

ACE software absolutely maintains the same abilities of IIB to enable procedural configuration of connection metadata. Configurable services are now policies (defined in policy projects), and can either be deployed in a BAR file or laid on to the server's filesystem as an override ... which works very nicely in container based architectures. On this basis, we don't think ACE has taken anything away from what was in IIB, so we're putting this idea into status "Not under consideration" for now ... but if we've misunderstood and you're actually only seeking enhancement to App Connect Designer, then it is certainly true that more could be done to extend configuration options in that environment to make them more amenable for override. If this is what you're after, to ensure we get the idea routed and considered by the right people, perhaps could we ask you to further clarify the precise part of the configuration metadata which you'd like to change, and also confirm that your deployment here is to Cloud Pak for Integration (as opposed to a native software installation directly on metal) ? Best Regards, Ben