IBM Maximo Manage v8 Admin cheat sheet

Security model layers: Users belong to Groups; Groups are granted permissions through Security Groups; Application and Object authorizations are separate records that both must allow an action.

Authorization precedence: a DENY on a more specific record (user-level) overrides an ALLOW inherited from a group; the most specific applicable authorization wins.

Application Designer controls presentation (tabs, fields, lookups); Database Configuration controls persistence (attributes, relationships, indexes); changing an attribute type requires an admin-mode restart and configdb run.

A Maximo Manage v8 environment runs on WebSphere Liberty (or traditional WAS) with the UI in the browser, business logic in the JVM, and the database (Db2, Oracle, or SQL Server) as the system of record.

Workflow design uses nodes (Start, Stop, Task, Condition, Manual Input, Subprocess) and connectors; a workflow must have exactly one Start node per process revision and be activated to run.

Escalations run scheduled actions (Java class, expression, or workflow) on a cron-like schedule; Cron Task Setup defines the schedule and instance parameters.

The Maximo Integration Framework (MIF) uses Publish Channels (outbound), Enterprise Services (inbound), and External Systems; the JMS queue and the cron task 'MIF Dispatcher' process messages asynchronously.

Domains in Maximo (e.g., ITEM, ASSET, LOCATION) are value-list lookups maintained in Domains application; ALN domains are validated against a Maximo value list, while SYNONYMDOMAIN uses a synonym list.

Logging and diagnostics: log4j properties control per-logger levels; 'Logging' application shows live loggers, and the System Properties application holds maximo.properties-equivalent settings such as mxe.adminmode.

Authentication options in v8 include native Maximo user registry, LDAP/Active Directory via VMM, SAML 2.0 single sign-on, and OpenID Connect; the user registry type is set in WebSphere Liberty configuration.

A user's default insert site (DEFSITE) determines which site's records default on creation; users without a default insert site see all sites they are authorized for.

Security Groups carry application authorizations, object authorizations, and data restrictions (site/org, GL account, labor, storeroom, etc.); a user inherits the union of group permissions minus explicit denies.

Password policy, session timeout, and lockout are set in the Users application and System Properties (mxe.user.password.*, mxe.webclient.sessiontimeout), not in the database schema.

Cron Task Setup instances can be started/stopped individually; deleting an instance stops it, and a 'Run Now' triggers one execution without changing the schedule.

The System Properties application (or maximo.properties file) is the authoritative place for tuning values; changes via the application may require a server restart depending on the property's 'Live Refresh' flag.

Database Configuration in admin mode locks the database from other users; you must apply configuration changes (configdb) and restart the JVM before the new schema is usable.

Communication Templates and the Notifications app govern outbound email; SMTP settings live in the System Properties (mail.smtp.*) and the 'Email Listener' cron task polls the inbox.

Migration Manager packages configuration objects (applications, domains, workflows) into packages for transport between environments; it does not move transactional data.

The Maximo Asset Management data model is object-centric: each application edits one or more business objects (e.g., ASSET, WORKORDER) whose attributes map to database columns.

Relationships define parent-child joins between objects (e.g., WORKORDER to ASSET via ASSETNUM); they drive lookups, child tables, and MIF processing.

A work order's status flows through WAPPR (waiting approval), APPR (approved), INPRG (in progress), COMP (complete), and CLOSE; status changes are governed by the Workflow or by the 'Change Status' action with domain validation.

Preventive Maintenance (PM) records generate work orders via the PM cron task; the PM's frequency, next due date, and 'Generate Work Orders' flag control scheduling.

The Job Plan library holds reusable task lists; applying a job plan to a work order copies tasks and can be re-applied only if not already present.

Inventory balances are held per storeroom/item; issues reduce the balance, receipts increase it, and reorder points trigger replenishment through the Inventory cron task.

The 'Maximo Manage' industry solution adds industry-specific objects (e.g., linear assets, fleet, or service management) on top of core Maximo Asset Management; administration still uses the same security, workflow, and configuration tools.

Report administration uses BIRT reports deployed to the Maximo server; report parameters and security are managed in the Report Administration application.

Bulk data operations: the 'Duplicate Record' and 'Select Records' actions plus the 'Run Action' automation script allow batch updates; large updates should be scheduled outside peak hours.

Automation Scripts run in JavaScript, Python (Jython), or Groovy on the server; they can be bound to an object's launch point (before save, after save, init, etc.) or invoked from an escalation or workflow.

Launch points define when a script fires: Object Launch Point (event-driven), Attribute Launch Point (field change), and Integration/Workflow launch points.

The Maximo Manage v8 UI is built on the Application Builder/Application Designer; you can add fields, change labels, set required flags, and configure lookups without code.

Conditional expressions in Application Designer (e.g., to hide a field) use the same expression language as workflow conditions and are evaluated server-side.

The 'Maximo Manage' v8 supports the 'Manage' role-based navigation; the Navigation menu and Start Center are configured per user/group via the 'Start Center' and 'Navigation' applications.

MIF error handling: failed messages go to the error queue (or 'Message Reprocessing' application); administrators can replay or delete failed messages after correcting the cause.

The 'Manage' v8 upgrade path requires running the updatedb utility and configdb after applying fix packs; always back up the database and the Maximo directory before upgrading.

Performance tuning levers: JVM heap size (set in the WebSphere Liberty jvm.options or server.xml), database indexes on frequently queried attributes, and cron task scheduling to avoid overlap.

Auditing is enabled per object/attribute in the 'Audit Setup' application; audit records are written to the MAXAUDIT table and viewed via the 'Audit' application or reports.