Application tier:(data collection)

The application collects data and provide access to BRM, and triggers Portal Business Processes–
Registration, Customer, Login/passwords, Activity,Purchasing, or Billing Data

Business Tier : (data proccesing)

It has 3 components 1.connection manager (cm) 2. facilities module (Fm) 3. external

modules (em)

cm : it provides an interface b/w client and rest ofthe system.client application connect to brm system throgh CM

fm : CMs include FMs that process the data captured by the client and it validates login and goes
to cm

em:it is a set of opcodes that perform BRM functions. However, it is not linked to a CM in the
same way that an FM is. Instead, it runs as a separate process that you must start and stop.

CMMP: Instead of configuring an application to connect directly to a CM, you can

configure it to connect to a Connection Manager Master Process (CMMP)

Data management Tier :( object Tier) ( data translation)

The data management tier consists of the following components:

Data Managers (DMs), which translate requests from CMs into a language that the database can
understand. For the BRM database, the language is SQL. There are also DMs for credit card
processors, Vertex, and so forth. See "About Data Managers (DMs)".

Oracle In-Memory Database (IMDB) Cache Data Manager (DM), which translates requests from
CMs into a language that Oracle IMDB Cache and the BRM database can understand.

Translates to different external systems– CC Clearing House, Tax software, LDAP, etc (dm_fusa,
dm_vertex)

Data Tier : (data storageand retrival)

The Portal Database– Oracle, SQLServer, DB2 ,..Interfaces available to external systems,
including payment, tax,email and directory servers ...API provides access to any external system,
including legacy databases– One-way or two-way communication