![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
You can create routes using the administration tool (see Chapter 6), or the administration APIs (see com.tibco.tibjms.admin.RouteInfo in the online documentation).To create a route using the administration tool, first connect to one of the servers, then use the create route command with the following syntax:
• name is the name of the server at the other end of the route; it also becomes the name of the route.
• URL specifies the other server by its URL—including protocol and port.If your environment is configured for fault tolerance, the URL can be a comma-separated list of URLs denoting fault-tolerant servers. For more information about fault tolerance, see Chapter 20, Fault Tolerance.
• zone_name specifies that 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).
•
• properties is a space-separated list of properties for the route. Each property has the syntax:For gating properties that control the flow of topics along the route, see Selectors for Routing Topic Messages.For properties that configure the Secure Sockets Layer (SSL) protocol for the route, see Routing and SSL.For example, these commands on server A would create routes to servers B and C. The route to B belongs to the one-hop zone Z1. The route to C belongs to the multi-hop zone ZM.You can display these routes using the show routes command in the administration tool:
• The Route column lists the name of the passive server.
• The T column indicates whether the route is active (A) or passive (P), from the perspective of server A.
• The ConnID column contains either an integer connection ID (if the route is currently connected, or a dash (-) if the route is not connected.Failover behavior for route connections is similar to that for client connections; see Configuring Clients for Shared State Failover Connections.
• Table 86 lists the parameters that you can specify in the routes.conf configuration file, or on the command line when creating a route. The parameters for configuring SSL between routed servers are similar to the parameters used to configure SSL between server and clients; see Chapter 19, Using the SSL Protocol.
Table 86 SSL Parameters for Routes ssl_issuer = certs\CA_root.pemssl_issuer = certs\CA_child1.pemssl_issuer = certs\CA_child2.pem The local server’s private key. If the digital certificate in ssl_identity already includes this information, then you may omit this parameter. You can set passwords using the tibemsadmin tool. When passwords are set with this tool, the password is obfuscated in the configuration file. For more information, see Chapter 6, Using the EMS Administration Tool. Specifies whether the server must verify the other server’s certificate. The values for this parameter are enabled and disabled.When omitted, the default is enabled, signifying the server must verify the other server’s certificate.When this parameter is disabled, the server establishes secure communication with the other server, but does not verify the server’s identity. Specifies whether the server must verify the name in the CN field of the other server’s certificate. The values for this parameter are enabled and disabled.When omitted, the default is enabled, signifying the server must verify the name of the connected host or the name specified in the ssl_expected_hostname parameter against the value in the server’s certificate. If the names do not match, the connection is rejected.When this parameter is disabled, the server establishes secure communication with the other server, but does not verify the server’s name. This parameter is relevant only when the ssl_verify_hostname parameter is enabled.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |