Sunday, August 3, 2008

Reporting tool & Operational History Viewer -

Hint - For local systems only (serves running the tracing server service there is nothing to configure except the printer mentioned below) no ODBC configuration is necessary.

Local systems, servers running the tracing service:

When using the reporting tool for the first time you must set a default printer under the reporting tool, even if no printer exists to fake out the system. May or may not be necessary to do more than once for different logins. Reports should then run.

Operational History Viewer should work.

To run OpHist and Reports on other servers you must share out both the Tracing folder and the Reports folder from the server running the MM tracing service.

C:\Program Files\Avaya Modular Messaging\Tracing

C:\Program Files\Avaya Modular Messaging\Tools\Diag\Reports

Remote systems, servers not running the tracing service:

On remote MAS (servers not running the MM tracing service) - This is where you have to do some ODBC configuration.

Under the ODBC you will have to map drives to files (be sure to check Reconnect at logon) in both the shared Tracing folder and the shared Reports folder.

Be careful with the instruction links below, I think the administration documentation is more than a little confusing but they show how to map the drives on the remote servers and point to the correct data source.

Hint – If under the System DSN if a source OperationHistory, TrxDB, or ReportsDB already exists (and they should) then you do not need to create or add them you simply need to configure (map a drive to the remote folder and point to the correct file) them.

Hint - Under the reporting admin you will have to configure the TrxDB and the ReportDB (the instructions do not mention the ReportDB and that is why I write these things).

So for Operation History, you configure and map OperationHistory (DSN) to the OpHist.mdb file (tracing folder) on the remote tracing server. 1 - thing to configure only.

And for Reports you configure the TrxDB (DSN) mapped to the TrxDB.mdb file (tracing folder) and you must also configure ReportDB (DSN) mapped to the reports.mdb (Reports folder). 2 - things to configure here.

http://support.avaya.com/elmodocs2/mm/r3_1_doc/CD_Master/a_mss_mas/MASAd-OHV-Und-Dat.html

http://support.avaya.com/elmodocs2/mm/r_4_0_doc/cd_frontend/a_mss_mas/MASAd-RT-Und-Dat.html

This sharing is login specific so mapping the data sources will have to be repeated for every login that is being used if they want the Reporting tool and Operation History to function.

1 comment:

Unknown said...

I really appreciate information shared above. It’s of great help. If someone want to learn Online (Virtual) instructor lead live training in Avaya Messenging Server
, kindly contact us http://www.maxmunus.com/contact
MaxMunus Offer World Class Virtual Instructor led training on in Avaya Messenging Server We have industry expert trainer. We provide Training Material and Software Support. MaxMunus has successfully conducted 100000+ trainings in India, USA, UK, Australlia, Switzerland, Qatar, Saudi Arabia, Bangladesh, Bahrain and UAE etc.
For Demo Contact us:
Name : Arunkumar U
Email : arun@maxmunus.com
Skype id: training_maxmunus
Contact No.-+91-9738507310
Company Website –http://www.maxmunus.com