[ https://issues.jboss.org/browse/TOOLSDOC-641?page=com.atlassian.jira.plug... ] Martin Malina commented on TOOLSDOC-641: ---------------------------------------- Hi [~mhusnain], ad 1., I agree with Andrej. It just an alternative to a local server - it depends on where you want to run the server where you want to deploy your app. You can lose data on your local system just as well as on a remote system if you don't do backups :) Ad 2., I don't know where we instructed users to use "Server is externally managed", but I remember that there was a requirement some time ago from some customers IIRC that they wanted to have a possibility to create a server adapter without the actual runtime being required - that is now possible with remote servers - you don't need to create a local runtime. But another requirement was to support a scenario where the users only want to deploy to the server, but don't want the IDE to start/stop the server for them - this is what "Server is externally managed" is for. But yeah, I would say there is no reason to instruct users to use one mode over another - it's better to leave it to them. But depending on their choice, there might be some additional settings necessary - if you use Management Operations, then you need to set up an admin user on the server (using SERVER_HOME/bin/add-user.sh) and also enter those credentials in the server editor or during the server start. -- This message was sent by Atlassian JIRA (v6.3.15#6346)