When targeting remote environments, installation creates the completed remote file, which is moved to the remote machine. In other words, a remote installation is one in which the application source code is generated on one computer and then installed for execution on another.
For example, a remote installation for UNIX or Linux and Oracle, although generated on Windows, produces an application that accesses Oracle and can be installed under UNIX or Linux.
Remote installation begins using the same generation process as used for local installation. The generation process creates the source code.
However, after the actual code is generated, the installation process for remote is very different. Remote installation creates a set of remote files that contain all of the components necessary to compile and install the application on a target system. These remote files must be moved to the target system and installed in an environment supported by CA Gen before the application can be used.
Note: The term remote file has superseded the use of the term Implementation Package (IP). There may still be references to IPs within some CA Gen documentation, or on some screens. The terms are synonymous.
Remote installation requires the presence of certain CA Gen components on the selected target system.
The installation of a generated GUI application or client, of a client/server application on another workstation, is also considered a type of remote installation. Unlike the type of remote installation that generates remote files and requires the presence of a remote installation tool, remote installation for GUI applications and clients means transferring (or copying) generated application executables (.EXE files), dynamic-linked libraries (DLLs), and other required files to a directory on the target workstation.
|
Copyright © 2013 CA.
All rights reserved.
|
|