System Database

During run time, the data dictionary is loaded into memory when the MXServer starts.
There are two types of data stored in the data dictionary:

Data dictionary data is metadata for every service, object, table, view, column, and so on that is used by the system.
Application data is data for every application object, such as work order, item, PO and so on.

If you create a new table, you must register that table in the data dictionary. ( Use database configuration application to create new tables for best practices.)

MAXTABLES : defines the tables for each application.
MAXVIEWS : contains the view definitions, which are the tables associated with the view.
MAXOBJECT : contains the class name. Every object is associated with a table or view.

The MaxObject table defines all the MBOs. There are three types of objects:

• standard objects, which directly represent a database table
  
• views, which represent database views
  
• non-persistent objects, which represent MBOs that exist in MXServer but do not persist - do not get saved - in the database

Classname is the java class file that is used with this object's MBOSet.
Entityname is the database table name or view name used by this object.
Extendsobject is the object name that this object extends. For example, WPITEM is the base table for the WPMATERIAL view. By extending the base table, the WPMATERIAL object inherits all the columns and all the business rules that WPITEM has. It then defines its own specific columns and business rules.

The WOCHANGESTATUS object is a non-persistent object. It is used to collect information for a work order status change, e.g. the new status. In the UI, the Change Status dialog is shown when the Change Status action is chosen. The fields in this dialog represent the WOCHANGESTATUS object. When the OK button is clicked, the collected information is used to actually change the status of the current work order.

Application Organization

Each application has a main object associated with it. There is one main object per application.

The main object is a table or view. Usually the name of the table or view is the same as or similar to the application name. For example, the WORKORDER table is the main object for the Work Order Tracking application.

Each application has only one main table or view associated with it. Every table or view is regarded as an object. From an object (table or view), you can access other objects (tables or views) using relationships.

Each object (table or view) is defined in the data dictionary with an associated class. The class is responsible for processing the object (table or view) and is associated with the object in the data dictionary.

For example;
Application - Work Order Tracking
Table - WORKORDER
WOSet - Class which is associated with table object
Data Dictionary - Includes definition of table object

Tivoli Process Automation Platform

The Tivoli Process Automation Platform includes extensive base capabilities.

• There is a common base storage for different databases (Oracle, SqlServer, and DB2). 
• The database data can be accessed with a common interface. Examples of application data are assets, CIs (Configuration Items), and metadata that defines the objects. 

The Tivoli Process Automation Platform is 100% J2EE compliant. 

• All the services are Web-based, and there is a common user interface that the user can configure. 
• There are also reports provided with the product, user-defined reports that can be created, a workflow engine, and the integration to external systems can be configured by the user.

One important feature of the Tivoli's process automation engine is that the user can configure the application. The data in the database, the UI screen, the reports, and the integration to external systems can all be configured.

Runtime Services

Runtime Services

These are the services that run within the MxServer. These services are Java classes and are defined in the data dictionary. (MAXSERVICE)
The name of these services are output to the console when the application starts.

Example:
[5/24/15 21:30:58:423 EEST] 0000000b SystemOut O 24 May 2015 21:30:58:423 [INFO] [] [] BMXAA6471I - Tivoli's process automation engine 7.5.0.5 Build 20130903-1504 DB Build V7505-43,
IBM Maximo Asset Management 7.5.0.5 Build 201309040937 DB Build V7503-01,
IBM Maximo Health, Safety and Environment Manager 7.5.1.0 Build 20130227-1709 DB Build V7510-01,
IBM TPAE Integration Framework 7.5.1.0 Build 20130829-1209 DB Build V7510-28 is starting.
[5/24/15 21:30:58:454 EEST] 0000000b SystemOut O 24 May 2015 21:30:58:454 [INFO] BMXAA6348I - The SECURITY service is starting.
[5/24/15 21:30:58:485 EEST] 0000000b SystemOut O 24 May 2015 21:30:58:485 [INFO] BMXAA6348I - The SIGNATURE service is starting.
[5/24/15 21:31:00:482 EEST] 0000000b SystemOut O 24 May 2015 21:31:00:482 [INFO] BMXAA6348I - The SYSTEM service is starting.
[5/24/15 21:31:00:482 EEST] 0000000b SystemOut O 24 May 2015 21:31:00:482 [INFO] BMXAA6348I - The MAXVARS service is starting.
[5/24/15 21:31:00:482 EEST] 0000000b SystemOut O 24 May 2015 21:31:00:482 [INFO] BMXAA6348I - The PERSON service is starting.
[5/24/15 21:31:00:497 EEST] 0000000b SystemOut O 24 May 2015 21:31:00:497 [INFO] BMXAA6348I - The COLLECTION service is starting.
[5/24/15 21:31:00:497 EEST] 0000000b SystemOut O 24 May 2015 21:31:00:497 [INFO] BMXAA6348I - The CITYPE service is starting.
[5/24/15 21:31:00:497 EEST] 0000000b SystemOut O 24 May 2015 21:31:00:497 [INFO] BMXAA6348I - The FEATURE service is starting.

Application services are based on Mbos
System services provide support functions for the application services, such as the database connectivity and security.

System Organization

System Organization

The system is a collection of applications.
For example, Assets, Tools, Locations, Users, Inventory, Invoices.

The applications are organized into modules by related business function.
For example, inventory-related applications, such as Tools, Item Master, and Storerooms are organized into the Inventory module.

The image on the right are some examples to modules. These modules have its particular applications that are categorized under it.

An application can belong to only one module, but you can move an application from one module to another.

Maximo Jython Tips

Jython script does not start If the selected value is same with the current value.

Maximo Architecture

MAXIMO has been designed with a J2EE component-based architecture.
The application itself is built on Internet standards, such as Java2 Enterprise Edition (J2EE), and deployed via commercially available application servers.
 J2EE defines the standard for developing multi-tier enterprise applications. It simplifies enterprise applications by basing them on standardized, modular components, by providing a complete set of services to those components, and by handling many details of application behavior automatically.

Tivoli's process automation engine applications run in a Java EE application server. At this time, it runs under IBM WebSphere or Oracle Weblogic.

Some IBM applications that run in the application servers are:

IBM Maximo Asset Management
IBM Tivoli Service Request Management

These applications use the Tivoli's process automation engine, a common set of facilities that offers a platform for developing applications.