• 所有的文件

    FME Server Architecture

    FME服务器系统由客户端层和服务器层组成，每个服务器层都有许多组件。

    FME Server Components

    1 Web Application Server

    A Java Web Application Server is required in order to run theFME Server Web User Interface,FME Server Web Services, and any other web clients. Depending oninstallationconfiguration, the Web Application Server may be a version of Apache Tomcat included with FME Server. (The version of Apache Tomcat for this documented release is8.5.14)。或者,它可能是一个servlet提供9月arately. Supported servlets are Apache Tomcat and Oracle WebLogic.

    2 Web Clients

    TheWeb User Interface包含在FME服务器上，可以在浏览器中运行：

    Custom web clients can be developed on top of the FME Server REST API.

    3 FME Server Web Services

    FME Server provides predefined services to carry out common tasks. Services provided with FME Server include:

    4 Non-Web Clients

    • FME Workbench is the authoring environment for FME Sever but can also be used to submit jobs to FME Server through a number of transformers.
    • FME Server Consoleis a command line interface to FME Server
    • Custom clients can be developed on top of the FME Server REST API service.

    5 REST API

    The FME ServerREST Serviceuses the FME Server Java API to send client requests to FME Server via the FME Server API.

    6 FME Server API

    All requests are sent to FME Server through the low-level FME Server API.

    7安全

    FME Server providesAuthentication and Access Controlusing the Java Authentication and Authorization Service (JAAS) framework.

    8 FME服务器核心

    TheFME Server Coremanages job requests, scheduling, and repository contents.

    9 Process Monitor

    TheProcess Monitorprovides fault tolerance functionality ensuring that the FME Server Core and FME Engines remain available to process requests. The Process Monitor also provides a mechanism for managing the FME Server and FME Engine components, including the ability to start, stop, restart and add components.

    10 FME Engines

    FME Enginesprocess job requests by running FME Workspaces. Each FME Engine processes a single request at a time. FME Server processing can be scaled by adding FME Engines to the same computer or to separate computers within a distributed FME Server environment.

    In a distributed environment, FME Engines run on a computer or computers that are separate from the FME Server host.

    11个数据集

    通常，FME服务器作业运行读取和/或写入数据的工作空间。FME Server管理员必须确保FME引擎具有对数据集或数据库的读取访问，并将Workspaces写入的任何目录或数据库的写入访问权限。

    12 FME Server Database

    The FME Server Core uses theFME Server Databaseto store job and repository information. The database should never be edited directly, although querying the database for job history and other statistical information is common.

    Expressinstallationsof FME Server run the FME Server Database on a version of the PostgreSQL database server. (The version of PostgreSQL for this documented release is9.5.12)。Distributed installations run the FME Server Database on a server provided separately. Supported database servers are PostgreSQL, Oracle, and SQL Server.

    13 File System

    In aDistributed/Fault Tolerant Installation，FME服务器系统共享组件安装在远程文件系统上的目录中，以启用来自不同计算机的访问权限。这些文件包括Repositories和Resources.

    FME服务器连接

    Note:For a complete list of ports used by FME Server, seeFME服务器端口.

    A

    Web Clients use the FME Server Web Services over HTTP. Communication is defined by the Web Services API, the REST API, and the FME Server API.

    B

    Non-web Clients use the REST API over HTTP.

    C

    Web客户端，FME服务器Web服务和非Web客户端使用FME Server API通过TCP / IP与FME服务器通信。通过端口7071将请求发送到FME服务器核心。通过由FME服务器核心创建的随机分配的端口将消息返回给客户端。

    D

    Web应用程序服务器通过端口7500通信给FME引擎。

    E

    The FME Server API sends job and repository requests to the FME Server Core over TCP/IP port 7071.

    F

    The Process Monitor monitors the FME Server Core processes and restarts them if they halt. The FME Server Core communicates with the Process Monitor over TCP/IP port 7500.

    G

    The Process Monitor monitors the FME Engine processes and restarts them if they halt.

    H

    Once registered (see L below), the FME Engines communicate with the FME Server Core over TCP/IP ports dynamically determined by the Core.

    I

    FME引擎从共享/登录的驱动器，数据库，Web服务等读取和写入数据。

    J

    FME服务器核心通过TCP / IP端口7082通过JDBC与FME服务器数据库通信。

    K

    The FME Engines communicate with the FME Server Database. The port varies depending on the selected database.

    L

    The FME Engines perform initial registration with the FME Server Core over TCP/IP port 7070.

    M

    The FME Server API can be used to send job scheduling requests to the FME Server Core over TCP/IP port 7073.

    N

    FME服务器API可用于通过TCP / IP端口7072向FME服务器核心发送通知请求。

    O

    Notification ServiceSubscribersperform initial registration with the FME Server Core over TCP/IP port 7074. Subscribers process notifications received by the FME Server Core.

    P

    Notification ServicePublishersperform initial registration with the FME Server Core over TCP/IP port 7076. The FME Server API can be used to relay requests to the FME Server Core over TCP/IP port 7075. For SMTP Publisher ports, seeFME服务器端口.

    Q

    The FME Serverconfiguration, andbackup and restorerequests, are communicated to the FME Server Core over TCP/IP port 7077.

    R

    进入Resourcesis communicated with the FME Server Core over TCP/IP Port 7079.

    S

    Communication with the FME ServerWebSocket Server发生在端口7078上。

    T

    Automatic (online)licensingrequests take place through HTTP over port 80.

    U

    FME服务器队列管理Job Queues和dispatches jobs as needed. Communication is over port 6379.