Root Elements
-
API
Api classes. -
Action
Custom Actions used to extend the Workflow or Service palette. -
Application
A classic presentation layer application. (deprecated) -
Aspect
Aspects encapsulate repeated structural or behavioural patterns seen in the business model and promote code re-use. -
Augment
Augments are used to extend a class for a given customer or business domain. -
Channel
Channels are abstract integration endpoints representating the Network Transport Layer. They are used to send or receive Messages. -
Class
A Class is an abstraction of a business model concept. -
CompositeDataSource
A Composite Datasource. -
Connections
Connections contain deployment settings for Datasources and Channels. -
Control
Custom Control Definition. -
DataSource
A datasource is a logical representation of physical storage that is used to create, read, update and delete object instances. -
Deployment
A deployment represents the configuration of one or more physical systems and the models deployed to those systems. -
Dialog
Dialogs are similar to Portlets, but are specifically used for creating, editing, and presenting information in a transactional, rather than informational way. -
ETLActivity
An ETL activity. -
Enumeration
Enumerations are a special type of Class that provide a list of values along with localizable captions. -
Environment
An Environment represents physical system configurations and combines server and connection settings into one convenient file. -
ExternalLibrary
ExternalLibraries reference jar files located in the project's /lib folder. This is for documentation purposes only. -
ExternalReport
A Pixel Perfect Report built using the Jasper Reporting Engine -
Facets
A set of facets that can be applied to metadata objects. -
File
A File Integration Channel. -
FileStorage
A FileStorage datasource is a logical representation of a file system for persistence. -
Filler
A presentation layer filler element -
Filter
Filter elements centralize the search configuration for a given class and are used by filter controls to present text search, filter tiles, and filter chips to end users. -
Form
Classic Presentation Forms contain user interface controls which display data for viewing, editing, and querying. (deprecated) -
Format
Format for a Typed Message -
HTMLTemplate
Template definition used by HTMLLabel script. -
HTTP
An HTTP Integration Channel. -
Interface
Lists of valid request and/or response messages for services, send and sendReceive steps, and 'any' message parts. -
Kafka
A Kafka Integration Channel. -
Layout
Layouts arrange and bind controls for use in Portlets and Dialogs. -
Loaders
A set of custom metadata loaders. -
Mail
An Integration Mail Channel. -
MenuItem
A presentation layer menu item. -
MenuLink
A presentation layer menu link. -
Message
A message carries information from a source system to a destination system over an integration channel. -
MessageQueue
Abstract integration endpoint representing a Message Queue. -
Metadata
Describes various attributes of a model, including its name, dependencies, and version -
NodeTypes
The set of node types that provide logical grouping of nodes in an application cluster. -
ObjectQueue
An ObjectQueue Integration Channel. -
Picker
Picker elements provide a consistent user experience for selecting objects. -
Portal
Declares the application's structure, including its set of workspaces. Model Server serves the application at *serverRoot*/ui/portal/*portalName*. -
Portlet
Portlets are the basic UI components that make up an application. They host one or more Layouts and present features to end users. -
RelationalDatabase
A RelationalDatabase datasource is a logical representation of the structure of a database. -
RelationalDatabaseAspect
RelationalDatabaseAspects are functional groupings of additional table aspects, and SQL objects that may be applied to other relational databases in your model. -
RelationalDatabaseAugment
Augments contribute tables and/or SQL objects to a given data source. They are used for modularization, i.e. separating the domain model into several modules without circular dependencies between them. -
Report
A report build using the NexJ Reporting Engine -
RuleSet
A set of rules to support run-time configurable business logic. -
SOADefinition
Services Oriented Architecture service definition. -
SOAImplementation
Services Oriented Architecture service implementation. -
Screen
Classic Presentation Screens group forms together visually and functionally. It represents one piece of functionality within an application. (deprecated) -
Separator
A presentation layer separator element. -
Server
A Server specifies it's type (e.g. WebSphere) and various other settings to support deployment. -
Service
Services provide integration service orchestration capabilities. They are essentially workflow for integration. -
ServiceDataSource
A ServiceDataSource datasource is a logical representation of a service for persistence. -
Stylesheet
Stylesheets contain a set of styles to apply to user interface elements. -
TCP
A TCP Integration Channel. -
Test
A Server test script used for performance and functional testing. -
Transformation
Transforms an instance of one message type to another message type. -
UDP
A UDP Integration Channel. -
UITest
Recorded user interactions to verify that the UI is invoking the Business Model correctly. -
UnitTest
A set of test cases to test Model functionality. -
UnitTestSuite
A set of unit tests to be run as a group to test model functionality. -
Upgrade
The set of changes to a model's Relational Datasource(s) from version to version. -
Workspace
Workspaces organizes portlets by function into pages and tabs. e.g. Contacts, Opportunities, ... -
XML
An XML Datasource