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.
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.
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:
In the next sections, you will set up Remote Deploy to deploy to a remote WebFOCUS Server.
After you have set up a remote server, you must set up the deployment scenario to deploy to it.
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.
You should see at least two folders under its name. An example of this is shown in the following image.
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.
Drag start.mnt to EDA/EDASERVE/APPPATH/FanClub, as shown in the following image.
Notice that the check mark icon appeared next to Start.mnt, and the Assigned attribute has changed to Yes.
You are now ready to deploy and run your application using your brand new deployment scenario.
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.
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.