Deploy a Configuration to a Production Environment

After you have tested your changes and verified that the configuration works, the next stage of the process is to send the configuration to a production Lasernet environment.

First, you must “commit” the configuration changes, which will create a new revision of the configuration. Then, at an appropriate time, you can use Deploy Commit to deploy that new revision to a production Lasernet environment.

Note

To “deploy” a configuration means to send it to a Lasernet environment, which will run the configuration.

Note

For Lasernet 10 documentation on this subject, see the Lasernet Config Server and Deployment Guide.

Deploy Commit

You can use the Lasernet Config web app to deploy any revision of a configuration.

You can use Lasernet Developer to deploy only the latest revision of a configuration.

Lasernet Config Web App

Lasernet Developer

To deploy the latest revision of a configuration to one or more environments, follow these steps:

1. In Lasernet Developer, open the configuration that you want to deploy.

2. In the Lasernet Developer toolbar, click Deploy Commit (see 1 in the image below).

   

3. In the Deploy configuration window, select the checkbox (2) for each environment that you want to commit the latest revision to.

   Note

   You can only deploy committed objects. If the workspace currently contains any uncommitted objects or resources, Lasernet Developer will display a warning.

   

   To commit objects and resources before deploying the configuration, click Commit below the warning then commit the objects and resources.

   To deploy without committing the objects and resources, do not commit the changes and proceed with the following steps.

4. Click Ok. Lasernet Developer displays a progress bar for the deployment.

5. After Lasernet has deployed the configuration, click Close.

After the process is complete, the selected environments are running the configuration.