Previous Topic: Separate Configuration and Data from CodeNext Topic: Startup and Hooks


Tie Boundary to Interior

Previously you set the class boundary. Now you need to tie the boundary to the interior to allow the configuring of the appliance initialization and startup. This allows your appliance to execute its own virtualized environment and boot its own operating system, application services, and other required software.

An appliance is not required to use any of these services. Only the exterior boundary, which is implemented by APK and described in the Set Class Boundary section.above, is what defines an appliance as far as CA AppLogic is concerned. The interior boundary services are provided to help adapt an existing generic service, such as a firewall, mail server, or Web server program, for use as a self-contained virtual appliance running in CA AppLogic.

This section contains the following topics:

Startup and Hooks

Terminals

Raw Interfaces

Volumes

Events

Performance Counters