About Client
Client is a SharePoint ISP and Microsoft Valued Partner well known for his products and ad-ins developed for Micorosoft ecosystem
Australia
Insurance
Challenges
- This is a product introduced by our client. This web based software provides a service that makes it possible for SharePoint site owners to plug in data from external web services by using a โno-touchโ approach, this all to enrich the SharePoint experience. Technically the product operates as a broker service for the SharePoint web services and external web services/APIs.
- User can subscribe to any services and then configure the service to get the data in his/her SharePoint site. Scheduling feature facilitate user to schedule any of the services so that broker engine populate data to the SharePoint site at specified intervalย ย
Technical Objective
- Job Schedulingย ย ย
- Persistent job scheduling : This product heavily uses scheduling for different services. The biggest challenge was to persist these scheduling without using any kind of service.ย ย
- Manage scheduling : User is able to add/modify/delete scheduling scheme for different services. This was achieved by exploring the database used by component. Out of the box method of that component was created to achieve this task.ย ย
- Less coding to add a new third party service in the existing product Reusable templates/Interfaces was created so that a new service (e.g. twitter service, fax service) can be added easily by just using these templates.
- Dynamic user controls : Predefined user controls have been created that can be used for all the services.ย ย ย
- Generalization of request using Web Application Description Language (WADL) : One of the challenges was to generalize the HTTP request needed to use the services. This has been achieved using xml representation of request called WADL. ย
Solution
- Hide the complexity of SharePoint services and build methods that can easily be used by passing simple parameters rather than xml parameters.ย ย
- Module implementation to generalize handling of HTTP request.ย ย
- Dynamic content loading.ย ย
- Use of jQuery to enhance the look and feel of interface.ย ย
- Schedulingย ย
- No code solution: User can customize the look and feel without going to the SharePoint site.ย ย
- Detect authentication method for different SharePoint site.ย ย
- Integration of โMicrosoft online servicesโ.ย ย
Benefits
- New service can be added with less coding effort.ย ย ย
- Output of services can be store in SharePoint lists.ย ย ย
- No need to get into the SharePoint server to configure TunnelPoint services.ย ย ย
- Nice load balancing feature of scheduling which is fast and light weight.ย ย ย
- Development Cost Reductionย ย ย
- No Server side code management headaches.ย ย
Technology Stack
