|
|
| |
|
 |
|
|
 |
|
| |
| Yes, select Tools/Options and go to
the 'Data Source Options' tab.
Then select the 'Automatically use this data source' option and click
the '>>'
button to select a data source. |
|
The upgrade process is completely automated.
Run omnianalyser.msi on the Integration Server to update the OmniAnalyser™ Integration
Server and webreports.msi to update the Web Reports. Then run a new Agent setup on each monitored server. Agents will upgrade automatically. |
| You need to create
a separate mailbox or Notes ID with mail file
for every monitored server, and one additional for the OmniAnalyser™
console. A single NT account (for
Exchange) or even the LocalSystem account (for Domino) can be used for
all OmniAnalyser™ services.
|
| It is strongly recommended to place
the agent software on the scanned
server, but as an exception, the agent can also be installed on a machine
which can access the scanned server via a LAN. The Integration Server and
the Web Reporting Server can be installed on one server as well as on separate machines in the same LAN. Higher performance may be achieved by installing OmniAnalyser™ Integration Server on the
same machine with SQL Server. It is also desirable to install
the Web Reporting Server there; in this case, IIS is also necessary on this machine
in order to publish Web Reports. |
| Install OmniAgent™ on a target server. Switch to Servers view in
the OmniAnalyser™ console, then right-click the blank area and select 'New' from the pop-up menu (alternatively, use “Edit/New” in the main menu). Specify the server’s name in the dialog box that appears. Select
the OmniAgent™ address by clicking 'Choose from Address Book'.
Check the requests that correspond to installed OmniAgent™ components. |
|
| |
|
 |
|
| |
There are 3 Agent states that may have different overhead:
background process, data acquisition process and mail scanning
process:
a) The background process uses about 10 MB of RAM as an NT service,
which runs at a specific interval. The schedule can be configured to any
time period you like, the default is every ten minutes.
b) The data acquisition process runs whenever there is a data
request, normally once a day. It consumes up to 20 MB of RAM and runs for about 5 minutes depending on the size of a tracking log
to be processed.
c) The mail scanning process runs usually once a night. For large
mail databases it can create a load of up to 60% CPU usage and
take several hours to complete. |
|
OmniAnalyser™
will not corrupt data in the situation described above. Mail and
data processing will continue next time OmniAnalyser™ launched. |
|
This error appears after there has been no user activity for
an extended period of time (by default 20 minutes). This is caused
by the built-in session timeout function of Microsoft Internet Information Server. When this message appears,
you should log off from the Web Reports and then log on again. If
the error appears frequently, you can increase the session timeout
value in the IIS manager. |
|
Yes, starting
from version 8. First, do a directory import using Tools, Import
GAL. Then right-click the server to be managed and select
“Manage options”. |
|
Both the OmniAnalyser™ server and agent
accounts must be local Administrators and have the “Logon as a service”
right. For additional requirements necessary for specific functions, please refer to
the OmniAnalyser™ manual. |
|
Yes. Prepare a service account with all required rights as
described in the OmniAnalyser™ manual. Log on using this account, configure its
MAPI profile to the OmniAnalyser™ mailbox, start OmniAnalyser™ and set it
to use the data source automatically. Select "Tools\Options\Directory import" and
uncheck “Show this window when importing GAL”. Start
"Programs\Hypersoft OmniAnalyser\Service\Install OmniAnalyser™ service" and type
in the required account information. Stop the service before working with the
OmniAnalyser™ console and performing any changes in the OmniAnalyser™ settings. |
|
OmniAnalyser™ logs its activity. The resulting log files are named in
accordance with the following convention: "HALog[<Year>-<Month>-<Day>][<Hour>h
<Minutes>m <Seconds>s].txt" and written
into the OmniAnalyser™ installation folder, subfolder Logs. There are two logging levels: Normal and Advanced. To choose a logging level, go to the Tools/Options/Logging tab. If 'Advanced' is selected,
OmniAnalyser™ will log almost everything it does, so log files may grow up dramatically and occupy a lot of space on the hard disk. The same logging options are available for
the OmniAnalyser™ Agent and all Agent components. |
|
To view the
OmniAnalyser™ reports, Internet Explorer 5.5 or higher and MSXML
3.0 or higher is required. It is not necessary to have any part
of OmniAnalyser™ or other software installed on your computer.
The user that will be viewing the reports should have access
rights to the OmniAnalyser™ database, otherwise he will not be
able to log in to the Web Reports. Please refer to the section 'Roles
and Permissions Management' of the Product Guide for further
information on the rights required to generate and schedule reports. |
|
The OmniAgent can
only answer requests corresponding to
installed components. Make sure in ´the OmniAnalyser™ console that
the request types enabled for every
server only include components installed on this server.
|
| Install and use
the OmniAnalyser™ Integration Server on the same machine that runs SQL server;
make sure the SQL Server is dedicated to
OmniAnalyser&trade,. Use high-performance RAID, CPU and memory for
the SQL server. Place the OmniAnalyser™ database file and transaction log on separate physical disks. |
| Click on the 'Export' link in the desired report's control
bar. This will copy the content of the current report page to the clipboard. Start Excel
or another application, and choose Edit/Paste from its menu. |
|
After you specified the filters for the
desired web report,
press the 'Schedule' button instead of the 'Generate' button. Set
the necessary scheduling and delivery
options. |
|
Regularly
check the reports “OmniAnalysesr™ operation status“ and
“Availability of information from servers”.
|
|
Use the web report "Database State" in the "OmniAnalyser™ Tools" folder.
|
|
Manually with the OmniAnalyser™ menu item "Tools/Clear Db"; or automatically as configured in the OmniAnalyser™ service configuration
|
|
Directory import does not work. Use the OmniAnalyser™ console to import your GAL and verify that the Address List report is not empty.
|
|
The full Monitoring component should be installed on the servers to be monitored. In the Web Reports,
open Monitoring, Real-Time Status. Insert a server object in the report. |
|
| |
|
 |
|
| |
|
OmniAnalyser™ works with mail tracking
logs that may be very large in size on heavily loaded mail servers.
Furthermore, it needs to consolidate databases from multiple servers.
The distributed architecture allows to perform parts of this work on each individual server.
OmniAnalyser™ distributes the data processing: every OmniAnalyser™ Agent extracts and
pre-processes the contents of the tracking logs and then sends it to the Integration Server.
The OmniAnalyser™ Agents extract only the information requested by OmniAnalyser™,
compress it (thus reducing data size by up to 90%) and send the data through e-mail, which
provides better
reliability and security than direct network access. Thus, the consumption of network resources is minimized, which supports the extremely high
scalability of OmniAnalyser™ and makes it suitable even for organizations with hundreds of
servers. |
|
OmniAnalyser™ is
designed to work as an enterprise solution for an entire
organization. However, if you wish, OmniAnalyser™ can also be scaled back to a
site level, as well as to any physical or logical part of an
Exchange organization. It also supports multiple integration
servers at different locations, i.e. one integration server
running at the site level, the other server running at the
enterprise level. |
|
OmniAnalyser™ supports
Microsoft SQL Server 7.0 or later and Microsoft Database Engine
(MSDE). |
The OmniAgent™ service should be installed on the
Windows machine that is “nearest” in the network topology to the
non-Windows system. It can communicate with the OmniAnalyser™ integration
server via POP3/SMTP. Non-Windows logs can be shared over the network for
the OmniAgent™ or regularly transferred to the OmniAgent™ machine by scheduled ftp client.
For Lotus Domino, iPlanet and SendMail running on Linux, native Linux agents are also available. |
|
OmniAnalyser™ can build reports from Trend ScanMail, IMSS and Sybari. Antivirus reports show blocked mails, found viruses, antivirus scan result and services state. Anti-spam statistics
are also available. |
|
OmniAnalyser™ works with MS Exchange, Lotus
Domino, SendMail, iPlanet and Postfix. Any SMTP/POP3 system can be used as transport between
the OmniAgents and the OmniAnalyser™ integration server. One OmniAnalyser™ installation
can include agents installed on any combination of different mail systems simultaneously. |
|
Please contact information@hypersoft.com for trial details. |
|
| |
|
 |
|
|
|
