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: |
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. For 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 user name for the Enterprise Message Service server. |
Password | Yes | The password assigned to the user name, 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 run time. |
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
If using TIBCO Rendezvous, the multicast URL is expressed in the following format: tibrv://service/network/daemon, where
|
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 policy. |
SecurityRole | No | Security role of a node for the secure ActiveSpaces channel in the metaspace. The values are:
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. |
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: |
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 |