To start with, you can create a new entry in the Servers view to connect to the remote application server. Open the Servers view, right click in the view and choose New > Server. Enter the address of your remote server and select the correct server type and runtime, for example:
You'll need to configure the connection settings with the right port numbers on the next page. I was using the default ports but use the Test Connection link to confirm everything is configured correctly:
Click finish to add the new connection to the Servers view.
In a normal workbench development environment, the local server is configured to use the contents of the CustomerResources project directly, so changes get picked up without any manual intervention. With a remote server however, you'll need to handle the process of updating DWLSchemas.jar and properties.jar before deploying the application. Also, because you didn't run the Prepare > Customize Configuration Files step of the set up wizard, there will be place holders in the .properties files. Instead of manually updating all the place holders for the target server, I used the administration console to export the deployed ear and extract the properties.jar file. You can get to the administration console by right clicking on the server that was configured above, and selecting Administration > Run administration console. Find the MDM application and export it as shown:
You can then extract the properties.jar which will contain all the right settings for the remote server. I used the following command:
jar -xvf MDM-App.ear properties.jar
Finally, it's useful to have a database connection to run any SQL that's generated for your module projects. There should be a Data Source Explorer view in the Data perspective. Right click on Database Connections, click New... and enter the connection parameters for the remote MDM database. For example, these were my settings:
Once everything is set up, the development process is not that different to using a local test server. Just don't forget to package up the contents of CustomerResources before deploying the application!