Registry Operation for MTELpage 2012

 

1.1       Focus

This instruction describes the registry functions in the MTELpage suite of applications. This instruction applies to MTELPage versions V3.50 (347) and above and MTELServe versions V3.3 (460) and above.

The registry is a table in the c:\mtelsys directory and contains settings for all MTELPage and MS applications. The table is a replacement for the older style Windows 95 system of storing configuration data for windows programs in resident global memory.

Instead MP suite of applications has individual database files located in a fixed directory in which registry like data are loaded into the application global memory.

When applications are shutdown the registry data is saved back to the table for safe keeping until the application is restarted.

The main reason for moving away from the windows based registry is that in computers with many users the registry was different for every user. MP changes could not be easily kept between users.

The second reason is the move to Windows Vista complicated the registry settings location and so the move to a table in a database became mandatory.

The third reason is the table data was easier to change and document then the registry information.

 

1.2       MTELServe/MTELPage Registry Operation

When a MP application starts it looks for its system file in c:\mtelsys directory. This is hard coded and MP will not start without this file.

The files for all the MP suite is as follows;

•     MTELPage            c:\mtelsys\mtelpagesysTCP.mdb

•     MTELserve S01    c:\mtelsys\mtelsrvs01.mdb

•     MTELserve S02    c:\mtelsys\mtelsrvs02.mdb

•     MTELserve S03    c:\mtelsys\mtelsrvs03.mdb

•     MTELserve S04    c:\mtelsys\mtelsrvs04.mdb

•     MTELserve S05    c:\mtelsys\mtelsrvs05.mdb

•     MTELDatabase     c:\mtelsys\mtelsysdb.mdb

Registry Read/Write

Each file contains several tables including a Registry table.

On start-up the application opens this database and reads in all the Registry data. If data fields are missing the application will use a default.

On shutting down the application writes back to the registry only the values in the Registry table.

To force the application to write all values to the table, there is a Force Registry function in the Advanced menu in MTELPage. This will empty the Registry table and then write all current settings to the Registry. Registry values not previously in the table will now be added and the value will be the hard coded default or a new value if the application has changed it.

It is important to perform the Force Registry on an application that is working satisfactory. Otherwise the function may write default data from start-up which may change during normal operation.

Default Settings

It is important to note that Default settings are primarily used to allow the application to initialise and correctly start up.

There is absolutely no guarantee that the settings will work for the immediate user.

Force Registry between versions

The use of the Force Registry function must only be done if the application is working successfully.

When moving to a new version of the application this is extremely important as the new version may delete older settings not required by the new version if the Force Registry is utilised. This has implications when rolling back to the previous version as it may not work as the deleted setting will then be populated with a default setting by the old version when rolling back and the application is restarted.

In general only use the Force Registry if instructed to from release notes accompanying the application.

1.3       MTELPage Registry

Registry Values for Version V3.50 and below

The table below is the registry with typical values and default values. There is also an explanation of the field.

Fields in Red are not in use and will be removed in future versions. To remove the fields use Force Registry in the future versions.

Fields in Purple are not valid for use in the QFRS/QAS implementations. These settings relate to directly connected paging servers.

1.4       MTELPage Registry Grouping

Registry Values for Version V3.50 and below

The table below is how the registry information relates to the application. Some settings operate together to form specific functions.

In MTELPage these groups of settings can be viewed in the Client Log then Settings tab.

An example of the printout is displayed as follows;

 -----------MTELsys File----------

File Location:- c:\MTELsys\mtelpagesysTCP.mdb

-----------General----------
                                                                                           
Customer:- QAS                                                                    Customer ID changes the operation of MTELpage for certain customers.
File Server is:- z:\pager
Client ID is:- c03                                                                    All Clients must have a unique customer id.
Client File:- cairns.mdb                                                         This is the default contact list.
Check for servers every (secs):- 60
Current Message ID Counter:- 5308
Max Number of Servers:- 0                                                    If set to 0 it disables checking for servers. Otherwise set it to the number of servers
TCP ALert to Servers:- True                                                   in operation.
                                                                                            TCP alert will always be set to True.
----------- Layout ----------

Tone Only permitted:- True
Blank Message (inserted):- Blank Message
Append Canned Messages:- True

-----------Backup-----------
                                                                                            There should only be backup client. Usually C99. All others should have a backup
BUSize is (days):- 7                                                                date of 2099.
BUDate is:- 15/10/2012 12:37:26 PM

-----------Reporting-----------                                           
                                                                                           There is only one reporting client in a system. Usually the C99 Client
Reporting Client:- True                                                         All other clients should be False. However the Region Test ID should always be 
Last Report:- 19/05/2012 8:00:00 AM                                     set as this setting allows MTELpage to filter the region for manual test purposes.
Region Test ID:- Central

-----------Protocol---------

Message Expire Time (hms) is:- 12:30:00 AM                          These settings are only for directly connected MTELPage systems.
Packet Protocol:- PET                                                           MTELPage connects to paging hardware servers using a TCP socket.
Remote E2054 System:- False                                                It then can use several different protocols across the TCP connection
TCP direct:- False                                                                 depending on the server.
TCP Port:- 3030
TCP IP:- e2m.hutch.com.au
TCP Auto Detect:- False
PET Capcode Enabled:- False
Add to PET packet Baud Rate:- False
TNPP Dedicated Freq Ch:- 2
TNPP Dedicated Function Mask:- 3

-----------Relay---------
                                                                                            These are the settings for sending messages to the MDS via the MTELRelay.
Relay Address is:- 192.168.0.43
Relay Port is:- 7003
Relay Port Active:- True
Paging 2 MDS:- HUTCH

 

[ Home ] [ Up ]  
Copyright © 2012-2021 MTEL Communications Pty Ltd
Last modified: 01-Jun-2022