Monthly Archives: May 2016

CodeIgniter and XMLRPC

What are we going to do?

We’ll mimic what we already achieved in CodeIgniter and NuSOAP post using XMLRPC method.

So, we’ll create two endpoints, one is for getting a CD info (function name : getCdInfo) and the other is for getting all of CDs listed (function name : getCds).

We’ll still implement all of our function inside Welcome controller. The difference is that the registration process is placed inside index() function while the implementation is outside index() function but still within Welcome class.

The Server

Here’s the configuration and registration process inside index() function:

Notice how I defined the endpoint name and register it. So, getCdInfo endpoint will be implemented in Welcome controller and getCdInfo function, while getCds endpoint will be implemented in Welcome controller as getCds function.
Now, here’s the implementation:

getCdInfo takes one parameter, so, we need to pass $request as getCdInfo function parameter while getCds function doesn’t take any parameter, so we omit it.
Pay attention on getCds function, you’ll learn how I implement an XMLRPC endpoint that return an array of array (a data table).

The Client

Same as CodeIgniter and NuSOAP, for simplicity, we’ll implement the client as part of Welcome controller. Here’s the client code:

getCdInfo call will output something like this:

While getCds will return something like this:

As you can see, the output of XMLRPC method is the same as NuSOAP method. No fixing needed!
Here’s the complete source code of our controller:

CodeIgniter and NuSOAP

What are we going to do?

We’ll use NuSOAP to create a webservice using CodeIgniter and consume it using CI also.

In this tutorial, we’ll use “cds” table from “cdcol” database bundled from XAMPP. “cds” table content looks like this:

cds table content

cds table content

Download NuSOAP here :
Extract “lib” folder from into your CI “application/libraries/”. We’ll create simple library warper for NuSoap.
Now, enter your CI “application/libraries/” folder and create a new file named “Nusoap_library.php”. Here’s the content:

We’ll use default controller from CI, i.e. Welcome.php. We’ll create two webservice endpoints: one for getting info about a CD based in it’s “id” and one for getting all of CDs.
All of webservice data types definition, registration and implmentation will be placed inside Wellcome controller’s “__construct()” function. Here’s the complete code for “__construct()” function:

The first step is loading the library and configuring your webservice:

We’ll define a new data type for our CD info based on “cds” table structure:

Now, our complex type that will hold list of CDs (array of CDs).

After finished defining all needed data types, we’ll register all needed webservice endpoint.
First endpoint is “getCdInfo” to get info about a CD based on it’s “id”. It takes one parameter (“id”) and return a “Cd” type.

Second endpoint is “getCds” to get all stored CD in the “cds” table. It takes no parameter and return an array of CDs.

Registration is finished, now onto the implementation. Here’s the code:

Pay attention, that I’m using “get_instance()” in order to query the database because we can’t call “$this” inside these endpoint functions.
Next, we’ll edit the default “index()” function, replace it with these:

You may try accessing your webservice from your browser and see how it looks

WSDL schema

WSDL schema

webservice description

webservice description

Now, some fixing!

Before accessing our webservice via a SOAP client, we need to fix NuSoap library. Open “application/libraries/lib/nusoap.php”, go to line 6132 and comment that line so it would look like this:

If you didn’t do this fixing step, you’ll get a blank result when calling an endpoint that return an array of data. Further testing using SoapUI will reveal some error like this:

Fixing is done, now we’ll test it.
For simplicity reason, we’ll put our client inside our Welcome controller. Here’s the code:

As you can see, the code is quite simple, $res1 will contain output from “getCdInfo” endpoint

and $res2 will contain an array of CDs as a result from calling “getCds”.

Here’s the complete source code of our controller, in case you missed something: