Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Provisioning the IPSCS

    For integration with the SRC software, the IPSCS must be provisioned in a specific way. All IPSCS service objects, including application signatures, service elements, TAPs, service bundles, and service offers, must be created.

    Before you introduce a new service that will be implemented by a DPI script service, you must create the service bundle and service offers. Before you remove a service, you must deactivate all sessions for the service before removing the corresponding service offers and bundles from the IPSCS.

    See Integration of the SRC Software and the Ellacoya DPI Platform.

    Service Bundles

    Enable usage collection on service bundles by checking Collect Start/Stop Usage Data and the Collect Transmit and Receive Byte Counts checkboxes in Service Creation Manager.

    Every DPI script service must have a corresponding ISPCS service bundle. To match the service bundle with the script service, the service bundle must have the same name as the DPI script service, but be prefixed by SDX_. For example, if the script service is called dpiService1, the service bundle must be called SDX_dpiService1.

    Service Offers

    Enable usage collection on service offers by checking the Enable Usage Collection checkbox in Service Creation Manager.

    For every combination of implemented services that could be active at the same time, there must be a service offer with the name prefixed by “ SDX_” configured in the IPSCS. The service offer must contain the service bundles that correspond to the services.

    When a script service activates or deactivates a service session, it checks the list of services that will be active after the activation or deactivation. The script service then searches for a service offer with the right set of service bundles. The script service keeps a local cache of all service offer names and which bundles they contain. If the cache does not contain a service offer with the right set of bundles, the script service reloads the service offers from the SLE. If necessary, the script service queries the SLE for all service offers in the configured domain. If the appropriate offer is not found after a reload, the service activation or deactivation fails with an exception.

    Traffic-Accounting Profiles

    For every service bundle, there must be a TAP with the same name as the service bundle.

    Modified: 2018-09-20