Page Tree


Previous Releases

FactoryStudio 8.1

Skip to end of metadata
Go to start of metadata

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. Use the following instructions to configure IIS.
  • 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”.

  • Verify if IIS is installed and running. For instance, by trying to open HTML
  • Enable .NET and .Svc Handlers for the WCF Service

For IIS 7.x:

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

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

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

Usually, the .NET Framework installation directory is: 

C:\Windows\Microsoft.NET\Framework\v4.0.30319, or

C:\Windows\Microsoft.NET\Framework64\v4.0.30319 (for x64 Windows)


For IIS 8.0:

Go to Program and Features. Choose, “Turn Windows features on or off“.

Enable the ASP.NET 4.5 option (Internet Information Services > World Wide Web Services > Application Development Features > ASP.NET 4.5:


Enable the HTTP Activation option (under .Net Framework 4.5 Advanced Services)


For .NET Framework versions newer than 4.5, the ASP.NET will be different (the same as the Framework version). But the configuration remains the same.


Verify that 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.)


From within the Factory Studio installation folder, run the utility:

InstallTWebServer.exe /uninstall

This will remove the default TWebServer installation.

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

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


A default IIS image should open on your browser.


After making sure the IIS is working, open ”Sites/Default Web Site/Add Application” and configure the information for the services:


TProjectServer:

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

You should allow “Everyone” access to at least read.

You must allow the “<ComputerName> IIS IUSRS “ user to read and write on the directories of the projects.

Example: For C:\FactoryStudio\Projects\<ComputerName>\IIS_IUSRS, the user must be included in the security permissions for reading and writing (full control) on the “C: FactoryStudio ” directory, and you must ensure that all subdirectories (Projects, Settings, etc.) inherit these permissions.


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 0. Example: ASP.NET v4.0.

You should allow “Everyone” access to at least read.

On IE, test the “http://localhost/fs-2014.1/service.svcurl 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:


iDataPanel Service

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

You should allow “Everyone” access to at least read.


iDataPanelImages (Virtual Directory)

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

You should allow “Everyone” access to at least read.


Anonymous Authentication” must be enabled for the services.


Go to the Compression module.

There’s check boxes. If it is not installed, you may see this yellow alert on the right side.

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 installed, click Add Roles and install it.

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

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


From the dropdown, select system.webServer/httpCompression.

Then, click on Dynamic Types. Now that you’re in the list editor, add application/json.

IIS must be restarted after configuring the services.


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

For the server certificate, you have two options.

The first is to acquire a paid certificate that will ensure your web security. The second one is to generate 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:

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

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.

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.

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


Verify the SSL Binding

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

Internet Explorer 7 and above will display an error page because the self-signed certificate was issued by your computer, not by a trusted Certificate Authority (CA). Internet Explorer 7 and above will trust the certificate if you add it to the list of Trusted Root Certification Authorities in the certificates store on the local computer or in Group Policy for the domain.


Click Continue to this website (not recommended).


*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.


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.


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.
Example
<!-- 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.





Common Errors

 Internet Explorer Security Settings


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 for this issue, 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.


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.

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.

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)
  • No labels