Showing posts with label sharepoint development companies. Show all posts
Showing posts with label sharepoint development companies. Show all posts

Monday, 28 October 2013

Why Executives Are Resisting SharePoint's Social Tools?

The social tools of SharePoint have lately faced a lot of criticism from executives. It is a fact that these social tools are considered as a major distraction and well as productivity hindrance. Moreover, many executives might also believe that these tools can usher in the threats of loss of intellectual property, cyber-attacks as well as corporate embarrassment. From their point of view, these tools are probable disasters which should better be completely done away with.

sharepoint webparts development, certified sharepoint developers, sharepoint application development
Many of these concerns might be legitimate, but that should not be the reason to shun SP social tools totally. Globally acclaimed SharePoint expert Richard Harbridge, has worked with a number of companies helping them to cope up with this problem. According to him, once the executives' concerns are understood and acknowledged, ways to reduce the risks can be demonstrated.

Major concerns of executives and means to alleviate them

1. Fear of negative comments: One of the things that executives worry about most is the situation wherein a dissatisfied employee might say something negative on the blog. Such corporate embarrassment can be avoided by adopting certain simple measures such as the addition of an approval feature within the blogs. Here the main issue is that executive or other supporting staff might not properly understand how these features can be used effectively. In that case, some amount of education will help.

2. Fear of wrong information usage: With SharePoint's social tools, executives often dread the fact that information might fall in the wrong hands. In the executives' opinion, loss of trade secrets and intellectual property is a huge risk. This can be addressed by amending or appending the existing policies pertaining to intellectual property, that are present in employee agreements or employee manuals. Any social technology including the intranet should not be exempt from respectful and ethical employee behavior as well as acceptable technology use practices.

3. Fear of wastage of time: According to many executives, once SharePoint social tools are introduced, a large number of people would be wasting time on what can be called as a 'Corporate Facebook'. But it should be noted that the tools have some substantial business value which most executives do not know. For instance, each time a user shares, rates or tags a piece of content, the same is noted by SharePoint and its search relevancy is increased. This enables people to easily locate what they are looking for, thereby mitigating the risk of obsolete or incorrect content being used.

In case executives are still concerned about productivity loss, setting the employees' expectation that, like their web browser or email, this is also a work technology, can do the desired job. In order to make the use of these SP tools by employees more effective, guidance, training or illustrations may be given on the means to utilize the technology within a work setting. Often, making use of stories to elaborate this can help immensely, particularly if the stories revolve around corporate culture or things like any practical use of the tool specific to the business.

4. Fear of viruses and cyber-attacks: Many are of the opinion that using SP social tools will make the systems vulnerable to cyber-attacks and viruses. These can be conveniently reduced by implementation of an enterprise ready social technology. A plethora of them have constraints imposed for preventing people from adding scripts as an instance to discussion boards, tags, status updates or embedded in any other social content.

5. Fear of employee harassment: Many feel that enhanced collaboration paves the way to increased employee harassment. It is significant to consider the matter of employee harassment, hence ensure that you append or amend the existing policies related to sexual harassment within employee agreements or manuals. Moreover, so far as ethical employee behavior or acceptable technology use is concerned, all social technologies including the intranet should not be exempt from the same.

The concern of your executives is valid, and cannot be denied. However, once these concerns are addressed through implementation of effective and simple safeguards, these types of situations can be done away with. And once accepted with open arms, SharePoint application development would help you leverage the power of social media.

We provide SharePoint webparts development services. If you would like to talk to one of our certified SharePoint developers, please get in touch with us at Mindfire Solutions.

Friday, 13 September 2013

Interoperability between Java and SharePoint 2013

Every time a software company brings out a new technology or product in the market, the focus is directed towards the endeavor of catering to the demands of users/customers concerning a specific functionality. Owing to such a need, companies often take route to creating an all – inclusive administrative solutions with the aim of selling a complete package. However, it must be noted that all documents and data created within the system often holds onto an importance, which reaches beyond commercial lifetime of a particular application of creation.


Java and Sharepoint Integration, custom sharepoint development, sharepoint developers
The importance of documents and data often surpasses the actual scope of parent or main application. For instance, documents that have been created in a proprietary system of document management might require an access from a corporate intranet or data present within system of custom relationship management might serve as an input to process of business documents creation.

Now, introduction of SharePoint 2013 has brought into fore the prospect of an effortless integration between a particular application and other external systems that has been implemented within technologies that are not of Microsoft. Well, in such a scenario, the RESTfull web service of SharePoint API increases communication with web application of Java. The chrome control of SharePoint enables the web application of Java to feature a similar kind of styling to that of hosted website.

The Layer of Communication with SharePoint

The web application of Java communicates to a car list in the hosted web, which is referred to as the Interopl and the data list is named as the Cars. The list features columns referring to the model, bran, and price. This particular application is named the Cars App and here is a quick look at the dependencies of the same within Java implementation.

  • json-lib 2.4 – helper classes influencing Json objects
  • resteasy-jaxrs 2.2.1.GA – RESTEasy enabled an easy access of the RESTfull SharePoint API
  • commons-httpclient 3.1- dependent on RESTEasy
  • httpclient 4.1.1 - dependent on RESTEasy
  • spring-web 2.5.6
  • spring-core 2.5.6
  • spring-webmvc 2.5.6
  • commons-logging 1.1.1

The Car service has been defined in order to write and read into Cars list featuring declaration file CarService.java. The implementation of Cars service features a member variable, which define parameters of authentication along with web service URIs endpoints pertaining to SharePoint and Cars list field names.


The particular service also incorporates a number of helper methods. The callRestEasyService helper methods read the data by conducting a HTTP Get as against the RESTfull API of SharePoint. The URI that is given in the req parameter defines just what is being recovered and retrieved. It strictly follows the protocol syntax of OData. In this particular scenario, it would refer to the items of the Car list.

To go for object creation in SharePoint through the RESTfull API, which refers to the Cars list items, it is required to provide a Form Digest, which can easily accessible via a POST To the hosted web endpoint “/_api/contextinfo”. The addRestEasyRetrieveDigest helper conducts the posts and goes through Form Digest. The actual definition of URI is given in the urlDigest of the variable.

The addRestEasyPost helper enables object creation in SharePoint through POSTs as mentioned in the protocol of OData. This particular method helps adding cars to the particular list. The parameter req features the URI of object creation, which refers to the Cars list here. Another detail that is often regarded while creating objects is the need of stating the type. In the particular list, the items refer to the SP.Data.CarsListItem type, which follows the convention SP.Data.<ListName>ListItem.

The parseJsonDigestValue helper method integrates the JSON response from the “/_api/contextinfo” endpoint recovering the form digest.

The parseJson helper translates the response of the JSON to the payload class of Cars retrieving the list.The Cars service explains the method getCars to read the items; whereas, the technique insertCar is used to write the items.

Custom SharePoint development teams can help you build projects within allocated budgets and time schedules.

We provide Java and SharePoint Integration services. If you would like to talk to one of our expert SharePoint developers, please get in touch with us at Mindfire Solutions.

Wednesday, 11 September 2013

SharePoint nuke complete integration - 10 Things you should not miss

DotNetNuke Corporation, a premier provider of adaptive web software which keeps the online presence of a business effective and relevant, came up with the availability of an improved SharePoint integration in the year 2012. This new SharePoint Connector is capable of rendering support to SharePoint 2007 as well as the 2010 version. It offers seamless integration between outstanding document management and web content management solution of DotNetNuke. Here we bring to you certain best practices which you must consider for proper integration.

1. Document Management: SharePoint is the finest document management system that is applicable for all businesses irrespective of the size. Utilizing this system, which is built within the cloud in order to make room for maximum accessibility and storage, group members are able to collaborate and share an apparently unlimited quantity of data and documents. It effectively integrates with Outlook and makes use of social tools for amplifying the organized, collaborative, atmosphere. It also facilitates transformation of raw data into interactive, beautiful reports by team members.

custom sharepoint development, sharepoint application development, sharepoint developers, DotNetNuke SharePoint integration
2. Integration with SharePoint: Automatic integration of DotNetNuke is possible, which implies that if the system is operated, no additional work is needed. But, when it comes to DNN Community, it can also integrate quite comfortably through custom modules. The goal is to develop a system which enables SharePoint to go for effective communication from behind firewalls with the public-facing website. This indicates that you will be capable of pushing documents towards a portal efficiently as well as safely on your DNN website. Filter rules can also be designed in order to find out where individual documents are going.

3. The DNN Enterprise: For those utilizing SharePoint as the document management system, and wishing to integrate the same into their website, the Nuke Enterprise edition is a good choice. With the help of this edition, custom integration is possible at a highly affordable cost. Through the connector, firewall issues can be bypassed and the content can be kept fresh, while publishing directly from the Document Library. Every document that is published is offered protection by the DNN role-oriented security network.

4. Avoidance of Firewall: Many companies make use of SharePoint as the document library and DNN as the public-facing website. In most cases this implies that the SharePoint server resides within the trusted zone while the DNN is made available to the public. All communications that take place between the two servers begin from the SharePoint server. This feature can be used without making any kind of modifications to the security policy.

5. Leveraging filtering views: The built-in views provided by document management system for filtering facilitate the use of the Create View UI. The views that have already been created can be used without the requirement for maintenance of two distinct filter sets. More time can be spent for development of core features as the time spent on development of filtering and associated UI features is reduced to a great extent.

6. Extended web application: When there is already a SharePoint web application making use of Active Directory for authentication, the same can be extended to support users from DotNetNuke. For this a DNS or hosts file entry needs to be created for the upcoming SharePoint site.

7. Modification of web.config files: A number of changes need to be considered within the web.config file in the SharePoint application. Before making any kind of modifications, it is advisable to create a backup.

8. Taking care of file size: With respect to the file size, DotNetNuke possesses an option beneath the host settings which limits the file size on the website. The files are compared against that number by the Connector. Files bigger than the stipulated limits of the website are not published.

9. Deletion from the document management system: In case “propagate deletions” is selected, the file that is deleted from the document management system also gets deleted from DNN. However, if the deleted file possesses references from a module, it will reveal broken links.

10. Handling permissions: Remember that permissions from a SharePoint to a DNN site are managed by DNN’s security model. It is not possible to manage permissions across SharePoint and DNN. This in because, in a number of cases, users and roles are different when it comes to the intranet and the public website.

Seamless integration, when effectively accomplished, empowers organizations to securely and effectively publish documents directly from SharePoint into their respective exterior-facing websites. Custom SharePoint development teams can help you build projects within allocated budgets and time schedules.

We provide SharePoint application development services. If you would like to talk to one of our expert SharePoint developers, please get in touch with us at Mindfire Solutions.