For client/server applications, procedure steps are packaged according to load module types.
For the server manager load module type, select the procedure steps to be packaged in the load module from the list of unpackaged procedure steps defined for the business system. Procedure steps that are online with no display appear in this list.
For the window manager load module type, select the procedure steps to be packaged from the list of unpackaged procedure steps defined for the business system. The procedure steps that are to be packaged in window load modules are online with display and with no display.
For both server manager and window manager load modules, you do not explicitly package action blocks. By adding procedure steps to a load module, all action blocks used by the procedure step are also included in the load module, as well as all action blocks used by other action blocks.
Packaging is dependent on the flow definitions for a client/server design. You cannot package the client and server procedure steps together because they will reside on different platforms. This may affect the procedure step definition and dialog flow design.
Downstream Effects: When generating for a remote installation, each load module becomes a separate remote file and is linked on the target system into a separate executable module. The Referential Integrity modules are packaged into a single remote file. The DDL associated with an application is packaged into a single remote file.
You can use the Filter feature to control the display of the unpackaged procedure steps.
|
Copyright © 2013 CA.
All rights reserved.
|
|