Syntax
list [<FILTER> ...]
| Name | Description |
|---|---|
<FILTER> |
Command filter, that is based on instance identifiers, types or statuses |
The list command gives the possibility to display the dynamic map of the instances
(dispatchers, guiders, raters, updaters, taxers and bulkloaders) that are deployed
within the Core Server system you are connected to.
This dynamic instance map:
Instance Statuses
In a Core Server system, each instance may have the following statuses:
| Instance Status | Definition | ||
|---|---|---|---|
| STARTING | The instance is executing its starting sequence | ||
| WAITING | This status represents an intermediate status that is only used to inform that the instance is currently registering on the dispatcher instance and is thus waiting for permission in order to continue the starting sequence of its services | ||
| ON | The instance services are started and ready for completing operation requests | ||
| STOPPING | The instance began executing a shutdown sequence | ||
| OFF | The instance is completely stopped and cannot perform any further operation | ||
| STANDBY | The instance is currently in standby, which means that this instance is excluded from the scope of the charging operations, and that its handled partitions have been transferred to the other instances whose status is "on" | ||
| GOING_INTO_STANDBY | The instance is going into standby, which means that this instance is still performing charging operations, while its handled partitions are being transferred to the other instances whose status is "on" | ||
Depending on the instance type, additional information can complete the status. For example: "Master" indicates that the related dispatcher is currently the master dispatcher instance.
To display information related to a subset of deployed instances, you can specify one or several of the following criteria (separated by the space character):
Note
When using several criteria:
Example
Considering the following filter:
dispatcher rater guider#1 on waiting
The following expression will be used to filter the dynamic instance map:
(<INSTANCE_TYPE=dispatcher> or <INSTANCE_TYPE=rater> or <INSTANCE_ID=guider#1>) and
(<STATUS=on> or <STATUS=waiting>)
And the following instances will be displayed:
Your user interface displays the following information about all the deployed instances (dispatcher, guider, rater, updater, taxer, and bulkloader):
+----+---------+-----+---------+---------+-------------+-----------+-------+------------+
|ID |HOSTNAME |HTTP |EXTERNAL |INTERNAL |CURRENT DATE |START DATE |STATUS | PARTITIONS |
+----+---------+-----+---------+---------+-------------+-----------+-------+------------+
| .. | |WS@ |TCP@ |TCP@ | | | | |
| | |HCI@ |TCP@ |TCP@ | | | | |
+----+---------+-----+---------+---------+-------------+-----------+-------+------------+
Legend:
| Column Name | Description | ||
|---|---|---|---|
| ID | The identifier of an instance of the SAP CC Core Server system; Use this identifier to define the target instances of your commands with Admin+ | ||
| HOSTNAME | The name or the IP address (IPv4 or IPv6) of the machine that hosts one or several instances of the Core Server system | ||
| HTTP (HCI, WS) | The visible access points of the HTTP communications dedicated to both the HCI and Web Services (WS) technical interfaces. The client applications or systems have to know this information as it defines the endpoints of the system. | ||
| EXTERNAL | The visible access points of the TCP/IP communications dedicated to the high-speed Message TCP technical interface. The client applications or systems have to know this information. | ||
| INTERNAL | The private access points of the internal TCP/IP communications between the different instances of the Core Server system. These settings are the base for the interinstance communications. | ||
| START DATE | The date and time when the instance started | ||
| CURRENT DATE | The current date and time of the instance in the SAP CC system | ||
| STATUS | The status of the instance | ||
| PARTITIONS | The CSV list of partition ranges handled by the instance (only for rater and guider instances) | ||
Tip
In your SAP system landscape, you can get the list of the client applications (or systems) connected via the Message TCP technical interface for convergent charging services: a mediation system, the SAP CC BART Server system, an SAP CC IEC application.
To work with this command in the user interface, you must have a specific role in your SAP CC user profile.
Refer to the SAP CC 5.0 Security Guide for more user assistance and information about the necessary authorizations.
server
-
To manage the SAP CC Core Server systemstandby
-
To enable or disable the standby status of rater and/or guider instancesping
-
To ping the SAP CC system or some specified instanceslist_clients
-
To display the list of connected SAP CC charging clients
Instance ID identifies an instance in a Core Server system uniquely. When several Core Server systems are deployed in your SAP system landscape, the instance ID information may be not unique anymore depending on the deployment options.
Consult the SAP CC 5.0 Application Help for more information about:
SAP CC provides several endpoints for accessing the Web Services. Consult the Endpoints of SAP CC Web Services section in the SAP CC 5.0 Web Services Documentation for more user assistance.
Consult:
| Code | Message | Action |
|---|---|---|
| err.communication_failure | Error: A communication failure occurred with {host}:{port}. | |
| err.invalid_filter | Error: Invalid filter: {filter} |