Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 2 TIBCO ActiveSpaces Fundamentals : Using Remote Clients

Using Remote Clients
If you have purchased a license for the Remote Client Edition of TIBCO ActiveSpaces, then you can implement ActiveSpaces on remote clients.
A remote client acts as a node without actually being a a member of the cluster. Remote clients can:
How Remote Client Communication Works
Remote clients are implemented as follows:
1.
You set up an as-agent, which plays the role of a seeder and a proxy server for remote clients.
2.
Using the as-agent, you issue a remote_listen command to contact the remote client and accept incoming remote client connections.
3.
Remote Clients and Seeding Distribution Scope
A remote client application can never become a seeder on a space. If an application that is remotely connected requests to join a space as a seeder, it will remain a leech. However, remote client applications can still create browsers or listeners with a distribution scope of “seeded.” In this case, the seeded scope becomes the scope of the proxying member of the metaspace through which the remote client is connecting (i.e,. the tuples that the proxy seeds on the space if any).

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved