ABL applications rely on a PROPATH environment variable to tell a given program where, in file-system storage, it can find an external procedure to execute at run time. This PROPATH value consists of path components, similar to an operating system Path or Java Classpath. Each component of the PROPATH is an absolute or relative pathname to a folder where external procedure files for the application can reside. You can also use dot (.) as a PROPATH component.
Similarly, for each AppObject and SubAppObject you define in ProxyGen, you must also specify the PROPATH components that ProxyGen requires to locate the external procedures for the object in its own working environment. You then select from the procedures available for each object's PROPATH to include as methods or as ProcObjects in the given AppObject or SubAppObject. Each AppObject and SubAppObject can specify the same PROPATH components, or each object can specify one or more unique PROPATH components. If the PROPATH components follow a logical organization, it might be useful to map those components to objects, but there is no required mapping between objects and PROPATH components.
Note: The PROPATH component settings in ProxyGen are not necessarily the same as the run-time PROPATH settings on the AppServer. In ProxyGen, you specify them only to locate procedures in the ProxyGen environment for defining the Open Client interface, not to execute the procedures on the AppServer. However you set up your PROPATH, you must ensure that the relative paths under the PROPATH component settings remain the same between the AppServer and ProxyGen.
