Page Tree


Previous Releases

FactoryStudio 8.1

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

If IIS was previously installed on your system, you will not be able to install our embedded web server (TWebServer.exe) when you install FactoryStudio. 
The FactoryStudio software will run without the web server, except by remotely accessing project configurations and serving runtime web pages; all other FactoryStudio engineering and runtime tools run without needing to install the TWebServer or to do any IIS configurationwebserver, however, you will not be able to remotely access project configurations or serve runtime web pages.  All other functionality works.

If you want to use IIs to enable remote engineering access and the web clients, you need to install some FactoryStudio services in IIS or enabled the TWebServer. IIS is also necessary when you want to run the runtime as a Windows Service, and to provide remote access to project web pages, iPad displays, and project engineering.

To enable the TWebServer, stop the IIS server or other applications that use port 80, and run the product installation. To setup the IIS server, follow the procedure in this chapter.

This section explains how to install these services in IIS. This explanation targets IIS 7.x and 8, but other versions should be similar.
You are going to install three services inside IIS:

  • TProjectServer —Allows you to remotely access your project configurations. 
  • TVisualizerWeb/TVisualizerRemote —Allows remote access to runtime displays. 
  • iDataPanel—Is the service that provides data to iOS devices. 
When you are finished developing and testing your project, you can deploy the runtime application so it can be used by end-users. Projects can be deployed to run locally on a stand-alone computer or embedded device, in a client-server distributed architecture, or on the cloud. This chapter discusses the various methods for deploying these applications.


In this section...

Page Tree
rootDeploying Applications


On this page:

Table of Contents
maxLevel2
stylecircle





Configuration Procedure


  1. Verify that IIS is installed by going to Control Panel > Administrative Tools and looking for Internet Information Services (IIS) Manager in the list. 
  2. Enable ASP.Net and .Svc Handlers for the WCF Service.

On IIS 7.x:


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

    • From the Microsoft .Net folder, open the Command Prompt and run the following commands:
          aspnet_regiis.exe -I -enable
          ServiceModelReg.exe -r
    • Microsoft .Net is installed in one of the following folders:
      • C:\Windows\Microsoft.NET\Framework\v4.0.30319 (for 32-bit operating systems)
      • C:\Windows\Microsoft.NET\Framework64\v4.0.30319 (for 64-bit operating systems)

For IIS 8.0:


    • From the Control Panel, go to Program and Features, then click “Turn Windows features on or off”.
    • Enable the ASP.NET 4.7 option. Navigate the tree: Internet Information Services > World Wide Web Services > Application Development Features > ASP.NET 4.7:

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


      3.   From the IIS Manager, verify that the .svc extension 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)


      4.   From the FactoryStudio installation folder, run the utility: InstallTWebServer.exe /uninstall, which will remove the default TWebServer installation. 


      5.   From the IIS Manager, go to Sites > Default Web Site > Add Application and configure the information for the services as described in following steps


      6.   For the TProjectServer, configure: 

    • Alias—TProjectServer 
    • Physical Path—C:\Program Files\Tatsoft\FactoryStudio (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: You should allow “Everyone” access, at least for reading
    • From IE, use the URL http://localhost/tprojectserver/service.svc to verify if the service was correctly installed. That should show a page with information about the service. 

      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

    • Note: Security should enable any user (Everyone), at least for reading.
    • On IE, test the http://localhost/fs-8.1/service.svc URL to verify the service was correctly installed. It should show a page with information about the service. 

      8.   For the 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.


      9.   Forthe DataPanelImages (Virtual Directory), configure:

    • AliasiDataPanelImages 
    • Physical PathC:\FactoryStudio Projects\iDataPanelImages 

      10.   Enable Anonymous Authentication for each of the services. 


     11.   Setup the Compression module. If it is not installed, you will see the alert boxes.


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


      If it's the dynamic compression is 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 compression for your site and ensure Dynamic Compression is checked. At this point, Dynamic Compression should be setup, but you really need to be specific about what mimeTypes will be compressed.

 
 
 
 
From the dropdown, select system.webServer/ webdev / httpCompression:

      Then click on Dynamic Types. Now that you are in the list editor, add application/json as shown below.

Image Removed

      After you've added them and closed

Close the dialog after you add it. 

Image Added


      12.   If your remote users cannot access FactoryStudio, you should allow Everyone access to the FactoryStudio folder, at least for reading. Right-click the folder, click the Security tab, click Edit, then add read permissions for Everyone.


Warning

IIS must be restarted after configuring the services.