An application is a platform-independent repository for a group of related components, such as, procedures, Master and Access Files, data files, HTML files, PDF files, and GIFs. It provides an area on the server that both confers a unique identity on the components of the application and facilitates the sharing of components across applications in an organized manner. This construct also simplifies the process of moving an application of a user from one platform to another and of deploying PC-developed applications.
These components are physically grouped together on an application by application basis for run-time execution. This physical grouping can be within an application under a common root or a virtual mapping to an application anywhere in the file system. The physical application or mapped name is referred to as the application name in this document. A comprehensive set of APPlication commands are provided to control/manipulate the application components, as well as to facilitate applications that can be written and deployed to any platform.
The physical location of an application and its components is determined by a configuration parameter called approot. This parameter is set at installation time and stored in the server configuration file, edaserve.cfg. The default value is dependent on the platform, relative to the install IDs home directory, where applicable, as indicated in the following chart.
Note: Where directories are referenced in the chart, single-level, lowercase application directories are created below the approot value. The application names must be lowercase and must not contain spaces. For a PDS deployment on the Unified Server, data sets are created for each component type using the approot value as the high-level qualifier.
|
Platform |
Default Value for approot |
|---|---|
|
Unified Server HFS Deployment Unified Server PDS Deployment |
.../ibi/apps approotvalue.appname.component_type |
|
UNIX |
.../ibi/apps |
|
Linux |
.../ibi/apps |
|
Windows |
...\ibi\apps |
|
OS/400 |
.../ibi/apps |
|
OpenVMS |
[.IBI.APPS] |
Two applications are provided during installation: a default application called baseapp and an application containing sample files called ibisamp.
Access to a particular application component can be explicit or implicit. Implicit access is dependent upon the search path in effect at the time of execution. The search path always includes the default application, baseapp. There is no need to explicitly declare this application.
Two applications are provided during installation: a default application called baseapp and an application containing sample files called ibisamp. In addition, when you connect to the server a temporary directory called foccache is added as the first directory in the search path. When you want to be able to reuse data within the same browser session, you can store the data in the form of a HOLD, SAVE, or SAVEB file in the foccache directory. As long as the browser session remains active, the files stored in the foccache directory can be referenced in requests.
You can change the search path from the Web Console, from the Data Management Console, or from within your application code. You can also change the search path temporarily to add application names to the beginning or end of an existing search path.
Note: For platforms that support the Universal Naming Convention (UNC), you can specify a network drive for approot. The UNC must be:
\\mynode\myshare\accnting
| WebFOCUS |