User's Guide

Define an application in a non-SD format
You either have the option of providing applications in non-SD format in tar or cpio format
archives that have been gzipped or compressed. This section explains how to write a
configuration file that describes an application in non-SD format
84
.
The archive that you will be installing the application with is assumed to contain no system specific
configuration.
You should configure the application as necessary with the command and script hooks provided by
Ignite-UX. The scripts that may be executed while installing the application should never query the
user because not all installations are attended. For a non-interactive installation (the user does not
have access to the console), a script that seeks input from the console would effectively hang the
installation process.
Writing the configuration file for
an application in non-SD format
In the following example, the application configuration file that this configuration will be placed in
is /var/opt/ignite/data/Rel_B.11.11/myapps_cfg.
#
# Definition of where my application is located
#
sw_source "my application archive" {
description = "my application"
source_format = archive
source_type="NET"
nfs_source = "10.2.72.150:/var/opt/ignite/My_Applications"
}
Next, you define a sw_source for the application including its location on the NFS server (at IP
address 10.2.72.150) in the /var/opt/ignite/My_Applications directory. Remember, this
directory must be exported from the NFS server so that it can be mounted. If you choose to limit
access to this directory, remember that you may want servers that obtain IP address via DHCP to be
able to mount the directory when setting its permissions.
sw_category "SiteApps" {
description = "My site applications"
}
The previous example defines a category that you can easily pick out in the list of applications in
the Software tab of the Ignite-UX GUI.
Next, define a 64-bit version of the application and ensure that you can load both the 32-bit and
64-bit versions of the application by making them exrequisties of each other. The impacts
statements are generated with the archive_impact command, and then manually tailored to
account for extra space in /opt, /var, and /tmp that the application requires as in the following
example.
sw_sel "MyApp,v=1.0,64bit" {
84
This section is not relevant to core operating system (OE) golden images. Additional configuration steps are required to define a core
operating system (OE) versus an application golden image.
180