Deploy a FactoryTalk Optix Application
Rockwell Automation
client devices automatically run FactoryTalk Optix Applications
upon deployment. Other client devices require you to start the application manually on the device or configure the application for automatic startup.Use
FactoryTalk Optix Studio desktop editor
to deploy to either local or remote devices. Use FactoryTalk Optix Studio web editor
to deploy to remote devices only. FactoryTalk Optix Studio
uses FactoryTalk Remote Access
to deploy to remote devices.
IMPORTANT:
If a
FactoryTalk Optix Application
is already running on a client device, deploying another FactoryTalk Optix Application
stops the other application.Prerequisites
- Confirm thatFactoryTalk Optix Application Update Serviceruns on the client device.IMPORTANT: To operate correctly,FactoryTalk Optix Application Update Servicerequires the TCP port 49100 to be reachable and a valid username with a configured password.
- Confirm that the client device has a valid license.IMPORTANT: If the client device is not licensed,FactoryTalk Optix Applicationsrun in the demo mode and stop automatically after 2 hours.
- Configure a device.IMPORTANT: Configure either a local or remote device. To configure a local device, see Manage client devices. To configure a remote device, openFactoryTalk® Hub™and accessFactoryTalk Remote Access. In FactoryTalk Remote Access Online Help, seeDomain viewand scroll toTo add a device. The remote device must also have theFactoryTalk Remote AccessRuntime client installed and configured. In FactoryTalk Remote Access Online Help, seeClient configuration.
- To deploy aFactoryTalk Optix Application
- Select the configured device.For more information, see Select a client device.
- If you selected a remote device, you must first establish a VPN connection to that device. SelectVPNRemote Desktop
- SelectRun
- Enter the user password for the client device and selectOK.
To stop the .
FactoryTalk Optix Application
on the client device, select Stop
NOTE:
Clicking and holding a button on remote desktop when remote desktop does not have focus automatically increments the button if it is configured with
MouseUp
and MouseClick
events. This is because bringing focus to remote desktop by clicking and holding the button automatically performs MouseUp
and MouseClick
events. Provide Feedback