![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Table 34 Configuration Files These configuration files can be edited by hand, but you can also use the administration tool or the administration APIs to modify some of these files. See Chapter 6, Using the EMS Administration Tool for more information about using the administration tool.
Table 35 ACL Parameters Name of the group to which you wish to add permissions. The designation all specifies a predefined group that contains all users. The permissions which can be assigned to queues are send, receive and browse. The permissions which can be assigned to topics are publish, subscribe and durable and use_durable. The designation all specifies all possible permissions. For information about these permissions, refer to When Permissions Are Checked and Inheritance of Permissions.Administration permissions are granted to users to perform administration activities. See Administrator Permissions for more information about administration permissions.This file defines bridges between destinations. See Destination Bridges for more information about destination bridges.The destination-name can be any specific destination or a wildcard pattern to match multiple destinations.
Table 36 Bridge Parameters For detailed information about message selector syntax, see the ’Message Selectors’ section in description for the Message class in TIBCO Enterprise Message Service Java API Reference.[multicast-channel-name][ttl = hops][priority = priority][maxrate = size [KB|MB|GB]][maxtime = seconds][interface = ip-address]
Table 37 Channel Parameters Note that the square brackets [ ] DO NOT indicate that the multicast-channel-name is an option; they must be included around the name.
• multicast-group-address is the multicast group IP address to which messages will be sent. The address must be between 224.0.0.0 and 239.255.255.255.
• multicast-port is the multicast port destination to which messages will be sent. The multicast port must be between 1 and 65535.For example, this will cause messages sent over the channel to be directed to the IP address 234.5.6.7 and multicast port 99: The number of hops between the server and multicast daemon is one plus the number of routers between them. For example, if the server and multicast daemon are in the same subnet, then there is one hop between them. If the server and multicast daemon are separated by a router, then there are two hops between them. Therefore, a ttl value of 1 means that the multicast data will remain on the local subnet while a ttl value of 2 will allow the messages to travel through one router into the next subnet. Specifies the channel's transmission priority when bandwidth is allocated. priority is given as a numerical ranking, where the highest priority is -5 and the lowest is 5. Note that a long maxtime will increase the amount of memory used by the server. The maximum amount of memory used by a channel will be maxrate * maxtime. For example, specifying a maxrate of 10MB and a maxtime of 10 seconds may require the server to buffer 100 megabytes of data for retransmissions. The IP address must be a multicast capable interface. On UNIX systems, you can determine whether an IP interface is multicast capable by running the ifconfig UNIX command.When this parameter is not included, the default value is 0.0.0.0, which causes the EMS server to use the system’s default interface.[route][nolocal]
Table 38 Durable Subscriber Parameters When present, the subscriber is another server, and the durable-name is the name of that server. For detailed information about message selector syntax, see the ’Message Selectors’ section in description for the Message class in TIBCO Enterprise Message Service Java API Reference.Conflict can also arise because of wildcards. For example, if a client dynamically creates a durable subscriber for topic foo.*, and an administrator later attempts to define a static durable for topic foo.1, then the server detects this conflict and warns the administrator.To configure durable subscriptions in this file, we recommend using the create durable command in the tibemsadmin tool; see create durable on page 133.If the create durable command detects an existing dynamic durable subscription with the same topic and name, it promotes it to a static subscription, and writes a specification to the file durables.conf.[factory-name] # mandatory -- square brackets includedurl = url-stringclientID = client-id
Table 39 Connection Factory Parameters Note that the square brackets [ ] DO NOT indicate that the factory-name is optional; they must be included around the name.
• generic: Generic connection
• xageneric: Generic XA connection
• topic: Topic connection
• queue: Queue connection
• xatopic: XA topic connection
• xaqueue: XA queue connection
• connections—Connect to the server with the fewest client connections.
• byte_rate—Connect to the server with the lowest byte rate. Byte rate is a statistic that includes both inbound and outbound data.When this parameter is absent, the default metric is connections. This parameter determines the behavior of the EMS client but does not affect the multicast daemon. The multicast daemon must listen for the client on the same port that the client uses to connect. To change the TCP port that the multicast daemon listens on, use the -listen command line argument in the daemon. See Command Line Options for more information.See Chapter 14, Using Multicast for information on multicast.
• enabled—multicast is enabled in the factory.
• disabled—multicast is disabled in the factorySee Chapter 14, Using Multicast for more information on multicast. To configure connection factories in this file, we recommend using the tibemsadmin tool; see create factory on page 133.
If a client program that a creates durable subscriber connects to server A using a load-balanced connection factory, then server A creates and supports the durable subscription. If the client program exits and restarts, and this time connects to server B, then server B creates and supports a new durable subscription—however, pending messages on server A remain there until the client reconnects to server A. group-name1:"description"group-name2:"description"
Table 40 Group Parameters This file directs the TIBCO Enterprise Message Service server to the JAAS LoginModule. See Loading the LoginModule in the EMS Server for more information about the jaas.conf file.
Note that, while including JNDI names is optional, the square brackets [ ] must be included around JNDI names if they are included. For more information about setting JNDI names, see create jndiname on page 133.Only queues listed in this file or queues with names that match the queues listed in this file can be created by the applications (unless otherwise permitted by an entry in acl.conf). For example, if queue foo.* is listed in this file, queues foo.bar and foo.baz can be created by the application.Properties of the queue are inherited by all static and dynamic queues with matching names. For example, if test.* has the property secure, then test.1 and test.foo are also secure. For information on properties that can be assigned to queues, see Destination Properties.For further information on the inheritance of queue properties, refer to Wildcards * and > and Inheritance of Properties.
Routes may only be configured administratively, using the administration tool (see Chapter 6), or the administration APIs (see com.tibco.tibjms.admin.RouteInfo in the online documentation). Directly editing the routes.conf file causes errors.[route-name] # mandatory -- square brackets included.url=url-stringzone_name=zone_namezone_type=zone_typetopic_prefetch=value
Table 41 Route Parameters [route-name] is the name of the passive server (at the other end of the route); it also becomes the name of the route. Note that the square brackets [ ] DO NOT indicate that the route-name is an option; they must be included around the name. The route belongs to the routing zone with this name. When absent, the default value is default_mhop_zone (this default yields backward compatibility with configurations from releases earlier than 4.0).
• The EMS server will refuse to start up if the zone type in the routes.conf file does not match the zone type already created in the $sys.meta file that holds the shared state for the primary and secondary server. Topic selectors (for incoming_topic and outgoing_topic parameters) control the flow of topics along the route. This file defines the locations, either store files, mstore, or a database, where the EMS server will store messages or metadata (if the default $sys.meta definition is overridden). You can configure one or many stores in the stores.conf file.Each store configured is either a file-based store, mstore, or a database store. File-based store and mstore parameters are described here. Database store parameters are described in Chapter 11, Using Database Stores.[store_name] # mandatory -- square brackets includedfile=name[file_minimum=value][file_truncate=value][processor_id = processor id][store_name]file=name[processor_id = processor-id][scan_target_interval=time msec|sec|min|hour|day]
Table 42 Store File Parameters Note that the square brackets [ ] DO NOT indicate that the store_name is an option; they must be included around the name.
• file — for file-based stores.
• mstore — for mstores.
• dbstore — for database stores. The filename that will be used when creating this store file. This parameter is required for both file and mstore types. For example, mystore.db.The location for this file can be specified using absolute or relative path names. If no path separators are present, the file will be saved in the location specified by the store parameter in the tibemsd.conf file, if any is specified there. Specify the processor-id as an integer. The processor ID is numbered starting at 0 and continuing to the number of processors available, minus 1. For example, if you have four processors, the available processor IDs are 0, 1, 2, and 3.This parameter has similar requirements, limitations, and benefits as the processor_ids parameter in tibemsd.conf. For use guidelines, see Performance Tuning. The size should be set to a size that is known to be acceptable for the disk where the store points to. For instance, if it is set to 2MB, your disk must be able to write a 2MB batch efficiently.If file_destination_defrag is zero or absent, the destination defrag feature is disabled. You can specify units of MB or GB. Zero is a special value, which specifies no minimum preallocation. Otherwise, the value specified must be greater than 4MB.If file_truncate is set to true, the file_minimum parameter prevents the EMS server from truncating the file below the set size. When file_truncate is true, the store file may be truncated, but not below the size set in file_minimum.When this parameter is absent, the default is true, and the server will periodically attempt to truncate the store file. The mode determines whether messages will be written to the store file synchronously or asynchronously. Mode is either:
• async — the server stores messages in this file using asynchronous I/O calls.
• sync — the server stores messages in this file using synchronous I/O calls.When absent, the default is async. Specify time in units of msec, sec, min, hour or day to describe the time value as being in milliseconds, seconds, minutes, hours, or days, respectively. For example: Specify time in units of msec, sec, min, hour or day to describe the time value as being in milliseconds, seconds, minutes, hours, or days, respectively. For example:This file defines the TIBCO Rendezvous certified messaging (RVCM) listeners for use by topics that export messages to a tibrvcm transport. The server preregisters these listeners when the server starts up so that all messages (including the first message published) sent by way of the tibrvcm transport are guaranteed. If the server does not preregister the RVCM listeners before exporting messages, the listeners are created when the first message is published, but the first message is not guaranteed.
Table 43 RVCM Listener Parameters
Note that, while including JNDI names is optional, the square brackets [ ] must be included around JNDI names if they are included. For more information about setting JNDI names, see create jndiname on page 133.Only topics listed in this file or topics with names that match the topics listed in this file can be created by the applications (unless otherwise permitted by an entry in acl.conf). For example, if topic foo.* is listed in this file, topics foo.bar and foo.baz can be created by the application.Properties of the topic are inherited by all static and dynamic topics with matching names. For example, if test.* has the property secure, then test.1 and test.foo are also secure. For information on properties that can be assigned to topics, see Destination Properties.For further information on the inheritance of topic properties, refer to Wildcards * and > and Inheritance of Properties.[transport_name] # mandatory -- square brackets included
Table 44 Transport Parameters [transport_name] The name of the transport. Note that the square brackets [ ] DO NOT indicate that the transport_name is an option; they must be included around the name.
• tibrv identifies TIBCO Rendezvous transport
• tibrvcm identifies TIBCO Rendezvous Certified Messaging transport
• tibss identifies TIBCO SmartSockets transportEach transport includes additional transport-specific-parameters: EMS sending clients can set the JMSDeliveryMode header field for each message. However, Rendezvous clients cannot set this header. Instead, these two parameters determine the delivery modes for all topic messages and queue messages that tibemsd imports on this transport.When absent, the default is TIBEMS_NON_PERSISTENT.
If you have multiple TIBCO Rendezvous transports configured in your transports.conf file, and if the EMS server fails to create a transport based on the last entry, the server will continue to traverse through the entries and attempt to create further transports.If type = tibrv, the extended syntax is:[service = service][network = network][daemon = daemon][temp_destination_timeout = seconds]See Rendezvous Parameters for descriptions.If type = tibrvcm, the extended syntax is:rv_tport = name # mandatory[cm_name = name][ledger_file = file-name][default_ttl = seconds]See Rendezvous Certified Messaging (RVCM) Parameters for descriptions.If type = tibss, the extended syntax is:[username = name][password = password][server_names = single_or_list_of_servers][project = name]See SmartSockets Parameters for descriptions.
Table 45 User Parameters User passwords are not entered in this configuration file, and remain empty (and therefore not secure) until you set them using the administration tool; see Assign a Password to the Administrator. You can also create users and assign passwords using API calls; see the API reference for the language you are working with.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |