Creating a DPI Script Service
To create a script service within the service scope:
- Within the service scope, create a script service with
the SRC CLI or the C-Web interface.
See Customizing Service Implementations or Configuring Script Services (C-Web Interface)
- Specify the values for the following options for the service.
Script Type
- Type of script that the script service uses.
- Value—You must use URL for DPI script services
Class Name
- Name of the class that implements the ScriptService SPI. The SAE instantiates this class when it starts the script service.
- Value—You must enter net.juniper.smgt.dpi.sle.EllacoyaScriptService for DPI script services
File/URL
- URL to the Java archive (JAR) files that are associated with the script.
- Value—For a DPI script service, you must include
all of the following JAR files.
- file:///opt/UMC/sae/var/scriptservice/dpi/lib/dpi-ss.jar,
- file:///opt/UMC/sae/var/scriptservice/dpi/lib/sle-client.jar,
- file:///opt/UMC/sae/var/scriptservice/dpi/lib/jbossall-client.jar,
- file:///opt/UMC/sae/var/scriptservice/dpi/lib/jdom.jar,
- file:///opt/UMC/sae/var/scriptservice/dpi/lib/jnet.jar,
-
file:///opt/UMC/sae/var/scriptservice/dpi/lib/log4j.jar

Note: All JAR files except dpi-ss.jar are Ellacoya SLE files, and must be compatible with the version of the SLE that is being used. Check the release notes for the version of the SLE that the JAR files packaged with the SRC software are from. If in doubt, replace the JAR files from the SLE installation, which can be found in <SLE install dir>/lib (for example: /opt/ellacoya/lib).