##### Compile

# Target Environment

A Target Environment defines the location to which the scripts will be compiled as well as the target language of the scripts. This feature allows you to create multiple target destinations for the compiled code. When you select Target Environment from the Compile menu, the Target Environment List dialog box displays.

The Environment List dialog box includes the following columns, TargetEnv Name, Description, and Code Target. Double-click on a TargetEnv Name in the list to open the Target Environment Properties dialog box for that Target Environment.

In addition:

- Use the Add button to create a new Target Environment.

- Use the Edit button to edit a selected Target Environment.

- Use the Copy button to copy a selected Target Environment.

- Use the Delete button to delete a selected Target Environment.

# Target Environment Properties dialog

This dialog box includes four tabs, General, Advanced, Configuration File, and Default Parameters, which are described below.

## General Tab

Fields | Description
TargetEnv Name | The Target Environment Name identifies the target environment to the user.
Description | This field contains a description of the target environment. It is used for informational purposes and is not used elsewhere in the system.
Target Directory | The Target Directory is used to indicate a folder for Genesys Agent Scripting to place the completed generated scripts. This location can be a folder on the machine on which Genesys Agent Scripting is installed or a folder on a network drive. The only restriction is that you must have write access to this location.
Simulate URL | The Simulate URL is the location from where Genesys Agent Scripting will simulate scripts. Genesys Agent Scripting allows you test compiled scripts in a browser. The Simulate URL tells Genesys Agent Scripting how to find the scripts on the Web Server.
Code Target | The Code Target field allows you to select the platform for the application. Currently, Genesys Agent Scripting can produce pages as JSP (Java Server Pages) for running on Java based web platforms or ASP (Active Server Pages) and ASPX (ASP.NET) for running on a web platform such as IIS.

## Advanced Tab

Fields | Description
Post Compile Procedure | A post compile procedure allows you to run a batch file as soon as the Genesys Agent Scripting has finished compiling the scripts. Use the Browse button to locate the Post Compile Procedure or enter the full path of the file to be run. An example of a post compile procedure is a script that uploads the compiled scripts to the production web server.
Do Not Overwrite Configuration File | If this box is checked, the Configuration File tab is disabled. It prevents you from assigning values to configuration file fields in the configuration file tab, which will overwrite existing values in the configuration file.
Compile with JMeter Support | If this box is checked, JMeter will be used to build a test script and simulate 1 to many users running the script at one time. This is useful for testing the throughput of a Genesys Agent Scripting application. If this option is selected, the JMeter code will be generated in the script. If it is not selected, the JMeter code will not be generated.
Use Async Framework | This option is only enabled for code targets of ASPX and JSP. If checked, it enables the use of the asynchronous events feature. Note: You must use Netscape version 6.0 or later when using a Netscape browser to view web pages generated when this option is enabled.
Advanced Java Options | This option is available when you select JSP as the Code Target.
Create Target as a .WAR File | If this box is checked, a .WAR file will be generated in the target directory that can be used for deployment to Application Servers (Tomcat and WebSphere Application Server). The name of the file will be the Project Book name, for example: ProjectBookName.WAR.
Java SDK Directory | If you selected Create Target as a .WAR File, a utility program from the Java SDK is used to create the .WAR file. The path to the Java SDK must be identified in order for this process to work properly. The path can be identified in the following ways: a. The Browse button allows you to identify the correct directory, otherwise b. The environment variable called "JAVA_HOME" will be used, otherwise c. The Java SDK must be in the host machine's path.

## Configuration File Tab

Fields | Description
Field Name | A field that has been marked as a configuration file.
Value | The value of the field.

ASP.NET (.NET Server) Target Environment Fields

GAS 7.2 supports Genesys integration with the ASP.NET platform. New configuration fields were added to the Configuration File tab for ASPX target environments (Compile > Target Environment) and these are used instead of the JSP AIL target environment configuration fields:

Existing JSP target environment fields:

- G_Config_ApplName

- G_Config_PrimaryHost

- G_Config_PrimaryPort

- G_Config_BackupHost

- G_Config_BackupPort

ASP.NET target environment fields (new for 7.2):

- G_NETServer_PrimaryHost

- G_NETServer_PrimaryPort

- G_NETServer_BackupHost

- G_NETServer_BackupPort

Notes:

- Now you can create an ASPX target environment for a Project Book that is created with the Genesys Agent Interaction Toolkit selected as the Base Toolkit.

- ASPX scripts created with the Genesys Agent Interaction Toolkit selected as the Base Toolkit require Genesys Integration Server version 7.2 or higher in the Genesys environment.

## Default Parameters Tab

Fields | Description
Field Name | A field that has been marked as parameters.
Value | The value of the field.