title: JCAPS deployment to multiple external system environments
body: <p>Hope a few people in here are familiar with JCAPS.
  Coming from pure j2ee world, it is difficult to digest the deployment model that JCPAS offers.
  While creating deployment profile, we need to map the resources (such as jdbc, webservice connector) to external systems. External systems are predefined with the target server ip, port, db name, credentials etc(in case of jdbc). So the problem is an EAR built for test environment can not be deployed to production environment.</p>
  
  <p>In simpler applications we could store database/credentials etc on to property files and hence EAR built for UAT could be deployed to Production with out any change.</p>
  
  <p>Is there a similar strategy available for JCAPS by which EARs built against an environment can be promoted to another seamlessly?</p>