Jump to: navigation, search

Difference between revisions of "HowTo:Install UBIK Web Service"


(Certificate)
(Certificate)
Line 60: Line 60:
 
File:UI Certificate.02.png|[[2 - Installed certificates]]
 
File:UI Certificate.02.png|[[2 - Installed certificates]]
 
File:UI Certificate.03.png|[[3 - Create self-signed certificate]]
 
File:UI Certificate.03.png|[[3 - Create self-signed certificate]]
File:UI Certificate.04.png|[[4 - Installed certificates]]
+
File:UI Certificate.05.png|[[4 - Import certificate]]
File:UI Certificate.05.png|[[5 - Import certificate]]
+
File:UI Certificate.04.png|[[5 - Installed certificates]]
 
</gallery>
 
</gallery>
  

Revision as of 13:23, 2 June 2014

This page describes how to set up a UBIK® web service on a Microsoft Internet Information Server (IIS) installed on Microsoft Server 2012. The web service is used to publish data from the UBIK® database to a mobile device (eg mobile phone, tablet).

Installation of Microsoft IIS

Install server role

Start the server manager to install the Internet Information Services (IIS) on Windows Server 2012 by

  1. Clicking the Windows Start button, point to Administrative Tools and choose Server Manager
  2. Clicking on Roles Summary
  3. Clicking on Add Roles
  4. Use the Add Roles wizard to add the web server role

Required roles and features

The Add Roles wizard installs only the default set of role services, which do not contain all the necessary features required for UBIK® web services. Therefore, additional IIS role services and features, such as Application Development or Health and Diagnostics, needs to be selected in the Select Role Services page of the wizard.

UBIK® web service requires at least the following roles

  • Microsoft .NET Framework 4
  • Microsoft .NET Framework 3.5
  • Webserver Application Development

and features

  • HTTP Actication (WCF Services)

Using a virtual server

A physical server with Microsoft Server 2012 can be used as the host system as well as a virtual server. Use Hyper-V to install and operate serveral virtual servers and proceed with the web server installation similar as for a physical server.

Configuration of the Web Server

The web server can be configured using the Internet Information Services (IIS) Manager console, which gets installed automatically. The console provides a graphical user interface to manage and configure the web server accordingly to the UBIK® web service.

See UBIK® Web Service Configuration for further details on configuration.

Add Application Pool

An application pool is a group of one or more URLs that are served by a worker process or a set of worker processes. Application pools set boundaries for the applications they contain, which means that any applications that are running outside a given application pool cannot affect the applications in the application pool.

Certificate

The web service communicates with the UBIK® client via an secured connection, which requires a SSL certificate on the server and client side. Use a public key certificate from a certificate authority or a self-signed certificate, both will work for UBIK®. A new self-signed certificate can be created in the Internet Information Server (IIS) Manager, exported using the export function and sent to the development team. As already mentioned, the client has to know this certificate as well, hence it need to be integrated it into the mobile application.

IC Attention.pngUBIK® requires a valid certificate for SSL encryption!

Bindings

Web sites and services have something called Server Bindings which represent the underlying address, port, and potentially a host header that the website is accessed using. The UBIK® client accesses the web service via a secured port (https), where it is necessary to configure the appropriate certificate.

Create new Web Application

In the IIS Manager expand the Default Web Site node and navigate through the folder structure to the folder containing the UBIK® web service components.

See Install UBIK® Web Service how to install the components.

Optional: Local IIS User

Create and use a local user on the web server if no appropriate domain-user is available.

Testing the new service

01 Test New Service

See also