Open topic with navigation

TIBCO ActiveSpaces® - Enterprise Edition 5.0.0

# Administration Service

Configure the ActiveSpaces Core Servers to run administration services rather than running standalone `tibdgadmind` administration daemons. Important points to note:

- Any environment that is using secure transports, except the one using TIBCO FTL-generated certificates, must run the administration daemon as a service.

- The `exepath` property must refer to the location of the `tibdgadminsvc` binary and not the `tibdgadmind` binary.

- If one of the Core Servers is running an administration service, all the Core Servers must run the administration service. It is done to ensure that whenever the realm is functioning, an administration service is available.

Here is an example of the configuration for a cluster containing three ActiveSpaces Core Servers that each runs an administration service.

Copy

    globals:
      core.servers:
        SRV1: localhost:8080
        SRV2: localhost:8081
        SRV3: localhost:8082
      max.log.size: 10485760

    servers:
      SRV1:
      - realm:
          data: TIBCO_HOME/activespacesdata/realm_data
      - tibdgadminsvc:
          exepath: /opt/tibco/as/current-version/bin/tibdgadminsvc
          logfile: TIBCO_HOME/activespacesdata/logs/tibdgadminsvc1.log
      SRV2:
      - realm:
          data: TIBCO_HOME/activespacesdata/realm_data
      - tibdgadminsvc:
          exepath: /opt/tibco/as/current-version/bin/tibdgadminsvc
          logfile: TIBCO_HOME/activespacesdata/logs/tibdgadminsvc2.log
      SRV3:
      - realm:
          data: TIBCO_HOME/activespacesdata/realm_data
      - tibdgadminsvc:
          exepath: /opt/tibco/as/current-version/bin/tibdgadminsvc
          logfile: TIBCO_HOME/activespacesdata/logs/tibdgadminsvc3.log

In this example, each ActiveSpaces Core Server hosts an administration service, the `max.log.size` property is configured globally but each administration service has its own `logfile`.

## Properties

The following table shows the properties that can be configured for the administration service and their corresponding `tibdgadmind` 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.

YAML Property | Command-Line Argument | Required/Optional
--- | --- | ---
exepath | None | Required
loglevel | --trace | Optional
logfile | --logfile | Optional
max.log.size | --max-log-size | Optional
max.logs | --max-logs | Optional
http.timeout | --http-timeout | Optional

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO ActiveSpaces® - Enterprise Edition

Copyright © 2009-2025. Cloud Software Group, Inc. All Rights Reserved.