UniPay Properties Definition


Property Location Types:


Database run-time property used by the application and stored within a database
Filerun-time property used by the application and stored within a file
Buildbuild-time property used by the application and stored within a file


Groups: All   General   Resources   Tokenization   FTP   FTP Gates   Unibroker  
System   Unibill   Remittance   Notifications   Defaults   Services   QA  

Available Properties for iapp_settings:



Property Definitions for iapp_settings:


unipay.contacts.financial-services.email   
Added On:  05/01/12
Legacy Name:  
Group:  Services
Status:  Active
Attributes:  
Email of the financial services department. The value is used in letters and emails that are sent on behalf of the department or mention this department's contact information.

Financial services department is the department responsible for the flow of transactions as well as remittances and reconciliations.
unipay.contacts.financial-services.name   
Added On:  05/01/12
Legacy Name:  
Group:  Services
Status:  Active
Attributes:  
Official name of the financial services department. The value is used in letters and emails that are sent on behalf of the department or mention this department's contact information.

Financial services department is the department responsible for the flow of transactions as well as remittances and reconciliations.
unipay.contacts.tech-support.email   
Added On:  05/01/12
Legacy Name:  
Group:  Services
Status:  Active
Attributes:  
Email of the tech support department. The value is used in letters and emails that are sent on behalf of the department or mention this department's contact information.

Tech support department is the department responsible for the system maintenance, user account setup and system integration certifications.
unipay.contacts.tech-support.name   
Added On:  05/01/12
Legacy Name:  
Group:  Services
Status:  Active
Attributes:  
Official name of the tech support department. The value is used in letters and emails that are sent on behalf of the department or mention this department's contact information.

Tech support department is the department responsible for the system maintenance, user account setup and system integration certifications.
unipay.features.terminal-last-activity-date-update-enabled   
Added On:  12/05/18
Legacy Name:  
Group:  Services
Status:  Active
Attributes:   Default ( true )
Indicates whether information about a last activity date and an operation submitted via TMS API for a terminal is updated.
unipay.system.node-codes   
Added On:  02/08/18
Legacy Name:  
Group:  Services
Status:  Active
Attributes:  
Code(s) of the UniPay node(s) that are going to be monitored by the JavaMelody service.

The following rules must be followed while setting the property:
  • Batch node codes must be listed first;
  • Real-time node codes must be listed second;
  • Batch and real-time node codes must be separated by a semicolon sign (;). On the user interface, batch and real-time nodes are already separated by being indicated in the different textboxes. For this reason, there is no need to use a semicolon sign for separation;
  • Node codes within a group (batch or real-time) must be separated by a comma sign (,);
  • Code(s) of the master node(s) must be followed by an asterisk sign (*), otherwise, the first node in the list is identified as a master node.

For example: unipay.system.node-codes=1,2*,3;1,4,5, where
  • 1 is both batch and real-time backup node;
  • 2 is a batch master node;
  • 3 is a batch backup node;
  • 4 and 5 are real-time backup nodes.

To apply changes in the node codes, you must restart Camel via the Job Object form on the System perspective.
unipay.unibroker.node-codes   
Added On:  02/08/18
Legacy Name:  
Group:  Services
Status:  Active
Attributes:  
Code(s) of the UniBroker node(s) that are going to be monitored by the JavaMelody service.

The following rules must be followed while setting the property:
  • Batch node codes must be listed first;
  • Real-time node codes must be listed second;
  • Batch and real-time node codes must be separated by a semicolon sign (;). On the user interface, batch and real-time nodes are already separated by being indicated in the different textboxes. For this reason, there is no need to use a semicolon sign for separation;
  • Node codes within a group (batch or real-time) must be separated by a comma sign (,);
  • Code(s) of the master node(s) must be followed by an asterisk sign (*), otherwise, the first node in the list is identified as a master node.

For example: unipay.system.node-codes=1,2*,3;1,4,5, where
  • 1 is both batch and real-time backup node;
  • 2 is a batch master node;
  • 3 is a batch backup node;
  • 4 and 5 are real-time backup nodes.

To apply changes in the node codes, you must restart Camel via the Job Object form on the System perspective.