FS
Documentation
You are here
Search
 

COSmanager/User Guide/Overview

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

From Documentation

< COSmanager | User Guide(Difference between revisions)
Jump to: navigation, search
Revision as of 06:26, 18 April 2006
Daniels (Talk | contribs)

← Previous diff		 Current revision
Daniels (Talk | contribs)
(→Application Development)
Line 1: Line 1:
== Overview == == Overview ==
-This chapter introduces you to COSmanager both from a management and a technical+ 
-perspective.+This chapter introduces you to COSmanager both from a management and a technical perspective.
At a management level, it explains: At a management level, it explains:
-• what COSmanager can do+*what COSmanager can do
-• the COSmanager family of applications.+*the COSmanager family of applications.
 + 
 + 
At a technical level, it introduces you to: At a technical level, it introduces you to:
-• setting up and using COSmanager+*setting up and using COSmanager
-• the COSmanager software environment, including its system account, directory+*the COSmanager software environment, including its system account, directory structure, access control, and variables
-structure, access control, and variables+*customizing COSmanager menus and scripts
-• customizing COSmanager menus and scripts+*the COSmanager user interface.
-• the COSmanager user interface.+ 
-This chapter contains useful information for helping you prepare to install and use+ 
-COSmanager. However, if you wish to get started immediately, skip to Installing+This section contains useful information for helping you prepare to install and use COSmanager. However, if you wish to get started immediately, skip to [[#Installing COSmanager|Installing COSmanager]].
-COSMOS on page 27.+ 
-8 Overview+<br>
-Management Overview+=== Management Overview ===
-COSmanager facilitates a standard approach to the management of distributed+ 
-Open Systems data centers, through:+COSmanager facilitates a standard approach to the management of distributed Open Systems data centers, through:
-• Automation of system management functions+*Automation of system management functions
-• Delegation of operations tasks+*Delegation of operations tasks
-• Control over data centre operations+*Control over data centre operations
 + 
 + 
It provides: It provides:
-• a full suite of powerful system management applications+*a full suite of powerful system management applications
-• sophisticated but easy-to-use access controls. COSmanager can only be+*sophisticated but easy-to-use access controls. COSmanager can only be invoked by authorized users. Users have limited ‘views’ of COSmanager functions based on their roles and responsibilities, enabling tight supervision to be maintained over access to key functions. Controls over shell access and super user privileges are also provided
-invoked by authorized users. Users have limited ‘views’ of COSmanager+*a standard interface to data center operations, through customized COSmanager menus and interfaces to third-party software
-functions based on their roles and responsibilities, enabling tight supervision+*a policies and procedures approach to data center management.
-to be maintained over access to key functions. Controls over shell+ 
-access and super user privileges are also provided+<br>
-• a standard interface to data center operations, through customized COSmanager+=== COSmanager Applications ===
-menus and interfaces to third-party software+COSmanager comprises a suite of applications that cover all the main areas of system management. These applications are designed to work well together and to integrate with third-party products.
-• a policies and procedures approach to data center management.+ 
-COSmanager Applications+ 
-COSmanager comprises a suite of applications that cover all the main areas of system+==== admin3G ====
-management. These applications are designed to work well together and to integrate+ 
-with third-party products.+admin3G provides a consistent interface to system administration and user management in multi-vendor, multi-host environments. It includes a comprehensive set of facilities that standardize and improve on the basic services provided by individual vendors. COSadmin services include:
-COS/Admin+*user administration
-COS/Admin provides a consistent interface to system administration and user management+*process management
-in multi-vendor, multi-host environments. It includes a comprehensive set+*filesystem management
-of facilities that standardize and improve on the basic services provided by individual+*basic performance monitoring
-vendors. COS/Admin services include:+ 
-• user administration+==== backup3G ====
-• process management+ 
-Overview 9+[[backup3G]] provides policy-based backup and data recovery in Open Systems data centers. backup3g’s flexible client/server model supports both centralized and distributed backup models, including backup of non-UNIX clients.
-• filesystem management+ 
-• basic performance monitoring+backup3G also supports:
-backup3g+*high-speed file recovery
-backup3g provides policy-based backup and data recovery in Open Systems data+*all standard UNIX backup formats (cpio, dump, tar and raw filesystem)
-centers. backup3g’s flexible client/server model supports both centralized and distributed+*flexible backup job scheduling, including automated and unattended backups
-backup models, including backup of non-UNIX clients (NT, Novell, Windows).+*multi-volume backups
-backup3g also supports:+*appending backups
-• high-speed file recovery+*tape stackers, jukeboxes and automated tape libraries
-• all standard UNIX backup formats (cpio, dump, tar and raw filesystem)+*drive pooling
-• flexible backup job scheduling, including automated and unattended backups+*full media management
-• multi-volume backups+*intelligent backup of Oracle databases through the ORAback module
-• appending backups+ 
-• tape stackers, jukeboxes and automated tape libraries+ 
-• drive pooling+==== duty3G ====
-• full media management+ 
-• intelligent backup of Oracle databases through the ORAback module+[[duty3G]] brings automation and scheduling to data center operations. Routine operations and system administration procedures can be encapsulated as duties. Duties can be scheduled to run on particular days or within a time-band. If operator input is required duty3G prompts the appropriate staff at the scheduled time, otherwise it starts the duty automatically. ‘At-request’ duties can be called up at any time. duty3g’s advantages include:
-COS/Batch+*it hides complexity: less-experienced staff can run most tasks without needing to remember complex commands
-COS/Batch has facilities for scheduling, submitting and controlling batch jobs.+*security: particular tasks requiring root privilege can be delegated to junior staff without them needing to be given the root password
-COS/Batch supports:+*automation: jobs that don’t require operator intervention run automatically at the scheduled time
-• job suites, comprising multiple related steps+*control: duty3G maintains an audit trail of what duties were performed or skipped, and whether duties that ran succeeded or failed.
-• inter-job dependencies+ 
-• flexible job scheduling+ 
-• an unlimited number of queues to stream jobs with similar priority or+==== sentinel3G ====
-requirements+
-10 Overview+[[sentinel3G]] provides network-wide event detection, service level monitoring and automated response. sentinel3G promotes a ‘service level’ approach to system management, and features:
-duty3g+*flexible response to events, including predefined automatic and manuallyinitiated responses and escalation of unresolved problems
-duty3g brings automation and scheduling to data center operations. Routine operations+*notification via e-mail, message box, fax or pager
-and system administration procedures can be encapsulated as duties. Duties can+*customized console views, allowing staff to quickly diagnose and resolve problems within their domain
-be scheduled to run on particular days or within a time-band. If operator input is+*optional knowledge bases for specific RDBMS, applications and clients
-required duty3g prompts the appropriate staff at the scheduled time, otherwise it+*interfaces to other system management products such as HP Openview and SunNet Manager
-starts the duty automatically. ‘At-request’ duties can be called up at any time.+ 
-duty3g’s advantages include:+== Setting Up and Using COSmanager ==
-• it hides complexity: less-experienced staff can run most tasks without needing+ 
-to remember complex commands+This topic provides an overview of how to install COSmanager and COSmanager applications, including setting up an initial configuration. If you are installing COSmanager for the first time, the steps are:
-• security: particular tasks requiring root privilege can be delegated to junior+#extract the FSinstall script from the COSmanager distribution
-staff without them needing to be given the root password+#install the COSmanager framework from the distribution by running the FSinstall script
-• automation: jobs that don’t require operator intervention run automatically+#set up an initial configuration for COSmanager by running a series of configuration tasks from the COSmanager configuration menu
-at the scheduled time+#install and configure each COSmanager application
-• control: duty3g maintains an audit trail of what duties were performed or+ 
-skipped, and whether duties that ran succeeded or failed.+ 
-COS/Patrol+When you restart COSmanager, the new applications will appear on your COSmanager main menu or button bar. A configuration menu for each application will appear on the Product configuration menu.
-COS/Patrol provides application and system resource monitoring, and is designed+ 
-to increase management efficiency of large-scale distributed computing environments.+ 
-COS/Patrol features:+{{Note| You should only need to run FSinstall once on a host. Once COSmanager is installed, you can use the COSmanager configuration menu to install COSmanager applications or to reinstall or upgrade the COSmanager framework.}}
-• proactive management of resources+ 
-• loadable knowledge modules+==== Installing COSmanager ====
-• built-in self-tuning and load balancing+ 
-• extensive database and platform support+To install COSmanager, you need access to a root shell, a COSmanager distribution, and a license key. The main steps in the procedure are:
-• interoperability with other management solutions+*in a root shell, unload the installation script FSinstall from the distribution into /tmp
-COS/Print+*run FSinstall. FSinstall creates the COSmanager user account and group, then copies the COSmanager files from the tape to the nominated directory
-COS/Print is an advanced network-aware print spooling and print management+*supply a license key to verify that your license is both current and valid for this host
-package for UNIX. COS/Print features:+*configure Terminfo definitions for all terminal types that will be used with COSmanager
-• print queue management, including reprinting and forward- and back-spaccosmos.+ 
-Overview 11+The installation procedure is explained in full in [[COSmanager/User_Guide/Installing_COSmanager | Installing COSmanager]]
-ing of print jobs+<br>
-• fine control over print job attributes, including job defaults or templates+ 
-• printer selection based on printer class, location and queue status+==== Initial Configuration ====
-• support for forms, filters and special stationery+ 
-• fault alerting and recovery+After installation the next step is to set up COSmanager, by logging in to the COSmanager user ID and running some or all of the configuration tasks. During configuration you will create at least one COSmanager user with Manager level access. Once this is done, access via the COSmanager account should be disabled, to prevent login access. The COSmanager account is only intended for initial setup.
-• compatibility with standard UNIX print commands (lp and lpd)+ 
-COS/Relay+The configuration procedure is described in detail in [[COSmanager/User_Guide/Configuring_COSmanager | Configuring COSmanager]]. This involves setting up details of the system management environment and specific functions to be performed.
-COS/Relay takes software from a central host and automatically compresses, distributes+ 
-and installs it on nominated target hosts. COS/Relay features:+Standard configuration uses a wide range of default settings, to which you add details of your system environment, users and administration procedures.
-• automatic software distribution and rollout+ 
-• error-checking and auditing+Customized configuration is more complex and would normally be used when setting up larger networked environments or more complex installations.
-• user-defined reusable configuration+ 
-• access control and security+Detailed planning of system management policies and procedures should take place prior to configuring COSmanager. Your COSmanager distributor can assist.
-• support for non-UNIX nodes+ 
-COS/Report+Once you have installed and configured the COSmanager framework the next task is to install your COSmanager applications. See [[COSmanager/User_Guide/Installing_Applications_and_Modules | Installing COSmanager Applications and Modules]].
-COS/Report provides secure report generation, distribution and viewing.+ 
-• reports can be taken from existing disk files or generated as required by+<br>
-another application or by COS/Report itself+ 
-• reports can be distributed by any service available on your network, including+==== Starting COSmanager ====
-network printer, e-mail or fax+ 
-• reports can be broken into logical views, so that information is tailored for+COSmanager is invoked by using the cos command. All attempts to invoke COSmanager applications are logged.
-different recipients+ 
-• multiple report generations can be stored on disk and easily retrieved+Authorized COSmanager users are system users who have been added to the COSmanager users table. They are given access to COSmanager using their own individual security profile.
-12 Overview+ 
-COS/Secure+System groups can also be added to the COSmanager users table, so users in these groups have general access to COSmanager even if they are not individually listed as COSmanager users.
-COS/Secure is a flexible framework for implementing your security policies. It provides:+ 
-• system access control, including control over login access and application+Users who are not in the COSmanager users table either personally or through their group have the privileges of the DEFAULT COSmanager user. Initially this gives only display capability. You can add other capabilities to expand access for DEFAULT users. If you remove all capabilities from the DEFAULT user then only authorized users and groups can access COSmanager.
-access+ 
-• audit trail management+
-• password strength control+
-• password aging+
-• periodic security checks as recommended by X/Open+
-COS/Sentinel+
-COS/Sentinel provides network-wide event detection, service level monitoring and+
-automated response. COS/Sentinel promotes a ‘service level’ approach to system+
-management, and features:+
-• flexible response to events, including predefined automatic and manuallyinitiated+
-responses and escalation of unresolved problems+
-• notification via e-mail, message box, fax or pager+
-• customized console views, allowing staff to quickly diagnose and resolve+
-problems within their domain+
-• optional knowledge bases for specific RDBMS, applications and clients+
-• interfaces to other system management products such as HP Openview and+
-SunNet Manager+
-COS/Chargeback+
-COS/Chargeback provides comprehensive resource accounting for distributed+
-Open Systems computing facilities. COS/Chargeback lets you monitor and calculate+
-charges for resources such as disk space, memory use, CPU time, and RDBMS use.+
-It features:+
-• data collection by user, group and project+
-• predefined ‘accountants’ for common UNIX and RDBMS services+
-Overview 13+
-• flexible charging rates+
-• output in graphical or tabular format or by export to a third-party spreadsheet,+
-presentation or data analysis package.+
-14 Overview+
-Setting Up and Using COSmanager+
-This topic provides an overview of how to install COSmanager and COSmanager+
-applications, including setting up an initial configuration.+
-If you are installing COSmanager for the first time, the steps are:+
-1. install the COSmanager framework from the distribution tape by running+
-the FSinstall script+
-2. set up an initial configuration for COSmanager by running a series of configuration+
-tasks from the COSmanager configuration menu+
-3. install and configure each COSmanager application+
-When you restart COSmanager, the new applications will appear on your COSmanager+
-main menu or button bar. A configuration menu for each application will+
-appear on the Product configuration menu.+
-Note You should only need to run FSinstall once on a host. Once+
-COSmanager is installed, you can use the COSmanager+
-configuration menu to install COSmanager applications or to+
-reinstall or upgrade the COSmanager framework.+
-Overview 15+
-Figure 1 — Overview of installing and configuring COSmanager+
-1. Install COSmanager+
-2. Run COSmanager+
-3. For each+
-initial configuration+
-from tape using+
-COSmanager product:+
-FSinstall+
-tasks+
-Install application+
-from tape through+
-the COSmanager+
-configuration menu+
-Configure the+
-application through+
-the product’s own+
-configuration menu+
-16 Overview+
-Installing COSmanager+
-To install COSmanager, you need access to a root shell, a COSmanager distribution+
-tape, and a license key. The main steps in the procedure are:+
-• in a root shell, unload the installation script FSinstall from the distribution+
-tape into /tmp+
-• run FSinstall. FSinstall creates the COSmanager user account and+
-group, then copies the COSmanager files from the tape to the nominated+
-directory+
-• supply a license key to verify that your license is both current and valid for+
-this host+
-• configure Terminfo definitions for all terminal types that will be used with+
-COSmanager+
-The installation procedure is described in full in Installing COSMOS on page 27.+
-Initial Configuration+
-After installation the next step is to set up COSmanager, by logging in to the COSmanager+
-user ID and running some or all of the configuration tasks.+
-During configuration you will create at least one COSmanager user with Manager+
-level access. Once this is done, access via the COSmanager account should be disabled,+
-to prevent login access. The COSmanager account is only intended for initial+
-setup.+
-The configuration procedure is described in detail in Configuring COSMOS on+
-page 35. This involves setting up details of the system management environment+
-and specific functions to be performed.+
-Standard configuration uses a wide range of default settings, to which you add+
-details of your system environment, users and administration procedures.+
-Customized configuration is more complex and would normally be used when setting+
-up larger networked environments or more complex installations.+
-Overview 17+
-Detailed planning of system management policies and procedures should take place+
-prior to configuring COSmanager. Your COSmanager distributor can assist.+
-Once you have installed and configured the COSmanager framework the next task+
-is to install your COSmanager applications. See Installing COSMOS Applications and+
-Modules on page 67.+
-Starting COSmanager+
-COSmanager is invoked by using the cos command. All attempts to invoke COSmanager+
-applications are logged.+
-Authorized COSmanager users are system users who have been added to the COSmanager+
-users table. They are given access to COSmanager using their own individual+
-security profile.+
-System groups can also be added to the COSmanager users table, so users in these+
-groups have general access to COSmanager even if they are not individually listed as+
-COSmanager users.+
-Users who are not in the COSmanager users table either personally or through their+
-group have the privileges of the DEFAULT COSmanager user. Initially this gives+
-only display capability. You can add other capabilities to expand access for+
-DEFAULT users. If you remove all capabilities from the DEFAULT user then only+
-authorized users and groups can access COSmanager.+
The GUI version of the main menu is a button bar: The GUI version of the main menu is a button bar:
-Figure 2 — COSmanager button bar (GUI version)+ 
-Note The options displayed depend on the user’s security profile and on+[[image:buttonbar.jpg|frame|left|Figure 2 — COSmanager button bar (GUI version)]]
-which applications are installed.+ 
-18 Overview+ 
-Selecting a button launches the main menu or window for the corresponding application.+{{Note|The options displayed depend on the user’s security profile and on which applications are installed.}}
-You can also launch an application directly from the command line:+ 
-cos application-name [ -v version ]+ 
-Examples:+Selecting a button launches the main menu or window for the corresponding application. You can also launch an application directly from the command line:
-See the cos(1) manual page for a full description of the cos command.+
-cos sentinel launches the default version of COS/Sentinel.+{{code|cos application-name [ -v version ]}}
-cos sentinel -v 1.0 launches version 1.0 of COS/Sentinel.+ 
-Overview 19+<br>
-The COSmanager Environment+ 
-This section gives a brief overview of COSmanager’s software environment. It+== The COSmanager Environment ==
-describes COSmanager’s directory structure, interfaces, and startup procedure, and+ 
-touches on customization, licensing, access security, and support procedures.+This section gives a brief overview of COSmanager’s software environment. It describes COSmanager’s directory structure, interfaces, and startup procedure, and touches on customization, licensing, access security, and support procedures.
-The COSmanager Environment+ 
-COSmanager creates an entry in the system password and group files, both called+<br>
-COSmanager. The password for the COSmanager account is set during the+=== The COSmanager Environment ===
-installation phase. This account is only used for the initial configuration.+ 
-COSmanager is installed in the home directory of the COSmanager account, by+COSmanager creates an entry in the system password and group files, both called cosmos. COSmanager is installed in the home directory of the cosmos account, by default /usr/cosmos, though you can choose a different directory. All the files are owned by cosmos and belong to the cosmos group, except for a handful of setuid commands and COSmanager tables that are owned by root or belong to group other.
-default /usr/COSmanager, though you can choose a different directory. All the+ 
-files are owned by COSmanager and belong to the COSmanager group, except+COSmanager creates its application framework and audit trails in the system spool area, and creates a crontab entry to cycle the audit trails automatically. COSmanager does not modify the UNIX kernel in any way. Only authorized COSmanager users can use a COSmanager application. Access control within COSmanager is provided through roles and capabilities, which determine each user’s ability to view or modify an application’s configuration or to run selected menu options.
-for a handful of setuid commands and COSmanager tables that are owned by root+ 
-or belong to group other.+COSmanager sets a number of variables in each COSmanager user’s environment when they start COSmanager. These mostly define directory names and the user’s access capabilities. You can check your environment by exiting to a shell from within COSmanager and running env.
-COSmanager creates its application framework and audit trails in the system spool+ 
-area, and creates a crontab entry to cycle the audit trails automatically.+The user interface is provided through a series of software tools called the Functional Toolset (see [[COSmanager_User_Man_pages | fs_tools(1)]]). Data management is handled by a set of relational database commands called The Functional Database (see [[COSmanager_Programmer_Man_pages | db(1)]]). The database provides well-defined interfaces to UNIX files, abstracted in terms of the relational database model.
-COSmanager does not modify the UNIX kernel in any way.+ 
-Only authorized COSmanager users can use a COSmanager application. Access+<br>
-control within COSmanager is provided through roles and capabilities, which determine+ 
-each user’s ability to view or modify an application’s configuration or to run+=== COSmanager Startup Procedure ===
-selected menu options.+ 
-COSmanager sets a number of variables in each COSmanager user’s environment+The cos command sets up the environment for the COSmanager user. Its main functions are as follows:
-when they start COSmanager. These mostly define directory names and the user’s+*display COSmanager version information (GUI)
-access capabilities. You can check your environment by exiting to a shell from within+*check that at least one COSmanager application has a valid licence
-COSmanager and running env.+*increase ULIMIT for this process to the maximum, to allow recovery of large files (ULIMIT is a system configuration parameter that defines the maximum size for a file)
-The user interface is provided through a series of software tools called the Functional+*execute the COSmanager profile. This sets environment variables containing print output control information, search paths, the preferred date format, and other settings
-Toolset (see fs_tools(1)). Data management is handled by a set of relational+ 
-database commands called The Functional Database (see db(1)). The+{{Note| Don’t edit the COSmanager profile. All these variables can be set from the Global parameters option under COSmanager configuration.}}
-database provides well-defined interfaces to UNIX files, abstracted in terms of the+ 
-relational database model.+*create environment variables describing COSmanager’s directory structure: its home directory ($APPL_HOME), the location of the database tables ($APPL_DB), and the application path ($APPL_PATH)
-20 Overview+*create environment variables for each of this user’s roles and capabilities. These determine which COSmanager facilities the user can access
-Figure 3 — COSmanager application structure+*check that one of the hosts on the network has been defined as the Master Administration Host
-COSmanager Startup Procedure+*if any application details have changed, rebuild this user’s top-level menu and Product configuration menu
-The cos command sets up the environment for the COSmanager user. Its main+*if authentication is required, ask for the user’s password
-functions are as follows:+*display the top-level menu or button bar for this user.
-• display COSmanager version information (GUI)+ 
-• check that at least one COSmanager application has a valid licence+<br>
-• increase ULIMIT for this process to the maximum, to allow recovery of+ 
-large files (ULIMIT is a system configuration parameter that defines the+=== Application Startup Procedure ===
-maximum size for a file)+ 
-• execute the COSmanager profile. This sets environment variables containing+When you launch an application from the COSmanager main menu or through the cos command, the following steps are also performed:
-print output control information, search paths, the preferred date format,+*check that the current version of the COSmanager framework is at least the minimum version required by this application
-and other settings+*if there is an application password, ask the user to enter it
-Note Don’t edit the COSmanager profile. All these variables can be set+*if authentication is required, ask for the user’s password
-from the Global parameters option under COSmanager+*prepend the application’s directories to the search paths.
-configuration.+*if an add-on module is installed under the application, prepend the module’s directories to the search paths
-• create environment variables describing COSmanager’s directory structure:+*create environment variables for any local roles and capabilities. These determine which facilities the user can access in this application
-its home directory ($APPL_HOME), the location of the database tables+*if there is an application profile, execute it. This sets any application-specific environment variables
-User Interface+*display the application’s top-level menu or button bar for this user.
-Application-+ 
-Specific+<br>
-Programs+=== To check the COSmanager environment ===
-Data Management+
-The Functional+
-Toolset+
-The Functional+
-Database+
-COSmanager+
-COS/Sentinel+
-backup3g+
-duty3g+
-…+
-Overview 21+
-($APPL_DB), and the application path ($APPL_PATH)+
-• create environment variables for each of this user’s roles and capabilities.+
-These determine which COSmanager facilities the user can access+
-• check that one of the hosts on the network has been defined as the Master+
-Administration Host+
-• if any application details have changed, rebuild this user’s top-level menu+
-and Product configuration menu+
-• if authentication is required, ask for the user’s password+
-• display the top-level menu or button bar for this user.+
-Application Startup Procedure+
-When you launch an application from the COSmanager main menu or through the+
-cos command, the following steps are also performed:+
-• check that the current version of the COSmanager framework is at least the+
-minimum version required by this application+
-• if there is an application password, ask the user to enter it+
-• if authentication is required, ask for the user’s password+
-• prepend the application’s directories to the search paths.+
-• if an add-on module is installed under the application, prepend the module’s+
-directories to the search paths+
-• create environment variables for any local roles and capabilities. These+
-determine which facilities the user can access in this application+
-• if there is an application profile, execute it. This sets any application-specific+
-environment variables+
-• display the application’s top-level menu or button bar for this user.+
-To check the COSmanager environment+
If you have shell access you can examine the environment variables created by COSmanager. If you have shell access you can examine the environment variables created by COSmanager.
-1. Exit to a shell from the COSmanager pulldown. Run the env command and+#Exit to a shell from the COSmanager pulldown. Run the env command and save the output in a file.
-save the output in a file.+#Exit to a shell from a COSmanager application. Run the env command and save the output in a second file.
-22 Overview+#Exit from COSmanager. Run env from the command line and save the output in a third file.
-2. Exit to a shell from a COSmanager application. Run the env command and+#Compare the output from the three env commands.
-save the output in a second file.+ 
-3. Exit from COSmanager. Run env from the command line and save the output+<br>
-in a third file.+ 
-4. Compare the output from the three env commands.+=== Licensing ===
-Licensing+ 
-COSmanager uses a host-based licensing scheme. You supply information for each+COSmanager uses a host-based licensing scheme. You supply information for each host on which the COSmanager framework and any COSmanager applications are to be run. Your COSmanager distributor will give you a set of license keys and product strings that encode information about which applications can be run on each host, and for how long (that is, whether for a trial period or indefinitely).
-host on which the COSmanager framework and any COSmanager applications are+ 
-to be run. Your COSmanager distributor will give you a set of license keys and product+{{Caution|Do not change the license key or product string. This will invalidate your license.}}
-strings that encode information about which applications can be run on each+ 
-host, and for how long (that is, whether for a trial period or indefinitely).+You will be prompted to enter the license key and product string during the installation procedure.
-Caution Do not change the license key or product string. This will invalidate your license.+ 
-You will be prompted to enter the license key and product string during the installation+Upon request, licensed COSmanager customers will be granted free of charge the right to use The Functional Toolset to develop local software applications on designated hosts.
-procedure.+ 
-Upon request, licensed COSmanager customers will be granted free of charge the+<br>
-right to use The Functional Toolset to develop local software applications on designated+ 
-hosts.+=== The COSmanager User Interface ===
-The COSmanager User Interface+ 
-The user interface to all COSmanager applications is provided through a series of+The user interface to all COSmanager applications is provided through a series of reusable software tools known collectively as The Functional Toolset. Both graphical (GUI) and character (CUI) mode interfaces are provided.
-reusable software tools known collectively as The Functional Toolset. Both graphical+ 
-(GUI) and character (CUI) mode interfaces are provided.+The GUI mode features a Motif-style ‘look and feel’. The CUI mode features a fullscreen mode with support for function keys and pop-up windows. As there are only a handful of different types of screen, the interface is very easy to learn.
-The GUI mode features a Motif-style ‘look and feel’. The CUI mode features a fullscreen+ 
-mode with support for function keys and pop-up windows. As there are only+Keyboard traversal in the GUI interface is consistent with the CUI version. This allows users to swap between X displays and character terminals with minimal retraining and without loss of productivity.
-a handful of different types of screen, the interface is very easy to learn.+ 
-Overview 23+The interface is described in detail in [[COSmanager/User_Guide/Appendices#Appendix_A_.E2.80.94_the_COSmanager_User_Interface| Appendix A—the COSmanager User Interface]].
-Keyboard traversal in the GUI interface is consistent with the CUI version. This+ 
-allows users to swap between X displays and character terminals with minimal+<br>
-retraining and without loss of productivity.+ 
-The interface is described in detail in Appendix A—the COSMOS User Interface.+=== Customizing COSmanager ===
-Customizing COSmanager+ 
-You can customize COSmanager menus, shell scripts and prompt forms to suit your+You can customize COSmanager menus, shell scripts and prompt forms to suit your site’s needs. For example, you can use COSmanager as a consistent front end to all your system administration applications by adding new options to existing COSmanager menus or to the application table.
-site’s needs. For example, you can use COSmanager as a consistent front end to all+ 
-your system administration applications by adding new options to existing COSmanager+ 
-menus or to the application table.+{{Caution| Don’t change the original COSmanager scripts. If you do, it will be harder to upgrade COSmanager and your changes may be lost. Instead, copy the file to the corresponding local directory and edit the copy.}}
-Caution Don’t change the original COSmanager scripts. If you do, it will harder to upgrade+ 
-COSmanager and your changes may be lost. Instead, copy the file to the corresponding+ 
-local directory and edit the copy.+The standard COSmanager scripts are stored in several subdirectories under $APPL_HOME, including:
-The standard COSmanager scripts are stored in several subdirectories under+:;$APPL_HOME/menu: menu description files
-$APPL_HOME, including:+:;$APPL_HOME/prompt: prompt forms
-There is a parallel directory hierarchy for your custom scripts;+:;$APPL_HOME/bin: scripts and executables
-$APPL_HOME/local. The COSmanager environment includes path variables listing+ 
-the directories to be searched for menus, executables and prompt forms. Scripts+There is a parallel directory hierarchy for your custom scripts; $APPL_HOME/local. The COSmanager environment includes path variables listing the directories to be searched for menus, executables and prompt forms. Scripts in the local directories appear earlier in the path than scripts of the same name in the COSmanager distribution.
-in the local directories appear earlier in the path than scripts of the same name in the+ 
-COSmanager distribution.+{{Caution| Don’t customize the COSmanager main menu COSmanager.menu or the COSmanager configuration menu COSconfig.menu. These are generated automatically whenever the application table is updated, so any manual edits you make will be overwritten.}}
-Caution Don’t customize the COSmanager main menu COSmanager.menu or the COSmanager+ 
-configuration menu COSconfig.menu. These are generated automatically+To add an option to the main COSmanager menu or button bar, add an entry to the application table. See To [[COSmanager/User_Guide/Managing_COSmanager_Applications#To_Add_a_Local_Application | Add a Local Application]].
-whenever the application table is updated, so any manual edits you make will be+ 
-overwritten.+<br>
-$APPL_HOME/menu menu description files+ 
-$APPL_HOME/prompt prompt forms+=== Access Security ===
-$APPL_HOME/bin scripts and executables+ 
-24 Overview+COSmanager users are assigned one or more roles. Each role identifies a responsibility or class of users in your organization, for example ‘Senior Operator’ or ‘User’. Within each COSmanager application, roles are defined in terms of the access capabilities they grant. In turn, capabilities determine what menu options and actions the user can perform.
-To add an option to the main COSmanager menu or button bar, add an entry to the+ 
-application table. See To Add a Local Application on page 83.+Users are granted access to COSmanager via options in the COSmanager configuration menu.
-Access Security+ 
-COSmanager users are assigned one or more roles. Each role identifies a responsibility+The default configuration (as distributed) includes the COSmanager user account, which is specified with the highest security level and super user privileges. This is provided to enable initial setup of security levels and super users.
-or class of users in your organization, for example ‘Senior Operator’ or ‘User’.+ 
-Within each COSmanager application, roles are defined in terms of the access capabilities+A number of roles are provided with COSmanager, including [[Manager]], [[Config]], [[Admin]], [[Auditor]], [[User]], and [[SeniorOp]].
-they grant. In turn, capabilities determine what menu options and actions the+ 
-user can perform.+ 
-Users are granted access to COSmanager via options in the COSmanager configuration+{{Note| Changes made to a user’s security profile don’t come into effect until the next time the user invokes COSmanager.}}
-menu.+ 
-The default configuration (as distributed) includes the COSmanager user account,+ 
-which is specified with the highest security level and super user privileges. This is provided+Many functions, particularly those that modify system files and COSmanager tables, require specific access capabilities. Users who do not have the right capabilities will not be able to access or even view these functions.
-to enable initial setup of security levels and super users.+ 
-A number of roles are provided with COSmanager, including Manager, Config,+<br>
-Admin, Auditor, User, and SeniorOp.+ 
-Note Changes made to a user’s security profile don’t come into effect until+=== Application Development ===
-the next time the user invokes COSmanager.+ 
-Many functions, particularly those that modify system files and COSmanager tables,+The Functional Toolset is the enabling technology used to develop COSmanager applications. It comprises a suite of reusable software tools and a database management system.
-require specific access capabilities. Users who do not have the right capabilities will+ 
-not be able to access or even view these functions.+The tools implement a consistent and well-defined user interface. The database allows full relational databases to be built and manipulated under UNIX using flat files for tables.
-Application Development+ 
-The Functional Toolset is the enabling technology used to develop COSmanager+Upon request, licensed COSmanager customers will be granted free of charge the right to use the Toolset to develop local software applications on designated hosts, for example to add to the facilities provided by COSmanager. See your COSmanager distributor to apply for a license.
-applications. It comprises a suite of reusable software tools and a database management+ 
-system.+{{Note|Support for local applications developed using the Toolset may be provided at the discretion of your COSmanager distributor. Such support is not covered under the terms and conditions of the COSmanager maintenance agreement.}}
-Overview 25+ 
-The tools implement a consistent and well-defined user interface. The database+<br>
-allows full relational databases to be built and manipulated under UNIX using flat+ 
-files for tables.+=== Customer Support Procedures ===
-Upon request, licensed COSmanager customers will be granted free of charge the+ 
-right to use the Toolset to develop local software applications on designated hosts,+On installation of COSmanager, clients will be provided with support service contact numbers and details of problem management procedures. Problems that are notified to Functional Software will be logged and tracked through to resolution. Normally, software modifications will not be distributed immediately to clients. At regular intervals, these modifications will be incorporated into a new version of COSmanager.
-for example to add to the facilities provided by COSmanager. See your COSmanager+ 
-distributor to apply for a license.+<br>
-Note Support for local applications developed using the Toolset may be+
-provided at the discretion of your COSmanager distributor. Such+
-support is not covered under the terms and conditions of the+
-COSmanager maintenance agreement.+
-Customer Support Procedures+
-On installation of COSmanager, clients will be provided with support service contact+
-numbers and details of problem management procedures.+
-Problems that are notified to Functional Software will be logged and tracked+
-through to resolution.+
-Normally, software modifications will not be distributed immediately to clients. At+
-regular intervals, these modifications will be incorporated into a new version of+
-COSmanager.+

Current revision

Contents

[edit]

Overview

This chapter introduces you to COSmanager both from a management and a technical perspective. At a management level, it explains:


At a technical level, it introduces you to:


This section contains useful information for helping you prepare to install and use COSmanager. However, if you wish to get started immediately, skip to Installing COSmanager.


[edit]

Management Overview

COSmanager facilitates a standard approach to the management of distributed Open Systems data centers, through:


It provides:


[edit]

COSmanager Applications

COSmanager comprises a suite of applications that cover all the main areas of system management. These applications are designed to work well together and to integrate with third-party products.


[edit]

admin3G

admin3G provides a consistent interface to system administration and user management in multi-vendor, multi-host environments. It includes a comprehensive set of facilities that standardize and improve on the basic services provided by individual vendors. COSadmin services include:

[edit]

backup3G

backup3G provides policy-based backup and data recovery in Open Systems data centers. backup3g’s flexible client/server model supports both centralized and distributed backup models, including backup of non-UNIX clients.

backup3G also supports:


[edit]

duty3G

duty3G brings automation and scheduling to data center operations. Routine operations and system administration procedures can be encapsulated as duties. Duties can be scheduled to run on particular days or within a time-band. If operator input is required duty3G prompts the appropriate staff at the scheduled time, otherwise it starts the duty automatically. ‘At-request’ duties can be called up at any time. duty3g’s advantages include:


[edit]

sentinel3G

sentinel3G provides network-wide event detection, service level monitoring and automated response. sentinel3G promotes a ‘service level’ approach to system management, and features:

[edit]

Setting Up and Using COSmanager

This topic provides an overview of how to install COSmanager and COSmanager applications, including setting up an initial configuration. If you are installing COSmanager for the first time, the steps are:

  1. extract the FSinstall script from the COSmanager distribution
  2. install the COSmanager framework from the distribution by running the FSinstall script
  3. set up an initial configuration for COSmanager by running a series of configuration tasks from the COSmanager configuration menu
  4. install and configure each COSmanager application


When you restart COSmanager, the new applications will appear on your COSmanager main menu or button bar. A configuration menu for each application will appear on the Product configuration menu.


Note
 Note
You should only need to run FSinstall once on a host. Once COSmanager is installed, you can use the COSmanager configuration menu to install COSmanager applications or to reinstall or upgrade the COSmanager framework.
[edit]

Installing COSmanager

To install COSmanager, you need access to a root shell, a COSmanager distribution, and a license key. The main steps in the procedure are:

The installation procedure is explained in full in Installing COSmanager

[edit]

Initial Configuration

After installation the next step is to set up COSmanager, by logging in to the COSmanager user ID and running some or all of the configuration tasks. During configuration you will create at least one COSmanager user with Manager level access. Once this is done, access via the COSmanager account should be disabled, to prevent login access. The COSmanager account is only intended for initial setup.

The configuration procedure is described in detail in Configuring COSmanager. This involves setting up details of the system management environment and specific functions to be performed.

Standard configuration uses a wide range of default settings, to which you add details of your system environment, users and administration procedures.

Customized configuration is more complex and would normally be used when setting up larger networked environments or more complex installations.

Detailed planning of system management policies and procedures should take place prior to configuring COSmanager. Your COSmanager distributor can assist.

Once you have installed and configured the COSmanager framework the next task is to install your COSmanager applications. See Installing COSmanager Applications and Modules.


[edit]

Starting COSmanager

COSmanager is invoked by using the cos command. All attempts to invoke COSmanager applications are logged.

Authorized COSmanager users are system users who have been added to the COSmanager users table. They are given access to COSmanager using their own individual security profile.

System groups can also be added to the COSmanager users table, so users in these groups have general access to COSmanager even if they are not individually listed as COSmanager users.

Users who are not in the COSmanager users table either personally or through their group have the privileges of the DEFAULT COSmanager user. Initially this gives only display capability. You can add other capabilities to expand access for DEFAULT users. If you remove all capabilities from the DEFAULT user then only authorized users and groups can access COSmanager.

The GUI version of the main menu is a button bar:

Figure 2 — COSmanager button bar (GUI version)
Figure 2 — COSmanager button bar (GUI version)


Note
 Note
The options displayed depend on the user’s security profile and on which applications are installed.


Selecting a button launches the main menu or window for the corresponding application. You can also launch an application directly from the command line:


code cos application-name [ -v version ]


[edit]

The COSmanager Environment

This section gives a brief overview of COSmanager’s software environment. It describes COSmanager’s directory structure, interfaces, and startup procedure, and touches on customization, licensing, access security, and support procedures.


[edit]

The COSmanager Environment

COSmanager creates an entry in the system password and group files, both called cosmos. COSmanager is installed in the home directory of the cosmos account, by default /usr/cosmos, though you can choose a different directory. All the files are owned by cosmos and belong to the cosmos group, except for a handful of setuid commands and COSmanager tables that are owned by root or belong to group other.

COSmanager creates its application framework and audit trails in the system spool area, and creates a crontab entry to cycle the audit trails automatically. COSmanager does not modify the UNIX kernel in any way. Only authorized COSmanager users can use a COSmanager application. Access control within COSmanager is provided through roles and capabilities, which determine each user’s ability to view or modify an application’s configuration or to run selected menu options.

COSmanager sets a number of variables in each COSmanager user’s environment when they start COSmanager. These mostly define directory names and the user’s access capabilities. You can check your environment by exiting to a shell from within COSmanager and running env.

The user interface is provided through a series of software tools called the Functional Toolset (see fs_tools(1)). Data management is handled by a set of relational database commands called The Functional Database (see db(1)). The database provides well-defined interfaces to UNIX files, abstracted in terms of the relational database model.


[edit]

COSmanager Startup Procedure

The cos command sets up the environment for the COSmanager user. Its main functions are as follows:


Note
 Note
Don’t edit the COSmanager profile. All these variables can be set from the Global parameters option under COSmanager configuration.


[edit]

Application Startup Procedure

When you launch an application from the COSmanager main menu or through the cos command, the following steps are also performed:


[edit]

To check the COSmanager environment

If you have shell access you can examine the environment variables created by COSmanager.

  1. Exit to a shell from the COSmanager pulldown. Run the env command and save the output in a file.
  2. Exit to a shell from a COSmanager application. Run the env command and save the output in a second file.
  3. Exit from COSmanager. Run env from the command line and save the output in a third file.
  4. Compare the output from the three env commands.


[edit]

Licensing

COSmanager uses a host-based licensing scheme. You supply information for each host on which the COSmanager framework and any COSmanager applications are to be run. Your COSmanager distributor will give you a set of license keys and product strings that encode information about which applications can be run on each host, and for how long (that is, whether for a trial period or indefinitely).


Caution
 Caution!
Do not change the license key or product string. This will invalidate your license.

You will be prompted to enter the license key and product string during the installation procedure.

Upon request, licensed COSmanager customers will be granted free of charge the right to use The Functional Toolset to develop local software applications on designated hosts.


[edit]

The COSmanager User Interface

The user interface to all COSmanager applications is provided through a series of reusable software tools known collectively as The Functional Toolset. Both graphical (GUI) and character (CUI) mode interfaces are provided.

The GUI mode features a Motif-style ‘look and feel’. The CUI mode features a fullscreen mode with support for function keys and pop-up windows. As there are only a handful of different types of screen, the interface is very easy to learn.

Keyboard traversal in the GUI interface is consistent with the CUI version. This allows users to swap between X displays and character terminals with minimal retraining and without loss of productivity.

The interface is described in detail in Appendix A—the COSmanager User Interface.


[edit]

Customizing COSmanager

You can customize COSmanager menus, shell scripts and prompt forms to suit your site’s needs. For example, you can use COSmanager as a consistent front end to all your system administration applications by adding new options to existing COSmanager menus or to the application table.


Caution
 Caution!
Don’t change the original COSmanager scripts. If you do, it will be harder to upgrade COSmanager and your changes may be lost. Instead, copy the file to the corresponding local directory and edit the copy.


The standard COSmanager scripts are stored in several subdirectories under $APPL_HOME, including:

$APPL_HOME/menu
menu description files
$APPL_HOME/prompt
prompt forms
$APPL_HOME/bin
scripts and executables

There is a parallel directory hierarchy for your custom scripts; $APPL_HOME/local. The COSmanager environment includes path variables listing the directories to be searched for menus, executables and prompt forms. Scripts in the local directories appear earlier in the path than scripts of the same name in the COSmanager distribution.


Caution
 Caution!
Don’t customize the COSmanager main menu COSmanager.menu or the COSmanager configuration menu COSconfig.menu. These are generated automatically whenever the application table is updated, so any manual edits you make will be overwritten.

To add an option to the main COSmanager menu or button bar, add an entry to the application table. See To Add a Local Application.


[edit]

Access Security

COSmanager users are assigned one or more roles. Each role identifies a responsibility or class of users in your organization, for example ‘Senior Operator’ or ‘User’. Within each COSmanager application, roles are defined in terms of the access capabilities they grant. In turn, capabilities determine what menu options and actions the user can perform.

Users are granted access to COSmanager via options in the COSmanager configuration menu.

The default configuration (as distributed) includes the COSmanager user account, which is specified with the highest security level and super user privileges. This is provided to enable initial setup of security levels and super users.

A number of roles are provided with COSmanager, including Manager, Config, Admin, Auditor, User, and SeniorOp.


Note
 Note
Changes made to a user’s security profile don’t come into effect until the next time the user invokes COSmanager.


Many functions, particularly those that modify system files and COSmanager tables, require specific access capabilities. Users who do not have the right capabilities will not be able to access or even view these functions.


[edit]

Application Development

The Functional Toolset is the enabling technology used to develop COSmanager applications. It comprises a suite of reusable software tools and a database management system.

The tools implement a consistent and well-defined user interface. The database allows full relational databases to be built and manipulated under UNIX using flat files for tables.

Upon request, licensed COSmanager customers will be granted free of charge the right to use the Toolset to develop local software applications on designated hosts, for example to add to the facilities provided by COSmanager. See your COSmanager distributor to apply for a license.


Note
 Note
Support for local applications developed using the Toolset may be provided at the discretion of your COSmanager distributor. Such support is not covered under the terms and conditions of the COSmanager maintenance agreement.


[edit]

Customer Support Procedures

On installation of COSmanager, clients will be provided with support service contact numbers and details of problem management procedures. Problems that are notified to Functional Software will be logged and tracked through to resolution. Normally, software modifications will not be distributed immediately to clients. At regular intervals, these modifications will be incorporated into a new version of COSmanager.


Retrieved from "https://documentation.fs.com.au/index.php/COSmanager/User_Guide/Overview"
Home : About : Contact Us : Site Map : Terms of Use
All trademarks and registered trademarks of products mentioned in this web site are recognised by Functional Software. Site content and images © 1997-2021 Functional Software