Start the Batch and
e
Procedure Servers

The
FactoryTalk Batch
and
FactoryTalk
e
Procedure
Servers may start automatically when the computer starts. By default the
FactoryTalk Batch
Server starts in production mode. If
FactoryTalk Batch
is not activated, run the tutorial in demo mode. While in demo mode, the
FactoryTalk Batch
Server runs for a two-hour period and then stops.
TIP: The
FactoryTalk Batch
Server does not start in production mode without activation. (See the
Activate Rockwell Software Products
insert included with the software CD.)
IMPORTANT:
If you are using
Windows
server to host your
FactoryTalk Batch
and eProcedure Server, ensure that the
Internet Explorer
Enhanced Security Configuration setting on the server has been turned off.
For instructions, see Microsoft Web site.
To start the Batch and
e
Procedure
Servers:
  1. Select
    Start
    , point to
    All Programs
    Rockwell Software
    FactoryTalk Batch Suite
    FactoryTalk Batch
    , and then select
    Batch Service Manager
    . The
    FactoryTalk Batch Service Manager
    opens.
    TIP: This procedure requires administrator privileges.
  2. If the
    FactoryTalk Batch
    Server is not already listed in the
    Service
    box, select it from the list.
  3. If the
    FactoryTalk Batch
    Server is running, select
    Stop
    .
  4. If the name of the computer where the
    FactoryTalk Batch
    Server is installed does not display in the
    Computer
    box, select the
    Select Computer
    button. The
    Select Computer
    dialog box opens.
  5. In the
    Enter the object name to select
    area, type the name of the computer where the
    FactoryTalk Batch
    Server is installed (or select
    Advanced
    to search for a computer). Select
    OK
    .
    TIP: The
    FactoryTalk Batch
    Service Manager must communicate with the
    Windows
    Service Manager of the selected computer to determine what services are available. There may be a noticeable delay as communications are established. If the Service Manager cannot communicate with the
    Windows
    Service Manager of the selected computer, a message displays.
  6. From the
    Service
    list, select
    FactoryTalk Batch Server
    .
    TIP: If
    No Batch Services
    displays in the list, the
    FactoryTalk Batch
    Server is not installed on the selected computer. See the for instructions.
  7. To start the
    FactoryTalk Batch
    Server in Demo mode, select
    Allow Demo Mode
    .
  8. Select the method to use for restarting the server.
    Methods for restarting the server
    Method
    Description
    Cold Restart
    The
    FactoryTalk Batch
    Server starts in a new instance without restoring data from its previous run. Batches are not added back to the batch list, and operator arbitration states are not recovered. For all batches that were not restored, batch completion events are recorded in the
    FactoryTalk Batch
    Event Journals. After a Cold Restart, you will not be able to resume execution of batches from the previous instance. If Security Authority is enabled, SAIs in a secured area model and any secured recipes must match the current Network FactoryTalk Directory SAI.
    Warm Restart
    Restarts the
    FactoryTalk Batch
    Server and attempts to restore the set of batches that were on the batch list when the server previously stopped. Batch complete events are added to the
    FactoryTalk Batch
    Event Journals for all batches that were not restored to the batch list. After a Warm Restart, any batches that are not restored cannot be recovered or resumed in the future. Batches are restored in Manual execution mode with active transitions in a HELD state. No validation for Security Authority is performed.
    Warm All Restart
    The
    FactoryTalk Batch
    server attempts to restart but will not restart if it is unable to restore all the batches to the batch list. If a Warm All Restart attempt fails, the ability to restore batches in the future is not affected. After the issues are resolved, another attempt to restore the batches to the batch list can be made using Warm Restart, Warm All Restart, or Hot Restart. This is the default setting for automatic restarts. Batches are restored in Manual execution mode with active transitions in a HELD state. No validation for Security Authority is performed.
    Hot Restart
    Follows all the startup rules of Warm All Restart. In addition, the
    FactoryTalk Batch
    Server attempts to restore batches to their last known state, including transition states and recipe modes, without any operator interaction.
  9. Select
    Start/Continue
    . The Service State area changes from STOPPED to START PENDING. After a few moments, RUNNING displays and the light changes to green.
    The
    FactoryTalk Batch
    Phase Simulator may start automatically and open a window. If so, minimize the window.
  10. Select the
    e
    Procedure
    Server from the
    Service
    list.
  11. Select the method to use for restarting the server.
    Methods for restarting the server
    Method
    Description
    Cold Restart - checked
    Restarts the
    FactoryTalk
    e
    Procedure
    Server in a cold state. All control steps, plus all signatures and previously-entered values associated with the control step due to parameter deviation or cancelled step verification signatures, are removed.
    Cold Restart - unchecked
    Restarts the
    FactoryTalk
    e
    Procedure
    Server, restoring the control steps that were active when the server previously terminated (the control step is restarted with a new reactivation number).
    (See Effects of warm boot on control steps for more information.)
  12. Select
    Start/Continue
    . The
    e
    Procedure
    Server starts running.
  13. Click
    Close
    to close the
    FactoryTalk Batch
    Service Manager.
    TIP: If conversation becomes LOST while running in Demo mode, make sure that the Simulator is running and try starting the server(s) again. See
    Start the FactoryTalk Batch Phase Simulator
    for more information.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal