Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
ContentIndex
  
[+] Expand All
[-] Collapse All

Symbols  A  B  C  D  E  G  I  L  M  N  O  P  R  S  T  W

 

Symbols

3GPP    
Charging-Rule-Base-Name
gateway    
configuration example
3GPP gateway    
charging rule    
installation example
removal example
charging rule installation    
service activation
charging rule removal    
service deactivation
charging rule report
Charging-Rule-Base-Name
Charging-Rule-Install
Charging-Rule-Name
configuration statements
configuration summary
directory-connection    
configuring
directory-eventing    
configuring
file logging    
configuring
grouped configurations    
configuring
Gx interface    
configuring
initial properties    
configuring
Juniper-Substitution
Juniper-Substitution-Name
Juniper-Substitution-Value
local properties    
configuring
managing
NIC proxies    
configuration prerequisites
resolution information, configuring
NIC proxy    
configuring
non-parameterized charging rule
object adapter Internet address    
configuring
overview
parameterized charging rule
PCRF
peer communication    
redundancy
restarting
SAE    
mapping between concepts
service accounting
service activation sequence
service deactivation sequence
service modification sequence
session termination sequence
starting
stopping
subscriber login sequence
subscriber logout sequence
subscriber type    
configuring
system logging    
configuring
3GPP Gy    
configuration statements
configuration summary
directory-connection    
configuring
directory-eventing    
configuring
file logging    
configuring
grouped configurations    
configuring
initial properties    
configuring
interface    
configuring
local properties    
configuring
managing
NIC proxies    
configuration prerequisites
resolution information, configuring
NIC proxy    
configuring
object adapter Internet address    
configuring
overview
peer communication    
redundancy
restarting
service activation sequence
service deactivation sequence
starting
stopping
subscriber login sequence
subscriber logout sequence
subscriber type    
configuring
system logging    
configuring
3GPP Gy NIC proxies    
cache, configuring    
SRC CLI
NIC replication, configuring    
SRC CLI
replication, configuring    
SRC CLI
resolution information, configuring    
SRC CLI
 

A

Application Services Gateway.     See Web Services Gateway    
arguments for scripts and methods
ASG (Application Services Gateway).     See Web Services Gateway    
 

B

B2B environments
business partner responsibilities    
Dynamic Service Activator
business partners
business-to-business environments
 

C

classify-traffic condition    
expanded classifiers    
configuring
clients    
gateway    
testing
Web Services Gateway
Web Services Gateway
configuration namespace
conventions    
notice icons
text
customer support    1
contacting JTAC
 

D

Diameter    
peers    
configuring    12
documentation    
comments on
dynamic properties
Dynamic Service Activator    
access constraints    
defining    12
access to attributes    
configuring, SRC CLI
access to methods    
configuring, C-Web interface
configuring, SRC CLI
access to methods and scripts    
configuring, C-Web interface    12
configuring, SRC CLI    12
access to scripts    
configuring, C-Web interface
configuring, SRC CLI
access to service sessions    
configuring, SRC CLI
API
attributes    
access to
configuring with C-Web interface
configuring with SRC CLI
gateway extension    
description
general properties    
configuring, C-Web interface
configuring, SRC CLI
groups    
configuring with C-Web interface
configuring, SRC CLI
interacting with Web application server    12
loading    
sample data
logging properties    
configuring, C-Web interface    12
configuring, SRC CLI
methods    1
access to    1234
monitoring with SRC CLI
NIC proxies, monitoring    
SRC CLI
NIC proxies, viewing    
C-Web interface
SRC CLI
overview
properties for clients and scripts    
configuring, C-Web interface    12
configuring, SRC CLI    12
redundancy
sample data    12
scripts    
access to    1234
service sessions    
access to
session handles    
configuring, SRC CLI
SOAP operations, monitoring    
SRC CLI
SOAP operations, viewing    
C-Web interface    12
starting with C-Web interface
starting with SRC CLI
statistics, viewing    
C-Web interface
SRC CLI
subscriber types    
configuring, SRC CLI
test environment    
configuring, SRC CLI    12
PCMM services
testing    1
clients    12
Web application gateway client    12
 

E

events, publishing    123
expanded classifiers    
configuring
 

G

gateway    
SRC    12
gateway extension
 

I

IMS service sessions    
configuring
test environment    
configuring
testing    12
SRC CLI
 

L

local properties    
configuration    
SRC CLI    12
directory location of SRC data, configuring    12
logging properties    
Dynamic Service Activator    1
configuring with C-Web interface    12
 

M

managing    
SAE via external applications    12
services via external application
manuals    
comments on
methods    
Dynamic Service Activator
 

N

namespace, configuration
NIC (network information collector)    
Dynamic Service Activator and
testing    
test data    12
test data, 3GPP Gy
NIC proxies    
cache, configuring    
SRC CLI    12
configuration prerequisites
Dynamic Service Activator    12
NIC replication, configuring    
SRC CLI    123
replication, configuring    
SRC CLI
resolution information, configuring    
SRC CLI    12
notice icons
 

O

operation    
Dynamic Service Activator
 

P

priorityList    123
publishing events    123
 

R

randomPick    123
redundancy    
Dynamic Service Activator
roundRobin    123
 

S

SAE (service activation engine)    
configuring 3GPP gateway as external plug-in
configuring 3GPP Gy as external plug-in
configuring IMS as external plug-in
managing via external applications    12
scripts    
running on SAE
services    
managing via external application
sessions    
service    
testing
SOAP    
interfaces, public
requests
SRC owners    1
Dynamic Service Activator
SRC SOAP Gateway.     See Web Services Gateway    
static properties
support, technical     See technical support    
 

T

technical support    
contacting JTAC
text conventions defined
 

W

Web application gateway client    
configuring, SRC CLI    12
Web application server    1
interacting with Dynamic Service Activator    12
Web applications    
Web Services Gateway
Web Services Description Language.     See WSDL    
Web Services Gateway    1
clients    1
managing
testing
Web application
wholesaler-retailer environments
WSDL files

Dynamic Service Activator Overview

Dynamic Service Activator enables business partners or their subscribers to dynamically activate services or run scripts on an SRC owner’s SAE through the SAE’s CORBA remote interface.

For managing services, Dynamic Service Activator supports a fixed set of methods and uses the SAE access interface module to access the SAE core API. For invoking scripts, Dynamic Service Activator uses the remote Java scripts interface module. These scripts can perform any function offered by the SAE’s core Java APIs.

For access control, Dynamic Service Activator requires the Juniper Networks database to be running on the same host.

The SRC owner is responsible for:

  • Deciding how to control clients’ access to methods and scripts. You can allow clients to access all methods and scripts in the directory or restrict clients’ access to specific methods and scripts.
  • Configuring Dynamic Service Activator. If you restrict clients’ access to specific methods and scripts, this task involves configuring a set of access controls between a client and each method or script that the client can use.
  • Creating Java scripts that Dynamic Service Activator will invoke on an SAE (see the SAE CORBA Remote API documentation on the Juniper Networks website at https://www.juniper.net/techpubs/software/management/src/api-index.html).

The business partner is responsible for:

  • Creating the gateway clients that communicate with the gateway.
  • Optionally, providing a way for subscribers to activate services; for example, through a portal.

Dynamic Service Activator Operation

The following steps explain how Dynamic Service Activator interacts with other components to enable the gateway client to execute a method or script on a particular SAE. Figure 2 illustrates the processes.

  1. The gateway client sends a SOAP message to the Web application server through HTTP.

    The request includes:

    • Name of the method or script that the gateway client wants to activate.
    • Arguments that the gateway client wants to pass to the method or script.
    • Type-value arguments that the gateway client passes to the method or script for one of the following:
      • Subscriber’s DN
      • Name with which the subscriber logs in
      • Name of the interface and name of the virtual router to which the subscriber connects
      • SNMP index of the interface and name of the virtual router to which the subscriber connects
      • Subscriber’s IP address, name of the managed interface, and name of the virtual router to which the subscriber connects
      • Subscriber’s primary username
      • Subscriber’s session handle
  2. The Web application server authenticates the gateway client’s identity.
  3. The Web application passes the SOAP request to Dynamic Service Activator.
  4. Dynamic Service Activator checks that:
    1. The Web application server has authenticated the gateway client and refused any requests from an unauthenticated gateway client.
    2. The gateway client is allowed to access the specified method or script.
    3. The arguments supplied by the gateway client satisfy any restrictions specified in the Dynamic Service Activator configuration that apply to the gateway client for the requested method or script.
  5. If the gateway client satisfies these requirements, Dynamic Service Activator passes an argument, such as a subscriber’s IP address specified in the Dynamic Service Activator configuration, to the network information collector (NIC).
  6. The NIC uses the argument to determine the SAE on which Dynamic Service Activator should execute the method or script.
  7. Dynamic Service Activator passes the name of the method or script and the associated arguments to the SAE through CORBA.
  8. The SAE executes the method or script and returns the expected output or SOAP fault codes through CORBA to Dynamic Service Activator.

    The expected output from the method or script depends on the values that the method or script is programmed to return. Some methods and scripts return no values; others may return a short indicator of the success or failure of the operation, an HTML page, or a complex data structure in a format the gateway client understands.

    For information about the SOAP fault codes that the methods and scripts return, see SOAP Fault Codes for Dynamic Service Activator.

  9. Dynamic Service Activator returns an output from the method or script to the gateway client through a SOAP response.

    Figure 2: Dynamic Service Activator Operation

    Dynamic Service Activator Operation

Related Documentation

Modified: 2016-05-26