Page History

Overview

If IIS is located when you install FactoryStudio

, you will not be able to install our embedded web server

, TWebServer.exe

.

The FactoryStudio software will run without the web server

. Most FactoryStudio engineering and runtime tools run without needing to install

our TWebServer or

doing any IIS configuration. TWebServer.exe is needed for remotely accessing project configurations and serving runtime web pages. 

If you want to enable remote engineering access and

web clients using IIS, you need to install some FactoryStudio services in IIS

. This page explains how to install FactoryStudio services in IIS; the explanation is for IIS 7.x, but other versions should be similar.

IIS is also necessary when you want to run the

Runtime as a Windows Service

and

still be able to provide

web pages, iPad

clients, and

remote engineering.

You are going to install three services inside IIS:

• TProjectServer

• which allows you to remotely access your project configurations.

• TWebClient/TSmartClient which allows remote access to runtime displays.

• The instructions to configure ISS can be found below.
• iDataPanel is the service which provides

• data to iOS devices.

Installation Procedure

This procedure was executed on Windows 7, x64, with IIS 7.5. With older operating systems and versions of IIS, the procedure may be slightly different, such as defining a “Virtual Directory” instead of “Add Application”.

• Check if IIS is installed and running. For instance, by trying to open HTML
• Enable .NET and

Configuration Procedure

• .Svc Handlers for the WCF Service

For IIS 7.x:

If IIS was installed after the installation of the .NET Framework it is necessary to , you must run and verify a the procedure as described on http://msdn.microsoft.com/en-us/library/ms752252.aspx which is to described on IIS Hosted Service Fails, which is to run the following programs using the command prompt as Administrator:

• • From the Microsoft .Net folder, open the Command Prompt and rung the following commands:

          aspnet_regiis.exe -I -enable

          ServiceModelReg.exe -r

”aspnet regiis –i –enable” (from the .NET Framework installation directory*)

Image Added

”ServiceModelReg.exe” -r (from the .NET Framework installation directory*)

Image Added

For IIS 8.0:

Go to Program and Features. Choose,

“Turn Windows features on or

off“.

Image Added

Enable the ASP.NET 4.

5 option (Internet Information Services > World Wide Web Services > Application

Development Features > ASP.NET 4.

5:

Image Removed

Image Added

Enable the HTTP Activation option (

under .Net Framework 4.

5 Advanced Services)

Image Added

Image Removed

      3.   From the IIS Manager, verify that the extension .svc is mapped to aspnet_isapi.dll.

• • If needed, follow the procedure described on http://msdn.microsoft.com/en-us/library/ms752252.aspx for the version of IIS you are using. 
    • The .NET Framework installation directory usually is: C:\Windows\Microsoft.NET\Framework\v4.0.30319, or C:\Windows\Microsoft.NET\Framework64\v4.0.30319 (for x64 Windows)

Image Removed

Check if the extension ”.svc” is mapped to ”aspnet isapi.dll” (The msdn.microsoft website, on the previous link, explains how to verify this for many IIS versions.)

Image Added

From within the Factory Studio       4.   From the FactoryStudio installation folder, run the utility:

InstallTWebServer.exe /uninstall

This , which will remove the default TWebServer installation. 

Image Removed

.

Image Added

Before configuring any application for IIS, it is recommended to check if IIS is working. To do so, open ”Sites/Default Web Site/Edit Permission”, and check if it is linked to the wwwroot folder.

Image Added

If so, go to the Actions pane and under Browse Web Site, click the link associated with *:80(http).

Image Added

A default IIS image should open on your browser.

Image Added

After making sure the IIS is working, open Sites, right click Default Web Site and select ''Add Application...",       5.   From IIS Manager, go to Sites > Default Web Site > Add Application  and configure the information for the services as described in following steps

Image Removed

      6.   For TProjectServer, configure: 

:

Image Added

TProjectServer:

• Alias: TProjectServer
• Physical Path: C
• Alias—TProjectServer 
Physical Path—C
• :\Program Files\Tatsoft\
FactoryStudio (Default folder. Make sure you use the correct path to the FactoryStudio installation folder.) 
• FactoryStudio  -> (If you've installed FactoryStudio in a non-default folder, use that location.)
• Application Pool: Configure any pool based to .NET
Application Pool—Configure any pool based on .NET 4.
• 0. Example: ASP.NET v4.0.
0 

Image Added

Image Removed

On

IE, use the

”http://localhost/tprojectserver/service.svc” url to verify if the service was correctly installed.

This should show a page with information about the service.

TWebClient/TSmartClient:

• Alias: fs-2014.1.
• Physical Path: C: Program Files Tatsoft FactoryStudio-2014.1 // → FactoryStudio installation folder.
• Application Pool: Configure any pool based to .NET

      7.   For TVisualizerWeb/TVisualizerRemote, configure: 

• Alias - fs-8.1 
• Physical Path—C:\Program Files\Tatsoft\FactoryStudio\fs-8.1 (Default folder. Make sure you use the correct path to the FactoryStudio installation folder.) 
Application Pool—Configure any pool based on .NET 4.
• 0. Example: ASP.NET v4.0.

Image Removed

Image Added

On IE, test the

“http://localhost/fs-

2014.1/service.svc” url to verify the service was correctly installed.

This should show a page with information about the service.

Go to MIME Types, and create the following MIME Type:

Image Added

iDataPanel Service

• Alias: iDataPanel.
• Physical Path: C: Program Files Tatsoft FactoryStudio fs-2014.1 // -> FactoryStudio folder.
• Application Pool: Configure any pool based to .NET

      8.   For iDataPanel Service, configure: 

• Alias—iDataPanel
• Physical Path—C:\Program Files\Tatsoft\FactoryStudio\fs-8.1 (Default folder. Make sure you use the correct path to the FactoryStudio installation folder.) 
Application Pool—Configure any pool based on .NET 4.
• 0. Example: ASP.NET v4.0
• Note: Security should enable any user (Everyone), at least for reading.

Image Removed

• .

Image Added

iDataPanelImages       9.   For DataPanelImages (Virtual Directory), configure:

Image Removed

Image Added

• Alias
—iDataPanelImages 
• : iDataPanelImages
• Physical Path
—
• : C:\FactoryStudio\Projects\
iDataPanelImages 
• iDataPanelImages

Image Added

“Anonymous Authentication” must be enabled for       10.   Enable Anonymous Authentication for each of the services. 

Image Removed

Image Added

Go to      11.   Setup the Compression module.

Image Added

If it is not installed, you will may see the alert boxes.

Image RemovedImage Removed

Image Removed

      12.   Create a new MIME Type for the .tzip extension

Image Removed

this yellow alert on the right side.

Image Added

If it is       If it's not installed, go to the Server Manager, Roles, Web Server. Under Role Services, check your installed Roles. If Dynamic Compression isn't is not installed, click Add Roles and install it.
 

Image Added

 
      You can go back to compression the Compression module for your site and ensure Dynamic Compression is checked. At this point, Dynamic Compression should be setupset up, but you really need to must be specific about what mimeTypes MimeTypes will be compressed.

Image Removed

Back to IIS Manager, go to the page for the SERVER, not the SITE. Click on, "Configuration Editor".

From the dropdown, select system.webServer

/httpCompression

.

Image Removed

Image AddedImage Added

      Then, click on Dynamic Types and now that you're in the list editor. Add application/json as seen below.

Image Removed

      After you've added them and closed the dialog.

.In the list editor, add "application/json."

Image Added

After you have completed all of the above steps, the IIS configuration for HTTP access is completed.

If you want to configure a HTTPS connection as well, follow the next steps.

How to Set Up SSL on IIS 

The steps for configuring Secure Sockets Layer (SSL) for a site are the same in IIS 7, IIS 6.0, and the above.  The steps include the following:

Get an appropriate certificate. Create an HTTPS binding on a site. Test by making a request to the site. Optionally configure SSL options by making SSL a requirement.

Obtain a Certificate

There are two options for the server certificate:

• Acquiring a paid certificate that will ensure your web security;
• Generating a self-signed certificate that will only be used for testing purposes.

We do not recommend using a self-signed certificate in final project deployment.

If you choose to use the self-signed certificate, follow the next steps.

Select the server node in the tree view, and double-click the Server Certificates feature in the list view:

Image Added

Click Create Self-Signed Certificate... in the Actions pane.

Image Added

Enter a friendly name for the new certificate, and click OK.

Now, you have a self-signed certificate. The certificate is marked for ”Server Authentication” use, which means it uses a server-side certificate for HTTP SSL encryption and for authenticating the identity of the server.

Create an SSL Binding

Select a site in the tree view and click Bindings... in the Actions pane. This brings up the Bindings Editor that lets you create, edit, and delete bindings for your Web site. Click Add... to add your new SSL binding to the site.

Image Added

The default settings for a new binding are set to HTTP on Port 80. Select https in the Type dropdown list. Select the self-signed certificate you created in the previous section from the SSL Certificate drop-down list, and click OK.

Image Added

Now, you have a new SSL binding on your site and all that remains is to check if it works.

Image Added

Verify the SSL Binding

In the Actions pane, under Browse Web Site, click the link associated with the binding you just created.

Image Added

Click Continue to this website (not recommended).

Image Added

*IMPORTANT: The self-signed certificate should only be used for local development. Microsoft Internet Explorer does not trust self-signed certificates by default for security reasons.

However, for testing propose, you need to follow the steps below:

1. Browse to your page (e.g. https://localhost:443) in Internet Explorer, which should use your self-signed SSL certificate. You should be greeted by an error message saying your certificate is not trustworthy.
2. Click “Continue to this website”.
3. Click on “Certificate error” in the address bar, and click “View certificates”.
4. Click “Install Certificate”.
5. Click “Place all certificates in the following store”, and click “Browse”. Do not rely on the preselected option to automatically select the certificate store as this will not work!
6. Inside the dialog box, click “Trusted Root Certification Authorities”, and click “OK”.
7. Finish the dialog.
8. When you get a security warning, click “Yes” to trust the certificate.
9. Reload your page, and the certificate should be working fine now. If the error persist, replace ”localhost” in the url with the UserName the certificate was Issued To. E.g.: https://WMSvc-ALEXISE3LH:443.

Image Added

Configure SSL Settings

Configure SSL settings if you want your site to require SSL or to interact in a specific way with client certificates. Click the site node in the tree view to go back to the site’s home page. Double-click the SSL Settings feature in the middle pane.

Image Added

Enable Web Client to use SSL Settings

 SmartClients Only

• Open the “Web.config” file in Windows. The files are located in:
  

  C:\ProgramFiles (x86)\Tatsoft\FactoryStudio
  C:\ProgramFiles (x86)\Tatsoft\FactoryStudio\fs-2014.1\

• You will find some comments regarding what command lines are used for HTTP.  So, you will need to comment out the HTTP lines and uncomment the HTTPS ones.

<!-- If using HTTP then Security Mode is None by default -->
<security mode="None" />
<!-- If using HTTP then Security Mode can use Windows Authentication -->
<!--
<security mode="Transport">
<transport clientCredentialType="Windows"/>
</security>
-->
<!-- If using HTTPS then Security Mode is Transport -->
<!--
<security mode="Transport">
<transport clientCredentialType="None"/>
</security>
-->

Replace with:

<!-- If using HTTP then Security Mode is None by default
<security mode="None" />
-->
<!-- If using HTTP then Security Mode can use Windows Authentication -->
<!--
<security mode="Transport">
<transport clientCredentialType="Windows"/>
</security>
-->
<!-- If using HTTPS then Security Mode is Transport -->

<security mode="Transport">
<transport clientCredentialType="None"/>
</security>

Repeat this procedure throughout the xml file.

WebClients (HTML5) Only

If using https to access a WebClient (HTML5), you must inform the application of the correct port number for this connection.

To do so, create a shortcut of the TStartup.exe application, or launch the command prompt from the installation folder (fs-xx.x). Add the project and html5port parameters as indicated in the image.

Image Added

Common Errors

 Internet Explorer Security Settings

Image Added

If you get an error message like the image above, it might be related to your Browser security settings. Microsoft's automatic updates of Internet Explorer may change some defaults on .NET support, which may cause your browser to have disabled XAML browser based applications.

In order to check if it works, open the ”Internet Options” of Internet Explorer, and navigate as shown in the image below.

Make sure that on the .NET Framework section, the XAML browser based applications is set to Enable.

Image Added

Missing File

If the error message you get is something like the following image, the problem might be related to some files being missing from the installation folder. To check for this, go to your products installation folder and search for that file.

If you do not find it, you should uninstall the product, and install it again.

Image Added

Binaries Modified

If the error message you get is something like the image, the problem might be related to some files being missing from the installation folder. To check for this, go to your products installation folder and search for that file.

If you do not find it, you should uninstall the product, and install it again.

Image Added

Firewall blocking

It is quite common for a firewall to prevent remote access to the application. So, before accessing remotely, try to open a local copy of the browser locally on the server.

Run the server and the client on the same computer before trying to remotely access the application.

http://localhost/fs-2014.2/TWebClient.Xbap or http://127.0.0.1/fs-2014.2/TWebClient.Xbap

Or, run the server and the client with another Port number. For example, 1234.

http://localhost/fs-2014.2:1234/TWebClient.Xbap or http://127.0.0.1:1234/fs-2014.2/TWebClient

Insufficient User Permissions

If you are unable to launch the client and the error message is different from the ones above, the user currently logged into the system might not have the necessary permissions to access the files through an HTTP or HTTPS connection.

To overcome this, launch the Command Prompt as an Administrator and execute the following commands:

For port used in HTTP (in this example 80)

netsh http add urlacl url=http://+:80/thtml5/+ sddl=D:(A;;GX;;;IU) For port used in HTTPS (in this example 4430)
netsh http add urlacl url=https://+:4430/thtml5/+ sddl=D:(A;;GX;;;IU)