2. Terminology:
Name/Acronym Definition
SMX Provides generic message handling functions
including reliable message routing between the
SMX clients, persistence of messages,
transformation of messages, and handling failures
Application Containers
(AC)
A business process that uses the SMX Core
framework to reference stored messages and
perform simple transformations to complex
business logic and user interface controls
Connectors Interfacing logic to external clients
Manageability Monitoring and control (configuration) of SMX
Core operations via a User Interface
Seygen Proprietary - Not to be distributed without prior written consent.
3. Technology Stack
SMX Core
WebLogic Middleware Application Server: WebLogic 12.1.2
Oracle Database Server: 11g Release 11.1.0.0.0
Java Virtual Machine: jdk170_76, Java Enterprise Edition Version 1.7.0_76 J2EE (EJB, MDB, JMX)
Rules Engine: DROOLS
Web Services (SOAP, JAX WS)
XML Tools (JDOM, XALAN, XQUERY)
Manageability
User Interface: Struts
3Seygen Proprietary - Not to be distributed without prior written consent.
7. What is SMX?
Designed to receive, store, transform, and forward
messages
Connectors: Multiple transports (Web services, HTTP/HTTPS, JMS,
MQ, Sockets, FTP)
Application Container: Container for Business Process. Container is
available for one or more clients.
SMX Core
C
O
N
N
E
C
T
O
R
W
I
T
H
A
C
C
E
S
S
P
O
I
N
T
S
Application
Container
Client
Seygen Proprietary - Not to be distributed without prior written consent.
8. Seygen Proprietary - Not to be distributed without prior written consent.
SMX Core Architecture
Application
Systems
Calling
System
Message
Acceptance
Application
Container
Transformations
Custom Bus. Logic
Delivery
Engine
Source
Systems
System
Site 1
Alert Management
Scheduling
Monitors
Manageability
Activity Log
Message Store
System
Site 2
System
Site N
.
.
.
Calling
System
Calling
System
Manageability User Interface
Configuration Dashboard
Alerts &
Status
User Mgmt.
O
U
T
B
O
U
N
D
C
O
N
N
E
C
T
O
R
I
N
B
O
U
N
D
C
O
N
N
E
C
T
O
R
SMX Core
9. Message Flow Through SMX
A flight is a grouping of
synchronous activities and
represents one leg of travel
that a message follows
through SMX
Design allows for optimal
resources (i.e. threads and
memory) usage and
scalability
Source
Client
Inbound
Connector
Inbound
Message
Acceptor
Inbound
Message
Handler
Application
Container
Delivery
Engine
Outbound
Connector
Destination
Client
Flight 1 Flight 2 Flight 3 Flight 4
Transport
Specific
Receive
Validate Persist,
Acknowledge
Recognize
Transformation
Engine XSLT
Deliver Transport
Specific
Send
Mediate, Correlate
Persist, Queue
Outbound Messages
Seygen Proprietary - Not to be distributed without prior written consent.