COSmanager/User Guide/Managing COSmanager Applications

This page was last modified 06:14, 6 August 2007.

From Documentation

< COSmanager | User Guide(Difference between revisions)

Current revision

Day-to-day configuration and administration within a COSmanager application is done mainly through the product’s own configuration menu. General management of applications and of the COSmanager framework is done through the COSmanager configuration menu.

This section describes how to customize and configure COSmanager, including:

re-licensing an application
changing the default version of an application
controlling who may access the application main menu and configuration menu
setting or changing an application password
deinstalling an application or module
customizing the text on COSmanager menus and button bars
changing the settings in the COSmanager global parameters

1 To License an Application
2 To Change the Default Version
3 To Control Access to Applications
4 To Deinstall an Application or Module
5 Maintaining the Application Table
- 5.1 To change application details
6 To Add a Local Application
7 Installing and Removing Software Patches
8 Changing Global Parameters

 *changing the settings in the COSmanager global parameters
+<br>
 == To License an Application ==
 You must have a valid license key before you install a COSmanager application. Temporary or permanent license keys can be obtained from your COSmanager distributor. You can enter a new license key, for example to extend a temporary license or to permanently license a product when its trial license is about to expire.
-*Select COSmanager configuration > COSmanager applications.
+#Select COSmanager configuration > COSmanager applications.
-*Select the application name then select Application > Licence.
+#Select the application name then select Application > Licence.
-*Now enter the information from the Licence Key Details form. Not all fields are required for all applications, but you must enter the details exactly as they appear on the form.
+#Now enter the information from the Licence Key Details form. Not all fields are required for all applications, but you must enter the details exactly as they appear on the form.
+#;Host name: Choose a host name or enter ALL if the license key covers all your hosts.
+#;Product code(s): Enter the list of product codes, each separated by a semicolon ( ; ).
+#;Options: Some products have separate licensing for clients and servers.
+#:Enter any options separated by a colon ( : ).
+#;Expiry date: If this is a temporary license (for example a trial or evaluation license), enter the expiry date in the form YYYYMMDD.
+#;Licence key: Enter the license key. A valid license key contains only dashes, numbers, and lower-case letters.
+#Press Accept.
-;Host name: Choose a host name or enter ALL if the license key covers all your hosts.
+<br>
-;Product code(s): Enter the list of product codes, each separated by a semicolon ( ; ).
-;Options: Some products have separate licensing for clients and servers.
-:Enter any options separated by a colon ( : ).
-;Expiry date: If this is a temporary license (for example a trial or evaluation license), enter the expiry date in the form YYYYMMDD.
-;Licence key: Enter the license key. A valid license key contains only dashes, numbers, and lower-case letters.
-*Press Accept.
 == To Change the Default Version ==
 You can install several versions of an application. The default version is the one that is run when a user selects this application from the COSmanager button bar or main menu.
 #Select COSmanager configuration > COSmanager applications.
 #Select a non-default version of an application.
 #Select Application > Default.
 This version of the application is now the default. You must exit and restart COSmanager for the change to take effect.
+<br>
 == To Control Access to Applications ==
 You can restrict which COSmanager users can use or configure particular COSmanager applications. If a user doesn’t have the right role to use an application, the product name will not appear on their COSmanager button bar or main menu. If a user doesn’t have the right role to configure an application, the product name will not be listed under their COSmanager configuration menu.
-Note that the Change security option only controls the ability to launch the application or its configuration menu. Once a user is in the application, access to particular menus, functions and options is controlled through the user’s roles and capabilities. See [[COSmanager Users and Access Controls]].
+Note that the Change security option only controls the ability to launch the application or its configuration menu. Once a user is in the application, access to particular menus, functions and options is controlled through the user’s roles and capabilities. See [[COSmanager/User_Guide/COSmanager_Users_and_Access_Controls | COSmanager Users and Access Controls]].
 You can also define a password for each application. Even users with the right access role must enter the correct password in order to use the application. Finally, you can require the user to enter their own password before getting access to use or configure an application. This prevents passers-by from getting unauthorized access to COSmanager through a temporarily unattended terminal.
+<br>
 === To define access security controls for an application ===
 #Select COSmanager configuration > COSmanager applications.
 #Select an application, then select Application > Change security and fill in the following fields:
+#;Appl. access: Choose one or more roles and capabilities. A user with any of these roles or capabilities will have access to launch the application.
+#:''ALL'' means every COSmanager user can launch the application.
+#;Authenticate?: Select yes to make users enter their own password before getting access to the application.
+#;Config access: Choose one or more roles or capabilities. A user with any of these roles or capabilities will have access to configure the application.
+#:''ALL'' means every COSmanager user can launch the application.
+#;Authenticate?: Select yes to make users enter their own password before getting access to configure the application.
-;Appl. access: Choose one or more roles and capabilities. A user with any of these roles or capabilities will have access to launch the application.
+<br>
-:ALL means every COSmanager user can launch the application.
-;Authenticate?: Select yes to make users enter their own password before getting access to the application.
-;Config access: Choose one or more roles or capabilities. A user with any of these roles or capabilities will have access to configure the application.
-:ALL means every COSmanager user can launch the application.
-;Authenticate?: Select yes to make users enter their own password before getting access to configure the application.
 === To set or change an application password ===
 If you set a password for a COSmanager application, users must enter the correct password before getting access to it.
 #Select COSmanager configuration > COSmanager applications.
 #Press Accept to save the new password.
+<br>
 === To remove an application password ===
 #Select COSmanager configuration > COSmanager applications.
 #Select an application, then select Application > Password.
 #Press Accept to remove the password from this application.
-=== To Deinstall an Application or Module ===
+<br>
+== To Deinstall an Application or Module ==
 #Select COSmanager configuration > COSmanager applications.
 #Select an application or module.
 #Select Application > Deinstall.
 #COSmanager displays information about this application.
 Press Accept to remove the software from disk and to remove its entry in the application table.
 Press Exit to leave the application as is.
-=== Maintaining the Application Table ===
+<br>
+== Maintaining the Application Table ==
 COSmanager keeps details of all your installed applications in the application table. The COSmanager applications option under COSmanager configuration has options for all the common application management tasks.
 You can also maintain these details directly through the Maintain tables option, for example, to change how the application appears in the COSmanager button bar and menus, or to add a non-COSmanager application to the COSmanager main menu.
- Note The Maintain options only affects entries in the application table, not the actual installed software.
- For example, Maintain > Remove only removes the application table entry;
+{{Note| The Maintain options only affects entries in the application table, not the actual installed software. For example, Maintain > Remove only removes the application table entry; Application > Deinstall also removes the software from disk.}}
- Application > Deinstall also removes the software from disk.
 The first time you start COSmanager after the application table has changed (for example when a new application is installed), COSmanager regenerates the COSmanager main menu and configuration menu.
+<br>
 === To change application details ===
-#Select COSmanager configuration > Maintain tables.
+#Select COSmanager configuration > Other Tables.
 #Select the ‘COSmanager Applications’ table, then select Table > Maintain. The COSmanager applications window is displayed, showing your installed applications. Note that ‘Manual’ and ‘Remote’ are built-in applications and cannot be deinstalled.
 #Select an application, then select Maintain > Change to list all its details.
-;Application: the application name.
+#;Application: the application name.
-;Title: the application title. If Button is not specified, Title is the name that appears on the COSmanager pulldown.
+#;Title: the application title. If Button is not specified, Title is the name that appears on the COSmanager pulldown.
-;Version: the version number.
+#;Version: the version number.
-;Patch level: the patch level of this application (the original version of any application is patch level 0).
+#;Patch level: the patch level of this application (the original version of any application is patch level 0).
-;Default: whether this is the default version of this application. For example, if you enter cos duty the default version of duty3g will be run.
+#;Default: whether this is the default version of this application. For example, if you enter cos duty the default version of duty3g will be run.
-:If you wish to run a different version, you must also supply the version number—e.g. cos duty -v version
+#:If you wish to run a different version, you must also supply the version number—e.g. cos duty -v version
-;Directory: the home directory of this application. If you need to move the directory for some reason, this is how you tell COSmanager the application’s new location.
+#;Directory: the home directory of this application. If you need to move the directory for some reason, this is how you tell COSmanager the application’s new location.
-;Abbreviation: the application’s abbreviation, used for licensing and when naming application-specific capabilities.
+#;Abbreviation: the application’s abbreviation, used for licensing and when naming application-specific capabilities.
+#:'''Caution -''' This setting should not be changed. If you to try to change the application abbreviation, you may invalidate your  software license or cause COSmanager’s access security controls not to work correctly.
+#;F/W version: the minimum version of the COSmanager framework required to run this application.
+#:'''Caution -''' This setting should not be changed. If you try to run this application under an unsupported version of the COSmanager framework, damage to the software or to your data may result.
+#;Description: a brief text description of the application. This appears as the help text for this application.
+#:&nbsp;
+#;The next group of fields define what details appear in the COSmanager menus.
+#;Button: the name that appears in the COSmanager button bar (GUI). If you leave this field blank, the application will appear on the COSmanager pulldown instead.
+#;Option: the name that appears in the COSmanager main menu (CUI).
+#;Action: the command that is run when this application is invoked from the COSmanager main menu.
+#;Config action: the command that is run when this application is invoked from the Product configuration menu.
+#:&nbsp;
+#;The next group of fields define which users are permitted to access which functions in this application.
+#;Application: the capabilities permitted to access the application main menu. A user must have at least one of these capabilities to use the main menu for this application. Enter ALL to give access to all COSmanager users.
+#;Configuration: the capabilities permitted to use the administration options for this application. A user must have at least one of these capabilities to use the Product configuration menu option for this application.
+#;Authentication: whether to authenticate the user before allowing them to run or administer the application.
+#:;None: no authentication required
+#:;Config: authenticate the user’s password before administering the application
+#:;Appl: authenticate the user’s password before running the application
+#:;Both: authenticate the user’s password before administering or running the application
+#;Add-on modules: a space-separated list of add-on modules installed under this application. This field is maintained by the  Application > Install and Application > Deinstall options and should not need to be manually edited.
- Caution This setting should not be changed.
+<br>
- If you to try to change the application abbreviation, you may invalidate your  software license or cause
- COSmanager’s access security controls not to work correctly.
-;F/W version: the minimum version of the COSmanager framework required to run this application.
+== To Add a Local Application ==
- Caution This setting should not be changed.
- If you try to run this application under an unsupported version of the COSmanager framework, damage to the software or to your data may result.
-;Description: a brief text description of the application. This appears as the help text for this application.
+You can add a local or non-COSmanager application to the COSmanager main menu by adding its details to the application table.
+#Select COSmanager configuration > Maintain tables .
+#Select the ‘COSmanager Applications’ table, then select Table > Maintain.
+#Select Maintain > Add and enter the following fields:
+#;Application: leave blank—this is used only for COSmanager applications.
+#;Title: the application title. If Button is not specified, Title is the name that appears on the COSmanager pulldown.
+#;Version: the version number (optional).
+#;Patch: level the patch level (optional).
+#;Description: a brief text description of the application. This appears as the help text for this application.
+#;Button: the name that appears in the COSmanager button bar (GUI). If you leave this field blank, the application will appear on the COSmanager pulldown under the name in Title.
+#:You can specify a custom icon to be displayed on the button. It must be a 32x32 bit icon in XPM format stored in $FShome/GUI/icons. The name must be <button>.xpm, where <button> is the button name in lower case. Example: $FShome/GUI/icons/report.xpm is the icon for the Report button.
+#;Option: the name that appears in the COSmanager main menu (CUI).
+#;Action: the command that is run when this application is invoked from the COSmanager main menu.
+#;Application: the capabilities permitted to access the application main menu. A user must have at least one of these capabilities to use the main menu for this application. Enter ALL to give access to all COSmanager users.
+#Press Accept to save the application. You will have to exit COSmanager then restart it to see the new option.
-The next group of fields define what details appear in the COSmanager menus.
-;Button: the name that appears in the COSmanager button bar (GUI). If you leave this field blank, the application will appear on the COSmanager pulldown instead.
-;Option: the name that appears in the COSmanager main menu (CUI).
-;Action: the command that is run when this application is invoked from the COSmanager main menu.
-;Config action: the command that is run when this application is invoked from the Product configuration menu.
-The next group of fields define which users are permitted to access which functions in this application.
-;Application: the capabilities permitted to access the application main menu. A user must have at least one of these capabilities to use the main menu for this application. Enter ALL to give access to all COSmanager users.
-;Configuration: the capabilities permitted to use the administration options for this application. A user must have at least one of these capabilities to use the Product configuration menu option for this application.
-;Authentication: whether to authenticate the user before allowing them to run or administer the application.
-:;None: no authentication required
-:;Config: authenticate the user’s password before administering the application
-:;Appl: authenticate the user’s password before running the application
-:;Both: authenticate the user’s password before administering or running the application
-;Add-on modules: a space-separated list of add-on modules installed under this application. This field is maintained by the  Application > Install and Application > Deinstall options and should not need to be manually edited.
-=== To Add a Local Application ===
-You can add a local or non-COSmanager application to the COSmanager main menu by adding its details to the application table.
-*Select COSmanager configuration > Maintain tables .
-*Select the ‘COSmanager Applications’ table, then select Table > Maintain.
-*Select Maintain > Add and enter the following fields:
-;Application: leave blank—this is used only for COSmanager applications.
-;Title: the application title. If Button is not specified, Title is the name that appears on the COSmanager pulldown.
-;Version: the version number (optional).
-;Patch: level the patch level (optional).
-;Description: a brief text description of the application. This appears as the help text for this application.
-;Button: the name that appears in the COSmanager button bar (GUI). If you leave this field blank, the application will appear on the COSmanager pulldown under the name in Title.
-:You can specify a custom icon to be displayed on the button. It must be a 32x32 bit icon in XPM format stored in
-$FShome/GUI/icons. The name must be <button>.xpm, where <button> is the button name in lower case. Example: $FShome/GUI/icons/report.xpm is the icon for the Report button.
-;Option: the name that appears in the COSmanager main menu (CUI).
-;Action: the command that is run when this application is invoked from the COSmanager main menu.
-;Application: the capabilities permitted to access the application main menu. A user must have at least one of these capabilities to use the main menu for this application. Enter ALL to give access to all COSmanager users.
-*Press Accept to save the application. You will have to exit COSmanager then restart it to see the new option.
 If there is a syntax error in the new generated COSmanager main menu, you won’t be able to correct the application details through the COSmanager configuration menu.
 $APPL_HOME/local/menu/COSmanager.menu after you have made your changes to the application details.
-=== Installing and Removing Software Patches ===
+<BR>
+== Installing and Removing Software Patches ==
 COSmanager applications are designed to be easy to customize and enhance. Much of the application software is comprised of scripts and database tables in the form of plain text files. COSmanager provides a mechanism to install and track updates to these files, so that minor enhancements and problem fixes can be installed quickly and easily between major software releases.
 A patch comprises one or more changed scripts. All scripts that have changed since the product was released are contained in the current patch. For example, a patch level 3 would also contain all the scripts that changed in patches 1 and 2. This means that there is only ever one patch available for a product, so patches can’t be installed out of order.
-===To install a patch
+<br>
-Patches are installed in the same way as applications and modules, through the
+=== To install a patch ===
-Application > Install option (see Application Installation on page 68).
-When an application patch is installed, all the scripts that were replaced are saved in
+Patches are installed in the same way as applications and modules, through the Application > Install option (see [[COSmanager/User_Guide/Installing_Applications_and_Modules | Application Installation]]). When an application patch is installed, all the scripts that were replaced are saved in a directory structure under <appl_home>/Install/Save-<patchlevel>, where <appl_home> is the home directory of the application or module.
-a directory structure under <appl_home>/Install/Save-<patchlevel>,
-where <appl_home> is the home directory of the application or module.
+<br>
-To remove (‘back out’) a patch
-Patches can’t be deinstalled like applications and modules through the Application
+=== To remove (‘back out’) a patch ===
-> Deinstall option. To remove a patch, follow these steps.
-. Open a shell from COSmanager (or su to COSmanager) and enter:
+Patches can’t be deinstalled like applications and modules through the Application > Deinstall option. To remove a patch, follow these steps.
-cd <appl_home>/Install/Save-<patchlevel>
+#Open a shell from COSmanager (or su to COSmanager) and enter: &nbsp;&nbsp;<tt>cd <appl_home>/Install/Save-<patchlevel></tt>
-. Next, enter:
+#Next, enter: &nbsp;&nbsp;<tt>find . -print | cpio -dump <appl_home></tt><br>This will copy all the saved scripts back to their original locations.
-find . -print | cpio -dump <appl_home>
+#Start COSmanager then select COSmanager configuration > Maintain tables .
-This will copy all the saved scripts back to their original locations.
+#Select the ‘COSmanager Applications’ table, then select Table > Maintain.
-. Start COSmanager then select COSmanager configuration >
+#Select the product that had the patch you wish to remove.
-Maintain tables .
+#Select Maintain > Change .
-. Select the ‘COSmanager Applications’ table, then select Table > Maincosmos.
+#Revert Version number and Patch level to the state they were in before the patch was installed.
-Managing COSmanager Applications 87
+#Press Accept to save the changes.
-tain.
-. Select the product that had the patch you wish to remove.
+<br>
-. Select Maintain > Change .
+=== To find the patch level of an application or module ===
-. Revert Version number and Patch level to the state they were in
-before the patch was installed.
+The full version number of an installed application includes the major version number of the application and the patch level. For example, if patch level 2 is installed for backup3g 3.2, its full version number becomes backup3g 3.2.2.
-. Press Accept to save the changes.
+#Select COSmanager configuration > COSmanager applications.
-To find the patch level of an application or module
+#Find the product and check its Version field. The third number is the patch level. Example: if the version for COS/Admin is 4.0.2, the patch level is 2.
-The full version number of an installed application includes the major version number
-of the application and the patch level. For example, if patch level 2 is installed
+The next major release of a product incorporates the changes in the patches to the previous version and its patch level becomes 0.
-for backup3g 3.2, its full version number becomes backup3g 3.2.2.
-. Select COSmanager configuration > COSmanager applications.
+<br>
-. Find the product and check its Version field. The third number is the
-patch level. Example: if the version for COS/Admin is 4.0.2, the patch level
+== Changing Global Parameters ==
-is 2.
-The next major release of a product incorporates the changes in the patches to the
+[[image:Global_settings.jpg]]
-previous version and its patch level becomes 0.
-Managing COSmanager Applications
+The Global parameters list contains a number of settings that you can use to customize how COSmanager works. These include:
-Changing Global Parameters
+;Customer name: the name that appears in the ‘About’ box (GUI version) and the screen title (CUI version).
-The Global parameters list contains a number of settings that you can use to
+;Search path: the UNIX search path for executables.
-customize how COSmanager works. These include:
-Customer name
+{{Caution| Don’t include {{icode|.}} (current directory) on the search path. This is recognized as an unsound security practise, as it may allow unauthorized users to run privileged commands. }}
-the name that appears in the ‘About’ box (GUI version) and the
-screen title (CUI version).
+<br />
-Search path the UNIX search path for executables.
+;Date format: the format in which dates are entered and displayed in COSmanager.
-Caution Don’t include . (current directory) on the search path. This is recognized as an
+;File creation mask: The default permissions assigned to files created by COSmanager.
-unsound security practise, as it may allow unauthorized users to run privileged commands.
+;Prompt entry mode: the default typing mode (Insert or Overtype) used for data entry in COSmanager prompt(1) forms.
-Date format the format in which dates are entered and displayed in
+;Default printer: the default printer used by the Print command (see below).
-COSmanager.
+;Printer type: the Terminfo name for the default printer.
-File creation mask
+;Print command: the UNIX command used to print data from scroll(1).
-The default permissions assigned to files created by COSmanager.
+;DB Print command: the UNIX command used to print data from db_scroll(1).
-Prompt entry mode
+;Pager command: the UNIX command to display paged text, such as man pages.
-the default typing mode (Insert or Overtype) used for data entry in
+;Curses timeout: whether the CUI version should use the Curses timeout facility. See [[COSmanager/User_Guide/Appendices#Intermittent_function_keys | Intermittent function keys]].
-COSmanager prompt(1) forms.
+;Load library path: the path to search for dynamic load libraries.
-Default printer
+;Domain Name: the internet Domain name of this host
-the default printer used by the Print command (see below).
-Printer type the Terminfo name for the default printer.
-Print command
-the UNIX command used to print data from scroll(1).
-DB Print command
-the UNIX command used to print data from db_scroll(1).
-Pager command
-the UNIX command to display paged text, such as man pages.
-Managing COSmanager Applications 89
-Curses timeout
-whether the CUI version should use the Curses timeout facility.
-See Intermittent function keys on page 146.
-Load library path
-the path to search for dynamic load libraries.
 To maintain a global parameter
-. Select Global parameters from the COSmanager configuration
+#Select Global parameters from the COSmanager configuration menu.
-menu.
+#Select the parameter, then select Parameter > Change value.
-. Select the parameter, then select Parameter > Change value.
+#Change the value of the parameter, then press Accept.
-. Change the value of the parameter, then press Accept.
+<br>

	Note
	The Maintain options only affects entries in the application table, not the actual installed software. For example, Maintain > Remove only removes the application table entry; Application > Deinstall also removes the software from disk.

	Caution!
	Don’t include `.` (current directory) on the search path. This is recognized as an unsound security practise, as it may allow unauthorized users to run privileged commands.

Search

COSmanager/User Guide/Managing COSmanager Applications

From Documentation

Current revision

Contents

To License an Application

To Change the Default Version

To Control Access to Applications

To define access security controls for an application

To set or change an application password

To remove an application password

To Deinstall an Application or Module

Maintaining the Application Table

To change application details

To Add a Local Application

Installing and Removing Software Patches

To install a patch

To remove (‘back out’) a patch

To find the patch level of an application or module

Changing Global Parameters