Assetize

Free tools / Maximo developer reference

JavaDocs, with a path to Jython.

Browse a Manage release, compare its API, or learn the classes behind your automation scripts.

Browse Manage 9.2

12,052 classes, 63,524 declared methods and constructors, 11,431 fields. The interactive reference supports Manage image snapshots from 8.5 to 9.3; 9.3 is pre-GA. Classic 7.6.x is outside this corpus.

Your Jython toolbox

  • psdi.mbo.Mbo — One business record: read and update attributes, follow relationships and participate in its transaction. Use the provided record.
  • psdi.mbo.MboRemote — The public business-record interface used by automation scripts and returned by record lookups. Use the provided record.
  • psdi.mbo.MboSet — A collection of records, including query state, traversal and transaction operations. Obtain from a relationship or server.
  • psdi.mbo.MboSetRemote — The collection interface used when a relationship or server lookup returns a set. Obtain from a relationship or server.
  • psdi.mbo.MboValue — The value and state of one attribute on a record, including its modification and read-only state. Obtain from a record.
  • psdi.mbo.MboValueAdapter — Base adapter for Java field behaviour such as validation, actions and lookup lists. Framework extension point.
  • psdi.mbo.SqlFormat — Formats Maximo SQL conditions with typed substitutions using object and attribute metadata. Import and construct a utility.
  • psdi.mbo.MboConstants — Named flags for record and field operations, including read-only state and validation behaviour. Import constants.
  • psdi.server.MXServer — The running Manage server and entry point for server services, dates and independent MBO sets. Import and get the running instance.
  • psdi.security.UserInfo — The user context attached to record operations: identity, language and interactive-session state. Obtain the current user context.
  • psdi.mbo.StatefulMbo — A business record that supports managed status transitions. Use a status-capable record.
  • psdi.app.workorder.WO — The WORKORDER business implementation, including work-order rules and status behaviour. Use a WORKORDER launch point.
  • psdi.util.MXApplicationException — A Maximo application error identified by message group and message key. Prefer the script service.
  • psdi.util.logging.MXLoggerFactory — Obtains a Maximo logger by its configured logger name. Import a static factory.
  • psdi.util.logging.MXLogger — Writes messages through the configured Maximo logging system. Obtain from MXLoggerFactory.

From a Java class to a Jython script

  1. 1. Start with the record

    Choose an object or attribute launch point. Maximo supplies mbo; your script works on that existing record.

  2. 2. Read Java signatures as Jython

    An instance method is called on a record or utility. A static method is called on its class. String maps naturally to text; use the listed parameter count and types to choose an overload.

  3. 3. Navigate related data

    A relationship returns a set; a set returns records. Follow the returned type to discover what you can call next.

  4. 4. Own your query lifecycle

    Open a separate set only when needed. Format the query, pass the user context and finish with cleanup and close.

  5. 5. Use the right field event

    Choose Validate for a rule and Action for dependent field changes. Select field flags deliberately.

  6. 6. Understand the user

    Keep the login identity, PERSON identifier and interactive state distinct.

  7. 7. Respect business operations

    Use the status transition method when changing status and let the object enforce its rules.

  8. 8. Verify the target release

    Compare the class and exact overload across your source and target releases. Use the test harness, then exercise the launch point in a Manage test environment.

Understand the connections

Class pages show configuration registrations, parameter and return-type references, and calls made by Assetize's sample scripts. Signatures do not contain IBM internal caller or downstream call graphs.

Explanations and examples are authored by Assetize. API presence comes from compiled image snapshots; registrations come from 9.0–9.2 metadata. Examples require their stated launch point and a test environment.