Wizard and Configuration Section

The Wizard and the Configuration section have the following fields.

Field Global Var? Description
Name No (Shown in the Wizard and then in the editor title only.) The name to appear as the label for the resource. Names follow Java variable naming restrictions. Do not use any reserved words.
Description No Short description of the resource.
Driver No Select the driver for the type of channel you are configuring:
  • TIBCO Rendezvous
  • Local
  • HTTP
  • JMS
  • ActiveSpaces
  • Hawk
Method of Configuration No Properties  - Select Properties to configure this channel resource using properties. See:

Resource - Select Resource if you have a shared resource in your project whose properties you want to reuse for this channel.

Note: The path to the resource and the resource name cannot contain any of the words listed in TIBCO BusinessEvents Architect’s Guide.

Resource No If you choose Resource as the method of configuration, the Resource field appears. Browse to and select the resource you want to use. As a convenience, you can open the selected resource by clicking the underlined label.
Configuration for TIBCO Rendezvous Channels
Service Yes The name of the service or port number through which Rendezvous sends messages. In most cases you can leave this field empty, accepting the default value.

For more information about the Rendezvous service parameter, see TIBCO Rendezvous Concepts or TIBCO Rendezvous Administration.

Default is 7500 (defined in Global Variables).

Network Yes The network over which Rendezvous sends messages. In most cases you can leave this field empty. For more information about the network parameter, see TIBCO Rendezvous Administration.

Default is an empty string (defined in Global Variables).

Daemon Yes The location of the Rendezvous daemon, which is usually expressed as a client socket number, for example 6555. In most cases, you can leave this field empty, accepting the default value. For more information about the daemon parameter, see TIBCO Rendezvous Concepts.

Default is tcp:7500 (defined in Global Variables).

Configuration for JMS Channels
ProviderURL Yes The URL at which TIBCO BusinessEvents can contact the Enterprise Message Service server.

Example: tcp://localhost:7222

UserName Yes A valid username for the Enterprise Message Service server.
Password Yes The password assigned to the username, above, for the purpose of accessing the Enterprise Message Service server.
IsTransacted Yes Accepts true or false. Specify true if the session has transaction semantics. Specify false if it has non-transaction semantics. For more information about the IsTransacted property, see TIBCO Enterprise Message Service documentation.
ClientID Yes The unique client ID of the connection.
Configuration for ActiveSpaces Channels
Metaspace Name No The name of a particular metaspace instance in TIBCO ActiveSpaces that the channel must connect to.

The metaspace must be created and initialized before the channel can use it at runtime.

Discovery URL No Specifies how a metaspace instance discovers the current metaspace members. Multicast discovery can use either PGM - Pragmatic General Multicast or RV - TIBCO Rendezvous protocol.

If using PGM protocol, the multicast URL is expressed in the following format:

tibpgm://destination port/interface;discovery group address/optional transport arguments, where

  • destination port specifies the destination port used by the PGM transport. If not specified, the default value of 7888 is used.
  • interface;discovery group address specifies the address of the interface to be used for sending discovery packets, and the discovery group address to be used. If not specified, it defaults to the default interface and discovery address, 0.0.0.0;239.8.8.8.
  • optional transport arguments specifies a semicolon-separated list of optional PGM transport arguments. By default, the PGM transport is tuned to provide the best performance according to the most common deployment architectures. The values of those optional arguments should be changed only when necessary and with care, since any inappropriate values could easily result in degraded performance of the product.

If using TIBCO Rendezvous, the multicast URL is expressed in the following format:

tibrv://service/network/daemon, where

  • service specifies the TIBCO Rendezvous service number (UDP port) that will be used. If not specified, the value defaults to 7889.
  • network specifies the interface and discovery group address that will be used to send Rendezvous discovery packets. The format is:
    interface; discovery_group_address

    If not specified, the default interface and discovery group address will be used. (tibrv://7889/;239.8.8.9/).

  • daemon specifies where to find the Rendezvous daemon. If not specified, it will try to connect to a local daemon on port 7500.
ListenUrl No The discovery mechanism is based on pure TCP.

All the designated well known metaspace members are identified by an IP address and a port number. This address and port are specified by the member’s Listen URL.

If not specified, the discovery process uses the default IP address and the first free TCP port that can be acquired from the operating system (starting 5000 and above).

RemoteListenUrl No This field is used to configure TIBCO ActiveSpaces Channel as a remote-discovery proxy. In this case, any remote client can connect to an ActiveSpaces metaspace via the ActiveSpaces Channel node.
EnableSecurity No Enables security for the ActiveSpaces channel when selected.

Note: Some fields are activated only for the specific security role or authorization polcy.

SecurityRole No Security role of a node for the secure ActiveSpaces channel in the metaspace. The values are:
  • Controller is dedicated to enforcing a security domain's defined security behavior for a metaspace associated with the security domain. Security domain controllers are the only discovery nodes in a metaspace.
  • Requestor just requires access to the data in the data grid, such as a seeder or a leech, and which need to be authorized by a controller. Requesters can never be used a discovery nodes.

The controller nodes are configured with a security policy file. The requester nodes provide a token file and additional credentials to the controller for authentication. The controller performs authentication as defined in its policy file and using the credentials provided by the requester.

If the Controller option is selected, then the following fields become active:
  • Identity Password
  • PolicyFile
If the Requestor option is selected, then the following fields become active:
  • Identity Password
  • TokenFile
  • Credential
Identity Password No The password for the identity key in the security policy file.
PolicyFile No Absolute path to the policy file which contains the security settings that the controller node enforces. It is generated using the as-admin utility.
TokenFile No Absolute path to the token file which is used by requestor to connect to a metaspace whose security is defined in the policy file.
Credential No Authentication policy to be used for authentication as specified in the policy file. The values are:
  • USERPWD - A user name and password based authentication is used. It activates the following fields:
    • Domain
    • Username
    • Password
  • X509V3 - The authentication source is an LDAP configured with certificate based authentication. It activates the following fields:
    • KeyFile
    • PrivateKey
Domain No Domain name for system based user authentication.
Username No User name for LDAP and system based authentication.
Password No Password for LDAP and system based authentication.
KeyFile No The absolute path for a file containing the key to use for LDAP with the certificate based authentication.
PrivateKey No The password for the identity key in the LDAP identity file specified in KeyFile