EC Application overview
EC is a lightweight message broker application and M3 integration platform that runs on Grid. EC Application enables M3 to communicate and integrate with internal and external resources through message or document exchange.
EC Application is uploaded to Grid through a LifeCycle Manager (LCM) client installed on a server. Users log in EC application through LDAP settings. LDAP means Light-Weight Directory Access Protocol, it determines how to name an object in an active directory.
The EC administration user interface runs on Grid UI framework which provides management and monitoring of partner agreements processed in EC. The EC Application pages in grid contain links to functionally grouped administrative tasks.
Here are the EC application components:
EC_Central Node
Also called CentralFileAccess (CFA), EC_Central node is a runtime component that runs as a grid node which provides file access service to all of the EC_Process and EC_MapGen nodes.
The Central File folder is a local folder in the domain accessible to the Grid Agent of the EC_Central
node. This Grid Agent must have Full Control access to the Central File folder, for example: \\local\
shared folder. This node runs detections, agreements, and process dispatchers. You must create the Central File
folder before you install EC Application in grid.
The Host machine for the Central File folder must have a running LCM Service, and the users
must have read/write access to the Central File folder location. LCM Service extracts the default
files upon installation.
CFA delegates tasks to Process nodes. When there are no process nodes running, EC_Central node also functions as a standalone node.
EC_Process Node
EC_Process node is an additional runtime component that runs the process flow of agreements received in EC from EC_Central node and peer process nodes. EC_Process node is dependent on EC_Central node to run.
EC_Process node is previously called MECServer node.
EC_MapGen Node
This server runs on grid nodes and generates mappings for runtime.
EC_MapGen node is previously called MapGen node.
For more information on generating and publishing a mapping, see Business Document Mapper User Guide.
EC_UI Node
This is the graphical interface of EC application. This replaced the previous Web Administration tool. In web EC UI, you can delete old data log from EC database, configure log settings, view message logs, view archived message files, and perform other EC management tasks.
EC Database
EC Database stores mapping data, partner agreements, and runtime log data. EC Database is required to run the grid nodes (EC_Central, EC_MapGen, EC_Process, and EC_UI). This database can be installed separately from the other components and in a location accessible to all EC grid nodes or on any other accessible server within the grid network.
See, the M3 Core Installation Guide and M3 Core Administration Guide.