[ https://issues.jboss.org/browse/TOOLSDOC-345?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-345: ------------------------------------------ [~rob.stryker]: I have a couple of statements about server instances, server adapters, and remote servers that I need you to verify. These derive from the understanding I am piecing together and might be woefully incorrect. Local servers: 1. You have a server runtime environment (e.g., EAP 6.0). 2. From this you can create many server instances (e.g., my_EAP1, my_EAP2). 3. The IDE needs a server adapter for each server instance so that the IDE and server instance can communicate. 4. The new server wizard creates both the server instance and server adapter for local servers. 5. Server adapters are listed in the servers tab. But for the main part local server instances and their adapters can be considered as one within the IDE. Remote servers: 6. Instead of a local server instance, you can have an existing remote server. 7. As with local server instances, the IDE needs a server adapter to communicate with remote servers. 8. To create a server adapter for a remote server, the server runtime environment of the remote system must be installed on the local system where the IDE is running. [Basically so they can share a common language/API/instruction set.] 9. The new server wizard only creates the server adapter for remote servers. 10. Again the server adapter is listed in the servers tab. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira