Example: Using the Sample COA Script Service
To use the sample COA script service provided:
- Import the sample script service using an LDAP browser.
The /SDK/scriptServices/coa/ldif/BOD1M.ldif file (in the
SDK+AppSupport+Demos+Samples.tar.gzfile) is the sample service definition for exchanging COA messages with a Cisco 10000 Series router. - Copy the /lib/coa.jar file used by the script service to a location that is accessible to the SAE by a URL, such as an FTP or HTTP server. If you do not have multiple SAEs, it can be convenient to copy the file to the /var/run directory in the SAE installation directory (/opt/UMC/sae by default).
- Modify the service substitutions for your device.
You can make these substitutions by defining the parameter substitutions in the BOD1M service with the SRC CLI or by passing the values through the SAE core API.
For information about parameter substitutions, see Configuring the COA Script Service (SRC CLI). For information about passing the values through the SAE core API, see Defining RADIUS Attributes for COA Requests with the API.
- Configure a subscription to the BOD1M service that is
activated on login.
For more information about subscriptions, see Subscriptions Overview.
If you are modifying the sample application, add the sae.jar and logger.jar files to the class path when you compile your application. These two files can be found in the lib directory of the SAE installation directory.
