Admin-Admin User Interface

Version 3 (Paul Holland, 03/29/2012 07:32 pm)

1 1 Paul Holland
h1. Administering FOSSology
2 1 Paul Holland
3 1 Paul Holland
The default administrator for fossology is the user +fossy+.  Any user with access level of *Full Administrator* is an admin.  Most users of fossology do not need to be an administrator.  Granting most users an access level of *Analyze* will allow them to upload files and perform analysis on those files as well as create their own folders and administer their own account. *Note* users with analyze permissions cannot delete folders or uploads (even their own).  Only admins can remove folders and uploads. 
4 1 Paul Holland
5 1 Paul Holland
Users with *delete* or *debug* access levels (which are greater than *analyze* level), can remove their own folders and uploads.
6 1 Paul Holland
7 1 Paul Holland
h2. Performing Administrative Functions
8 1 Paul Holland
9 2 Paul Holland
!ui-menu-admin.png!
10 1 Paul Holland
11 1 Paul Holland
h3. Buckets
12 1 Paul Holland
13 1 Paul Holland
Buckets are an advanced feature that allows arbitrary grouping of items.  For example, a bucket could be defined to hold any license that matches GPL.
14 1 Paul Holland
15 2 Paul Holland
!buckets-menu.png!
16 1 Paul Holland
17 1 Paul Holland
Before creating or modifying an existing bucket it's important to make sure that the user understands [[buckets|Creating Bucket Pools]].
18 1 Paul Holland
19 2 Paul Holland
!bucket-duplicate.png!
20 1 Paul Holland
21 1 Paul Holland
h3. Customize 
22 1 Paul Holland
23 1 Paul Holland
The customize menu allows the administrator to customize the FOSSology web site.  See [[config-How to Configure the FOSSology site|Configuring the FOSSology Site]] for the details.
24 1 Paul Holland
25 3 Paul Holland
!admin-customize.png!
26 1 Paul Holland
27 1 Paul Holland
h3. Dashboard 
28 1 Paul Holland
29 1 Paul Holland
*Dashboard* provides a quick, useful overview of Job Queue, Database Contents, Repository Disk Space, and Database Metrics.
30 1 Paul Holland
31 1 Paul Holland
32 1 Paul Holland
!ui-menu-dashboard.png!
33 1 Paul Holland
34 1 Paul Holland
35 1 Paul Holland
When you select *Admin > Dashboard*, as shown above, the following screen is displayed.  Note that the *Job Queue* information provides links to additional information.
36 1 Paul Holland
37 1 Paul Holland
38 1 Paul Holland
!ui-menu-admin-dashboard-screen-v1.png!
39 1 Paul Holland
40 1 Paul Holland
41 1 Paul Holland
h3. Database Administration
42 1 Paul Holland
43 1 Paul Holland
Checking the Database, Database performance
44 1 Paul Holland
45 1 Paul Holland
!ui-menu-admin-database.png!
46 1 Paul Holland
47 1 Paul Holland
h4. Checking the Database for Inconsistencies
48 1 Paul Holland
49 1 Paul Holland
On occasion, the database can become inconsistent. For example, there may be pfile records without ufile entries, or ufile entries that are not linked by any uploadtree records. Inconsistencies usually arise due to failed unpacking, partial deletions, and testing. 
50 1 Paul Holland
51 1 Paul Holland
Temporary inconsistencies may exist when a file is uploaded, being unpacked, or being deleted.
52 1 Paul Holland
53 1 Paul Holland
  * An uploaded file -- before being unpacked -- can appear inconsistent.
54 1 Paul Holland
  * The unpack system creates ufiles and pfiles first, then links them together when it completes.
55 1 Paul Holland
  * The delete system removes records in series, so a partial delete (or delete in progress) can show inconsistencies. 
56 1 Paul Holland
57 1 Paul Holland
*Admin > Database > Check* provides information about tasks running in the job queue that may make records appear inconsistent.
58 1 Paul Holland
59 1 Paul Holland
*Admin > Database > Check Templates* provides information about license templates that require cleaning-up, and provides clean-up capabilities.
60 1 Paul Holland
61 1 Paul Holland
h4. Improving Database Performance
62 1 Paul Holland
63 1 Paul Holland
Database performance can be improved by optimizing table memory allocation. The database supports two methods:
64 1 Paul Holland
65 1 Paul Holland
  *  *vacuum* to free deleted rows
66 1 Paul Holland
  *  *analyze* to precompute row counts
67 1 Paul Holland
68 1 Paul Holland
These two functions are called by most agents on an as-needed basis. However, you can also start them yourself when needed. 
69 1 Paul Holland
70 1 Paul Holland
Keep in mind that running these functions too often can also negatively impact database performance, since the database will spend more time cleaning than doing real work.
71 1 Paul Holland
72 1 Paul Holland
*Admin > Database > Vacuum and Analyze* provides access to these functions. 
73 1 Paul Holland
74 1 Paul Holland
h4. Viewing, Exporting, and Applying Database Schema
75 1 Paul Holland
76 1 Paul Holland
*Admin > Database > Schema* is only used for installation and debugging purposes.  Otherwise, you should not need to use this functionality. 
77 1 Paul Holland
78 1 Paul Holland
It is strongly advised that you do not use *Schema* functionality unless you are a very experienced FOSSology administrator and know exactly what you are doing.
79 1 Paul Holland
80 1 Paul Holland
+*WARNING!*    Improper use of this functionality can destroy your FOSSology database!+
81 1 Paul Holland
  
82 1 Paul Holland
h3. Groups
83 1 Paul Holland
84 1 Paul Holland
Use the Groups menu to define [[how_to_use_tags_and_groups|Groups and Tags]].
85 1 Paul Holland
86 1 Paul Holland
!ui-admin-groups.png!
87 1 Paul Holland
88 1 Paul Holland
h3. Viewing Agent Status
89 1 Paul Holland
90 1 Paul Holland
You can view the Show Agent Status screen by selecting *Admin > Scheduler> Status*.
91 1 Paul Holland
92 1 Paul Holland
!ui-menu-admin-scheduler.png!
93 1 Paul Holland
94 1 Paul Holland
!ui-menu-admin-scheduler-status-screen.png!
95 1 Paul Holland
96 1 Paul Holland
h3. License Administration
97 1 Paul Holland
98 1 Paul Holland
To administer the various license types, use the *Admin > License Admin* menu.
99 1 Paul Holland
100 1 Paul Holland
!ui-admin-licenseAdmin.png!
101 1 Paul Holland
102 1 Paul Holland
h3. Administering Users
103 1 Paul Holland
104 1 Paul Holland
*Admin > Users* provides a means of user account administration.  You can add or delete users, edit user account information, and set various user-specific security and access paramaters.
105 1 Paul Holland
106 2 Paul Holland
!ui-menu-admin-users.png!
107 1 Paul Holland
108 1 Paul Holland
109 1 Paul Holland
h3. keep me for now... use for the orig ui discussion
110 1 Paul Holland
111 1 Paul Holland
The options vary based on where the data to upload is located. The data can be uploaded from:
112 1 Paul Holland
113 1 Paul Holland
    * Your browser system - Use the *Upload > from File* option to select and upload the file. While this can be very convenient (particularly if the file is not readily accessible online), uploading via your web browser can be slow for large files, and files larger than 650 Megabytes may not be uploadable.
114 1 Paul Holland
115 1 Paul Holland
    * The FOSSology web server. Use the *Upload > from Server* option to specify a file or path on the web server. This option is intended for developers who have mounted directories containing source trees. The directory must be accessible via the web server's user.
116 1 Paul Holland
117 1 Paul Holland
    * A remote server - Use the *Upload > from URL* option to specify a remote server. This is the most flexible option, but the URL must denote a publicly accessible HTTP, HTTPS, or FTP location. URLs that require authentication or human interactions cannot be downloaded through this automated system.
118 1 Paul Holland
119 1 Paul Holland
Use the *Upload > One-Shot Analysis* option to upload a single file for license analysis (similar to upload from file). The analysis is done in real-time.  Note the limitations that are listed on the *One-Shot License Analysis* screen.
120 1 Paul Holland
121 1 Paul Holland
Use the *Upload > One-Shot Copyright/Email/URL* option to upload a single file for copyright, email and URL analysis (similar to upload from file). The analysis is done in real-time.  Note the limitations that are listed on the *One-Shot Copyright/Email/URL* screen.
122 1 Paul Holland
123 1 Paul Holland
If your system is configured to use multiple agent servers, the data area must be mounted and accessible to the FOSSology user (fossy) on every agent system. See the section [[scheduler#Configuring the Scheduler]] in the [[Scheduler]] documentation.