Perl JSON-RPC Client Binding


Raritan's JSON-RPC Perl bindings require the following perl packages:


In dnf-based Linux distributions the following command will install the required packages:

dnf install "perl(LWP::Protocol::https)" "perl(LWP::UserAgent)" \
"perl(HTTP::Request::Common)" "perl(JSON)" \
"perl(JSON::RPC::Common::Marshal::HTTP)" "perl(Error)" \
"perl(Data::Dumper)" "perl(parent)"


There are various Perl distributions available for Windows (see http://perl.org/get.html). The bindings were tested with ActiveState Perl (http://www.activestate.com/activeperl/downloads). After installing ActiveState Perl, the required modules can be installed with the following command:

ppm install LWP::Protocol::https LWP::UserAgent HTTP::Request::Common \
JSON JSON::RPC::Common::Marshal::HTTP Error Data::Dumper parent

Note on SSL Certificate Verification

All Raritan devices enforce use of HTTPS when accessing the JSON-RPC service. By default, programs written with this client binding try to verify the authenticity of the server when connecting. This requires a valid SSL certificate to be installed on the device. When trying to connect to a device without a valid SSL certificate the client program will terminate with an error message.

It is possible to disable the SSL certificate verification by setting the 4th parameter of Raritan::RPC::Agent() to 1.


my $agent = new Raritan::RPC::Agent($url, "admin", "raritan", 1)


Getting device information:


use Raritan::RPC;
use Data::Dumper;
my $agent = new Raritan::RPC::Agent('https://my-emx.example.com', 'admin', 'raritan');
my $emx = $agent->createProxy('/model/emd');
my $metadata = $emx->getMetaData();
print Dumper($metadata);


$VAR1 = {
'hwRevision' => '0x01',
'ctrlBoardSerial' => 'PNW1691120',
'fwRevision' => '',
'nameplate' => {
'model' => 'EMX2-888-v0',
'imageFileURL' => '',
'manufacturer' => 'Raritan',
'rating' => {
'voltage' => '100-240V',
'current' => '0.7A',
'power' => '70VA',
'frequency' => '50/60Hz'
'partNumber' => 'emx2-888',
'serialNumber' => 'PH81234567'
'macAddress' => 'fe:00:10:42:00:67'

Configuring the SNMP agent:

use Raritan::RPC;
my $agent = new Raritan::RPC::Agent('https://my-device.example.com', 'admin', 'raritan');
my $snmp_proxy = $agent->createProxy('/snmp');
my $config = $snmp_proxy->getConfiguration();
$config->{v2enable} = 0;
$config->{readComm} = 'public';
$config->{writeComm} = 'private';

IDL-to-Perl Mapping

IDL Modules and Perl Package Names

All classes dealing with Raritan JSON-RPC communication are located in Perl packages starting with Raritan::RPC. All named sections in IDL files (module, interface and enumeration) provide a scope for their included identifiers and are added as further components to the Perl package name.

Interfaces and Methods

IDL interfaces are mapped to Perl proxy classes which provide all methods defined by the IDL interface and its bases. Perl methods require the same number of scalar arguments as defined in the IDL signature. Simple types like integers, strings or enumerations are passed by scalar value; structures, vectors and maps are passed by reference. Output parameters are passed as references to a scalar variable which will be modified to point to the returned value. If the method is declared to have a non-void return type the Perl method will return a single scalar value.


# no parameters, no return value
# two input parameters, integer return value
$ret = $user_manager->createAccount('newuser', 'newpassword');
# one output parameter, integer return value
my $results;
$ret = $diagnostics->listTcpConnections(\$results);


IDL structures are mapped as scalar references to Perl hashes. Each element of the structure results in a hash entry whose key is the element identifier and whose value is a Perl scalar. When passing a structure to a method call addtional hash entries are ignored.


$ssh_settings = {
'allowPasswordAuth' => 1,
'allowPublicKeyAuth' => 0


Enumerated values are referenced by their fully-qualified name:

$ret = $outlet->setPowerState(Raritan::RPC::pdumodel::Outlet::PowerState::PS_ON);


Vectors are mapped as scalar references to Perl lists. Each list entry must be a scalar.

$recipients = [ 'somebody@invalid.com', 'somebody.else@invalid.com' ];
$smtp->testConfiguration($cfg, $recipients);


Maps are mapped as scalar references to Perl hashes:

$priorities = {
'important_client' => Raritan::RPC::webcam::Priority::VERY_HIGH,
'other_client' => Raritan::RPC::webcam::Priority::LOW
$ret = $webcam->setClientTypePriorities($priorities);


In case of error conditions during a proxy method call or the createProxy funtion exceptions will be thrown. They can be caught using the try statement from the Perl::Error module.

The following exceptions are defined:

Example for catching an exception:

use Raritan::RPC;
use Error qw(:try);
try {
print "Querying firmware version ... ";
my $agent = new Raritan::RPC::Agent('https://my-device.example.com', 'admin', 'raritan');
my $firmware_proxy = $agent->createProxy('/firmware');
my $version = $firmware_proxy->getVersion();
print "Success\n";
print "Firmware version: $version\n";
} catch Raritan::RPC::HttpException with {
my $e = shift;
print "ERROR: ", $e;

Raritan::RPC::Agent Method Reference

Constructor: new Raritan::RPC::Agent($url, $user, $password, $no_cert_check)

Creates a new agent.


If username or password are omitted, it is necessary to call either set_auth_basic() or set_auth_token() before the first request.

set_auth_basic($user, $password)

This method enables HTTP basic authentication using username and password.



This method enables HTTP authentication using a session token. A session token can be obtained by calling the newSession method of the session.SessionManager interface.



Returns the current timeout and optionally sets a new request timeout.



createProxy($rid, $basetype)

Creates a new proxy object for the given resource id.

This method will query the type information for the specified resource ID and create a proxy object which provides all methods defined in the IDL definition.

When connecting to very old firmware versions (PX2 2.2 and earlier, EMX 2.0 and earlier) the type information of a resource ID cannot be queried. In this case the $basetype argument is required.




Enables request tracing. When verbose mode is enabled all JSON-RPC requests and responses will be echoed to the console.