Variable usage for dynamic configuration using customer_overrides.properties : YCP75_00014 : Cannot Resolve Variable.

Symptom

In MCSF version 8.5, variables can be used to configure certain properties in the Application Manager. Here is an example:

Instead of hard coding the Provider URL in any service configuration, variable values can be stored in the customer_overrides.properties file.

Provider URL in the service: ${my_Variable_Name}

In the customer_overrides.properties: yfs.my_Variable_Name= jnp://<hostname>:<port>

The ear would need to be rebuilt for the properties to take effect.

Detailed documentation is available in the Extending Transactions customization guide shipped with the product.

Usage of Dynamic configuration variables:


For Asynchronous service: Values for the variables are read from the customer_overrides.properties file present in the <INSTALL_DIR>/properties directory.

For Synchronous service: Values for the variables are read from the customer_overrides.properties file present in the EAR.
If the changes made in the properties file are not reflected in the EAR and the system cannot read the variable values, the following error as mentioned below is seen.

<Errors>
<Error ErrorCode="YCP75_00014" ErrorDescription="Cannot Resolve Variable." ErrorRelatedMoreInfo="" ErrorUniqueExceptionId="10.11.26.5112619934092300000000000020">
<Attribute Name="ErrorCode" Value="YCP75_00014" />
<Attribute Name="ErrorDescription" Value="Cannot Resolve Variable." />
<Attribute Name="Variable" Value="TEST_PROVIDER_URL" />
<Attribute Name="ErrorUniqueExceptionId" Value="10.11.26.5112619934092300000000000020" />