Metaspace

The Metaspace shared resource describes the metaspace connection information.

General

The General panel shows the package that stores the Metaspace shared resource and the shared resource name. You can also provide a description for the shared resource in this panel.

The following table describes the fields in the General panel of the Metaspace shared resource:

Field Module Property? Description
Package No Specifies the package that stores the Metaspace shared resource.
Name No Specifies the name to be displayed as the label for the Metaspace shared resource in the process.
Description No (Optional) Specifies a short description for the shared resource.

MetaSpace

In the MetaSpace panel, you can provide the information of the metaspace that the plug-in connects to.

The following table describes the fields in the MetaSpace panel of the Metaspace shared resource:

Field Module Property? Description
Metaspace Name Yes Specifies a metaspace name.
The metaspace name must start with a letter or a digit. The name can include alphanumeric characters, "-", or "_". The default metaspace name is ms.
Note: Metaspace shared resources in the same application must use different names.
Member Name Yes (Optional) Specifies a unique name to identify each member connected to the metaspace.
Discovery URL Yes (Optional) Specifies the URL of a metaspace used by a member to connect to the metaspace.

TIBCO Rendezvous, Pragmatic General Multicast (PGM), and TCP are three discovery protocols that are used in TIBCO ActiveMatrix BusinessWorks Plug-in for ActiveSpaces. PGM is the default discovery mechanism.

TIBCO ActiveMatrix BusinessWorks Plug-in for ActiveSpaces supports connecting to a metaspace as a remote client.

See TIBCO ActiveSpaces Developer’s Guide for detailed information.

Listen URL Yes (Optional) Specifies the URL that indicates the interface and the TCP port used to listen for incoming connections from new members to the metaspace.

The format of the Listen URL is tcp://interface:port.

See TIBCO ActiveSpaces Developer’s Guide for detailed information.

Remote Listen URL Yes (Optional) Specifies the URL that indicates the IP address and TCP port with which this proxy metaspace member listens for remote client connections to the metaspace.
The format of the remote listen URL is tcp://interface:port.
Note: A remote client application can never become a seeder in a space.

See TIBCO ActiveSpaces Developer’s Guide for detailed information.

Allowed Invocation Thread Count Yes (Optional) Specifies the maximum number of threads used for invocation.

The default value is 32.

Connect timeout (milliseconds) Yes (Optional) Specifies the amount of time in milliseconds that the member waits for a connection to the metaspace.

The default value is -1, which indicates that the member can wait for a connection to the metaspace indefinitely.

See TIBCO ActiveSpaces Java API Reference for more information.

Member timeout (milliseconds) Yes (Optional) Specifies the amount of time in milliseconds that the member waits for a reconnection after the connection to the metaspace terminates unexpectedly.

The default value is 30000.

See TIBCO ActiveSpaces Java API Reference for more information.

Cluster suspend threshold Yes (Optional) Specifies the minimum number of the lost host connections that cause the suspension of membership operations.

The default value is -1, which indicates that no matter how many host connections are lost, the membership operations are never suspended.

Data Store Location Yes (Required for share-nothing persistence only) Specifies the directory where persisted data is stored.

Secure

In the Secure panel, you can specify whether or not to secure the information stored in the data grid. If you select the Secure Metaspace check box, both transport data and stored data are protected in the connected metaspace.

You have to use the TCP discovery mechanism to apply security to the metaspace.

When you select the Secure Metaspaces check box, the following fields are displayed:

Field Module Property? Description
Domain Role No Indicates the role of the plug-in.
  • If you choose REQUESTOR, the role of the plug-in is a requestor, and the plug-in can request security services from a security domain controller.
  • If you choose CONTROLLER, you can create a domain controller by creating a security metaspace.
Note: Requestors can never be used as discovery nodes.

See TIBCO ActiveSpaces Developer’s Guide for detailed information.

Security Policy File Yes (Optional) Specifies a policy file for the security domain controller.
Note: The policy file is required if you choose CONTROLLER from the Domain Role list.
Security Token File Yes (Optional) Specifies a token file for the security domain requestor that is authenticated by a security domain controller.
Note: The token file is required if you choose REQUESTOR from the Domain Role list.
Identity Password Yes (Optional) Specifies the password to access the security policy file and the security token file.
Credentials No (Optional) Select from the following ways to authenticate requestors:
  • NONE: no authentication is used.
  • USERPWD: user name and password authentication. By default, this option is selected.
  • X509V3: certificate-based authentication against an LDAP server.
The following fields are available when you select USERPWD from the Credentials list:
Domain Yes Specifies the domain name defined in the security policy file:
  • system: operating system user authentication
  • ldap: LDAP user authentication
User Name Yes Specifies the user name for the domain authentication.
Password Yes Specifies the password for the domain authentication.
The following fields are available when you select X509V3 from the Credentials list:
Key File Location Yes Specifies the directory in which the PKCS#12 file that contains the certificate information is located.
Password Yes Specifies the password for the private key stored in the PKCS#12 file.