Opens the Deploy to MobileTogether Server dialog, in which you specify: (i) server connection details, and (ii) deployment properties of the project on the server. On clicking OK, the currently active MobileTogether design file is deployed to MobileTogether Server.
The following details are required for deployment:
•Server name and port: The port refers to the MobileTogether Server administrator port and must match the Administrator Ports setting of MobileTogether Server. If you use SSL, make sure that you use the secure port of MobileTogether Server.
•User name and password: The user name and password of a user that has been given the privilege Save workflow from designer. MobileTogether Server users and their privileges are specified in the Users and Roles settings of MobileTogether Server.
•Login: Specify whether login is direct or as a domain user. (If login is as a domain user, then the domain-specific user name and password can be used.) From the options in the combo box, select Directly or the domain you wish to use. Only those domains are displayed in the combo box that have been configured on the server for active directory login. For more information about configuring the server for active directory login, see the MobileTogether Server user manual.
•Active configuration of global resources: Select the active configuration from the available configurations in the dropdown list of the combo box. The available configurations are those that are defined in the Global Resources Definitions file and are automatically obtained from there. See the section Altova Global Resources for details.
•Automated test cases: Displays the recorded base test runs (the test cases) of the design. Select the test cases that you want to deploy. Use the Ctrl and Shift keys to select multiple test cases.
•Deployment path and solution description: The path and name of the deployed solution, and the description of the solution that will appear on the server.
•Save design changes on deploying: The project file is saved before deploying, so that the latest changes to the design are included.
•Reset persistent client data on next workflow run: Resets persistent client data when the solution is run the next time.