Glossary
- Framework
-
Combination of an application architecture and standardized components and tools.
- Business framework
-
Area that processes business logic for enterprises' applications.
- Application framework
-
Semi-complete application used to develop specific applications.
- Business rule
-
Knowledge, rules, and ways to perform or process work.
- Product factory
-
System that supports systemic functions in the company-wide business area of product planning, development, operation, and evaluation, develops product shape, and provides product information to the business system.
- Structure
-
Standard data structure used in service modules.
- Message
-
An input or output message can be defined to transfer information such as input and output data type, its length, and message type.
- Map
-
Defines mapping rules between messages and structures.
- Service module
-
Minimum unit module that provides service.
- Business module
-
Functional block module that contains application processing logic.
- Studio
-
Integrated development tool for server program development. It allows message development, SQL development, service flow design, and business module creation.
- Integrated server
-
ProFrame-based server that manages resources.
- Test framework
-
Testing tool for developed service and business modules.
- Meta
-
Data dictionary that registers and manages various types of terms such as IT terms, application terms, database table names, and column names.
- Middleware
-
Software that is between applications and an operating system (such as Unix and Windows).
- Channel-Tier
-
Input and output data processing layer that is one of the 3 tiers presented by ProFrame architecture.
- Business-Tier
-
Layer that provides module structure based on common system functions and common application layer functions. It is one of the 3 tiers presented by ProFrame architecture.
- CommBuff
-
ProFrame interface module used to share data between application modules.
- Data-Tier
-
Layer that separates a database access module from applications to improve business logic performance and allows to access databases in the same method. It is one of the 3 tiers presented by ProFrame architecture.
- Dynamic call
-
ProFrame interface module used to dynamically replace libraries during system operation.
- EMB
-
TmaxSoft’s proprietary technology that implements intra-SOA by realizing the concept of microflows presented by Gartner. It has an architecture that visualizes service processing flows and minimizes dependency between applications.
- ProMapper
-
Framework mapping engine that creates a library available in C.
- DBIO
-
Standard method to access a database.
- Hot deploy
-
Function that provides reliable and uninterrupted service by enabling real-time dynamic replacement of only changed modules without server downtime when internal logic of services and modules is changed.
- Memory manager
-
If there is a memory leak in an application or a framework, the entire system’s performance is degraded. Since ProFrame controls memory through a module called Memory Manager, it is possible to fundamentally prevent memory leaks.
- EMB designer
-
Service and application processing flow design tool embedded in Studio.
- Deploy
-
Deploys developed source and binary to a development operating system.
- Dlupdate
-
Combines compiled source files to a library and loads it to shared memory.
- T-Cache architecture
-
Structure that supports quick access to frequently used data during system operation to improve performance and enable data synchronization.
- TP Monitor
-
Transaction management middleware that monitors sessions, which are operating with various protocols, and transactions, which are minimum processing units between systems and databases, to keep and maintain them consistently.