Maximo Application Suite pod details

Pods are used for IBM® Maximo® Application Suite and IBM Maximo Manage.

Maximo Application Suite core pods

ibm-mas-operator
The operator that manages Maximo Application Suite core. Watches the Maximo Application Suite CR specifications. This operator deploys the following pods:
  • ltpakeysgenerator
  • coreapi
  • internalapi
  • admindashboard
  • homepage
  • navigator
  • usersynccoordinator
  • groupsynccoordinator
  • workspacecoordinator
  • catalogmgr
  • catalogapi
  • mobileapi
  • monagentmas
ibm-truststore-mgr-controller-manager
The operator subsystem that is responsible for handling the truststore request and adding the provided truststore in the format that is consumed by the servers.
{instance_name}-accapppoints
A reporter pod that pulls data from IBM Suite License Service, converts AppPoints reports to Account Contractual Usage events and license usage reports to Account Adoption Usage events, and pushes the events to Behaviour Analytics Services (BAS) every hour.

For more information, see AppPoints and Administering licenses and AppPoints usage.

{instance_name}-admin-dashboard
The Maximo Application Suite core admin dashboard UI pod, which is the user interface for Maximo Application Suite administration for system administration work and user management.

The URL is https://admin.{masdomain}/

For more information, see Administering Maximo Application Suite.

{instance_name}-adoptionusageapi
An API pod that enables the adoption usage process by providing an API, which is started by coreapi that is used to share information about users when they login to any application.
{instance_name}-adoptionusage-reporter
A reporter pod that pulls the data that is related to adoption of different applications by users. It gathers the number of users and total AppPoints of these users who log in to each of the Maximo Application Suite applications, whenever the users log in to these applications. This application runs as a cronjob and sends this data to Data Reporter Operator (DRO). DRO in turn sends this data to IBM growth stack including Segment and Amplitude where different IBM roles like Product management or Operations can understand adoption patterns of different Maximo Application Suite applications by using relevant dashboards.
Note: Starting in IBM Maximo Application Suite 9.0, 8.11.7, and 8.10.10, the User Data Services (UDS) is deprecated and replaced with IBM Data Reporter Operator (DRO).

For more information, see Data Reporter Operator.

{instance_name}-catalogapi
A pod that provides read access to the catalog inventory.

For more information, see Deploying applications, add-ons and industry solutions.

{instance_name}-catalogmgr
A pod that provides the inventory management and AppPoint reservation APIs.
{instance_name}-coreapi
The Maximo Application Suite CoreAPI pod that provides an HTTPS API to support working with Kubernetes resources. Primarily acts as a proxy to the Kubernetes APIs and MongoDB integration.
{instance_name}-coreidp
A Liberty-based server that handles the authentication, access management, and user privileges authorization that is managed by Maximo Application Suite. This pod integrates with internal application by using the OpenID Connect (OIDC) flow and SAML.

For more information, see Authentication methods.

{instance_name}-coreidp-login
The coreidp login pods that host the login page and superuser login logic for Maximo Application Suite. Not meant to be a Maximo Application Suite endpoint but used as part of the redirect during the Maximo Application Suite authentication flow.

The URL is https://auth.{masdomain}/login/

{instance_name}-entitymgr-addons
Add-ons configuration.

For more information, see Deploying add-ons.

{instance_name}-entitymgr-bascfg
The entity manager that is used to manage DRO integration with Maximo Application Suite. This pod generates internal certificates, performs configuration verification, and deploys all Data Reporter Operator related pods. This pod watches the BASCfg CR. This operator deploys the following pods:
  • milestonesapi
  • adoptionusageapi
  • adoptionusagereporter
  • accapppoints
  • adoptionusagemetering

For more information, see Behavior Analytics Services.

{instance_name}-entitymgr-coreidp
The entity manager that is used to manage Coreidp integration with Maximo Application Suite. Generates internal certificates, performs validations, and deploys coreidp-login and coreidp pods. This pod watches the Coreidp CR. This operator deploys the oidcclientregcoreidpcoreidplogin pod
{instance_name}-entitymgr-idpcfg
The entity manager that is used to manage identity provider (IDP) integration with Maximo Application Suite. Generates internal certificates and performs configuration and verification. This pod watches SAML and LDAP configuration through the IDPCfg CR. This operator deploys the oidcclientregcoreidpcoreidplogin pod.
{instance_name}-entitymgr-jdbccfg
The entity manager that is used to manage JDBC integration with Maximo Application Suite and perform configuration validation. This EntityMgr watches the JDBCCfg CR.

For more information, see Updates to JDBC configuration and other data resources are not applied in the Maximo Manage application.

{instance_name}-entitymgr-kafkacfg
The entity manager that is used to manage Kafka integration with Maximo Application Suite and perform configuration validation. This EntityMgr watches the KafkaCfg CR.

For more information, see Apache Kafka.

{instance_name}-entitymgr-mongocfg
The entity manager that is used to manage Mongo integration with Maximo Application Suite and perform configuration validation. This EntityMgr watches the MongoCfg CR.

For more information, see MongoDB.

{instance_name}-entitymgr-objectstorage
The entity manager that is used to manage ObjectStorage integration with Maximo Application Suite and perform configuration validation. This EntityMgr watches the ObjectStorageCfg CR.
{instance_name}-entitymgr-pushnotificationcfg
The entity manager that is used to manage PushNotification integration with Maximo Application Suite and perform configuration validation. This EntityMgr watches the PushNotificationCfg CR. This operator deploys the pushnotificationservice pod.

For more information, see Push notifications.

{instance_name}-entitymgr-scimcfg
The entity manager that is used to manage the System for Cross-domain Identity Management (SCIM) integration with Maximo Application Suite and perform configuration validation and resources creation, such as scimsync-agent job and scimsync liberty pod. This EntityMgr watches the SCIMCfg CR. This operator deploys the scimsyncagentscimsync pod.
{instance_name}-entitymgr-slscfg
The entity manager that is used to manage IBM Suite License Service (SLS) integration with Maximo Application Suite and perform configuration validation and resources creation, such as licensing-mediator pod. This pod is also responsible for registering the SLS client in the SLS server. This pod watches the SLSCfg CR. This operator deploys the licensing mediator pod.

For more information, see IBM Suite License Service.

{instance_name}-entitymgr-smtpcfg
The entity manager that is used to manage SMTP integration with Maximo Application Suite and perform configuration validation. This pod watches the SMTPCfg CR.

For more information, see Simple Mail Transfer Protocol configuration.

{instance_name}-entitymgr-watsonstudiocfg
The entity manager that is used to manage IBM Watson® Studio integration with Maximo Application Suite and perform configuration validation. This pod watches the WatsonStudio CR.

For more information, see IBM Watson Studio.

{instance_name}-entitymgr-ws
The entity manager that is used to manage workspace creation in Maximo Application Suite. This EntityMgr watches the Workspace CR.
{instance_name}-groupsync-coordinator
The group sync manager pod that coordinates the group sync activities between Maximo Application Suite and applications.
{instance_name}-homepage
The pod for the Maximo Application Suite core homepage UI. The main page when you are not running in a workspace-based endpoint.

The URL is https://home.{masdomain}/

{instance_name}-internalapi
The internal API pod that provides the internal version of the Maximo Application Suite Administrative API, for example, user management. Used only by internal components for application-to-application communication.
{instance_name}-licensing-mediator
Proxy server for that SLS service. Acts as an integration point between Maximo Application Suite and SLS.
{instance_name}-milestonesapi
The milestones API pod that is responsible for reporting critical user events, which are known as milestones, to Data Reporter Operator.
{instance_name}-mobileapi
The mobile API pods that provide the mobile application package API and serve the navigator application package. Integrates with coreapi.
{instance_name}-monagent-mas
A pod that is responsible for monitoring the health of general components in Maximo Application Suite and reporting to the Suite CR.
{instance_name}-navigator
A workspace-based UI that acts as a home page where users can access any application.
{instance_name}-usersync-coordinator
The user sync manager pod that coordinates the user sync activities between Maximo Application Suite and Applications.

For more information, see Administering users and user access.

workspace-coordinator ({instance_name}-workspace-coordinator)
The workspace sync manager pod that coordinates the workspace sync activities between Maximo Application Suite and applications.

Maximo Manage pods

ibm-mas-manage-operator
The overall main operator that is responsible for creating the following suboperators and the artifacts that are in the Manage application level.
  • Workspace operator (entitymgr-ws)
  • Application status operator (entitymgr-appstatus)
  • BDI operator (entitymgr-bdi)
  • User sync agent (usersyncagent)
  • Group sync agent (groupsyncagent)
Uses the ManageApp CR.
ibm-truststore-mgr-controller-manager
The truststore manager that creates and updates various truststores that are consumed by Manage servers. Truststore manager is created when the Manage operator is installed.
admin-build-config (admin-build-config-#-build)
The Red Hat® OpenShift®BuildConfig that generates the image for the manage-maxinst pod. Can have the following statuses:
  • Completed if the image is successfully built.
  • Error if a problem occurred during the build process.
It is created by the ManageWorkspace operator during the reconciling of the ManageWorkspace.
Note: If any issues occur when the image is pulled, the log includes the details of downloading base images/customzation archive.
ui/cron/mea/report-build-config-#-build
The job pod Red Hat OpenShift BuildConfig that generates the build liberty server images for the ii, cron, mea,and report server bundles. Can have the following statuses:
  • Completed if the image is successfully built.
  • Error if a problem occurred during the build process.
ManageWorkspace operator during reconciling of the ManageWorkspace.
Note: Usually the issue is captured by the admin-build-config pod unless it is a network issue.
{instance_name}-entitymgr-appstatus
The operator that tracks the status conditions for all the custom resources (CRs) that are managed by the WorkSpace operator. including the following CRs:
  • ManageWorkspace
  • ManageBuild
  • ManageDeployment
  • ManageServerBundle
{instance_name}-entitymgr-bdi
The operator that is responsible for deploying the necessary Kubernetes resources to run the build data interpreter (BDI) application, for example, Deployment, Service, NetworkPolicy, and Configmaps. Uses the BuildDataInterpreter CR that is created by the Manage workspace operator. The BDI is installed when Maximo Aviation or Maximo Asset Configuration Manager is installed as a component of Maximo Manage. A separate pod that runs independently of other Manage pods. Validates and reports configuration status of configuration-managed assets in Manage.
{instance_name}-entitymgr-ws
The operator that is responsible for creating, managing, upgrading, and deleting the Manage system in the workspace.
  • Maximo Manage Database maxinst/updateDB
  • The deployment of the server bundles MXServer running inside a Liberty container.
  • Creates the Maximo Manage Build CR that builds the Admin Image Maxinst/Updatedb and the Websphere Liberty Profile images ServerBundle.
{instance_name}-groupsyncagent
Synchronize the user group into Maximo Manage from Maximo Application Suite. The valid Manage user will be added to the group by using the Maximo integration framework. The Maximo Enterprise Adapter or all server bundle is required for group sync tasks.

For more information, see Security and user management.

{instance_name}-{workspace_name}-all/cron/report/mea/ui
Specifications that describe a Manage server bundle. Represents a set of Manage Liberty servers that load balance for a type of work load. The all server bundles is the Manage server bundle, which includes the following types:
cron
Components that are required for cron tasks.
mea
The enterprise web services API.
Note: This server bundle type is required for user/group synchronization unless the administrator selects the all server bundle for the Manage deployment.
report
Components for reports.
ui
The user interface components.

For more information, see Server bundle overview.

{instance_name}-{workspace_name}-manage-maxinst
The Manage admin server, which is used for administrative tasks such as running the maxinst/updated B and installing languages. Contains the full SMP folder, which provides access to all binary files, dbc files, and admin tools utilities.

For more information, see Administrative tasks for Maximo Application Suite.

{instance_name}-{workspace_name}-jmsserver-0
The Manage server bundle for stand-alone JMS components. For more information, see Configuring a JMS server for Maximo Manage.

Only one JMS server is allowed. For more information, see Scaling JMS servers

{instance_name}-monitoragent
The Manage Monitoring agent that collects statistics about application usage and performance. Administrators can configure Prometheus service monitoring and then use visualization software, such as Grafana, to view the usage information that the agent collects.

For more information, see Monitoring agent for Maximo Manage.

{instance_name}-usersyncagent
Synchronizes users from the Maximo Application Suite user registry to the user registry in Maximo Manage. Any action, such as create, update, or delete, for a Maximo Application Suite user who has access to Maximo Manage will be synchronized into Maximo Manage through the Maximo integration framework. The Maximo Enterprise Adapter or all server bundle is required to perform the user sync tasks.

For more information, see User synchronization