Using the Design Tool to Deploy a Model

To use the Design Tool to deploy a model, select a deployment option: Deploy to the Local Server or Deploy to Remote Server. The Deploy to Remote Server option deploys the model to any designated remote server.

Web services are automatically provided by the session server as an embedded SOAP stack or REST service after a model package is deployed with the WSDL and metadata generated at deployment, for more information view Deploy Web Services.

If your integration solution includes a Web application created with Verastream's Web Builder, you must also deploy the Web application files. See Deploying a Verastream Web Application for more information.

Select Deployment Options

The Deploy to Local Server or Deploy to Remote Server commands on the Design Tool's File menu, deploy the model using the default host name and port number, with no session pool. To modify these defaults or to use a session pool, set deployment options:

  1. On the File menu, select Deployment Options.

  2. The Host tab of the Deployment Options dialog box displays the host name and port number that the server connects to when the model is loaded. If you don't use the Deployment Options dialog box, the Deploy to Local Server command will deploy the model using the default host name and port number, and without a session pool.

    The first time this dialog box is used with a particular model, the host name and port numbers displayed are copied from the default values stored in the model file. Using the edit boxes on the Host tab, change these to whatever is required for your server.

  3. Proceed to the Sessions tab. To deploy the model without using a session pool, select the Deploy as a single session radio button and skip to step 7 below.

    If your model uses a session pool, select the Deploy as a session pool radio button and provide the session pool name, the startup entity name, and the minimum and maximum numbers of sessions.

  4. Proceed to the Variables tab. If the default variable values stored in the model are suitable for all pooled sessions, clear the Provide variable values for pool check box and proceed to step 7.

    Otherwise, check the Provide variable values for pool check box and proceed to the next step.

  5. The names of the variables defined in the model appear in the Variable column of the Variable names table.
  6. The Recording tab controls model debug options. The default, Record Nothing, is appropriate for most cases. Change these settings if you want to take advantage of the Model Debug Messages feature. Click OK.

Resetting Deployment Options

Click the Defaults button to reset the model's deployment options back to the default settings.

Deploy to the Local Server

  1. On the File menu, select Deploy to Local Server.
  2. Click OK to dismiss the confirmation dialog box.

Deploy to Remote Server

You can use a Host Integrator server other than the one included with the Design Tool for your test or small production deployment.

This option is limited to the same basic settings as the local server deployment; it does not include all the options available when deploying to a non-local server using the packagemodel and activatemodel commands.
  1. On the File menu, select Deploy to Remote Server.
  2. Type in the name of the Verastream server. This is a network name or IP address.
  3. Click Deploy.

View Deployed Model in Administrative Console

In the Administrative Console you can verify that the model, pool, and model variable lists have successfully deployed.

  1. Open the Administrative Console and, if necessary,connect to your management server.
  2. Open the Session Server Explorer. (Perspective > Host Integrator > Session Servers)
  3. In the left pane, open Installation > Servers > [your server name]. Double-click on the Models, Model Variable Lists, or Pools items to view the configuration tab in the right pane, associated with each. You can right-click on an item and choose Properties to view the specific properties for each model, model variable list, or pool.
Because any changes that you may make to model or session pool configurations (except pool scheduling) in the Administrative Console are overwritten by subsequent deployments from the Design Tool or by the activatemodel command, it is best to make those changes in the Design Tool.


Related Topics
Bullet Deployment Overview
Bullet Using Commands to Deploy a Model Package