12.What is the reason for connecting different GoI
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
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
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
- A channel for locating and providing services from and
to other departments.
19. How can I integrate my published web-service with
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
A department connecting to eSangam would observe following
- 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
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.
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.
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.