Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

You open the SAP CC Processing agent configuration dialog from a workflow configuration. To  To open the SAP CC Batch agent configuration, click  Build → New Configuration. Select  Workflow from the Configurations dialog. When prompted to  Select workflow type, select Realtime. Click Add agent and select SAP CC Batch from the Processing tab of the Agent Selection dialog.

...

SAP CC Batch agent configuration - Connection tab

Setting

Description

Hosts

In this section, add the IP address/hostname and external charging port of at least one SAP Convergent Charging Core server Dispatcher Instance.

Enable Authentication

Select this check box to enable charging API authentication.

Note

Note!

Charging API Authentication is only available for SAP CC version 4.1 SP2 and later.

User Name

SAP CC user id

Password

The password for the SAP CC user

Timeout

The timeout (in milliseconds) to apply for each connection

Enable Secured Connection

Select to use TLS encrypted communication with Hosts.

For more information about setting up Secured Connection, refer to SAP CC Secured Connection.

Keystore Path

The path to the keystore on an Execution Container host. The path must be the same for all hosts.

Note

Note!

The keystore format to be used by this particular agent is PKCS12 only.

Keystore Password

The password for the keystore

Advanced Settings Tab

The Advanced Settings tab contains extended configuration options for the agent.

...

SAP CC Batch agent configuration - Advanced Settings Tab

Setting

Description

Enable Debug Events

Select this check box to enable debug mode. This option is useful for testing purposes.

Convert BigDecimal Response to String

Select this check box to allow the conversion of the BigDecimal data type from the SAP Convergent Charging response into string. By default, the check box is empty.

Note

Note!

In terms of backwards compatibility, enabling this option prevents any compatibility issues with workflows that support the configurations from before the BigDecimal data type was introduced in version 8.0.5.0.