When you select remote installation, the Generate and Install processes create remote files. These files contain all the necessary elements to install an application on CA Gen equipped target system.
There are three different types of remote files created for each application. These are listed in the following table along with a description of their contents and location.
|
Type |
Number |
Workstation Location |
Naming Convention |
Description |
|---|---|---|---|---|
|
Load Module |
One or more per application. |
Depending on the language selected for your application, in the C subdirectory under your model directory. |
The name of your load module followed by the file extension .RMT |
Application source code for a single load module. |
|
Database |
Usually one per application. |
In the DDL subdirectory under your model directory. |
The name of your database followed by the file extension .RMT |
DDL for an application database. For target system implementation, all load modules for a CA Gen application usually share a common database. |
|
RI |
One per application |
Depending on the language selected for your application, in the C subdirectory under your model directory. |
CASCADE |
RI trigger source for an application. These routines implement referential integrity for the entire application. |
The remote files need to be copied or moved from their location on the workstation to the target system for installation, further testing, and production execution.
After the load modules are copied to the target system, they can be deleted from the workstation, along with all the source components used to generate them. However, if you prefer, the source components can be stored on the workstation so that only the changed components need to be regenerated if testing on the target system reveals some problems.
|
Copyright © 2013 CA.
All rights reserved.
|
|