In our current setup, we install the Deployer as a Java application on our OTAP servers. The T and P environments both have Staging and Live targets. Our infrastructure is setup in such a way that the filesystem storage locations in Staging differ from the filesystem storage locations in Live. This could be solved by using separate Deployers for Staging and Live, but we would prefer to be able to deploy the same application package for the Deployer to both Staging and Live instead.
In light of the above, I was wondering if it is possible to influence the (used location of the) cd_storage_conf.xml configuration as used by the Broker? I could envision a solution like on of the following:
- Package 2 versions of cd_storage_conf.xml, for Staging and Live. By using our own Java code in the Storage config retrieval process, we could then decide – based on some environment/JNDI setting – which cd_storage_conf.xml to use.
- Or package 1 version of the cd_storage_conf.xml, but inside it use some placeholder for (part of) the filesystem locations. By using our own Java code in the Storage config retrieval process, we could then resolve – based on some environment/JNDI setting – the value of the placeholder.
Or maybe some other solution might be possible?