Fiddler Testing.

Sending Post request through fiddler

GetToken


Method : POST
URL : http://localhost:53463/api/selfcare/gettoken/

Request Headers:
User-Agent: Fiddler
Host: localhost:53463
Content-Length: 22
Content-Type: application/json

Request Body :

{"Msisdn":"777482148"}

Login

Method : POST
URL : http://localhost:53463/api/selfcare/login/

Request Headers:
User-Agent: Fiddler
Host: localhost:53463
Content-Length: 22
Content-Type: application/json

Request Body :

{"Msisdn":"777482148", "Token":"xxxx"}

OperatorMediator.Api

Operator Mediator services will be hosted on LGN ( Lanka Gate Network).

Operator Mediator's responsibility is to route service requests executed by the clients to its respective operator service.

When the request hits the Mediator API, the mediator look-up for the respective service endpoint base on the clients msisdn/phone number and the execute the operator's respective service and return the results to the clients.
All the communication between client-mediator, mediator-operator are synchronize.

Operator.Dto : Re-defined DTOs

New DTOs (Data Transfer Object) have been introduced and modified existing to be shared between
LGN, Operators and clients (web and mobile apps).
Purpose of the new DTOs apply uniformity over data between clients, lgn and operators.

Figure 1 shows the new Dtos listed in a separate project.

Figure 1

Operator API : Exposing Operator API as REST service

While testing the REST API using fiddler, a strange issue pops up.
The method ( Login) receive live instance of the parameter object, but the properties of the object contains null values.


Figure 1 shows how the method being called via Fiddler.

Figure 1

Figure 2 shows how the method received input parameter instance with empty/null properties

Figure 2

Finally found a solution while googling the relevant issue.

Android : Getting on with Andriod.

Some screens done in the Android as a result of following Android tutorials.


Figure 1 shows the Get token screen

Figure 1

Figure 2 shows the sing in with the token and the phone number.

Figure 2

Reading REST, ASP.NET WEB API

It is required to expose the Operator services to be access by the LGN as RESTful services.
From the LGN to other consumers like Mobile devices. and the web site hosting by the LGN will be consume REST service so gaining more knowledge of REST is required at this stage as well we how to create REST service using ASP.NET WEB API.

Selection of REST service over SOAP decision resulted over following reasons.

REST doesn't required fat stack like SOAP such as  SOAP require the consumer to create proxies in order access the services.

REST works over HTTP and inherit HTTP protocols disciplines.

NO require of WSDL

For the security it depends on HTTPS

Following Links are in the list of  "Currently reading...."

Learn REST
A Brief Introduction to REST
Introduction to ASP.NET Web API
Creating a REST service using ASP.NET Web API
ASP.NET WebAPI: Getting Started with MVC4 and WebAPI
Routing in ASP.NET Web API
Routing and Action Selection

Web GUI

In order come up with a good and creative concept for the mSelfCare web portal.
I requested one of my friends to help me as I'm not a creative and UI expert.

My friend has done the following web GUI concepts for me.

Figure 1 shows the login screen

Figure 1

Figure 2 shows the Topup screen

Figure 2

Figure 3 shows the services screen

Figure 3

Figure 4 shows the transaction screen

Figure 4

Figure 5 shows the overview screen

Figure 5