HATS Connection profiles need ability to use environment properties

A common issue for HATS is that connection properties need to be tweaked or customized to the particular environment that they are deployed to. This might be because the pooling limits differentiate in an environment, the user id's differentiate in an environment, or screen settling or other profile details just need to be different.

In the past we have utilized deployment methods that alter the HATS connection profiles or the default connection for the project at deployment time (or build time, which means a different "executable" is deployed to a particular environment")

Those methods, while still viable, are not really desirable due to testing and deployment process issues that arise from these methods.

Clients will have different server instances... Dev, QA, UAT, PROD for instance. Each of these environments is a different z/OS Host system with a different appliction server for each. Each requires different user id's to facilitate connection pooling. Each requires different connection pool min/max connections. Each may require some other different parameters for the connection profile.

What would be ideal is if we could do this via application server environment properties and use those in the connection profile. i.e. have a the maxconnections property with a value of $maxConnectionsInPool$ that is derived from the server environment properties. HATS does not support this. supporting the use of Liberty server environment variables in it's connection profiles.