Configure presentation engines

Add a native presentation engine or a web presentation engine to your project.
TIP: Each project can contain a single native presentation engine and a single web presentation engine. If your project runs on the Embedded Edge Compute Module 1756-CMEE1Y1, add a web presentation engine and delete the native presentation engine.
  1. In
    Project view
    , right-click the
    UI
     folder and select
    New
    .
  2. Select one of these presentation engines:
    • Native presentation engine
      . Create a native presentation engine when you are going to run
      FactoryTalk Optix
       as an application on the local device. For a typical HMI scenario, this is the direct rendering of the
      FactoryTalk Optix Application
       on the screen of the target device.
    • Web presentation engine
      . Create a web presentation engine to run
      FactoryTalk Optix
       as a service on the runtime device or to run
      FactoryTalk Optix
       as an application in order to interact with the system using a web client.
      FactoryTalk Optix
       as a service automatically runs the deployed application with or without a user interface. This mode is generally used when there is no local operator on the runtime device.
  3. (optional) Select the
    Native presentation engine
     and make any necessary changes in
    Properties
    .
    • Dynamic variables polling time
      . Time interval between variable readings.
    • Text render type
      . Specify how text renders to the UI control.
    • Virtual keyboard
      . Select the default virtual keyboard. See Keyboards.
    • LoginWindow
      . Login window type that shows at session start when no user is logged in.
    • Start window
      . Window object type created at the start of a session.
    • Starting user
      . User that authenticates the session.
    • Style sheet
      . Style graphic objects.
    • Session
      . UI Session object to use.
  4. (optional) Select the
    Web presentation engine
     and make any necessary changes in
    Properties
    .
    • Dynamic variables polling time
      . Time interval between variable readings.
    • Protocol
      . Protocol for communication between web clients and the web server.
    • IP address
      . The address for the web server to listen on. Must be a valid IP address of a local device.
      TIP: Set
      0.0.0.0
       to make the web server listen on all available addresses of the local machine. Set a specific address other than
      0.0.0.0
       to ignore requests to local addresses different from the entered one.
    • Port
      . Port for communication between web clients and the web server.
    • Hostname
      . Name used to generate a self-signed certificate for HTTPS protocol. If empty, the certificate generates based on the machine name.
    • Maximum number of connections
      . Maximum web clients that can connect to the web server.
    • Allowed remote sources
      . List of remote sources that you can load or use to access the current resource. Accepted formats include name of Internet host or IP address. URL pattern, port number, and path are optional. Wildcards (*) such as *.example.com are accepted for subdomains, host addresses, and port numbers.
      TIP: Enter
      Allowed remote sources
       to specify which URLs can embed the current resource. Allowed remote sources provides greater security and control when loading and accessing remote resources.
    • Enable automation IDs
      . Enable automated IDs for automated testing. See Automation IDs.
    • Allowed local sources
      . List of file extensions served by the
      WebPresentationEngine
      . The minimum required configuration is:
      *.html, *.css, *.js, *.ttf
      By right-clicking the field and selecting
      Set default safe values
      , you can set the following default values:

        images
        *.png, *.jpg, *.jpeg, *.gif, *.bmp, *.svg

        video
        *.avi, *.mov, *.mkv, *.mpg, *.mp4, *.wmv

        text files
        *.pdf

        font files
        *.ttf, *.otf

        web files
        *.html, *.css, *.js

      Follow these conventions:
      • You can use specific file names, such as
        myfile.txt
      • You can use wildcards (
        *
        ) to match patterns, for example,
        file*.txt
         matches
        file1.txt
        ,
        file123.txt
         and so on.
      • The following folders are restricted:
        /projectfiles/netsolution
        ,
        /projectfiles/pki
        ,
        /applicationfiles/
        .
      • All rules are case insensitive.
      TIP: Using
      *
       to share all files triggers a warning during deployment and logs during execution.
    • Virtual keyboard
      . Select the default virtual keyboard. See Keyboards.
    • LoginWindow
      . Login window type that opens when you start a session and no user is logged in.
    • Start window
      . Window object type created at the start of a session.
    • Starting user
      . User that authenticates the session.
    • Style sheet
      . Style graphic objects.
    • Session
      . UI Session object to use.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal