HP OpenVMS Systems Documentation

4 Registering an Application

Overview of Application Registration

Features Provided by Application Registration

The Purpose of Application Registration

General Steps for Registering an Application

Step 1: Modifying Font and Color Resources

Modifying Font Resources

Modifying Color Resources

Step 2: Creating the Desktop Application Root

Step 3: Creating the Registration Package Directories

Step 4: Creating the Actions and Data Types for the Application

Actions and Data Types Required by an Application

Location for Action and Data Type Definition Configuration Files

Ways to Create Actions and Data Types

To Create Actions and Data Types Using Create Action

To Create Actions and Data Types Manually

Step 5: Putting the Help Files in the Registration Package

Step 6: Creating Icons for the Application

Icons Required for the Desktop

Step 7: Creating the Application Group

Creating the Application Group Directory

Application Group Name

Configuring the Application Group To Use a Unique Icon

Creating the Contents of the Application Group

Step 8: Registering the Application Using dtappintegrate

To Register an Application with dtappintegrate

How dtappintegrate Integrates Applications

Example of Creating a Registration Package

When an application is fully registered onto the desktop, it has:

• Its own application group at the top level of the Application Manager

• An action that starts the application. The action is represented by an icon in the application group

• Optionally, data types for its data files

• It does not involve modification of the application executable itself. Therefore, you can register existing applications on a system.

• It does not require that any of the application's delivered files (such as the executable and app-defaults) be moved to other file locations.

• It can be undone easily. The dtappintegrate tool, which is used to register applications, provides a command-line option for reversing the process.

• A system administrator who wants to register an existing application onto the desktop

• A software programmer who wants to create an installation package for a desktop-smart application

Overview of Application Registration

• The purpose of application registration
• Features provided to your application by application registration

Features Provided by Application Registration

• Locate your application.

  Upon installation, your application is "registered" into the Application Manager and has its own application group.

  Figure 4-1 Application groups at the top level of Application Manager

  

• Start your application.

  The application group for your application contains an icon the user can double-click to start your application.

  Figure 4-2 An application group containing an icon to start the application

  

• Identify and manipulate data files. The application's data files will have a unique icon in File Manager.

  The user can use data file icons to:

• Start (Open) the application

• Print data files

  Figure 4-3 A data file's pop-up menu containing ``Open'' and ``Print''

  

• Perform other operations, such as mailing, compressing, viewing, or playing (audio) data

The Purpose of Application Registration

• Action and data type definition files
• Icon image (pixmap or bitmap) files
• A directory and files that create the application group
• Optionally, desktop help files and Front Panel definition files

It can be difficult to administer an application when its configuration files are scattered among numerous directories. Therefore, the desktop allows an application to keep all its desktop configuration files gathered under a single directory. This grouping of files is called a registration package.

If the application is desktop smart, it supplies a registration package as part of its installation package. If you are a system administrator creating the configuration files yourself, you can create the registration package yourself.

The configuration files in the registration package are not available to the desktop because they are not located in the proper search path directories. The process of placing these files in the proper locations is called registering, or integrating, the application.

The desktop provides a tool, dtappintegrate, that performs the registration by creating symbolically linked representations of the files in the proper search path directories.

Many desktop-smart applications will automatically run dtappintegrate during the installation process. If you are a system administrator integrating an existing application, you can run it yourself after you've created the registration package.

Once an application is registered on a system's desktop, the application is available to all users on the system. If the system is configured as a desktop application server, the application will also be available to other systems throughout the network.

The dtappintegrate tool has a command-line option that reverses the process by breaking the links. This makes it easy to remove the application from the Application Manager so that it can be moved to a different application server or updated.

General Steps for Registering an Application

1. Modify any application resources that set fonts and colors. Otherwise, the desktop's dynamic fonts and colors will not work properly.

   See "Step 1: Modifying Font and Color Resources".

2. Create an application root location.

   See "Step 2: Creating the Desktop Application Root".

3. Create the directory structure underneath the application root.

   See "Step 3: Creating the Registration Package Directories"

4. Create the actions and data types for the application.

   See "Step 4: Creating the Actions and Data Types for the Application".

5. Put the help files in an appropriate directory.

   See "Step 5: Putting the Help Files in the Registration Package".

6. Create the icons for the application

   See "Step 6: Creating Icons for the Application".

7. Create the application group for the application.

   See "Step 7: Creating the Application Group".

8. Register the application using dtappintegrate.

   See "Step 8: Registering the Application Using dtappintegrate".

Step 1: Modifying Font and Color Resources

The desktop provides mechanisms for setting and manipulating interface fonts and window colors. In order for an application to use these mechanisms properly, you may have to modify the application's app-defaults file.

Modifying Font Resources

The desktop Style Manager will set interface fonts for applications created using OSF/Motif 1.2 (or later versions) if the application does not specify application-specific interface fonts.

Style Manager provides two fonts:

system font

Used by system areas such as labels, menus, and buttons

user font

Used for editable areas such as text fields

If you want the application to use the Style Manager fonts, you should remove any application resources that interface specify fonts. The desktop will automatically set the application's resources appropriately:

FontList

Set to system font

XmText*FontList

Set to user font

XmTextField*FontList

Set to user font

Modifying Color Resources

The easiest way to use the dynamic colors provided by the desktop is to remove any application color resources for background and foreground color.

Step 2: Creating the Desktop Application Root

The registration package files for the application are grouped beneath a directory called the application root, or app_root. The app_root directory used for the desktop configuration files can be the same directory as the application's installation app_root or some other location.

For example, suppose an application is installed under a directory /usr/BTE. This same directory could be used as the app_root for the desktop configuration files. However, if you are integrating an existing non-desktop smart application, it is recommended that you create a different desktop app_root directory. This will prevent the configuration files you create from being overwritten when you update the application.

For example, a system administrator might want to create a directory /etc/desktop_approots/BTE as the desktop app_root directory.

Step 3: Creating the Registration Package Directories

The registration package is the group of desktop configuration files used by the desktop to provide a graphical interface for the application.

Registration Package Contents

• Action and data type definition files
• Icon image files
• An application group directory and its contents
• Optionally: help data files and a Front Panel configuration file

Figure 4-4 A registration package beneath an application root directory

The major categories of configuration fields under the app_root/dt/appconfig directory are:

Subdirectory

Contents

types

Action and data type definition files

help

Desktop help files

icons

Bitmap and pixmap image files used by the application's actions and data types

appmanager

The directory and contents that create the application group

To Create the Registration Package

• app_root/dt/appconfig/types/language

• app_root/dt/appconfig/help/language

• app_root/dt/appconfig/icons/language

• app_root/dt/appconfig/appmanager/language/appgroup_name, where appgroup_name is the name of the application group.

Figure 4-5 Application group at the top level of the Application Manager

The dtappintegrate tool operates only on the desktop configuration files in the types, help, icons, and appmanager directories. The application's binary executable, app-defaults, and message catalog files are administered separately.

Step 4: Creating the Actions and Data Types for the Application

Actions and data types provide a user interface for the application.

• Actions provide a user interface for the command to launch the application.

• Data types provide customized appearance and behavior for the application's data files.

Actions and Data Types Required by an Application

• An action that opens the application.

• A data type for the data files of your application. If you create a data type, you will also want to create:
  • An Open action for the data files of your application
  • A Print action for the data files of your application

• A data type for the application group (see "Configuring the Application Group To Use a Unique Icon").

Location for Action and Data Type Definition Configuration Files

Place files containing actions and data types under the application root in the directory app_root/dt/appconfig/types/language. The default language is C.

Figure 4-6 Action and data type definition files

Ways to Create Actions and Data Types

• Use the Create Action tool.

  Create Action provides an easy-to-use interface with text fields that you fill in. However, the tool has certain limitations.

• Create the definitions manually.

  This requires you to learn the syntax for creating the definitions, but provides access to the full range of functionality.

To Create Actions and Data Types Using Create Action

For more information about Create Action, use its online help or see Chapter 9, "Creating Actions and Data Types Using Create Action."

1. Open the Desktop_Apps application group and double-click Create Action.

2. Use Create Action to create the action and data type definitions for the application and its data type.

   The configuration file created by Create Action will be written to HomeDirectory/.dt/type/action_name.dt. The action file (the executable file with the same name as the action) is placed in your home directory.

3. Test the action using the action file created in your home directory.

4. Copy the action definition file HomeDirectory/.dt/type/action_name.dt to the app_root/dt/appconfig/types/language directory.

5. After the application group directory has been created (see "Step 7: Creating the Application Group"), copy the action file HomeDirectory/action_name to the app_root/dt/appconfig/appmanager/language/appgroup_name directory.

To Create Actions and Data Types Manually

Action and data type definition files must follow the naming convention name.dt.

You can place all your action and data type definitions in one file or distribute them among multiple files. For each file, use a file name that system administrators will easily connect with your application.

Action and data type names must be one word (no embedded spaces). You can use an underscore character. By convention, the first letter of the action or data type name is capitalized. Do not use an existing action name or file name. Use a name that advanced users and system administrators will easily connect with your application.

If you want the application's icon labeled with a different name than the action name, include a LABEL field in the action definition.

For more information about creating actions and data types, see:

• Chapter 8, "Introduction to Actions and Data Types"
• Chapter 9, "Creating Actions and Data Types Using Create Action"
• Chapter 10, "Creating Actions Manually"
• Chapter 11, "Creating Data Types Manually"

Step 5: Putting the Help Files in the Registration Package

If the application includes a desktop help volume (a help volume created with the desktop Help Developer's Kit), the help volume master file (*.sdl) should be placed in the directory app_root/appconfig/help/language.

Graphics used by the help files are usually placed in a graphics subdirectory. The graphics must be located in the same directory relative to the master help volume (*.sdl) file as when the help volume was created.

If the application does not provide a help volume, you can create one if you have the Help Developer's Kit.

There are two levels of integration of a help volume:

• Full integration.

  When desktop help is fully integrated, the help volume can be accessed from the application--for example, by on-item help and the Help menu. Full integration involves modification to the application's executables.

• Partial integration.

  When desktop help is partially integrated, it is available from the top level of the Help Manager. However, you cannot access the help volume from the application's windows. You can also provide an action to access the help from the application group. The following example action displays the help volume located in the help master file MyApp.sdl:

  ACTION OpenMyAppHelp
  {
    LABEL           MyAppHelp
    ARG_COUNT       0
    TYPE            COMMAND
    WINDOW_TYPE     NO_STDIO
    EXEC_STRING     /usr/dt/bin/dthelpview -helpVolume MyApp
    DESCRIPTION     Displays help for the MyApp application.
  }
  
  

Step 6: Creating Icons for the Application

The desktop provides default icons for actions, data types, and application groups. However, you will probably want to create unique icons for the application.

Icons are placed in the directory app_root/dt/appconfig/icons/language.

Icons Required for the Desktop

• Action icon. This is the icon the user double-clicks to start your application (actions). It is referenced in the ICON field of the action that launches the application.

  Supply three sizes: tiny, medium, and large.

• Data type icon. This icon is used to represent the application's data files in File Manager. It is referenced in the ICON field of the data type definition.

  If your application supports multiple data types, you should provide a different icon for each data type.

  Supply two sizes: tiny and medium.

• Application group icon. This is the icon representing the directory at the top level of the Application Manager. It is referenced in the ICON field of the data type definition for the application group. (See "Step 7: Creating the Application Group".)

  Supply two sizes: tiny and medium.

.

If you do not provide bitmap files, the desktop maps the color specifications of the pixmap files into black and white. However, this mapping may not produce the appearance you want.

For more information about icons, see "Icon Image Files".

Step 7: Creating the Application Group

Once you have created the action and data type definitions for the application, you must create the configuration files responsible for creating what the user actually sees--the application group and its contents.

The application group is a directory at the top level of the Application Manager (see Figure 4-1).

There are three steps to creating the application group:

• Create the application group directory in the registration package.

• Optional: configure the application group to use a unique icon. This involves creating the data type definition for the application group directory.

• Create the contents of the application group.

Creating the Application Group Directory

Figure 4-7 The appmanager directory

Application Group Name

Figure 4-8 The application group name (<appgroup_name>)

The name can be any allowable file (directory) name. Use a name that describes the application.

Configuring the Application Group To Use a Unique Icon

If you want to provide a unique icon for the application group, you must create:

• A data type for the directory that appears at the top level of Application Manager.

• Open and Print actions for the data type.

DATA_ATTRIBUTES  Media_ToolsAppgroup
{
   ACTIONS       OpenInPlace,OpenNewView
   ICON          MediaTools
   DESCRIPTION   Double-click to open the Media_Tools \
                 application group
}

DATA_CRITERIA           Media_ToolsAppgroupCriteria1
{
   DATA_ATTRIBUTES_NAME Media_ToolsAppgroup
   MODE                 d
   PATH_PATTERN         */appmanager/*/Media_Tools
} 

Figure 4-9 shows the relationship between the application group name and the data type definition. The PATH_PATTERN field in the data type definition connects a unique icon to the application group.

Figure 4-9 How an application group gets a unique icon

You should also create an Open and Print action for the application group data type:

ACTION Open
{
   ARG_TYPE     Media_ToolsAppGroup
   TYPE         MAP
   MAP_ACTION   OpenAppGroup
}

ACTION Print
{
   ARG_TYPE     Media_ToolsAppGroup
   TYPE         MAP
   MAP_ACTION   PrintAppGroup
}

Creating the Contents of the Application Group

In addition to one or more action icons, the application group may contain:

• One or more README files
• One or more sample data files
• Templates
• An icon the user can double-click to view help information
• A man page
• A specialized Front Panel control

Creating the Action File (Application Icon)

An action icon is created by creating an executable file with the same name as the action it will run:

app_root/dt/appconfig/appmanager/appgroup_name/action_name

For example, if you've created an action named BestTextEditor that runs the BestTextEditor application, you would create an executable file named BestTextEditor. In File Manager and the Application Manager, the action file will use the icon image specified in the action definition.

Figure 4-10 illustrates the relationship between the action definition, action file, and actual entry in the Application Manager window.

Figure 4-10 The application icon is a file in the application group

Read Me Files

• README
• readme
• README.*
• Read.*.Me
• read.*.me
• READ.*.ME

Creating a Specialized Front Panel Control

You might want to create a Front Panel configuration file containing a control definition for your application if you want users to be able to install a control that behaves differently than the action icon--for example, if the control monitors a file and changes appearance when the monitored file changes.

Front Panel configuration files are placed in the app_root/dt/appconfig/types/language directory. The naming convention is name.fp.

If you supply a configuration file containing a control, the user can add the control to a subpanel by dropping the *.fp file on the Install Icon control in the subpanel.

For example, the following definition can be placed in a Front Panel configuration file in the application group. If the user drops this file on an Install Icon control in a subpanel, a control is created in the subpanel that runs a single instance of the BestTextEditor application. If BestTextEditor is already running, the window is moved to the top of the window stack in the current workspace.

CONTROL BestTextEditorControl
{
   TYPE          icon
   ICON          BTEFPanel
   PUSH_RECALL   True
   CLIENT_NAME   BTEd
   PUSH_ACTION   BTEditor
   DROP_ACTION   BTEditor
   HELP_STRING   Starts the BestTextEditor application.
}

• Chapter 13, "Advanced Front Panel Customization"
• The dtfpfile(4) man page

Step 8: Registering the Application Using dtappintegrate

Once you've created a registration package under an application root, you are ready to perform the actual application registration.

Application registration creates links between the registration package and the directories located along the desktop search paths (see "How dtappintegrate Integrates Applications").

To Register an Application with dtappintegrate

1. Log in as root.

2. Run the command:

   /usr/dt/bin/dtappintegrate -s  app_root
   
   

   where app_root is the desktop application root directory. For more information, see the dtappintegrate(1) man page.

3. Open the Desktop_Tools application group and double-click Reload Applications.

4. Verify that the application is properly registered:

   a. Display the top level of the Application Manager. The new application group should appear in the Application Manager.

   b. Open the application group and double-click the action icon.

Syntax and Options for dtappintegrate

dtappintegrate -s app_root [-t target_path ] [-l language ] [-u]

-s app_root

Required parameter. Specifies the application root under which the appication has been installed.

-t target_path

Optional parameter, defaults to the system location /etc/dt/appconfig. Specifies the location to which the desktop configuration files are linked. You must use a location on the application search path.

-l language

Optional parameter, defaults to all languages. Specifies which language-dependent desktop configuration files to integrate.

-u

Optional parameter. Un-integrates the application, removing all the links set up during integration.

How dtappintegrate Integrates Applications

Actions and Data Types

app_root/dt/appconfig/types/language/*.dt

/etc/dt/appconfig/types/language/*.dt

Help Information Files

app_root/dt/appconfig/help/language/help_file.sdl

/etc/dt/appconfig/help/language/help_file.sdl

Icon Files

app_root/dt/appconfig/icons/language/icon_files

/etc/dt/appconfig/icons/language/icon_files 

Application Group

app_root/dt/appconfig/appmanager/language/appgroup_name

/etc/dt/appconfig/appmanager/language/appgroup_name

Example of Creating a Registration Package

Information You Need to Know About ``BestTextEditor''

• It was installed into the directory /usr/BTE.

• The user's session language is the default value, C.

• The command line to start BestTextEditor is:

  BTEd {filename]
  
  

  where filename is the name of the data file to open in the new window. BestTextEditor creates its own window--that is, it does not run inside a terminal emulator window.

• BestTextEditor creates and uses two types of data files:
  • Documentation files. They use the naming convention *.bte. BestTextEditor provides a command line for printing its .bte data files. The syntax of this command is:

    BTEPrint [-d destination] [-s] filename
    
    

    where:

    -d destination

    Specifies destination printer.

    -s

    Specifies silent printing. The application's print dialog box is not displayed.

    filename

    Specifies the file to be printed.

  • Template files. They use the naming convention *.tpl. Template files cannot be printed.

• The existing, non-desktop app-defaults files for BestTextEditor contain resources for interface fonts and foreground and background colors.

• An online help volume for BestTextEditorwas created using the desktop Help Developer's Kit. When the online help volume was built, it used the following source files:

  ... /BTEHelp.htg
  ... /graphics/BTE1.xwd
  ... /graphics/BTE2.xwd
  
  

  and generated the file ... /BTEHelp.sdl.

Steps to Registering ``BestTextEditor''

1. Modify font and color resources.

   In BestTextEditor's app-defaults file, remove resources that set:

   • Fonts for text.

   • Colors for foreground and background.

2. Create the application root.

   Create the directory:

   /desktop_approots/BTE
   
   

   If you are integrating an existing application, you should create the application root directory elsewhere than in the installation location for the application; otherwise, the configuration files you create may be removed when you update the application.

3. Create the registration package directories.

   Create these directories:

   /desktop_approots/BTE/dt/appconfig/types/C
   /desktop_approots/BTE/dt/appconfig/help/C
   /desktop_approots/BTE/dt/appconfig/icons/C
   /desktop_approots/BTE/dt/appconfig/appmanager/C/BestTextEditor
   
   

4. Create the actions and data types for the application.

   a. Create the configuration file for the action and data type definitions:

   /desktop_approots/BTE/dt/appconfig/types/C/BTE.dt
   
   

   b. Create the action definition for running BestTextEditor:

   ACTION BTEditor
   {
      WINDOW_TYPE  NO_STDIO
      ICON         BTERun
      DESCRIPTION  Double-click this icon or drop a BTE data \
                   file on it to run BestTextEditor.
      EXEC_STRING  /usr/BTE/BTEd %Arg_1%
   }
   
   

   c. Create the data type for *.bte files:

   DATA_ATTRIBUTES BTEDataFile
   {
      DESCRIPTION  BestTextEditor data file.
      ICON         BTEData
      ACTIONS      Open,Print
   }
   
   DATA_CRITERIA BTEDataFileCriteria1
   {
      DATA_ATTRIBUTES_NAME  BTEDataFile
      NAME_PATTERN          *.bte
      MODE                  f
   }
   
   

   d. Create the data type for *.tpl files:

   DATA_ATTRIBUTES BTETemplateFile
   {
      DESCRIPTION  BestTextEditor template file.
      ICON         BTETempl
      ACTIONS      Open
   }
   
   DATA_CRITERIAL BTETemplateFileCriteria1
   {
      DATA_ATTRIBUTES_NAME  BTETemplateFile
      NAME_PATTERN          *.tpl
      MODE                  f
   }
   
   

   e. Create the Open action for *.bte files.

   ACTION Open
   {
      ARG_TYPE     BTEDataFile
      TYPE         MAP
      MAP_ACTION   BTEditor
   }
   
   

   f. Create the Print action for *.bte files.

   Here are simple Print actions that will print the data files. These actions require a value for the LPDEST environment variable and ignore the -s print option. (If LPDEST isn't set, the action may fail.)

   ACTION Print
   {
      ARG_TYPE     BTEDataFile
      TYPE         MAP
      MAP_ACTION   BTEPrintData
   }
   
   ACTION BTEPrintData
   }
      WINDOW_TYPE  NO_STDIO
      EXEC_STRING  BTEPrint -d $LPDEST %Arg_1%
   }
   
   

   Here is another version of the BTEPrintData action and an accompanying script. Together, they handle situations where LPDEST is not set or if silent printing is requested.

   ACTION BTEPrintData
   {
      WINDOW_TYPE  NO_STDIO
      EXEC_STRING  /usr/BTE/bin/BTEenvprint %(File)Arg_1%
   }
   
   

   The contents of the /usr/BTE/bin/BTEenvprint script is:

   # BTEenvprint
   #!/bin/sh
   DEST=""
   SILENT=""
   if [ $LPDEST ] ; then
      DEST="-d $LPDEST"
   fi
   BTEPrint $DEST SILENT $1
   
   

   g. Create the Open action for *.tpl files:

   ACTION Open
   {
      ARG_TYPE    BTETemplateFile
      TYPE        MAP
      MAP_ACTION  BTEditor
   }
   
   

   h. Create the Print action for *.tpl files:

   ACTION Print
   {
      ARG_TYPES   BTETemplateFile
      TYPE        MAP
      MAP_ACTION  NoPrint
   }
   
   

   NoPrint is a built-in action that displays a dialog box telling the user the file cannot be printed.

5. Put the help files into the registration package.

   a. Place the help files in the following locations:

   /desktop_approots/BTE/dt/appconfig/help/C/BTEHelp.sdl
   /desktop_approots/BTE/dt/appconfig/help/C/graphics/BTE1.xwd
   /desktop_approots/BTE/dt/appconfig/help/C/graphics/BTE2.xwd
   
   

   b. Create the file:

   /desktop_approots/BTE/dt/appconfig/types/C/BTEhelp.dt. 
   
   

   Put the following action definition in the file:

   ACTION BTEHelp
   {
      WINDOW_TYPE   NO_STDIO
      EXEC_STRING   /usr/dt/bin/dthelpview -helpVolume \
                    BTEHelp.sdl
      DESCRIPTION   Opens the BestTextEditor help volume.
   }
   
   

6. Create icons for the application.

   Use Icon Editor to create the icons. Use these size guidelines:

   Name

   Size

   basename.t.pm

   16 by 16

   basename.m.pm

   32 by 32

   basename.l.pm

   64 by 64

   Create these icon files in the directory
   /desktop_approots/BTE/dt/appconfig/icons/C:
   • Icons to represent the action that runs the application: BTERun.t.pm, BTERun.m.pm, BTERun.l.pm

   • Icons to represent *.bte files: BTEData.t.pm, BTEData.m.pm,

   • Icons to represent *.tpl files: BTETempl.t.pm, BTETempl.m.pm

   • Icons to represent the application group (used in step 7): BTEApp.t.pm, BTEApp.m.pm

7. Create the application group.

   a. If you haven't already done so, create the directory.

   /desktop_approots/BTE/dt/appconfig/appmanager/C/BestTextEditor
   
   

   b. This step is optional. It provides a unique icon for the application group icon by creating a data type and associated actions for the application group. If you omit this step, the application group will use the default icon.

   Add the following data type and action definitions to the file /desktop_approots/BTE/dt/appconfig/types/C/BTE.dt.The data type specifies the icon to be used by the BestTextEditor application group. The actions provide the same Open and Print behavior as the built-in application groups.

   DATA_ATTRIBUTES BestTextEditorAppGroup
   {
      ACTIONS     OpenInPlace,OpenNewView
      ICON        BTEApp
   {
   
   DATA_CRITERIA BestTextEditorAppGroupCriterial
   {
     DATA_ATTRIBUTES_NAME   BestTextEditorAppGroup
     MODE                   d
     PATH_PATTERN           */appmanager/*/BestTextEditor
   }
   
   ACTION Open
   {
     ARG_TYPE     BestTextEditorAppGroup
     TYPE         MAP
     MAP_ACTION   OpenAppGroup
   }
   
   ACTION Print
   {
     ARG_TYPE     BestTextEditorAppGroup
     TYPE         MAP
     MAP_ACTION   PrintAppGroup
   }
   
   

   c. Create an icon in the application group that will start the application. To do this, create the file:

   /desktop_approots/BTE/dt/appconfig/appmanager/C/BestTextEditor/BTEditor
   
   

   and make the file executable.

   d. Create the action file in the application group that will open the help volume. To do this, create the file:

   /desktop_approots/BTE/dt/appconfig/appmanager/C/BestTextEditor/BTEHelp
   
   

   and make the file executable.

   e. Put other files into the application group; for example, "read me" files, sample data and template files.

8. Register the application.

   In a terminal emulator window:

   a. Log in as root.

   b. Run the command:

   /usr/dt/bin/dtappintegrate -s /desktop_approots/BTE
   
   

   c. Open the Desktop_Tools application group and double-click Reload Applications.