thanks for reply, how about if we have 2 different databases to hold the schemas of each pega instance? can these 2 pega instances share same jboss instance? my guess is that, maybe pega code has 'hard-coded" JNDI reference names, that might be the root cause of conflict in this setup ?
The deployment contents will be stored in %JBOSS_HOME%\standalone\data\content directory.
In the deploying process of the second instance, new contents will be also be created in %JBOSS_HOME%\standalone\data\content directory. However, JBoss now believes the content in the first deployment are redundant and will remove these files. At this point you will only be able to startup the second instance, but not the first one.
To overcome this, I copied the content of %JBOSS_HOME%\standalone\data\content before deploying the 2nd instance and then merge it back after the deployment process of the 2nd instance.