Configuration responsibilities in Maximo® Asset Management Multitenancy
The system provider and tenants share responsibility for configuring and managing system functionality, data, security, and integration.
The system provider prepares the system to support tenant
functionality including configuring system properties, defining a
default autonumbering format, creating templates for workflows, reports,
and cron tasks. Tenants can change some of the initial configurations
and modify templates to meet their business needs. Changes that a
tenant makes apply to functionality in that tenant entity only, and
do not affect the functionality of other tenants. Learn
more about responsibilities for configuration of system functionality
Before adding any tenants, the global administrator prepares
the database, including configuring common data and template data,
creating extension tables, and defining the length of general ledger
accounts. As soon as the first tenant is added to the system, the
configurations that the global administrator can perform are restricted
to ensure that tenant changes are not overwritten. When a tenant is
added, the tenant database administrator configures a general ledger
account and can perform some database changes in the Database Information
application. Learn more about responsibilities for
configuration of data
The system provider is responsible for configuring system-level
security, including choosing the authentication method, configuring
directory services, and configuring default user IDs and privileges.
Tenants can use their own corporate directory servers or use directory
services provided by the system provider. Tenants are responsible
for managing users and security groups and for synchronizing user
information with the directory server. Learn
more about responsibilities for configuration of security and users
In a multitenancy environment, tenants can use the integration
framework to exchange data with external applications and systems.
The system provider deploys servers for storing interface tables and
file directories, and configures Java Message Service (JMS) queues
and cron tasks that tenants can use for integration. When adding a
tenant, the multitenancy manager specifies the path to an interface
table directory and to a file directory that is specific to that tenant.
The multitenancy manager provides the details of the JMS queues to
the tenant so that the tenant can specify these queues when configuring
integration components. Learn
more about responsibilities for configuration of integration