The tibasMetaspace_Connect Method

Typically, one of the first things an ActiveSpaces process does is connect to a metaspace.

Before an application can do anything with ActiveSpaces, it must be connected to a metaspace.

As mentioned in TIBCO ActiveSpaces Concepts, there are two modes of connection to a metaspace—as a full peer or as a remote client. Regardless of the connection mode, the API calls to use to connect to a Metaspace are the same.

The Metaspace.connect() method—or, in C, the tibasMetaspace_Connect() call—has two input parameters:

  • name
  • a MemberDef object

The tibasMetaspace_Connect() function returns a metaspace object that you can use to define a space or join a space. The input parameters are explained in more detail in the sections that follow.

Metaspace Name

The metaspace name is a string containing the name of a particular metaspace instance. The name must only contain alphanumeric characters, with the exception of - (hyphen) and _ (underscore), where _ (underscore) cannot be the first character. If null or an empty string is given as argument to the connect call, the default metaspace name of ms will be used.
Note: The naming constraints for Metaspace names also apply to Space names.

MemberDef Object

The MemberDef object contains the attributes of the connection to the metaspace:

  • discovery attribute
  • listen attribute
  • MemberName attribute
  • Discovery Attribute
    The discovery attribute specifies how this instance of the metaspace discovers the current metaspace members.
  • Listen Attribute
    Regardless of the mechanism used for the initial metaspace member discovery phase, the members of the metaspace always establish TCP connections to each other.
  • MemberName Attribute
    The MemberName attribute specifies a string that indicates the member name. Each member must have a unique name in the metaspace.
Related concepts
Related reference