This window has configurations for advanced options that are not required for normal MIS Communicator operation. The most likely option you will need to use in this page is the option to configure MIS Communicator Service.
The service is not installed -when you see this message, it means MIS Communicator is not configured to run as a Windows Service, and in this case, if you Log Off, or you you restart your machine, MIS Communicator will not be running. See the Execution Modes section for more details.
This is the name you wish the service to have. It is important as it will be the name of the service if you try to find it in Windows Services Application to make any additional configuration.
It is also important in case yo need to have more than one MIS Communicator installation on the same Windows Machine, as it will be used to differentiate the different MIS Communicator services.
Once you have the service name configured you can use the Install Service button to install the Windows Service.
If the service is already installed, you can use the Uninstall Service button to uninstall the service.
If you want to have multiple MIS Communicator installations, you should not have any service with name MISCommunicator.
As you probably noticed this is the default service name, and if you have an instance iwth this service name installed, when you try to configure the second instance, it will have this name configured by default, and it will incorrectly think that the service is already installed.
When MIS Communicator is configured to run as a service, you can activate a Monitor service that will monitor whether the service is active and responding by trying to establish a TCP/IP connection to each of the configured network ports, and in case of failure it will re-start the service automatically.
It is usefull if you need to ensure a 24/7 running state for MIS Communicator, this will help to deal with abnormal cases where MIS Communicator service stops responding, either due to system issues or to possible errors in MIS Communicator itself.
If you enable this option, you are activating an ODBC connection sharing in MIS Communicator. This option can be usefull if you have a cost associated with each connection to a database, since it allows you to share those connections with multiple devices.
If you set for example 2 connections as the maximum, if a device makes a database connection it will activate a first connection to the database. If it is running a long time query, and a second device connects in that period, a new connection will be created. When a third device connects, if the 2 previous connections still have a query executing, then this will wait until one of them finishes its query and at that moment, it will be given access to the connection that is Idle to run the query.
So this will create a waiting queue on the recieved requests, on a query by query base, and it will create at maximum the defined number of connections to satisfy the requests on that queue.
When the Log function is enabled, MIS Communicator will record an exhaustive Log of every operation performed in either an SQLite database or into TXT files.
This option will record the mentioned log into an SQLite database under the folder Log inside MIS Communicator installation folder. This log can be read either by using Log option in available from the Main Window or by using an external tool to read SQLite databases like SQLite Studio.
This option is not normally active. If enabled it will log all Keep Alive packets sent by the clients. It is only usefull for trying to deal with connectivity issues, and should not normally be active, because it will create many unusefull Log entries that will take up disk space.
This option allows you to limit the time that the logs will be kept in the database. If you dont specify a value, the logs will never deleted.
Enter the number of days that you want to keep the Log, and any Log entries that are older, will automatically be deleted by MIS Communicator.
As mentioned, this option will make an exhaustive Log of all the operations in a database.
You need to be aware that making this log takes both time and disk space. Taking time also means that it will affect the performance of MIS Communicator. If you are getting performance issues with your requests to MIS Communicator, try to disable this option to see if it helps. If it does consider disabling or replacing with Log to file option.
This option will record the mentioned log into TXT files inside the Log folder. It will reate one file for each day.
This option is better than the Log to database in terms of performance, since it is faster to write data to a plain TXT file than it is to a database, but it has the big disadvtange when it comes to reading the Log, since you will have to use a Text Editor like Notepad to read this Log.
The main use case for this option is when you are getting a peformance impact on our application due to the Log to database option, and you have already gone through the testing stage in your deployment cycle when you may need to make a lot of Log queries, but you still want to get a Log of all the operations in case something abnormal shows up, you have the possibility to use this option instead.
When Kalipso action PrintOnPC is executed, if this file path is defined, then the output of the print will be set to the specified file. This option may be useful, for example during development, when you are using a PDF printer to test, you can use this option to specify the output PDF file name.
These options are related to a specific product call MSS. If you are using that product you should read its documentation to know how to properly use these options.