Proxy

Proxies are not typically run in ActiveSpaces Core Servers, however, you can run them in the Core Servers if need be. For development environments, it might be appropriate to configure an ActiveSpaces Core Server that hosts a state keeper, an administration service, and a proxy. In such an environment, starting the grid involves starting the ActiveSpaces Core Server and the node.

The following example provides a simple configuration suitable for a development environment. In this example, there is one ActiveSpaces Core Server that hosts a state keeper, an administration service, and a proxy. The only other component that you must start to create a running grid is a node.

globals:
  core.servers:
    SRV1: localhost:8080

servers:
  SRV1:
  - realm:
      data: TIBCO_HOME/activespacesdata/realm_data
  - tibdgkeeper:
      exepath: /opt/tibco/as/current-version/bin/tibdgkeeper
      name: k1
      logfile: TIBCO_HOME/activespacesdata/logs/_default-k1.log
  - tibdgadminsvc:
      exepath: /opt/tibco/as/current-version/bin/tibdgadminsvc
      logfile: TIBCO_HOME/activespacesdata/logs/tibdgadminsvc.log
  - tibdgproxy:
      exepath: /opt/tibco/as/current-version/bin/tibdgproxy
      name: p1
      logfile: TIBCO_HOME/activespacesdata/logs/_default-p1.log

Properties

The following table lists the properties that you can configure for the administration service and their corresponding proxy command-line arguments. Other command-line arguments, such as the URL for the realm and any security-related arguments are not required because the connection to the realm and authentication is handled by the hosting ActiveSpaces Core Server.