In this section: |
When you build your applications using Developer Studio tools, each of the project files are stored in dedicated folders on the development server. When procedures are run against the WebFOCUS Reporting Server, the procedure code is sent across the wire to the Reporting Server for execution, but the code is not stored there.
The Reporting Server uses one of two methods to locate the target procedure: APP PATH or EDAPATH.
You can use one of the following strategies when you build your applications:
For HTML files that are built with external graphical tools or coded manually in a text editor, you will need to decide whether to run the application with APP PATH or EDAPATH logic. You must make sure that application files are deployed to a directory included in EDAPATH or APP PATH, depending on which search path you plan to use.
SET EDAPATH=+D:\ibi\apps\ggdemo; -1. D:\ibi\apps\ncp; -2. D:\ibi\apps\centcorp\centdata; -3. D:\ibi\apps\centcorp\centfex; -4. D:\ibi\apps\template; -5. D:\ibi\apps\myapp1; -6. D:\user_directory\corpapp\myapp2;
where:
Specify paths for directories containing sample data sources and applications for use within Information Builders products.
Are directories added to the search path to identify files associated with user-created applications.
Reference: |
The Application Namespace feature (also known as the APP PATH command) is enabled in every installation of a WebFOCUS Reporting Server by default. It is utilized by Developer Studio when you work in the Data Servers or Managed Reporting areas. When you work in the Projects area, the APP PATH command in the WebFOCUS Reporting Server is not processed because each project uses its own search path (APP PATH). Each search path in the project is based on directories added to the project from the Directories tab in the Properties dialog box. The default baseapp directory is always used in the Projects, Data Servers, and Managed Reporting areas. For details about the Properties dialog box, see Viewing and Modifying Project Properties in Creating a Reporting Application in the Creating Reporting Applications With Developer Studio manual.
The APP PATH command determines the search path for application components. The APP ENABLE setting in your server profile activates the feature, which provides benefits to developers for organizing their application resources on the server. A migration feature is provided on the Server Console, to convert your old server profile to the new syntax. For more information, see the Server Administration for UNIX, Windows, OpenVMS, IBM i, and z/OS manual.
On UNIX, Windows, and IBM i, application (project) names are single-level directories under the Application Root directory (APPROOT directory). You can specify multiple application names to extend the search path by adding directories to the Directories tab on the Properties dialog box for the project.
On UNIX, Windows, OpenVMS, and IBM i, Managed Reporting and Data Servers application names are single-level directories under the Application Root directory (APPROOT directory). You can specify multiple application names on APP PATH to extend the search path.
When APP PATH is used, the following search order is in effect:
If APP PATH is issued without an application name, the current APP PATH setting is removed from the search path.
For a more detailed look at working with applications and APP commands, see Managing Applications.
The following chart indicates the search paths for the following APP commands:
Enables the application search, disables EDAPATH, EDASYN, and EDASYNR.
Disables the current application path.
Defines the directory to hold temporary files.
Designates the application as the location for Master Files and Access Files created with the HOLD command.
Designates the application as the location for data files created with the HOLD command.
Platform |
APPROOT setting |
Search path |
---|---|---|
z/OS, IBM i |
ibi/apps |
ibi/apps/application_name
ibi/apps/baseapp
$EDAHOME/catalog |
Windows |
ibi\apps |
ibi\apps\application_name
ibi\apps\baseapp
%EDAHOME%\catalog |
MVS |
EDAARH.MYAPPS |
Master Files EDAARH.MYAPPS.APP1.MASTER.DATA EDAARH.MYAPPS.BASEAPP.MASTER.DATA ddname IBIMFD Access Files EDAARH.MYAPPS.APP1.ACCESS.DATA EDAARH.MYAPPS.BASEAPP.ACCESS.DATA ddname IBIAFD FOCEXEC Files (RPCs) EDAARH.MYAPPS.APP1.FOCEXEC.DATA EDAARH.MYAPPS.BASEAPP.FOCEXEC.DATA ddname IBIFEX |
OpenVMS |
disk$dua0: [EDA.IBI.APPS] |
disk$dua0:[EDA.IBI.APPS.APP1] disk$dua0:[EDA.IBI.APPS.BASEAPP] EDAHOME [.CATALOG] |
WebFOCUS and Developer Studio use other APP commands internally, so you do not have to issue them, unless that is your preference. For more information about APP commands, see Managing Applications.
Deploy Wizard and APP PATH Logic
The Deploy Wizard in the Developer Studio toolset uses APP PATH logic to create the necessary directories under the web server and the WebFOCUS Reporting Server. Before you can deploy projects in Developer Studio, you must set APPROOT variables in two files:
For details about the Deployment tab on the Properties dialog box, see Viewing and Modifying Project Properties in Creating a Reporting Application in the Creating Reporting Applications With Developer Studio manual.
Note: You must also specify this APPROOT path as a virtual directory on the web server. Alternatively, you can set APPROOT to any other directory designated to hold the user interface files for a deployed application.
For complete information on configuring WebFOCUS to receive deployed applications, see Partitioning and Deploying Project Files in the Creating Reporting Applications With Developer Studio manual.
WebFOCUS |