FAQs

For Additional Queries Contact us
1. What is eSangam?

eSangam : eGovernance Services Integration framework, formerly NSDG (National e-Governance Services Delivery Gateway) is a standards based messaging middleware for achieving secure messaging and interoperability across departmental applications. The framework also provides supporting services for seamless integration and service delivery i.e., centralized connector hosting, workflow management, joined up services delivery and self registration and online service access approval mechanism. For more details, Click Here

2. What is SSDG?

SSDG stands for the State e-Governance Services Delivery Gateway. SSDG is a productized version of eSangam. SSDG has been envisaged to be deployed at the State level to facilitate message exchange between the applications in the State.

The vision for national gateway is to service the Central MMPs and Line Ministries. The State Gateways are being installed in the State Data Centres and will service all the State Departments and Line Ministries. The State Gateways and the National Gateway are interconnected forming a constellation of Gateways called eSangam, servicing the needs of various departments across the length and breadth of the country.

3. What are Domain Gateways?

The gateways implemented in specific business verticals/departments for the respective projects to route requests between their front end and back end applications are known as Domain Gateways. Various departments at the Centre or at the State level may have the requirement of their own gateways to address their business specific requirements.

4.Who is a Service Provider?

The back-end government departments offering e-services to citizens and businesses, and to other government departments, are collectively referred to as Service Providers (SP).

5. Who is a Service Access Provider?

You can register yourself either as a SAP(Service Access Providers) or as a SP(Service Provider). SAP will register themselves with the eSangam to provide access to the certain e-Governance services to citizens. SP's will be mainly the government departments which will provide e-Governance services. They need to register their services with the eSangam.

6. What is Gateway Service Provider (GSP)?

A Gateway Service Provider (GSP) is an agency who undertakes the operation and maintenance activities of a specific installation (Central, State or Domain) of the Gateway.
7.Who is the Gateway Service Provider for eSangam?

Centre for Development of Advanced Computing, Mumbai (C-DAC) has been entrusted the responsibility of operation and maintenance of the Gateway on behalf of the Government of India.

8. What is the Gateway Constellation?

eSangam has been developed to service the Central MMPs. SSDG's€™ are the productized version of eSangam, which are being installed in the various State Data Centres. The SSDG'€™s will service the various State Government departments. Domain Gateway's€™ are being set up in various MMP's€™ in order to service the specific needs of the MMP. The SSDG's€™, eSangam and Domain Gateways are interconnected via the Internet to form a constellation of Gateways, which will help service the various departments across the length and breadth of the country.

9. What is National Services Directory (NSD)?

The National Services Directory (NSD) is the central registry of all Gateways and their services in the Gateway Constellation. If any service is not available in the local Gateway, then gateway can resolve the service with the help of NSD.

10.What is the reason for connecting different GoI departments?

Unlike point to point connections between departments which create a mesh and also does tight coupling between applications, National e-Governance Service Delivery Gateway is a standards based messaging switch which simplifies this task by providing seamless interoperability and exchange of data across heterogeneous departmental applications with the help of e-Governance Gateway Standards (IIP, IIS, IGIS) that are based on open standards (XML and SOAP). Thus this middleware infrastructure will serve as a one stop shop for all the Government departments who need these common services in their workflows for providing services to the citizens and to delink the front-end from back-end.
The latest version of eSangam support lightweight eSangam messages through SOAP and REST protocols supporting XML and JSON data formats.

About Integration


12.What is the reason for connecting different GoI departments?

The services provided by government departments can be availed at a single place/ portal by connecting them to the Service Access provider through gateway. A department can register themselves in eSangam as eSangam user and can act as Service Provider, Service access Provider, Service Integrator and all of these at the same time. For example, a User registered on eSangam can provide some services to be accessed by other departments, can access some services provided by the other departments and at the same time can provide the technical support to some other department in developing their connectors and integrating the services.

13.How do I get information regarding integration with eSangam?

An Integration Kit will be provided at the time of integration of services with eSangam. This kit provides a comprehensive overview of how the various entities viz Service Providers, Service Access Providers and Domain Gateway Providers can access the Gateway and the Policies in place for these associations. The document provides in depth insight into the procedure for accessing the Gateway in terms of the Forms to be completed and Authorizations to be furnished for gaining access to the Gateway. It further provides the list of reports that the various entities that associate with the Gateway will receive.

14. How do I integrate with eSangam?

C-DAC Mumbai is the GSP (Gateway Service Provider) for eSangam. However, the Integration support will be provided by one of the System Integrators selected by Meity. The system Integrator will provide the connector templates and guidelines for facilitating communication with the Gateway.

15. What platform is eSangam available on?

eSangam is designed and developed using Open Standards and Open source facilities. Details are available on request.

16.I have a Dot Net application. Can I integrate with eSangam?

Any Dot Net application can integrate with eSangam. This will require making some changes to your application so as to call the web service of the eSangam based on the IIP and IIS protocols. The other option is to use the Dot Net Generic Connector provided by the CDAC to communicate with the eSangam.

17. I have a legacy system running in my department. Can I integrate it with eSangam?

Yes, you can. Necessary additions will have to be undertaken in the legacy application in order for it to communicate with eSangam based on IIP and IIS protocols.
18. I have already published a web-service for my application. Do I need to use eSangam? How can I benefit?

Web services makes ones platform ready for interoperability (provided certain disciplines and conformances are obeyed). We appreciate the readiness of a department to interoperate which has published its services as web-service. The following will be the two key benefits of exposing the service via the Gateway vis-à-vis a purely Web Services model.
  • A readily available PKI based security perimeter thereby reducing levels of information security infrastructure for department.
  • A channel for locating and providing services from and to other departments.
19. How can I integrate my published web-service with eSangam?

You have a choice of building and deploying web-service proxies for the Gateway's web-service. Alternately, you may opt for C-DAC services to provide you Generic Connectors and guidelines for interfacing with Gateway's web-service.

20.I am from a Government Department. How can eSangam benefit me?

A department connecting to eSangam would observe following benefits
  • The middleware ensures end to end secure communication between the service seeker and the service provider.
  • By connecting to a Gateway in the Gateway constellation, the departmental applications can avail all the services offered by other departmental applications connected to the Gateways in the constellation. A department can provide joined up/integrated services by using the services of other departmental applications connected to the Gateway constellation.
21. I want to provide Government Services on my portal. How can I use eSangam for the same?

For this you will have to integrate your portal application with the eSangam. The portal will have to be registered with eSangam as a Service Access Provider (SAP).
Now There are two specifications of eSangam.
  1. IIP and IIS protocol
    To use this you can either integrate your application yourself by changing your application to communicate with eSangam based on IIP and IIS protocols or you can use connectors provided by C-DAC for integration with eSangam.
  2. Non IIP protocol.
    This is a newly added specification which has support for soap and rest api. You can generate a soap or a rest request from your environment and this will be converted to Non IIP specification by connectors which will be hosted at eSangams environment.


Security



22. How can I obtain standards for communication with eSangam?

Standards will be made available on request. An email can be sent to nsdg@cdac.in.

23. What data encryption mechanism is used by eSangam?

For IIP Specification
The Gateway provides the option for use of digital signature and certificates to all stakeholders interacting with the gateway for identification, authentication and authorization. The SHA1 and W3CSigned authentication is in use to restrict unauthorized access from SAP to its Services with the help of these authentication mechanisms. eSangam provides the following three levels of authentication.
  1. Authentication with username and password
  2. Authentication using encryption technique
  3. Authentication using W3C signatures

For Non IIP Specification
Here the Gateway provides mechanism for SHA-256 authentication. Since in non iip the interface to the gateway is through centralized connectors the departments are provided with an option to implement any additional layer of encryption as per their choice to provide additional security.

24. Is eSangam secure? What security features implemented at gateway?

Yes it is secure. The following three features have been implemented at gateway:-
  • Security compliance of the eSangam infrastructure as per ISO 17799:2005/BS7799-1:2005.
  • PKI based Authentication at eSangam ensures integrity, non-repudiation, and confidentiality for End to End secure message exchange.
  • Use of bidirectional SSL for end to end communication thereby ensuring security during transmission of messages.

Others

25. Is there any front-end application to register the service with eSangam?

Yes. We have a web portal where you can register as a user (SAP/SP/SAPSI/SP SI). Here User can register services, request for access to a service, grant permission to other users for accessing your service etc. You can visit the portal and download the manual or contact our team for more details.

26. How do eSangam ensure that the services of the SP are being accessed by authorized Service Access Providers?

The criteria of access control would be defined by the SP for a given service at the time of registration with the Gateway provider.

27. What is Connector?

A Connector is a software module for facilitating interfacing with gateway (protocol conversion). Gateway communication based on IIP/IIS grammar and application need not be aware of IIP/IIS structuring in order to be able to communicate with Gateway.

28.Will C-DAC provide the connector to SP / SAP?

  1. For IIP Specification
    In order to connect to a Gateway, two connectors are required :€“ Generic Connector and Application Specific Connector. The Generic Connector is provided by C-DAC€“ Mumbai free of charge. However the Application Specific Connector will have to be developed by SP/SAP.
  2. For Non IIP Specification
    In case of non iip, there is only one connector and that will be hosted at eSangams environment. CDAC will provide a template for this connector in which user will need to make few changes as per individual requirements.


29. Is there any automated notification for services which will be added or deleted by SP at later stage?

This facility is not available as of now. This feature is planned for roll out in the next release.

30. What is synchronous and asynchronous communication?

  • Synchronous Services: The services that require the connection between SAP (service seeker) and SP (service provider) to be present from the point of request to the time that the service response is received from the SP are called Synchronous service. For e.g.: - Verify Unique ID of Citizen.
  • ASynchronous Services: Services that do not require continuous connection between SAP and SP fall under the category of Asynchronous services. In this type of a service, SAP requests a service from eSangam and eSangm sends the acknowledgement back to SAP. eSangam forwards the request to the SP and once a response is received from the SP, eSangam forwards the response to the SP. For e.g : - Request for Birth Certificate.


31. Who decides that a particular service is synchronous or asynchronous?

The SP decides the mode of the Services at the time of registering the service with eSangam. The SAP will be able to access the Services only in the mode specified by the SP during registration s with the Gateway.

32.What is the version of .Net required for the integration with the Gateway?

.Net framework version 2.0 and above can be used for integration with the Gateway.
33. What is the scalability in terms of message throughput available for eSangam?
The Gateway can process upto 250 messages per second with a response time of 3 seconds. eSangam is scalable to achieve a throughput of 1000 messages per second with a response time of 3 seconds.