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 Legacy ActiveSpaces metaspace. A metaspace is an instance of a cluster of application processes deployed using Legacy 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 Legacy 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

  • 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 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 Legacy ActiveSpaces channel as a remote-discovery proxy. In this case, any remote client can connect to an Legacy ActiveSpaces metaspace via the Legacy ActiveSpaces Channel node.
EnableSecurity Yes Enables security for the Legacy 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 Legacy 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.
  • Requester 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 as 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 Requester option is selected, then the following fields become active:

  • Identity Password
  • TokenFile
  • Credential

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:
  • 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 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.