The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter explains how to install, compile, and run the Cisco SCA BB Service Configuration API.
•Compiling and Running the Service Configuration API
•Service Control Engine Platform Setup
You can run the Service Configuration API on Win32, Solaris, and Linux platforms.
Compiling and running Java programs using the Service Configuration API requires JDK and JRE versions 1.4 or 1.5.
Note To use the API with Java 1.5, you must set a special JRE option (see Running the Service Configuration API with Java 1.5).
The Service Configuration API distribution is packaged in the file serviceconfig-java-api-dist.tgz, which is included in the SCA BB installation package.
The Service Configuration API distribution package installs the following folders and files:
•<installation folder>
–README
•<installation folder>\doc
–serviceconfig-javadoc.zip—The Service Configuration API Javadoc documentation
•<installation folder>\lib
–serviceconfigapi.jar—The Service Configuration API library
–jdmkrt.jar
•This folder may contain additional library JAR files that are necessary for the Service Configuration API operation.
To install the package, unpack the TGZ file (keeping the folder structure) to an empty folder.
•On Win32 platforms, use any common Windows compression utility to extract the file.
•On Linux/Solaris platforms, use:
#>tar -xvfpz serviceconfig-java-api-dist.tgz
The Service Configuration API is now installed and ready for use.
In order to compile and run a program that uses the Service Configuration API, you must have serviceconfigapi.jar in the CLASSPATH.
For example, if your program source is in MyApiClass.java, your compilation command line should be:
#>javac -classpath .;<installation folder>\lib\serviceconfigapi.jar MyApiClass.java
To run the program, the command line should be:
#>java -cp .;<installation folder>\lib\serviceconfigapi.jar MyApiClass
To use the Service Configuration API with Java 1.5, some library classes must precede the JRE classes in the boot classpath. Add the following argument to the command line:
-Xbootclasspath/p:<installation folder>/lib/jdmkrt.jar
For example:
#>java -Xbootclasspath/p:<installation folder>/lib/jdmkrt.jar -cp .;<installation folder>/lib/serviceconfigapi.jar MyApiClass
The following sections describe the configuration that is performed on the Service Control Engine (SCE) platform to allow correct Service Configuration API functioning.
The Service Configuration API configures SCA BB, which should be installed on the SCE platform. For more information, see the Cisco Service Control Application for Broadband User Guide.
The Service Configuration API uses the Proprietary Remote Procedure Call (PRPC) protocol as a transport for the connection to the SCE. PRPC is a proprietary RPC protocol designed by Cisco. For more information, see the Cisco SCMS SCE Subscriber API Programmer's Guide.
Before using the Service Configuration API, ensure that:
•The SCE is up and running, and reachable from the machine that hosts the Service Configuration API
•The PRPC server on the SCE has started