Deploying Your Project to a Different WebFOCUS Server

How to:

Up until this point, you have been running your project locally. Now that the project is fairly complete, deploy it to another WebFOCUS Server.

You determine where your procedure is deployed using a deployment scenario. The deployment scenario maps all of the components in your project to a WebFOCUS Server or a web server. Then, at deployment time, WebFOCUS Maintain makes sure that all the pieces get updated in the appropriate locations.

By default, all WebFOCUS Maintain projects contain a Local Deploy scenario, which deploys your project to your local development server.

You can have more than one deployment scenario, so depending on which deployment scenario is active, your application can be deployed in several places.

You can deploy and run your project on a different remote WebFOCUS Server, if you have already set up WebFOCUS Developer Studio to access a remote WebFOCUS Server. For more information, see the Creating Reporting Applications With Developer Studio manual.

Top of page

Procedure: How to Create a Deployment Scenario
  1. Create a new deployment scenario by right-clicking the FanClub project in the Explorer window, clicking Project Deployment, and then clicking New Scenario.
  2. In the New Scenario dialog box, give your new deployment scenario the name Remote Deploy.
  3. Click Next, as shown in the following image.

  4. Enter fanclub as the target application name, as shown in the following image.

    Note: If you choose to deploy to your development server, you must enter a name other than Fanclub, which is your development directory, as the target application name.

    New Scenario Wizard Window

  5. Click Next.
  6. Select Start.mnt as your starting object, as shown in the following image.

    New Scenario Wizard Window

  7. Click Next.
  8. Review the information and press Finish.

    WebFOCUS Maintain adds a new folder, Deploy, to the list of folders under the project in the Explorer. Open the Deploy folder. You will see two deployment scenarios:

    • Local Deploy is the default deployment scenario created when you created your project. It deploys your project locally on your machine. You cannot modify or delete this deployment scenario.
    • Remote Deploy is the deployment scenario you just created, as shown in the following image.

      Deploy Folder

    In the next sections, you will set up Remote Deploy to deploy to a remote WebFOCUS Server.

Top of page

Procedure: How to Set up a Deployment Scenario

After you have set up a remote server, you must set up the deployment scenario to deploy to it.

  1. In the FanClub project, open the Deploy folder.
  2. Open Remote Deploy.

    On the left side, you see the files that are in your project. Currently, you have two: fannames.mas and start.mnt.

    On the right side, you see the servers to which you can deploy project files. In this example, there are two: localhost (your local WebFOCUS Server) and Remote Server, but you may have more. An example of this is shown in the following image.

    Scenario Editor

  3. Expand your remote server by clicking the + button next to its name.

    You should see at least two folders under its name. An example of this is shown in the following image.

    Remote Server folders

    Folders that start with WEB represent servers at your target server. Folders that start with EDA represent WebFOCUS Servers at your target server. In general, you deploy files that you create with WebFOCUS Developer Studio (WebFOCUS files, Maintain files, Master Files) to the WebFOCUS Server, and you deploy third-party files (HTML files, images, script files) to the web server. There are exceptions to this rule. See Partitioning and Deploying Project Files in the Creating Reporting Applications With Developer Studio manual for more information.

  4. Assume that fannames.mas already resides on your target web server. This means that you do not need to deploy fannames.mas, since it is already there.

    Drag start.mnt to EDA/EDASERVE/APPPATH/FanClub, as shown in the following image.

    Scenario Editor Window

    Notice that the check mark icon check icon appeared next to Start.mnt, and the Assigned attribute has changed to Yes.

  5. You do need to tell the FanClub application where to find the fannames data source. Right-click the target server, and click Set Server Paths.
  6. In the Set Running Paths for Server dialog box, add the directory where the fannames data source resides to the Running Paths box, as shown in the following image. If this server is similar to your installation, this file is likely to be in the Maintain directory. Otherwise, you can open the Remote Application Servers in the Explorer, and open the target server.

    Set Running Paths for Server dialog box

  7. When you are done, click OK.

You are now ready to deploy and run your application using your brand new deployment scenario.

Top of page

Procedure: How to Deploy and Run Your Application Using Your New Deployment Scenario
  1. On the Exploring toolbar, make Remote Deploy your current deployment scenario by selecting it from the pull-down menu of deployment scenarios.
  2. Click the Deploy and run scenario button , either in the Remote Deploy window, or on the Exploring toolbar.

    WebFOCUS Maintain copies files to the remote server, while displaying the Deploying Application dialog box, as shown in the following image.

    When it is done, click Close to run the application.

    Note: The fannames data source on the remote server may have different data from your local copy.

  3. When you are done running your application, click Exit and then close the Developer Studio Viewer.
  4. In the Maintain Development Environment, close the Remote Deploy deployment scenario.

Since WebFOCUS Developer Studio and WebFOCUS Maintain share their Deploy tool, more detailed information about deploying is available in the Creating Reporting Applications With Developer Studio manual.