Have an account?

  •   Personalized content
  •   Your products and support

Need an account?

Create an account

Cisco SCMS SM Java API Programmer Guide, Release 5.1.x

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

Cisco SCMS SM Java API Programmer Guide, Release 5.1.x

Chapter Title

Nonblocking API

Results

Updated:
March 6, 2015

Chapter: Nonblocking API

Nonblocking API

Published: March 9, 2015

Introduction

This chapter introduces features unique to the Nonblocking API. It presents all Nonblocking API methods and provides code examples for each method.

This chapter consists of the following sections:

Reliability Support

The Nonblocking API can work in two different modes—reliable and nonreliable. When the mode is not specified, the default is reliable mode.

Reliable Mode

In reliable mode, the API ensures that no requests to the Cisco Service Control Subscriber Manager are lost. The API maintains an internal storage for all API requests that are sent to the Cisco Service Control Subscriber Manager. After a reply from the Cisco Service Control Subscriber Manager is received, the request is considered committed and the API can remove the request from its internal storage. If the connection between the API and the Cisco Service Control Subscriber Manager fails, the API accumulates all requests in its internal storage until the connection to the Cisco Service Control Subscriber Manager is established. On reconnection, the API resends all noncommitted and committed requests to the Cisco Service Control Subscriber Manager, so that no requests are lost.

Note In reliable mode, the order of resending requests is guaranteed. The API resends the requests in the order in which they were called.

Nonreliable Mode

In nonreliable mode, the API does not ensure that requests sent to the Cisco Service Control Subscriber Manager are executed. In addition, all requests that are sent by the API when the connection to the Cisco Service Control Subscriber Manager is down are lost unless an external reliability mechanism is implemented.

Autoreconnect Support

The Nonblocking API supports autoreconnection to the Cisco Service Control Subscriber Manager to address connection failures. When this option is activated, the API can determine when the connection to the Cisco Service Control Subscriber Manager is lost. When the connection is lost, the API activates a reconnection task that tries to reconnect to the Cisco Service Control Subscriber Manager until it is successful.

Note The autoreconnect support option can be activated in both reliability modes.

Multithreading Support

The Nonblocking API supports an unlimited number of threads calling its methods simultaneously.

Note In a multithreaded scenario for the Nonblocking API, the order of invocation is guaranteed. The API performs operations in the same order in which they were called.

ResultHandler Interface

The Nonblocking API enables you to set a result handler. A result handler is an interface with two methods, handleSuccess and handleError, as represented in the following code:

public interface ResultHandler {
/**
* handle a successful result
*/
public void handleSuccess(long handle, Object result);
 
/**
* handle a failure result
*/
public void handleError(long handle, Object result);
}
 

You should implement this interface if you want to be informed about the success or error results of operations performed through the API.

Note This is the only interface for retrieving results. Results cannot be returned immediately after the API method has returned to the caller.

Note To receive operation results, set the result handler of the API before calling API methods for which you want to receive results. Set the result handler after the API is connected (as in the “ResultHandler Interface Example” section).

Both handleSuccess and handleError methods accept two parameters:

  • Handle—Each API operation return-value is a handle of type long. This handle enables correlation between operation calls and their results. When a handle operation is called with a handle of value X, the result will match the operation that returned the same handle value ( X) to the caller.
  • Result—Actual result of the operation. Some operations may return a result of NULL.

ResultHandler Interface Example

The following example is a simple implementation of a result handler that prints a message to stdout (when the result is successful) or to stderr (when the result is a failure). This main method initiates the API and assigns a result handler.

For correct operation of the result handler, follow the code sequence presented in this example.

Note This example does not demonstrate the use of callback handles.

import com.pcube.management.framework.rpc.ResultHandler;
import com.pcube.management.api.SMNonBlockingApi;
 
public class ResultHandlerExample implements ResultHandler{
 
public void handleSuccess(long handle, Object result) {
System.out.println("success: handle="+handle+", result="+result);
}
 
public void handleError(long handle, Object result) {
System.err.println("error: handle="+handle+", result="+result);
}
 
public static void main (String args[]) throws Exception{
if (args.length != 1) {
System.err.println("usage: ResultHandlerExample <sm-ip>");
System.exit(1);
}
 
//note the order of operations!
SMNonBlockingApi nbapi = new SMNonBlockingApi();
nbapi.connect(args[0]);
nbapi.setResultHandler(new ResultHandlerExample());
nbapi.login(...);
}
}

Nonblocking API Construction

In addition to the constructors described in the “API Construction” section, the Nonblocking API provides constructors that enable you to set the reconnect period and the reliability mode.

Nonblocking API Syntax

The syntax for the additional Nonblocking API constructors is as follows:

public SMNonBlockingApi(long autoReconnectInterval)
public SMNonBlockingApi(boolean reliable, long autoReconnectInterval)
public SMNonBlockingApi(String legName, long autoReconnectInterval)
public SMNonBlockingApi(String legName, boolean reliable, long autoReconnectInterval)

Nonblocking API Arguments

The following list describes the constructor arguments for the additional Nonblocking API constructors:

  • autoReconnectInterval—Defines the interval (in milliseconds) between attempts to reconnect, as follows:

– If the value is 0 or less, the reconnection task is not activated (no autoreconnect is attempted).

– If the value is greater than 0 and if there is a connection failure, the reconnection task is activated every autoReconnectInterval milliseconds.

Default value is –1 (no autoreconnect is attempted).

Note To enable the autoreconnect support, the connect method of the API must be activated at least once. For more information, see the “Nonblocking API Code Examples” section.

  • reliable—An argument that defines whether the API should work in reliable mode, as follows:

– TRUE—The API works in reliable mode.

– FALSE—The API works in nonreliable mode.

Default value is TRUE (the API works in reliable mode).

Nonblocking API Examples

The following example constructs a reliable API with an autoreconnection interval of 10 seconds:

SMNonBlockingAPI nbapi = SMNonBlockingAPI(10000);
nbapi.connect(<SM IP address>);
 

The following example constructs a reliable API without autoreconnection support:

// API construction
SMNonBlockingAPI nbapi = SMNonBlockingAPI();
// Connect to the API
nbapi.connect(<SM IP address>);
 

The following example constructs a nonreliable API with autoreconnection support:

// API construction
SMNonBlockingAPI nbapi = SMNonBlockingAPI(false,10000);
// Initial connection - to enable the reconnect task
nbapi.connect(<SM IP address>);

Nonblocking API Initialization

The Nonblocking API enables you to initialize certain internal properties to customize the API. This initialization is performed by using the API init method.

Note For the settings to take effect, the init method must be called before the connect method.

You can set the following properties:

  • Output queue size—The internal buffer size that limits the maximum number of requests that can be accumulated by the API until they are sent to the Cisco Service Control Subscriber Manager. The default is 1024.
  • Operation timeout—The desired timeout (in milliseconds) on a nonresponding proprietary remote procedure call (PRPC) protocol connection. The default is 45 seconds.

Nonblocking API Initialization Syntax

The syntax for the Nonblocking API init method is as follows:

public void init(Properties properties)

Nonblocking API Initialization Parameters

The Nonblocking API init method has the following parameters:

  • properties (java.util.Properties)—Enables setting the following properties described previously:

– To set the output queue size, use prpc.client.output.machinemode.recordnum.

– To set the operation timeout, use prpc.client.operation.timeout.

Nonblocking API Initialization Example

The following Nonblocking API code illustrates how to customize properties during initialization. Note that the init method is called before the connect method.

// API construction
SMNonBlockingAPI nbapi = SMNonBlockingAPI(10000);
// API initialization
java.util.Properties p = new java.util.Properties();
p.setProperty("prpc.client.output.machinemode.recordnum", 2048);
p.setProperty("prpc.client.operation.timeout", 60000);// 1 minute
nbapi.init(p);
// initial connect to the API to enable the reconnect task
nbapi.connect(<SM API address>);

Nonblocking API Methods

This section describes the methods of the Nonblocking API.

All methods return a handle of type long that can be used to correlate operation calls and their results. See the “ResultHandler Interface” section.

The operation results passed to the result handler are similar to the return values described in the same method in the Chapter 3, “Blocking API”, except for the following:

  • Basic types are converted to their Java class representation. For example, int is translated to java.lang.Integer.
  • Return values of Void are translated to NULL.

Note An error is passed to the result handler only if the matching operation in the Blocking API generates an exception with the same arguments that correspond to the state of the Cisco Service Control Subscriber Manager database at the time of the call.

All methods will generate java.lang.IllegalStateException if called before a connection with the Cisco Service Control Subscriber Manager is established.

This section describes the following methods:

login

This section provides the syntax for the login operation.

Syntax

The login syntax is as follows:

public long login(String subscriberName,
String[] mappings,
short[] mappingTypes,
String[] propertyKeys,
String[] propertyValues,
String domain,
boolean isMappingAdditive,
int autoLogoutTime)
 

The operation functionality is the same as the matching Blocking API operation. See the “login” section for more information.

logoutByName

This section provides the syntax for the logoutByName operation.

Syntax

The logoutByName syntax is as follows:

public long logoutByName(String subscriberName,
String[] mappings,
short[] mappingTypes)
 

The operation functionality is the same as the matching Blocking API operation. See the “logoutByName” section for more information.

logoutByNameFromDomain

This section provides the syntax for the logoutByNameFromDomain operation.

Syntax

The logoutByNameFromDomain syntax is as follows:

public long logoutByNameFromDomain(String subscriberName,
String[] mappings,
short[] mappingTypes,
String domain)
 

The operation functionality is the same as the matching Blocking API operation. See the “logoutByNameFromDomain” section for more information.

logoutByMapping

This section provides the syntax for logoutByMapping operation.

Syntax

The logoutByMapping syntax is as follows:

public long logoutByMapping(String mapping,
short mappingType,
String domain)
 

The operation functionality is the same as the matching Blocking API operation. See the “logoutByMapping” section for more information.

loginCable

This section provides the syntax for the loginCable operation.

Syntax

The loginCable syntax is as follows:

public long loginCable(String CPE,
String CM,
String IP,
int lease,
String domain,
String[] propertyKeys,
String[] propertyValues)
 

The operation functionality is the same as the matching Blocking API operation. See the “loginCable” section for more information.

logoutCable

This section provides the syntax for the logoutCable operation.

Syntax

The logoutCable syntax is as follows:

public long logoutCable(String CPE,
String CM,
String IP,
String domain)
 

The operation functionality is the same as the matching Blocking API operation. See the “logoutCable” section for more information.

Nonblocking API Code Examples

This section presents example code for logging in and logging out subscribers.

Login and Logout

The following example logs in a predefined number of subscribers to the Cisco Service Control Subscriber Manager and then logs them out. Note the implementation of a disconnect listener and a result handler.

package nonblocking;
 
import com.pcube.management.framework.rpc.DisconnectListener;
import com.pcube.management.framework.rpc.ResultHandler;
import com.pcube.management.api.SMNonBlockingApi;
import com.pcube.management.api.SMApiConstants;
 
class LoginLogoutDisconnectListener implements DisconnectListener {
public void connectionIsDown() {
System.err.println("disconnect listener:: connection is down");
}
}
 
class LoginLogoutResultHandler implements ResultHandler {
int count = 0;
//prints a success result every 100 results
public synchronized void handleSuccess(long handle, Object result) {
Object tmp = null;
if (++count%100 == 0) {
tmp = result instanceof Object[] ? ((Object[])result)[0] : result;
System.out.println("\tresult "+count+":\t"+tmp);
}
}
 
//prints every error that occurs
public synchronized void handleError(long handle, Object result) {
System.err.println("\terror: "+count+":\t"+ result);
++count;
}
//waits for result number 'last result' to arrive
public synchronized void waitForLastResult(int lastResult) {
while (count<lastResult) {
try {
wait(100);
} catch (InterruptedException ie) {
ie.printStackTrace();
}
}
}
}
 
public class LoginLogout {
public static void main (String args[]) throws Exception{
//check arguments
checkArguments(args);
int numSubscribersToLogin = Integer.parseInt(args[2]);
 
//instantiation
SMNonBlockingApi nbapi = new SMNonBlockingApi();
try {
//initation
nbapi.setDisconnectListener(
new LoginLogoutDisconnectListener());
nbapi.connect(args[0]);
LoginLogoutResultHandler resultHandler =
new LoginLogoutResultHandler();
nbapi.setResultHandler(resultHandler);
//login
System.out.println("login of "+numSubscribersToLogin +" subscribers");
for (int i=0; i<numSubscribersToLogin; i++) {
nbapi.login("subscriber"+i, //subscriber name
getMappings(i), //a single ip mapping
new short[]{
SMApiConstants.MAPPING_TYPE_IP
},
null, //no properties
null,
args[1], //domain
false, //mappings are not additive
-1); //disable autologout
}
resultHandler.waitForLastResult(numSubscribersToLogin);
//logout
System.out.println("logout of "+numSubscribersToLogin +" subscribers");
for (int i=0; i<numSubscribersToLogin; i++) {
nbapi.logoutByMapping(getMappings(i)[0],
SMApiConstants.MAPPING_TYPE_IP,
args[1]);
}
resultHandler.waitForLastResult(numSubscribersToLogin*2);
} finally {
nbapi.disconnect();
}
}
static void checkArguments(String[] args) throws Exception{
if (args.length != 3) {
System.err.println("usage: java LoginLogout "+
"<SM-address> <domain> <num-susbcribers>");
System.exit(1);
}
}
//'automatic' mapping generator
private static String[] getMappings(int i) {
return new String[]{ "10." +((int)i/65536)%256 + "." +
((int)(i/256))%256 + "." + (i%256)};
}
}
 

The following example logs in a predefined number of IPv6 subscribers to the Cisco Service Control Subscriber Manager and then logs them out. Note the implementation of a disconnect listener and a result handler.

package nonblocking;
 
import com.pcube.management.framework.rpc.DisconnectListener;
import com.pcube.management.framework.rpc.ResultHandler;
import com.pcube.management.api.SMNonBlockingApi;
import com.pcube.management.api.SMApiConstants;
class LoginLogoutDisconnectListener implements DisconnectListener {
public void connectionIsDown() {
System.err.println("disconnect listener:: connection is down");
}
}
class LoginLogoutResultHandler implements ResultHandler {
int count = 0;
//prints a success result every 100 results
public synchronized void handleSuccess(long handle, Object result) {
Object tmp = null;
if (++count%100 == 0) {
tmp = result instanceof Object[] ? ((Object[])result)[0] : result;
System.out.println("\tresult "+count+":\t"+tmp);
}
}
//prints every error that occurs
public synchronized void handleError(long handle, Object result) {
System.err.println("\terror: "+count+":\t"+ result);
++count;
}
//waits for result number 'last result' to arrive
public synchronized void waitForLastResult(int lastResult) {
while (count<lastResult) {
try {
wait(100);
} catch (InterruptedException ie) {
ie.printStackTrace();
}
}
}
}
public class LoginLogout {
public static void main (String args[]) throws Exception{
//check arguments
checkArguments(args);
int numSubscribersToLogin = Integer.parseInt(args[2]);
//instantiation
SMNonBlockingApi nbapi = new SMNonBlockingApi();
try {
//initation
nbapi.setDisconnectListener(
new LoginLogoutDisconnectListener());
nbapi.connect(args[0]);
LoginLogoutResultHandler resultHandler =
new LoginLogoutResultHandler();
nbapi.setResultHandler(resultHandler);
//login
System.out.println("login of "+numSubscribersToLogin +" subscribers");
int subsCount = 0;
 
outer:for(int j=0x0;j<=0xf;j++)
{
for(int i=0x0000; i<=0xffff;i++)
{
nbapi.login("sub"+subsCount,new String[]{"2001:200:"+Integer.toHexString(j)+":"+Integer.toHexString(i)+"::/64"}, new short[]{SMApiConstants.MAPPING_TYPE_IPV6}, new String[]{"upVlinkId"},new String[]{ "85"}, "subscribers", true, -1);
subsCount++;
if(subsCount == numSubscribersToLogin)
break outer;
}
}
 
 
 
resultHandler.waitForLastResult(numSubscribersToLogin*2);
//logout
subsCount = 0;
System.out.println("logout of "+numSubscribersToLogin +" subscribers");
outer:for(int j=0x0;j<=0xf;j++)
{
for(int i=0x0000; i<=0xffff;i++)
{
 
nbapi.logoutByMapping("2001:200:"+Integer.toHexString(j)+":"+Integer.toHexString(i)+"::/64",
SMApiConstants.MAPPING_TYPE_IPV6,
args[1]);
subsCount++;
if(subsCount == numSubscribersToLogin)
break outer;
 
}
}
resultHandler.waitForLastResult(numSubscribersToLogin*2);
} finally {
nbapi.disconnect();
}
}
static void checkArguments(String[] args) throws Exception{
if (args.length != 3) {
System.err.println("usage: java LoginLogout "+
"<SM-address> <domain> <num-susbcribers>");
System.exit(1);
}
}
//'automatic' mapping generator
private static String[] getMappings(int i) {
return new String[]{ "10." +((int)i/65536)%256 + "." +
((int)(i/256))%256 + "." + (i%256)};
}
}
 

Nonblocking API Code for High Performance Example

This section contains the example code for logging in and logging out subscribers in multiple connections for high performance. Each API connection will login or logout using different set of subscribers.

import java.util.concurrent.ExecutorService;
import java.util.concurrent.Executors;
 
import com.pcube.management.framework.rpc.DisconnectListener;
 
import com.pcube.management.framework.rpc.ResultHandler;
 
import com.pcube.management.api.SMNonBlockingApi;
 
import com.pcube.management.api.SMApiConstants;
 
class LoginLogoutDisconnectListener implements DisconnectListener {
public void connectionIsDown() {
System.err.println("disconnect listener:: connection is down");
}
}
 
class LoginLogoutResultHandler implements ResultHandler {
int count = 0;
//prints a success result every 100 results
public synchronized void handleSuccess(long handle, Object result) {
Object tmp = null;
if (++count%100 == 0) {
tmp = result instanceof Object[] ? ((Object[])result)[0] : result;
System.out.println("\tresult "+count+":\t"+tmp);
}
}
//prints every error that occurs
public synchronized void handleError(long handle, Object result) {
System.err.println("\terror: "+count+":\t"+ result);
++count;
}
//waits for result number 'last result' to arrive
public synchronized void waitForLastResult(int lastResult) {
while (count<lastResult) {
try {
wait(100);
} catch (InterruptedException ie) {
ie.printStackTrace();
}
}
}
}
 
public class SMAPIMultipleConnectionExample {
private static final int NTHREDS = 15;
public static void main (String args[]) throws Exception{
 
//check arguments
checkArguments(args);
 
String smAddr=args[0];
int numThreads=Integer.parseInt(args[1]);
int numSubs=Integer.parseInt(args[2]);
int startSubSuffix=Integer.parseInt(args[3]);
int firstOctect=Integer.parseInt(args[4]);
boolean additivaMapping=Boolean.parseBoolean(args[5]);
String domain=args[6];
ExecutorService executor = Executors.newFixedThreadPool(NTHREDS);
int start = startSubSuffix;
SMNonBlockingApi snbapi = null;
int startIp = firstOctect;
for (int i = 0; i < numThreads; i++) {
/*
* This code for creating multiple api connections based on thread count*/
snbapi=new SMNonBlockingApi();
try {
snbapi.connect(smAddr);
} catch (Exception e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
Runnable worker = new LoginLogoutThread(snbapi,numSubs,start,String.valueOf(startIp),additivaMapping,domain);
start = start + numSubs;
//Just increasing the 10 for next set off IPs for next thread
startIp = startIp+10;
 
executor.execute(worker);
}
executor.shutdown();
while (!executor.isTerminated()) {
}
}
static void checkArguments(String[] args) throws Exception{
 
if (args.length != 7) {
System.err.println("usage: java LoginLogout "+
"<SM-address> <num-threads> <num-susbcribers> <start-subname-suffix> <first-octect> <additive-mapping> <domain> ");
System.exit(1);
}
}
}
class LoginLogoutThread implements Runnable {
 
private int totalSubscribers =0;
private int startCount =0;
String startIp = null;
String domain = "subscribers";
boolean additiveMapping=true;
SMNonBlockingApi nbapi;
LoginLogoutThread(SMNonBlockingApi nbapi,int totalSubscribers,int startCount,String startIp,boolean addMap,String domain) {
this.nbapi=nbapi;
this.totalSubscribers = totalSubscribers;
this.startCount = startCount;
this.startIp = startIp;
this.additiveMapping = addMap;
this.domain=domain;
}
public void run() {
try {
//instantiation
LoginLogoutResultHandler resultHandler =new LoginLogoutResultHandler();
nbapi.setResultHandler(resultHandler);
 
final long startT = System.currentTimeMillis();
int total = startCount+totalSubscribers;//(startCount+num)-1;
System.out.println("login of "+totalSubscribers +" subscribers");
 
for (int i=startCount;i<total;i++)
{
try
{
nbapi.login("subscriber"+i, //subscriber name
new String[]{((startIp+"."+ ((i>>16)%256)) + '.' + (((i>>8))%256)) + '.' + (i%256)}, //a single ip mapping
SMApiConstants.ALL_IP_MAPPINGS
,
 
null, //no properties
null,
domain, //domain
false, //mappings are not additive
-1); //disable autologout
}
catch (Exception e)
{
//Log the error
}
}
resultHandler.waitForLastResult(totalSubscribers);
 
long milli = (System.currentTimeMillis() - startT);
long secs = milli/1000;
 
long loginRate = (totalSubscribers*1000)/milli;
System.out.println("**********************************************");
System.out.println("total seconds for "+totalSubscribers+" logins: " +secs);
System.out.println("logins per second : " + loginRate);
System.out.println("**********************************************");
System.out.println("logout of "+totalSubscribers +" subscribers");
for (int i=startCount;i<total;i++)
{
try
{
nbapi.logoutByMapping(((startIp+"."+ ((i>>16)%256)) + '.' + (((i>>8))%256)) + '.' + (i%256),
SMApiConstants.MAPPING_TYPE_IP,
domain);
 
}
catch (Exception e)
{
//Log the error
}
}
resultHandler.waitForLastResult(totalSubscribers*2);
 
long milliseconds = (System.currentTimeMillis() - startT);
long totalsecs = milliseconds/1000;
 
long logoutRate = (totalSubscribers*1000)/milli;
System.out.println("**********************************************");
System.out.println("total seconds for "+totalSubscribers+" logout: " +totalsecs);
System.out.println("logout per second : " + logoutRate);
System.out.println("**********************************************");
}
catch(Exception e){
e.printStackTrace();
}
finally
{
nbapi.disconnect();
}
}
}

 

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

Related Cisco Community Discussions

About Us
Contact Us
Work with Us