Wizard and Configuration Tab
The Wizard and Configuration tab have the following fields.
Field | Global Var? | Description |
---|---|---|
Wizard | ||
File Name | No | The name to appear as the label for the resource. Names follow Java variable naming restrictions. Do not use any reserved words. Names must be unique within a folder. See
Identifier Naming Requirements.
Unlike other resource identifiers shared resource identifiers can have spaces in the name. The name then appears in the title of the resource. |
Configuration | ||
Description | No | Short description of the resource. |
Metaspace Name | Yes | Specifies a TIBCO ActiveSpaces metaspace. A metaspace is an instance of a cluster of application processes deployed using TIBCO ActiveSpaces. The application processes are typically deployed on multiple hosts that are interconnected by a network.
The default value for this field is ’ms’. |
MemberName | Yes | Name the AS channel will take when connecting to ActiveSpaces metaspace |
Discovery URL | Yes | 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 | Yes | 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 | Yes | 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 | Yes | Enables security for the ActiveSpaces connection resource when selected.
Note: Some fields are activated only for the specific security role or authorization policy. |
SecurityRole | Yes | 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 | Yes | The password for the identity key in the security policy file. |
PolicyFile | Yes | 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 | Yes | Absolute path to the token file which is used by requester to connect to a metaspace whose security is defined in the policy file. |
Credential | Yes | Authentication policy to be used for authentication as specified in the policy file. The values are: |
Domain | Yes | Domain name for system based user authentication. |
Username | Yes | User name for LDAP and system based authentication. |
Password | Yes | Password for LDAP and system based authentication. |
KeyFile | Yes | The absolute path for a file containing the key to use for LDAP with the certificate based authentication. |
PrivateKey | Yes | The password for the identity key in the LDAP identity file specified in KeyFile. |