How to: |
A deployment scenario provides a means of identifying project files for distribution to target servers in a WebFOCUS environment.
You can create more than one deployment scenario for a project, and you can view and modify the properties of an existing scenario.
Developer Studio supplies a deployment scenario named Local Deploy, which it uses to prepare files to run on a local server. Do not modify or remove Local Deploy.
The New Scenario Wizard dialog box opens, as shown in the following image.
When Smart Deploy is active for a deployment scenario, after its first successful deployment, date and time information is stored in your Project GFA file for each file being deployed. Each subsequent Deploy action then compares the date and time stamp of the source files in your project against the date and time stamps stored in the Deployment Scenario. With Smart Deploy, only newer files will be deployed to the destination, where the source file has a newer time stamp than the one stored in the GFA.
Note:
A project file that was used in a deployment scenario and deleted outside of Developer Studio (or from another project in which it was shared).
or
A file located in a directory that changed and can no longer be found.
If this option is selected, the deployment scenario will not fail if it contains unresolved files. However, when the deployment process completes, it will display information about files skipped during the process because they were unresolved.
Although this code (XML) is not needed at run time once the .WFM files have been created during the deploy process, keeping it in the remote copy of the file can be an added safeguard should anything happen to the original version. MNT files deployed without the form code cannot be reopened in an MDE session.
Note: The XML code for the form should never be edited manually. Use the MDE to open and edit .MNT files containing forms.
Click Next to proceed to the next Scenario Wizard window, as shown in the following image.
HTML, GIF, JPG, VBScript, and JavaScript files are partitioned to the default web server. Executable WebFOCUS procedures (.fex and .mnt files) are partitioned to the default WebFOCUS Reporting Server.
By default, Developer Studio does not partition Master Files and Access Files in order not to overwrite production files with the same name on the deployment server.
Selecting an environment from this list does not force the deployment of files as defined in the scenario.
You can change the definition of the scenario.
This list is not active if you choose the value NONE for the Default partition environment.
If you are deploying files to your development server, you must provide a target application name other than your development directory.
If you are deploying files to a WebFOCUS Reporting Server on z/OS, the target application name can be up to eight characters. For deployment servers on all other supported platforms, the name can be up to 18 characters. Spaces are not allowed. (If a space is entered, it is converted to an underscore.)
Click Next to proceed to the next Scenario Wizard window, as shown in the following image.
This option is enabled only when files are added to the application and when the option to partition files has been selected.
You must ensure that the deployed application has access to the file to avoid an error at run time.
You must ensure that the deployed application has access to the file to avoid an error at run time.
Click Next to proceed to the next Scenario Wizard window, as shown in the following.
The Deploy Properties dialog box opens, displaying the General, Comment, and Deployment tabs.
The General tab is selected by default. It displays the CLSID, ProgID, and a description.
WebFOCUS |