Your last error is a configuration error .... Not getting support as expected is not nice. Try to understand all technical steps to get it up and running and do as much possible to analyze where the issues are. I avoide the word installation because for a project manager this all is the installation. He does not know better, should be helped to understand. Your deployment-registry and software-order and software depot is reflecting what is copied-pasted to machines. For techies that is the installation part. You added JBOSS as 3-party component it belongs to that. There is always some uncertainty on versions fixes dependicies. With a 9.4 you will get the VMware fabric tools included. The next part is the configuration step, Giving port-numbers dns-adresses users passwords as described and requested. This is generating a lot of scripts for all additional steps. Several are interacting to each other. Many are doing updates in the metadatabase using the SAS metadataserver. As soon you can run the metadataserver check that one (analyse those logs) As soon you can run the webserver check that one (analyse those logs) Than proceed with the detailed solutions. It is in this part you have the error message. It is stopped saying a configuration file is not there. It could be caused by malfunction of the SAS metadata server or webcontainer (jboss). Check the logs of those steps. It gives the impression you can proceed and try this step later again when the root cause is solved.
... View more