Portal3G Customization Files
This page was last modified 01:08, 16 April 2007.From Documentation
(Difference between revisions)
| Revision as of 01:05, 16 April 2007 Daniels (Talk | contribs) (→General Configuration) ← Previous diff |
Current revision Daniels (Talk | contribs) |
||
| Line 17: | Line 17: | ||
| *:This file defines the help popups that are available through the portal3G interface. | *:This file defines the help popups that are available through the portal3G interface. | ||
| - | ====http.ini==== | + | *http.ini |
| + | *:This is the HTTP local machine configuration, to help portal3G interface with the web server installation. | ||
| - | This is the HTTP local machine configuration, to help portal3G interface with the web server installation. | + | *icon_mapping |
| + | *:allows the overlay of a new icon set, without the need to edit the Unix side source of sentinel3G | ||
| - | ====icon_mapping==== | + | *modules.ini |
| - | + | *:Defines which modules are available for the top banner bar. At the moment, only Event History is supported in this position. | |
| - | allows the overlay of a new icon set, without the need to edit the Unix side source of sentinel3G | + | |
| - | + | ||
| - | ====modules.ini==== | + | |
| - | + | ||
| - | Defines which modules are available for the top banner bar. At the moment, only Event History is supported in this position. | + | |
| === View Configuration === | === View Configuration === | ||
| - | ====banner.ini==== | + | *banner.ini |
| + | *:Describes the behaviour and appearance of the top banner bar. | ||
| - | Describes the behaviour and appearance of the top banner bar. | + | *global.ini |
| + | *:This is the big one. This file describes most of the configurable settings for each portal3G installation. | ||
| - | ====global.ini==== | + | *windows.ini |
| - | + | *:Describes the default appearance of window types | |
| - | This is the big one. This file describes most of the configurable settings for each portal3G installation. | + | |
| - | + | ||
| - | ====windows.ini==== | + | |
| - | + | ||
| - | Describes the default appearance of window types | + | |
| === Report Configuration === | === Report Configuration === | ||
| Line 47: | Line 41: | ||
| The files listed below affect the look and behaviour of the generated reports. For the most part, the descriptions are the same, and most of the content is very similar. | The files listed below affect the look and behaviour of the generated reports. For the most part, the descriptions are the same, and most of the content is very similar. | ||
| - | ====availability.ini==== | + | *availability.ini |
| + | *:This file contains the definitions for the availability reports. You can define things such as image size, parameters, period, titles and descriptions. This is generally a compound report, so this file also allows you to configure each sub-report individually. | ||
| - | This file contains the definitions for the availability reports. You can define things such as image size, parameters, period, titles and descriptions. This is generally a compound report, so this file also allows you to configure each sub-report individually. | + | *availability_transaction.ini |
| + | *:This file contains the definitions for the availability reports. You can define things such as image size, parameters, period, titles and descriptions. This is generally a compound report, so this file also allows you to configure each sub-report individually. | ||
| - | ====availability_transaction.ini==== | + | *content_transaction.ini |
| + | *:This file contains the definitions for the availability reports. You can define things such as image size, parameters, period, titles and descriptions. This is generally a compound report, so this file also allows you to configure each sub-report individually. | ||
| - | This file contains the definitions for the availability reports. You can define things such as image size, parameters, period, titles and descriptions. This is generally a compound report, so this file also allows you to configure each sub-report individually. | + | *customer.ini |
| + | *: customer ini | ||
| + | *email.ini | ||
| + | *: | ||
| - | ====content_transaction.ini==== | + | *halfpoint_transaction.ini |
| + | *:This file contains the definitions for the availability reports. You can define things such as image size, parameters, period, titles and descriptions. This is generally a compound report, so this file also allows you to configure each sub-report individually. | ||
| - | This file contains the definitions for the availability reports. You can define things such as image size, parameters, period, titles and descriptions. This is generally a compound report, so this file also allows you to configure each sub-report individually. | + | *https_transaction.ini |
| + | *:This file contains the definitions for the availability reports. You can define things such as image size, parameters, period, titles and descriptions. This is generally a compound report, so this file also allows you to configure each sub-report individually. | ||
| - | ====customer.ini==== | + | *security.ini |
| + | *service_details.ini | ||
| - | ====email.ini==== | + | *service_summary.ini |
| - | + | *transaction_summary.ini | |
| - | + | ||
| - | ====halfpoint_transaction.ini==== | + | |
| - | + | ||
| - | This file contains the definitions for the availability reports. You can define things such as image size, parameters, period, titles and descriptions. This is generally a compound report, so this file also allows you to configure each sub-report individually. | + | |
| - | + | ||
| - | ====https_transaction.ini==== | + | |
| - | + | ||
| - | This file contains the definitions for the availability reports. You can define things such as image size, parameters, period, titles and descriptions. This is generally a compound report, so this file also allows you to configure each sub-report individually. | + | |
| - | + | ||
| - | ====security.ini==== | + | |
| - | + | ||
| - | ====service_details.ini==== | + | |
| - | + | ||
| - | ====service_summary.ini==== | + | |
| - | + | ||
| - | ====transaction_summary.ini==== | + | |
| == Global Menu Configuration Files == | == Global Menu Configuration Files == | ||
| Line 86: | Line 73: | ||
| The base set of files located in the global menu configuration directory are: | The base set of files located in the global menu configuration directory are: | ||
| - | ====corporate.menu==== | + | *corporate.menu |
| - | + | *other.menu | |
| - | ====other.menu==== | + | *partners.menu |
| - | + | *reports.menu | |
| - | ====partners.menu==== | + | *resellers.menu |
| - | + | *tabs.menu | |
| - | ====reports.menu==== | + | *tools.menu |
| - | + | ||
| - | ====resellers.menu==== | + | |
| - | + | ||
| - | ====tabs.menu==== | + | |
| - | + | ||
| - | ====tools.menu==== | + | |
Current revision
Contents |
[edit]
Global Configuration Files
[edit]
General Configuration
Most of the files in this section should not need to be changed.
- arp.ini
- This file simply contains the path to the Arp program.
- discovery.ini
- This file allows detection of Knowledge Bases, and tests connectivity.
- eventmgr.ini
- This file contains a list of available Event Hosts. They will be displayed in order of appearance on this list on the login screen. This only needs changing if you are running multiple Event Hosts through a single portal3G installation.
- help.ini
- This file defines the help popups that are available through the portal3G interface.
- http.ini
- This is the HTTP local machine configuration, to help portal3G interface with the web server installation.
- icon_mapping
- allows the overlay of a new icon set, without the need to edit the Unix side source of sentinel3G
- modules.ini
- Defines which modules are available for the top banner bar. At the moment, only Event History is supported in this position.
[edit]
View Configuration
- banner.ini
- Describes the behaviour and appearance of the top banner bar.
- global.ini
- This is the big one. This file describes most of the configurable settings for each portal3G installation.
- windows.ini
- Describes the default appearance of window types
[edit]
Report Configuration
The files listed below affect the look and behaviour of the generated reports. For the most part, the descriptions are the same, and most of the content is very similar.
- availability.ini
- This file contains the definitions for the availability reports. You can define things such as image size, parameters, period, titles and descriptions. This is generally a compound report, so this file also allows you to configure each sub-report individually.
- availability_transaction.ini
- This file contains the definitions for the availability reports. You can define things such as image size, parameters, period, titles and descriptions. This is generally a compound report, so this file also allows you to configure each sub-report individually.
- content_transaction.ini
- This file contains the definitions for the availability reports. You can define things such as image size, parameters, period, titles and descriptions. This is generally a compound report, so this file also allows you to configure each sub-report individually.
- customer.ini
- customer ini
- email.ini
- halfpoint_transaction.ini
- This file contains the definitions for the availability reports. You can define things such as image size, parameters, period, titles and descriptions. This is generally a compound report, so this file also allows you to configure each sub-report individually.
- https_transaction.ini
- This file contains the definitions for the availability reports. You can define things such as image size, parameters, period, titles and descriptions. This is generally a compound report, so this file also allows you to configure each sub-report individually.
- security.ini
- service_details.ini
- service_summary.ini
- transaction_summary.ini
[edit]
Global Menu Configuration Files
The base set of files located in the global menu configuration directory are:
- corporate.menu
- other.menu
- partners.menu
- reports.menu
- resellers.menu
- tabs.menu
- tools.menu