1. Open the Deploy folder for the project. Right-click the deployment scenario that you are defining, and select Open.
2. The left window pane displays information about the individual files that are visible from the project search path.

   The icons next to some files are unavailable. This indicates that the files are available, but not active for your project. You can click the binoculars icon to show the files that you added to your project and hide the inactive files. However, you can deploy even the files that you did not add to your project.

   The value of Assigned is No if the file has not been assigned to a server for deployment. Assigned is Yes if you have assigned the file to a server for deployment.

   Note: If you cannot see the value in the Assigned column or the full application path in the Location column, drag your cursor to the right to expand the Application Files window.

3. The right window pane displays the environments you have identified and optionally configured to accept project files.

   For a web server, you can create one or more subfolders on the deployment path. For example, you might separate HTML files from image files by creating an individual folder, or central location, for each type:

   1. Select and right-click the current web server deployment path (for example, WEB/APPROOT/Sales).
   2. Select New Folder from the shortcut menu. At the cursor location in the entry field, enter the name of the new folder.

      Note: You must design the application properly in order to take advantage of a multi-level directory structure on the deployment environment.

4. In the right pane, open the environment on which you are partitioning the files. In the following example, the Test Environment includes a web server and a server node that can be used for deployment.

   

   In the example:

   • The web server is defined by the node WEB, followed by the descriptive name APPROOT and the name of the directory that will be created when the files are deployed (sales).
   • A WebFOCUS Reporting Server is defined by the node EDA and the name of the server (for example, EDASERVE), followed by the descriptive name APPPATH and the name of the directory that will be created when the files are deployed (sales).

   The developer selected NONE as the default partition environment when creating the new deployment scenario. For an example of the window that opens when you select a default partition environment, see Working in a Default Partition Environment.

5. Drag one or more files from the left window pane and drop them into the right window pane on the applicable server.

   See Guidelines for Deploying Files for information that will help you deploy files to the applicable server.

   To remove a partitioned file from the right window pane, right-click it and select Remove.

   In this example, the file named launch_qty.htm is an HTML page from which a user can run a report named stockqty.fex. To partition these files appropriately, you would drag launch_qty.htm to the web server, and stockqty.fex to the WebFOCUS Reporting Server.

   On the toolbar, these buttons enable you to do the following while you remain in the Scenario Editor:

   Name	Button	Description
   Deploy scenario		Deploys (moves) the files to the servers based on the partitioning defined in the current deployment scenario.
   Deploy and run scenario		Deploys the files to the servers and then runs the starting object defined in the current deployment scenario.
   Run scenario		Runs the starting object defined in the current deployment scenario.
   Displays all files in the project path		Displays available items in the project path. The icons next to some files are unavailable. This indicates that the files are available, but not active for your project. You can click the binoculars icon to show the files that you added to your project and hide the inactive files. However, you can deploy even the files that you did not add to your project.

   These buttons are also available on the toolbar in the Explorer.

6. When you have finished partitioning files, choose one of the options in step 5 or close the window. You can perform any of the options in step 5 outside the Scenario Editor. See Step 4: Deploy the Project Files.

• Typically, you will deploy HTML, GIF, JPG, VBScript, and JavaScript files to a web server. Executable WebFOCUS procedures (.fex, .mnt, and .sty files) will go to a WebFOCUS Reporting Server.

  If the deployed FOCUS procedure has a reference to a style sheet (.sty) file and the generated procedure uses a stylesheet different from the default, you must deploy the style sheet to the Reporting Server, or else the report will not run.

  To view and deploy the .sty file, you must add the filter for this file to the project level or an available virtual folder (for example, Procedures) to view files of this type in the project and in the Scenario Editor.

  Usually, you will not deploy Master Files (.mas) or Access Files (.acx). Master Files and Access Files may already reside on the deployment WebFOCUS Reporting Server or subserver in applications configured to contain them. If you deploy these types of files, you may overwrite production files with the same name on the deployment server.

  Proprietary FOCUS data sources (.foc) files cannot be deployed. If you try to drag an invalid file type to the Reporting Server, an error message appears.

• For files containing the command -HTMLFORM filename:
  • If you are deploying a procedure that contains -HTMLFORM filename (including procedures created with the HTML Composer), also deploy the referenced HTML file to the WebFOCUS Reporting Server.

    In this scenario, the procedure must be launched in order to execute the report.

  • When you use the HTML Composer to create reports with parameters, you must deploy the referenced HTML file containing the launch form to both the web server and the WebFOCUS Reporting Server.

    In this scenario, the HTML file must be launched from the web server.

In this example, the developer selected the Test Environment as the default partition environment when creating the deployment scenario.

Developer Studio automatically partitions the .jpg and .htm files to the web server, and the .fex files to the WebFOCUS Reporting Server, as shown in the following image.

Files in the Name display field that have a check icon next to them have been partitioned.

You can set the execution search path for a deployed application on a Reporting Server. The Reporting Server will use the path specified to locate the resources for that application.

This feature is useful if you set up common resources shared by multiple applications. It allows you to point a server to a common location to find the resources it needs to run a specific application.