Get current tenant database configuration

This GET operation retrieves a list of the current tenant database configuration which includes the database username, password, and url.

GET /pcc/spcm/oam/tenants

HEADER INFO

tenant: <tenantName>

authorisation: HTTP Basic Auth

accept: application/json

permissions: SPCM_OAM_READ_PERMISSION

JSON response

When you run this API operation, you receive a JSON response including an array of tenants which includes the name and the configuration.

The configuration includes the username, password, and url of the tenant database.

{
    "name": "tenant.0.1",
    "config": {
        "jdbc.username": "greatest-user",
        "jdbc.password": "secret-password",
        "jdbc.url": "jdbc:mysql://localhost/database1"
    },
    "name": "tenant.1.1",
    "config": {
        "jdbc.username": "greatest-user-ever",
        "jdbc.password": "secret-password-again",
        "jdbc.url": "jdbc:mysql://localhost/database2"
    }
}

OAM tenant configuration descriptions

These are the JSON key-value pair descriptions for the SPCM OM API tenant configuration operations.

Field Type Description

name

string

The name of the tenant, slice, and shard.

The format is <tenant>.<slice>.<shard> For example: theTenant.1.0.

config

list

An object list containing the following:

jdbc.username = the tenant database username
jdbc.password = the tenant database password
jdbc.url = the url for the tenant database

HTTP response codes

Code Description

200

success!

207

Multistatus response

Check out HTTP statuses for more details.

This is not applicable to all operations.

400

malformed request

401

unauthorised; bad username or password

403

forbidden; user does not have appropriate privileges

404

tenant not found

409

conflict with target resource

This often occurs if the item already exists, such as a plan, group, or name.

This is not applicable to all operations.

412

failed validation; this typically means that a property was not set or a value is out of range.

example

HTTP 412
{
  "errors" : [
        {
          "field" : "name",
          "description" : "name is mandatory"
        }
    ]
}

422

failed processing (after passing validation).

example

HTTP 422
{
    "message": "Subscriber max plan count exceeded",
    "errorCode": 1
}

500

internal error

503

request rejected due to overload