Working with Remote Clients

If you have purchased the TIBCO ActiveSpaces Remote Client in addition to the Enterprise Edition, then you can implement applications that run on remote clients and which communicate with a space running on the core ActiveSpaces cluster.

Java applications that connect remotely to the metaspace need to use the MemberDef's setRemoteDiscovery call to specify the list of well known addresses to connect to.

C applications need to set the Discovery URL attribute in the memberDef object to specify the remote listen URL that was specified when the as-agent was started on a seeder device in the core cluster.

Remotely connected client applications have access to the same features as any other applications, however they can never be seeders on a space. If an application remotely connected asks to get a space as a seeder it will get a handle on the space but will remain a leech. The SEEDED distribution scope is the scope of the proxy client they are connected to.

Also, while remotely connected clients can invoke methods on the space members, on can not invoke methods remotely on a remote client application.

• Connecting a Remote Client
  On the device that will act as the full peer proxy to the remote clients, run the as-agent program, and specify the discovery URL, the listen URL, and the remote listen URL.
• Starting as-agent to Listen for a Remote Client
  Start an as-agent with remote_listen parameter that points to a URL and specific port.
• Connecting to the Seeder from the Remote Client
  After the as-agent is running on the seeder, remote clients can connect to a metaspace and a space on the proxy machine.