eGov Opensource

eGovernments Foundation transforms urban governance with the use of scalable and replicable technology solutions that enable efficient and effective municipal operations, better decision making, and contact-less urban service delivery.

Our comprehensive software products enable Governments to put their resources to efficient use by minimising overheads. We also help bring in transparency, accountability and citizen centricity in the delivery of Government services.

eGovernments Foundation has been in the forefront of implementing eGovernance solutions since 2003. Our products have been serving over 275 ULBs across the country. Our time tested products have impacted the ULBs in a large way. We have also been involved in several eGovernance initiatives in the country.

Our primary business motivator is to increase the footprint of eGovernance across the country and help adoption in as many ULBs as possible. Going opensource with our products is a measure in this direction. It also gives us the ability to tap into the immense talent pool in India for strengthening and improving our cities. Open source also blends well with our ethical fabric of being open and transparent in our business.

Issue Tracking

Report issues via the eGov Opensource JIRA.

License

The eGov suit is released under version 3.0 of the GPL.

Powered By

User Guide

This section contains steps that are involved in build and deploy the application. FAQ related to various deployment and development issues are discussed here

Prerequisites

Database Setup

Create a database and user in postgres

Elastic Search Setup

Elastic seach server properties needs to be configured in elasticsearch.yml under <ELASTICSEARCH_INSTALL_DIR>/config

cluster.name: elasticsearch-<username> ## Your local elasticsearch clustername, DO NOT use default clustername
transport.tcp.port: 9300 ## This is the default port

Building Source

Clone the eGov repository

$ mkdir egovgithub
$ cd egovgithub
$ git clone https://github.com/egovernments/eGov.git

Change directory to <CLONED_REPO_DIR>/egov/egov-config/src/main/resources/config/ and create a file called egov-erp-<username>.properties and enter the following values based on your environment config.

search.hosts=localhost
search.port=9300
search.clusterName=elasticsearch-<username>

mail.enabled=false ##Enables or disabled email sending, this is enabled (true) by default
mail.port=465
mail.host=smtp.gmail.com
mail.protocol=smtps
mail.sender.username=abc123@gmail.com
mail.sender.password=12345

sms.enabled=false  ##Enables or disables SMS sending, this is enabled (true) by default
sms.provider.url=http://some.sms.provider.url
sms.sender.username=sms_username
sms.sender.password=sms_user_password
sms.sender=sms_sender_id

#Following are the http sms request parameter names, replace with sms provider specific request param name.
sms.sender.req.param.name=senderid
sms.sender.username.req.param.name=username
sms.sender.password.req.param.name=password
sms.destination.mobile.req.param.name=mobileno
sms.message.req.param.name=content

#In addition to the above standard parameters, any additional static parameters can be added here with 
#respective key=value, delimit with &
sms.extra.req.params=foo=bar

#SMS response error codes, replace with sms provider specific error code
sms.error.codes=401,403,404,405,406,407,408,409,410,411,412,413,414

#If sms gategway response doesn't contain error message, to log error messages for the above code then add error message entry like following
#<sms_errorcode>=<sms_error_message>
#eg:401=Invalid Username or Password

One can override any default settings available in /egov/egov-egi/src/main/resources/config/application-config.properties by adding an entry in egov-erp-<username>.properties.

Database properties are defined in the persistence-config.properties.

db.url=jdbc:postgresql://localhost:5432/postgres
db.username=erp_owner
db.password=erp_owner

Change directory back to <CLONED_REPO_DIR>/egov
Run the following commands, this will cleans, compiles, tests, migrates database and generates ear artifact along with jars and wars appropriately

mvn clean package -s settings.xml -Ddb.user=<db_username> -Ddb.password=<db_password> -Ddb.driver=<driver_class_fqn> -Ddb.url=<jdbc_url>

Redis Server Setup

By default eGov suit uses embedded redis server (work only in Linux & OSx), to make eGov suit works in Windows OS or if you want to run redis server as standalone then follow the installation steps below.

Installing redis server on Linux

sudo apt-get install redis-server

Installing redis server on Windows :- There is no official installable avialable for Windows OS. To install redis on Windows OS, follow the instruction given in https://chocolatey.org/packages/redis-64
Once installed, set the below property in egov-erp-override.properties or egov-erp-<username>.properties.

redis.enable.embedded=false ## true by default

to control the redis server host and port use the following property values (only required if installed with non default).

redis.host.name=<your_redis_server_host> ## localhost by default
redis.host.port=<your_redis_server_port> ## 6379 by default

Deploying Application

Configuring JBoss Wildfly

Download and install customized JBoss Wildfly Server from here. This server contains some additional jars that are required for the ERP.
In case properties needs to be overridden, edit the below file (This is only required if egov-erp-<username>.properties is not present)

<JBOSS_HOME>/modules/system/layers/base/

org
└── egov
  └── settings
    └── main
        ├── config
        │   └── egov-erp-override.properties
        └── module.xml

Update settings in standalone.xml under <JBOSS_HOME>/standalone/configuration

Check Datasource setting is in sync with your database details.

<connection-url>jdbc:postgresql://localhost:5432/<YOUR_DB_NAME></connection-url>
<security>
  <user-name><YOUR_DB_USER_NAME></user-name>
  <password><YOUR_DB_USER_PASSWORD></password
</security>

Check HTTP port configuration is correct in

<socket-binding name="http" port="${jboss.http.port:8080}"/>

Change directory back to <CLONED_REPO_DIR>/egov and run the below command

 $  chmod +x deploy-local.sh
$ ./deploy-local.sh

Alternatively this can be done manually by following the below steps.

Copy the generated exploded ear <CLONED_REPO_DIR>/egov/egov-ear/target/egov-ear-<VERSION> in to your JBoss deployment folder <JBOSS_HOME>/standalone/deployments
Rename the copied folder egov-ear-<VERSION> to egov-ear-<VERSION>.ear
Create or touch a file named egov-ear-<VERSION>.ear.dodeploy to make sure JBoss picks it up for auto deployment

Start the wildfly server by executing the below command

 $ cd <JBOSS_HOME>/bin/
 $ nohup ./standalone.sh -Dspring.profiles.active=production -b 0.0.0.0 &

-b 0.0.0.0 only required if application accessed using IP address or domain name.

Monitor the logs and in case of successful deployment, just hit http://localhost:<YOUR_HTTP_PORT>/egi in your favorite browser.
Login using username as egovernments and password demo

Accessing the application using IP address and domain name

This section is to be referred only if you want the application to run using any ip address or domain name.

1. To access the application using IP address:

Have an entry in eg_city table in database with an IP address of the machine where application server is running (for ex: domainurl="172.16.2.164") to access application using IP address.
Access the application using an url http://172.16.2.164:8080/egi/ where 172.16.2.164 is the IP and 8080 is the port of the machine where application server is running.

2. To access the application using domain name:

Have an entry in eg_city table in database with domain name (for ex: domainurl= "www.egoverpphoenix.org") to access application using domain name.
Add the entry in hosts file of your system with details as 172.16.2.164 www.egoverpphoenix.org (This needs to be done both in server machine as well as the machines in which the application needs to be accessed since this is not a public domain).
Access the application using an url http://www.egoverpphoenix.org:8080/egi/ where www.egoverpphoenix.org is the domain name and 8080 is the port of the machine where application server is running.

Always start the wildfly server with the below command to access the application using IP address or domain name.

 nohup ./standalone.sh -b 0.0.0.0 -Dspring.profiles.active=production &

Developer Guide

This section gives more details regarding developing and contributing to eGov suit.

Repository Structure

egov - folder contains all the source code of eGov opensource projects

Check out sources

git clone git@github.com:egovernments/eGov.git or git clone https://github.com/egovernments/eGov.git

Prerequisites

Install your favorite IDE for java project. Recommended Eclipse or IntelliJ IDEA
Install maven >= v3.2.x
Install PostgreSQL >= v9.3
Install Elastic Search >= v1.7.1
Install Jboss Wildfly v9.0.x
Git and JDK 8 update 66 or later

Note: Please check in eGov Tools Repository for any of the above software installables before downloading from internet.

1. Eclipse Deployment

Install Eclipse Mars Eclipse Mars
Import the cloned git repo using maven Import Existing Project.
Install Jboss Tools and configure Wildfly Server.
Since jasperreport related jar's are not available in maven central, we have to tell eclipse to find jar's in alternative place for that navigate to Windows -> Preference -> Maven -> User Settings -> Browse Global Settings and point settings.xml available under egov-erp/
Double click on wildfly9.x --> open launch configurations --> edit VM arguments and add string '-Dspring.profiles.active=production' at the end of existing VM arguments.
Now add your EAR project into the configured Wildfly server.
Start Wildfly in debug mode, this will enable hot deployment.

2. Intellij Deployment

TODO - Contribution welcome

3. Database Migration Procedure

Any new sql files created should be added under directory <CLONED_REPO_DIR>/egov/egov-<javaproject>/src/main/resources/db/migration
Core product DDL and DML should be added under <CLONED_REPO_DIR>/egov/egov-<javaproject>/src/main/resources/db/migration/main
Core product sample data DML should be added under <CLONED_REPO_DIR>/egov/egov-<javaproject>/src/main/resources/db/migration/sample
All sql scripts should be named with following format.
Format V<timestamp-in-YYYYMMDDHHMMSS-format>__<module-name>_<description>.sql
DB migration will automatically happen when application server starts, incase required while maven build use the above given maven command.

Migration file name sample

V20150918161507__egi_initial_data.sql

For More details refer Flyway

Note: This system is supported

OS:-

Linux
Mac
Windows (If Redis server standalone installed).

Browser:-

Chrome (Recommended)
Firefox

petmongrels/eGov

eGov Opensource

Issue Tracking

License

Powered By

User Guide

Prerequisites

Database Setup

Elastic Search Setup

Building Source

Redis Server Setup

Deploying Application

Configuring JBoss Wildfly

Accessing the application using IP address and domain name

1. To access the application using IP address:

2. To access the application using domain name:

Developer Guide

Repository Structure

Check out sources

Prerequisites

1. Eclipse Deployment

2. Intellij Deployment

3. Database Migration Procedure

Migration file name sample