This project belonged to AT&T.

FPP is a client which triggers microservices to create account_id. Once the account_id is created, it generates successful response. This response is the request for other microservices, either it may be revenue or inventory. This microservice creates new request_id and our timer application, which is running under Jboss, will pick the new request and generate the report and save that report in DB as clob. The data present in clob is converted into xml format and the data is transferred into particular path in Linux machine then success acknowledgement is returned to FPP which is the client for this application. if it is unsuccessful then it will retry for 3 times. If in all the 3 trials we get Failure response then same failure status is sent to the client according to business logic which is shared by the client.

This Project belonged to Bharti Airtel for Africa.

OverScratchCard is an application used for recharging the balance of SIM card.

If any person scratches the recharge code written in top up vouchers more than required and some of the number of the code gets omitted due to over scratching, then this application is used by retailers or customer care people to verify the user and the number is correct or not and then recharging the same with the proper code.

Previously application was authenticating the user details from IBM side using the client servers.

The new code developed used the Single Sign Out. The details filled by the user gets authenticated from the client side. Application redirects to client link to authenticate and then after authenticating comes back to the application and retrieves the Group Id using database and then after that it follows to retrieve the Role Id and then Links according to the Role Id and displays to the user as per his role (e.g. admin, retailer or customer care) for further use of recharging the number with the correct value.

Including, I was involved in handling the Service request and the Incidents occurring in the application as L3 Ticket Manager. I was involved in raising Service Request, opening polices between two servers, and raising Change Requests for the deployments

The objective of this project is to provide a reliable e-commerce platform that helps to sell a wide range of goods online. We used Java along with Spring framework to build the platform make available for the end users.

The objective of this project is to provide a reliable e-commerce platform that helps to sell a wide range of goods online. We used Java along with Spring framework to build the platform make available for the end users.

Edge is a part of IoT which mainly focuses on maintaining and looking after all the Stores of Walmart ensuring there is no kind of defect. There are four different Data Extractors Present in stores which regularly checks for all the physical constraints that needs to be prefect for storing foods and ensuring that they should not decay with time.

Edge is a part of IoT which mainly focuses on maintaining and looking after all the Stores of Walmart ensuring there is no kind of defect. There are four different Data Extractors Present in stores which regularly checks for all the physical constraints that needs to be prefect for storing foods and ensuring that they should not decay with time.

FPP is a client which triggers microservices to create account_id. Once the account_id is created, it generates successful response. This response is the request for other microservices, either it may be revenue or inventory. This microservice creates new request_id and our timer application, which is running under Jboss, will pick the new request and generate the report and save that report in DB as clob. The data present in clob is converted into xml format and the data is transferred into particular path in Linux machine then success acknowledgement is returned to FPP which is the client for this application. if it is unsuccessful then it will retry for 3 times. If in all the 3 trials we get Failure response then same failure status is sent to the client according to business logic which is shared by the client.

FPP is a client which triggers microservices to create account_id. Once the account_id is created, it generates successful response. This response is the request for other microservices, either it may be revenue or inventory. This microservice creates new request_id and our timer application, which is running under Jboss, will pick the new request and generate the report and save that report in DB as clob. The data present in clob is converted into xml format and the data is transferred into particular path in Linux machine then success acknowledgement is returned to FPP which is the client for this application. if it is unsuccessful then it will retry for 3 times. If in all the 3 trials we get Failure response then same failure status is sent to the client according to business logic which is shared by the client.

OverScratchCard is an application used for recharging the balance of SIM card. If any person scratches the recharge code written in top up vouchers more than required and some of the number of the code gets omitted due to over scratching, then this application is used by retailers or customer care people to verify the user and the number is correct or not and then recharging the same with the proper code. Previously application was authenticating the user details from IBM side using the client servers. The new code developed used the Single Sign Out. The details filled by the user gets authenticated from the client side. Application redirects to client link to authenticate and then after authenticating comes back to the application and retrieves the Group Id using database and then after that it follows to retrieve the Role Id and then Links according to the Role Id and displays to the user as per his role (e.g. admin, retailer or customer care) for further use of recharging the number with the correct value.

OverScratchCard is an application used for recharging the balance of SIM card. If any person scratches the recharge code written in top up vouchers more than required and some of the number of the code gets omitted due to over scratching, then this application is used by retailers or customer care people to verify the user and the number is correct or not and then recharging the same with the proper code. Previously application was authenticating the user details from IBM side using the client servers. The new code developed used the Single Sign Out. The details filled by the user gets authenticated from the client side. Application redirects to client link to authenticate and then after authenticating comes back to the application and retrieves the Group Id using database and then after that it follows to retrieve the Role Id and then Links according to the Role Id and displays to the user as per his role (e.g. admin, retailer or customer care) for further use of recharging the number with the correct value.