Jump to: navigation, search

Build and Deploy

DevGuide2.png Purpose: To build and deploy your Genesys Web Engagement application.

Once you have created and configured a Genesys Web Engagement application and implemented a Genesys Web Engagement model, you must build and deploy your application, before you start your Servers.

Build your Application

DevGuide2.png Purpose: To create the application's files that will be deployed in the next step.

Start

  1. Navigate to the installation directory of Genesys Web Engagement and open a new Windows Console.
  2. Type:
    build <application name>

End

The script starts building .war files used for deployment. If the build is successful, the console output displays a BUILD SUCCESSFUL messages at runtime, and the .war files are created in the following Genesys Web Engagement sub-directories:

  • apps\<application name>\backend\target\MyProject-wmbackend-0.1
  • apps\<application name>\frontend\target\MyProject-wmfrontend-0.1

In addition, a new map.xml file is created in the \apps\<application name>\proxy\target\ directory.
Next Steps
Resultset next.png Deploy your Application

Deploy your Application

DevGuide2.png Purpose: Copy the application's file at the proper location.

Prerequisites

  • Your build was successful. If your build fails due to errors, try to fix them, then rebuild. You can neither deploy nor start your Web Engagement servers if the build is not successful.

Start

  1. Navigate to the installation directory of Genesys Web Engagement and open a new Windows Console.
  2. Type:
    deploy <application name>

End

The deploy script copies files to the appropriate locations. If the deploy is successful, the script output displays the following messages:

Application '<application name>' is used
1 file(s) copied. 1 file(s) copied. 1 file(s) copied.

Do not deploy if errors occurred during the building step! See Build your Application.


Next Steps
Resultset next.png Start your Servers

This page was last modified on February 27, 2013, at 07:55.

Feedback

Comment on this article:

blog comments powered by Disqus