FactoryTalk ProductionCentre (FTPC) is Rockwell's MES platform based on J2EE, XML Web Servers, Pnuts scripting language.

1.FTPC architecture

    FTPC architecture is divided into four layers, comprising: a client (Client Tier), Web layer (Web Tier), business logic (Business Tier), database (Database Tier)

2. The database layer

Plant Operations store all database tables, indexes, stored procedures, stored functions and so on.

3. Yewuluojiceng

Business logic

  Plant Operations service session bean one layer as a single point of access. Session bean application use cases, transaction management process, and coordinates access to the lower component (e.g., the entity bean, and other data access objects helper object). This is achieved as a stateless session bean layer, which provides better scalability and performance than stateful session bean, because the thread safety can be guaranteed on a non-blocking client access business methods. Stateless session bean provides EJB - all of the major advantages of container-managed lifecycle.

Data access logic

Handling data processing program store and retrieve data objects transmitted to a logical database tables. Using these data processing session bean classes access the database directly through JDBC. Plant operation does not use persistence and container-managed entity bean. Data transfer object is a set of classes to pass all the necessary information. Designed in a simple format is particularly suitable for transfer between different layers of the system to transfer all the necessary information about each type of object Plant Operations. For certain types of data, the data is cached in the intermediate layer, and this data is rarely changed. These data cache is designed to to maintain consistency between multiple application servers through a coordinated database.

4.Web layer

Web layer is mainly released to the Web clientEnterprise Java Beans (EJB) business logic. It consists of the following three components:

• HTTP Server

• SOAP Engine

• Plant Operations XML Web Services

5. Client

    Client consists of the following three types:

• HTML-based client (Shop Operations). The client can run at the underlying HTML mode, but does not support transactions.

• Java-based client (Process Designer and Shop Operations). Shop Operations and Process Designer application can be run in a Java-based mode.

• Custom client application integration with customers, communicate with the service through the Plant Operations Plant Operations XML Web Service.

The client may communicate with the intermediate Plant Operations in two ways:

• XML Web Services

• RMI/IIOP calls to session beans

Plant Operations client (Process Designer and store operation) is designed to use RMI / IIOP (default) or SOAP communication.