I detta projekt har SharePoint integrerats i SiteVision. Flera av SiteVision AB:s kunder har efterfrågat en möjlighet att integrera produkten med SharePoint. Microsoft tillhandahåller inga direkta API:er för SharePoints objektmodell i Java som SiteVision är skrivet i. SiteVision AB visste inte hur kunderna ville kunna arbeta med SharePoint i SiteVision och var angelägna om att ta reda på detta. Det övergripande syftet med denna rapport har varit att möjliggöra en attraktiv integration av SharePoint från SiteVision. Detta har utförts genom att undersöka vilka delar av SharePoint som SiteVision AB:s kunder vill kunna komma åt från SiteVision och hur kunderna vill kunna komma åt dessa delar i SiteVision. Undersökningen har genomförts genom kvalitativa intervjuer med några av SiteVision AB:s kunder. Undersökningen har visat att kunderna helst vill ha en integration mot SharePoints dokumenthanteringssystem. De vill ha möjligheten att lista filer från SharePoint i SiteVision utifrån en given mapp eller metadata. De vill även kunna söka efter SharePoint-filer i SiteVision. Ett internt API för kommunikation mot SharePoint i Java har konstruerats. Efter kundernas önskemål har en SiteVision-modul som listar filer utifrån en angiven mapp skapats. Dessutom har en enkel prototyp till sökmodul konstruerats. Resultaten från intervjuerna kan inte anses vara representativa för hela kundkretsen men gav en indikation om vad som skulle utvecklas först. Projektets mål är uppfyllda men modulerna behöver utvecklas vidare innan de kan lanseras. / In this thesis project, SharePoint has been integrated in SiteVision. Several customers of SiteVision AB have requested an integration of SharePoint from SiteVision. Microsoft doesn’t provide any API for Java to SharePoint object model. SiteVision AB did not know in what form the customers wanted to access SharePoint from SiteVision but was keen to find out. The overall aim with this thesis has been to make an appealing integration of SharePoint from SiteVision possible. This has been accomplished by performing a study investigating what parts of SharePoint the customers wanted to access from SiteVision and in what form they wanted to access it. The study has been performed by qualitative interviews with some of the customers of SiteVision AB. The study has shown that the customers most of all wants to integrate the document management system of SharePoint. They want to be able to view SharePoint files inside SiteVision based on a provided folder, or file meta data. They also want to search for SharePoint files in SiteVision. An internal API for communication with SharePoint in Java has been constructed. Based on the customers’ requests, a SiteVision module that lists SharePoint files based on a folder has been created. Furthermore, a simple prototype for a search module has been constructed. The results from the study cannot be considered as representative of all customers but gave an indication of what should be developed first. The overall aim has been fulfilled but the modules need additional developing before they can be released.

De flesta organisationer idag jobbar i någon typ av projektbaserad arbetsform. Ett sätt att effektivisera sina projekt kan vara att använda sig av lämpliga IT-stödsystem. Genom att ge projektet en intern yta för kommunikation- och informationshantering kan både moral och samarbetseffektiviteten att öka. Ett intranät är ett system som fyller just dessa funktioner och som många företag redan har, men inte alltid använder till just projekt. Anledningen till att varför ett intranät inte alltid är används är p.g.a. den höga administrationstiden som krävs för att anpassa verktyget att passa just organisationens projekt. I den här studien undersöks vilket intranätverktyg som är mest lämpat för projekthantering och hur ett förbättrat stöd kan åstadkommas. I studien identifieras de tre populäraste intranätverktygen i Sverige som EPiServer, SiteVision och SharePoint. Dessa undersöks närmre genom semistrukturerade intervjuer med konsulter inom varje verktyg. Med en kvalitativ och kvantitativ analys av intervjuerna så bedöms SharePoint som dess mest lämpade intranät för projekthantering. En fallstudie utförs hos JSC IT-Partner AB – ett IT-konsultföretag i Småland. I fallstudien utvecklas en IT-artefakt under forskningsmetodiken Design Science med ett inslag av den agila systemutvecklingsmetoden Scrum. IT-artefakten är en SharePoint App som ämnar att underlätta skapandet av projektportaler i JSC:s intranät. Artefakten evalueras genom ett försök att replikera den projektportal som redan används av JSC, men som inte är automatiserad. Resultatet av evalueringen ligger till grund för studiens resultat som visar att ett förbättrat stöd för projekthantering kan uppnås inom intranät med hjälp av programmering. I slutet av studien diskuteras de begränsningar som kan upplevas när ett intranät används för projekthantering och de problem som uppkommit under utvecklingsprocessen av artefakten. I studien diskuteras inte konsekvenserna av att införa en organisations projektverksamhet i ett intranät. JSC använde sedan tidigare sitt intranät för projekthanteringen och därmed undersöks inte övergången från externa system till ett intranät. / Many organisations today work with some kind of project oriented working method. One way to make it more efficient could be to use suitable IT support systems. By giving a project an internal area for communication and information management could increase members both morale and social collaboration. An intranet is a system that fulfil these conditions and is already highly used by organisations, but not so much for project management. This is partially because of the high amount of administration time required for successfully adapting the system for the specific organisations projects. This study examines different intranet systems to find the most suitable for project management and how it can be improved. In this study the three most popular intranet systems in Sweden is identified as EPiServer, SiteVision and SharePoint. These systems are investigated further by semi-structured interviews with consultants from each of the systems. With a qualitative and quantitative analysis SharePoint is recognized as the most suitable system for project management. A case study is performed at JSC IT-Partner AB – and IT Consultant Company in Småland. During the case study an IT artefact is developed by the combination of the research method Design Science and the agile system development method Scrum. The artefact is a SharePoint App that intend to facilitate the creation of project portals in JSCs intranet. The artefact is evaluated by trying to replicate the existing project portal that is already used by JSC, but that is not automated. The result from the evaluation is used when analysing and discussing the result from this research that proves that project management can be improved in intranets by the help of programming. In the end of this report there is a discussion about different limits that may occur when using an intranet for project management and what problems that were encountered during the development process of the artefact. There is no discussion about what impact using an intranet for project management may have for the organisation. JSC was already using their intranet for project management at the time and the purpose of the case study was not to analyse the consequences when moving from an external system to the organisation’s internal intranet.

The aim of this project has been to explore alternative technical solutions for making own extensions in the CMS SiteVision. The purpose of these extensions is to retrieve data from an external API (Office 365) which requires OAuth 2.0 authentication. Additional, the alternative technical solutions have been evaluated and compared. The comparisons have been made based on criteria developed through interviews with professional IT-consultants. The purpose of the project has been to contribute to more efficient digitization, integration and individualization of datasystems. Within the project, an applied example (POC) has been created to show examples of how the technology can be used. In this example, Java Portlets have been used to implement the above functionality. WebApps in SiteVision have also been studied since this technology is an alternative to Java Portlets. The survey shows that it is fully possible to create a separate extension in SiteVision that performs authentication with OAuth 2.0 and then uses it to retrieve data from an external API. The results from the comparison between the two different Java Portlets and WebApps technologies show that there are pros and cons of each technique. The alternatives studied where comparable in performance. Individual circumstances can dictate which alternative is best. / Det övergripande syftet med detta projekt har varit att bidra till en effektiviserad digitalisering och individualisering. Målet för projektet har varit att undersöka alternativa tekniska lösningar för att göra egna tillägg i CMS:et SiteVision. Tillägg vars uppgift består i att hämta data från ett externt API (Office 365) som kräver autentisering med OAuth 2.0. Vidare har de alternativa tekniska lösningarna värderats och jämförts. Jämförelsen har gjorts utifrån kriterier som tagits fram genom intervjuer med utvecklare på ett IT-konsultbolag. Inom projektet har ett tillämpat exempel (POC) skapats för att visa exempel på hur tekniken kan användas. I detta exempel har Java Portlets använts för att implementera ovanstående funktionalitet. Även WebApps i SiteVision har studerats då den tekniken utgör ett alternativ till Java Portlets. Undersökningen visar att det är fullt möjligt att skapa ett eget tillägg i SiteVision som genomför autentisering med OAuth 2.0 och sedan använda denna för att hämta data från ett externt API. Resultaten från jämförelsen mellan de två olika teknikerna Java Portlets och WebApps visar att det finns för- och nackdelar med respektive teknik. Båda alternativen framstår som jämstarka i jämförelsen. De individuella omständigheterna kring ett framtida användande bör fälla avgörandet för vilken teknik som väljs.

This report has conducted a research of comparing a few open source search engines. The research contains two evaluation processes, the first evaluation will evaluate each open source search engine found on today’s market. Points will be given between one to five points depending on how well the open source search engine meets the requirements. The open source search engine with the highest score will then be chosen for implementation. The first evaluation resulted in Elasticsearch being the selected open source search engine and will continue to the implementation phase. The second evaluation will be measuring the system performance and the relevance of the SERP (Search Engine Results Pages). This phase will evaluate the system performance by taking time measurements on how long it takes for the search engines to deliver the SERP. The relevance of the search results will be judge by a group of CSN employers. The group will be giving point be-tween one to five points depending on the relevance of the SERP. It will eval-uate Elasticsearch with the search engine CSN are using today on their web-site (www.csn.se). This phase resulted in Elasticsearch being the better in performance measurements but not in the relevance of the SERP. This was discussed and came to the conclusion that most points were lost because of the first search result Elasticsearch delivered. If this search result was re-moved Elasticsearch could deliver as good results as the old search engine. The survey came to the conclusion that Elasticsearch is recommended for CSN if certain problem areas could be corrected before implementation into their systems.

This report describes the process and steps in detail that needed to be taken in order to meet the end users’ needs. The purpose of this study is to develop a dynamic module based on user-centered design (UCD) for Pulsen’s (pulsen.se) new website using the con-tent management system (CMS) SiteVision. UCD integrated with agile development methodologies is an effective combination to increase the focus of a development project on the end users’ needs. In this study we show the pervasiveness of the two methods combined in a development project. The module’s functionality is to allow the end user to quickly - and without effort - sort and filter news articles, events and job postings into lists that will be embedded and reusable on their new website. Manual adaptation of custom modules was configured directly through JavaScript code which made them error prone, causing the modules not to function properly. To combat this problem, we used contextual inquiry (CI) along with usability testing as data gathering methods with both Pulsen’s editors and external participants. The usability tests were used to plan and evaluate the functionality of the prototype in order to make it as user-friendly as possible. The study resulted in an interface with user defined variables derived from a JavaScript module.

The ability to reach a wider public using the Internet has brought the world a wide varietyof online retailers offering their customers to purchase almost anything from the comfortof their home. With this increase in online retailing, a need for automation has been developedby the users. To be able to decrease the administrative tasks to a bare minimum allowsretailers to focus on their core business instead. With this new request for automation, businesssystems are becoming more and more popular and to be able to integrate the web sitewith a business system results in lower administrative workload. A variety of systems arealready available for the public to use for integrating a web shop to a number of differentbusiness systems. These systems are however often restrictive and will provide a frameworkfor developing the web shop themselves. One web content management system that lacksthis kind of support is SiteVision. On behalf of Soleil IT, a Proof of Concept was developedto investigate the feasibility of integrating a web shop developed in SiteVision, with a businesssystem for automation of administrative tasks. The implementation included featuressuch as retrieving products from the business system and displaying them on the web site,and the ability to purchase a set of products which should generate an order in the businesssystem. RESTful web services was used to transmit data between the business system andthe web shop. This project resulted in a successful integration of the business system VismaAdministration and a web shop developed in SiteVision. The project showed the feasibilityof performing such an integration and also exposed any restrictions that the setup may have.