When project artifacts have been designed and tested they are ready to deploy to a host for execution - either immediately or for a scheduled execution plan. Deployment is achieved by creating events for the actions that you want to deploy, then copying those actions to the appropriate host for execution. Although events can be created on projects, they can only run on a host which has an active event monitor of the appropriate kind. The event on the host must have status enabled and the host must be currently online with appropriate services installed, see Event overview, Event monitoring overview and Event enablement.
Actions can be copied to hosts
either by dragging or copy and paste, see Drag
or copy and paste. Alternatively you can select an action type from
the particular host where the action is to be executed, i.e. from under
the Hosts node 
in Explorer, then right-click and select
Assign action to host. This presents you with a list of all the actions
available of this action type. You can make your selection of actions
that you want to assign to this current host, see Host
menu for more. As with dragging and dropping, or cutting, copying
or pasting, when you assign an action to a host you also have the option
to copy events as well as you are prompted:
Do you wish to copy all events that belong to the action to this host? Press Yes or No buttons as appropriate.
Note that when actions are copied to hosts it is in fact a shortcut to the action that is pasted on the host, rather than a full replica copy of the action. This means that when you make changes to an action or activity on a project, these changes will also be automatically implemented on the host. However it is different when actions are copied between projects, as in this case it is a replica copy that is created into the new project and so changes in this case which are made to the original or the copy action will not reflected in the other project. See Drag or copy and paste for more on this distinction between shortcuts and copies.
When an action with events is copied to a host you will be prompted whether you want to copy these events as well as the actions, see Event overview for details of the relations between actions and events. Alternatively you can create the events directly on the host, see Copy event for details of the various ways that events can be created on a host.
Note that when events are copied from a project, then it is a full replica copy that is created on the host, not a shortcut. This means that when you make changes to events on a project, these changes do not update events that have been copied from the project onto a host.
At any time an action can be modified on the local "project" server then copied to update the version on the production host.
Related topics include Concept overview, Projects overview, Hosts overview, Data source overview, Event overview