TIX 6 Configuration file
This page describes the TIX configuration files and describes the different options. Changes to the configuration file will affect the running TIX instance. Note that all properties may be suffixed with a nodeId to make a property value specific to a TIX node.
System and connectivity.
Property name | Description |
|---|---|
tix.serverAddress | Server address. This address will be used as client address when calling http resources outside the application. This is only needed if the GTN application server is bound to an address that is not the default address. |
tix.scheme | Legal values: http or https. Specifies the protocol for GTNet communication. Should be https, unless you really know what you're doing. |
tix.client.keyStoreURL | Location of the java key store. |
tix.client.keyStorePassword | Jave keystore password. |
tix.trustStoreUrl | Location of the trust store. |
tix.trustStorePassword | Trust store password. |
qtix.remote.jmx.url | Service URL to the QTIX that the TIX will use when managing the queues. Must be set if the TIX configured (via standalone-tix.xml) to use QTIX. Example: service:jmx:remoting-jmx://localhost:9999 The qtix.remote.jmx.url should be removed or set to empty if the TIX is not connected to a QTIX instance. |
tix.uploadDir | Pattern for describing location where copies of all received data files are placed. Default value is 'target/uploads/${node}'/yyyy/MM-dd The pattern is based on the Java SimpleDateFormat pattern. It is required to contain a ${node} variable which will make sure that files belonging to different TIX-nodes are kept separate. |
network.read.timeout | Timeout for wating for data from external services. |
network.connection.timeout | Timeout for connecting to external services. |
story.url | URL to Story, used when redirecting for changing password. |
hub.access | true for TIX servers that should connect to the GTNet. |
hub.url | GAP url address to a GTNet HUB |
mds.service.id | Service Id for the MasterDataServer. Will be resolved in GNS. |
mds.url | URL of the MasterDataServer. An alternate way of specifying MasterDataServer connectivity. |
gns.env | Specifies which GNS ENV this TIX belongs to. |
gns.service.id | Service ID of the GNS service. |
tix.export.preprocess-group-size | Export message grouping size. Controls the size of the export processing workloads. The default size is 10. |
epcis.strictConformance | If true, the TIX will enforce strict validation of EPCs to conform with the EPCIS specification. |
alarms.disabled | If true, the TIX will ignore all messages processed from the TIXPostImportQueue, that means that no ImportContext will be evaluated with the alarms registered. |
email.disabled | If true, the TIX will ignore all messages processed from the TIXEmailQueue, that means the TIX will not send the messages as email. |
remote.connection-factory | the name of the remote connection factory to use, a remote connection factory must be made available for remote lookup by adding ' Example: jms/RemoteConnectionFactory remote standalone.xml <connection-factory name="RemoteConnectionFactory"> <connectors> <connector-ref connector-name="netty" /> </connectors> <entries> <entry name="RemoteConnectionFactory" /> <entry name="java:jboss/exported/jms/RemoteConnectionFactory" /> <!-- enable remote lookup --> </entries></connection-factory> |
remote.context-factory | the name of the context factory (default) Example: org.jboss.naming.remote.client.InitialContextFactory |
remote.provider-url | the URL to the other TIX Example: remote://0.0.0.0:4447 remote standalone.xml <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}"> <socket-binding name="remoting" port="4447" /></socket-binding-group> |
remote.username | the username to use when creating a connection, a user from the configured Example: guest |
remote.password | the password to use when creating a connection Example: guest |
remote.queue-name | the name of the remote queue to send messages to, queue must be made available by remote JMS. Example: jms/queue/RemotePreImportQueue remote standalone.xml / jms-destinations <jms-queue name="PreImportQueue"> <entry name="/queue/PreImportQueue" /> <entry name="java:jboss/exported/jms/queue/RemotePreImportQueue" /> <!-- enable remote lookup --></jms-queue> |
Data and presentation.
Property name | Default value | Description |
|---|---|---|
|
| Timezone used for presentation |
|
| Image to use in the web interface. It will be scaled to 106x41 |
| 200 | Max number of EPCs accepted when converting Event to ttdata. Events containing more EPCs will not be converted. |
| 1024 | The max width for the width parameter in imagemap/png endpoint. |
| 768 | The max height for the height parameter in imagemap/png endpoint. |
| ** | The symbols/text to replace unresolved references in the |
| 1024 | The max size for the size parameter in icon endpoint. |
| 20 | Default page size of object query. |
| 1000 | Default page and and max event size for query epcis events. |
| "Unknown type" | Customize the label that is shown in the graphs for entities that don't have a trdType. |
|
| If true, only cbv standard values are allowed for the standard cbv vocabularies. |
|
| If true, a default data access control file will be used to limit remote data access, if no data access control has been uploaded. |
| 120 (seconds) | Lifetime of redirecting sso keys. |
Logging
Property name | Default value | Description |
|---|---|---|
logging.remotecall.info-threshold | 1000 (milliseconds) | Access to remote services are always logged as level DEBUG. If the call took longer than the info-threshold, it will be logged as INFO. |
logging.remotecall.warn-threshold | 5000 (milliseconds) | Access to remote services are always logged as level DEBUG. If the call took longer than the info-threshold, it will be logged as WARN. |
logging.throughput.max-elements | 10000 | TIX records throughput during activity for measuring peak performance. This property limits the size of the thoughput log. |
logging.throughput.min-elements | 100 | The lowest number of elements required to create an averaged value. |
logging.throughput.short-average-window-size | 10 | Used to log a short-term average. Shows abrupt changes in performance faster. |
logging.throughput.max-time | 3600 (seconds) | logging.throughput.max-elements limits the averaging window size by number of elements, this property limits the averaging window by time. |
logging.throughput.log-frequency | 60 | Specifies how often the throughput should be logged. Default value is 60, for every 60 seconds. |