C1000-141 System Configuration

System Configuration Detailed Explanation

1. Server Configuration and Optimization

Maximo typically runs on application servers, like IBM WebSphere or Oracle WebLogic. These application servers handle the business logic, processing, and requests for the Maximo application. Here’s how to set up and optimize these servers:

• Java Virtual Machine (JVM) Configuration: The JVM is where the Maximo application runs on the server. Configuring the JVM is essential for performance. Important settings include:
  • Heap Memory: This is the memory the JVM uses to run Maximo. The heap memory should be large enough to handle Maximo’s workload but not so large that it overuses system resources. Typically, administrators set initial and maximum heap sizes to help prevent frequent adjustments that can slow down the system.
  • Thread Pool Sizes: Thread pools allow Maximo to handle multiple requests at once. Adjusting thread pool sizes ensures that the server can handle many users without overwhelming it. It’s essential to balance the thread pool size to match the workload without overloading the server’s CPU.
  • Garbage Collection: JVM automatically clears unused memory through “garbage collection.” By configuring garbage collection settings, you can reduce pauses when the JVM clears memory, especially under heavy loads. Use tools to monitor garbage collection performance and adjust as needed.

Proper server configuration and optimization ensure that Maximo remains responsive, even under high demand.

2. Database Configuration

Maximo’s performance relies heavily on efficient database management, as it stores all the essential data. Maximo supports several databases, like DB2, Oracle, and SQL Server, and configuring the database for optimal performance is critical.

• Table Partitioning: Large tables can slow down database performance. By dividing large tables into smaller, more manageable partitions, Maximo can process queries faster. For example, partitioning data by date or region can improve performance when accessing specific records.

• Index Configuration: Indexes help the database locate specific records quickly. Like a book’s index, a database index reduces search time. Configuring indexes for frequently accessed columns, like asset IDs or work order numbers, can significantly reduce query time. However, too many indexes can slow down updates, so use them strategically.

• Database Connection Pooling: Each time Maximo accesses the database, it opens a “connection.” A connection pool is a pre-allocated group of database connections, ready to be used when needed. By setting up a connection pool, Maximo can quickly reuse connections, reducing the time spent opening and closing connections. Adjust the pool size based on expected user activity to avoid database overload.

With these configurations, the database can handle Maximo’s data demands more efficiently, improving response times.

3. Maximo System Parameters

Maximo offers a range of system parameters that allow administrators to customize various system behaviors. Here’s how parameters can be used to tailor Maximo to specific needs:

• Work Order Numbering Rules: Maximo generates unique identifiers for work orders automatically. System parameters let you adjust the numbering pattern, so it aligns with organizational standards. For instance, you might want work orders to start with a prefix or follow a specific numeric sequence.

• Time Zone Settings: If your organization operates in multiple time zones, you’ll want to set the correct time zones for each site. Maximo allows time zone customization, ensuring that timestamps on work orders, logs, and other records accurately reflect local time.

• Default Currencies and Units: System parameters let you set the default currency and measurement units, like USD for currency or inches for length. This is particularly useful if Maximo is used across different regions, as you can ensure data consistency in reports and transactions.

By configuring system parameters, you can adjust Maximo’s core functions to match your organization’s operational requirements.

4. Service Configuration and Scheduled Tasks

Maximo includes several built-in services and scheduling capabilities to automate tasks and processes, keeping operations running smoothly.

• Built-In Services: Maximo has services such as report generation, notification services, and data import/export. Configuring these services allows Maximo to perform automated tasks, like generating a report every morning or sending notifications when certain conditions are met (like a work order approval).

• Scheduled Tasks: Scheduled tasks help you automate routine maintenance activities. You can set schedules for:

  • Data Import/Export: Automate data transfers to and from Maximo, such as updating inventory levels or importing equipment data from an external system.
  • Report Generation: Schedule regular reports, like daily work order summaries or monthly asset usage reports, so managers receive up-to-date information automatically.
  • Service Restarts: Sometimes, services may need to restart to ensure they function correctly, especially after configuration changes. Scheduling regular service restarts can help prevent issues without disrupting regular operations.

Automating tasks with scheduled services saves time, reduces errors, and keeps Maximo running smoothly without constant manual intervention.

5. Multi-language Support

If your organization operates in different regions or serves a multi-lingual user base, Maximo’s multi-language support can help provide localized experiences for users.

• Language Packs: Maximo supports various languages through language packs, which translate the user interface and system messages. For example, if you operate in both English and Spanish regions, you can install the Spanish language pack, so users in Spanish-speaking regions can view Maximo in their preferred language.

• Installing Language Packs: To enable multi-language support, you need to install the required language packs during Maximo’s configuration. After installation, users can switch languages based on their preferences.

• Managing Regional Settings: Besides language, multi-language support also includes regional settings like date formats and currency symbols. These settings ensure users see information in a format that makes sense for their region.

Multi-language support is essential for organizations operating globally or across regions with different languages, helping users interact with Maximo comfortably in their language.

6. Custom Fields and Object Structure

Every organization has unique data requirements. Maximo lets you customize fields and database structures to match specific business needs, ensuring that all necessary information is captured and accessible.

• Adding Custom Fields: Sometimes, you’ll need fields not included in Maximo’s default setup, like a unique ID for tracking assets or a field for specific work order details. Maximo allows you to add custom fields to data tables to capture this additional information. For instance, you might add a “Warranty Expiry Date” field for assets or a “Priority Level” field for work orders.

• Customizing Object Structures: Maximo’s data is organized into objects (like assets, work orders, or locations). Customizing these objects allows you to expand data categories and integrate additional data. For example, you might create a custom object for tracking contract information if it’s essential to your maintenance operations.

• Maintaining System Performance: When adding custom fields and objects, ensure that these additions don’t slow down Maximo. Too many custom fields can impact performance, especially if they involve large datasets. Carefully plan customizations to balance functionality with efficiency.

• Compatibility with Upgrades: Custom fields and structures should be created in a way that doesn’t interfere with future system upgrades. Maximo updates could overwrite certain custom configurations, so it’s crucial to document customizations and verify compatibility after each upgrade.

Custom fields and structures allow Maximo to better align with your organization’s specific data requirements, enabling more precise tracking, reporting, and decision-making.

Summary

System configuration in Maximo involves setting up and customizing various elements to optimize performance, tailor functions, and meet specific business needs. Here’s a recap:

1. Server Configuration and Optimization: Set up and optimize the application server (JVM) to handle Maximo efficiently.
2. Database Configuration: Configure the database for quick data retrieval with table partitioning, indexes, and connection pooling.
3. Maximo System Parameters: Adjust system parameters for personalized workflows, time zones, and numbering conventions.
4. Service Configuration and Scheduled Tasks: Automate tasks and services, like data imports and notifications, for seamless operation.
5. Multi-language Support: Enable multi-language support with language packs and region-specific settings.
6. Custom Fields and Object Structure: Add fields and customize objects to capture unique data while ensuring compatibility and system performance.

These configurations let you make Maximo a more effective, efficient tool that matches your organization’s exact needs.

System Configuration (Additional Content)

1. Maximo System Properties Management

System Properties in Maximo allow administrators to tune global settings, optimize system performance, and control application behavior.

1.1 Overview of System Properties

• Found under System Configuration → Platform Configuration → System Properties.
• Changes take effect immediately or after a system restart.

1.2 Key System Properties for Performance Optimization

• Database Query Optimization:
  • mxe.db.fetchResultLogLimit → Limits the number of records a query returns to prevent system overload.
    • Example: Set to 5000 to prevent large queries from impacting performance.
• BIRT Report Security:
  • mxe.report.birt.disableReportSecurity → Controls whether users need authentication to view reports.
    • Setting to 1 disables security checks for better performance but may expose sensitive reports.
• Background Jobs Execution Frequency:
  • mxe.crontask.history.cleanupdays → Controls how long historical cron task logs are kept.
  • Example: Set to 30 days to avoid excessive database growth.
• Concurrent Users Limit:
  • mxe.maxconcurrentlogins → Defines maximum concurrent user sessions.
    • Example: Set to 100 to prevent system overload during peak hours.

1.3 Modifying System Properties

1. Go to System Configuration → Platform Configuration → System Properties.
2. Find the property you want to update.
3. Change the value and click “Save”.
4. Apply Changes: Click Live Refresh or restart the system if required.

2. Maximo Business Objects (MBO) Management

Maximo uses Maximo Business Objects (MBOs) as its data modeling framework, handling all data retrieval, updates, and processing.

2.1 Understanding MBOs

• MBOs Represent Business Entities
  • Example:
    • WORKORDER → Represents Work Orders.
    • ASSET → Represents Assets.
• MBO Operations:
  • add() → Creates a new record.
  • save() → Saves changes to the database.
  • delete() → Deletes a record.

2.2 MBO Performance Optimization

• Lazy Loading:

  • Prevents unnecessary data fetching.

  • Example: Load only work orders in OPEN status:

    workorder.status = 'OPEN'
    

• MBO Relationships (Avoiding N+1 Query Issues):

  • Optimizing joins between tables to prevent excessive queries.
  • Example: Prefetch asset details in a single query instead of multiple individual queries.

2.3 Creating a Custom MBO

• Use Database Configuration:
  • Define a new MBO (e.g., CUSTOM_ASSET).
  • Establish relationships with existing MBOs (e.g., linking to ASSET).
  • Use Application Designer to create UI elements for the new MBO.

3. Electronic Signature (eSignature) & Audit Logs

Maximo allows eSignatures and audit logs to enforce data integrity and compliance.

3.1 Configuring eSignature (Electronic Signature)

• Used for critical actions, such as approving purchase orders or changing asset status.
• How to Enable eSignature:
  1. Go to System Configuration → Platform Configuration → eSignature Options.
  2. Select the action that requires a signature.
  3. Enable “Require Electronic Signature”.

3.2 Audit Logs (Tracking Changes)

• Tracks who changed what and when.
• Example: Track work order status changes.
  1. Go to System Configuration → Platform Configuration → eAudit Enabled Objects.
  2. Enable audit for WORKORDER.STATUS.
  3. View logs in Application Logs.

3.3 Compliance & Security

• SOX (Sarbanes-Oxley), HIPAA, GDPR Compliance.
• Audit logs ensure non-repudiation and accountability.

4. Migration Manager (Environment Management)

The Migration Manager allows administrators to transfer configurations between different Maximo environments.

4.1 Why Use Migration Manager?

• Ensures consistent configurations across environments.
• Reduces manual configuration errors when migrating from TEST → PROD.

4.2 Key Features

• Migrates:
  • Object Structures
  • Custom Fields
  • Security Groups
  • Automation Scripts

4.3 Migration Process

1. In the source environment:

• Create a Migration Package (System Configuration → Migration Manager).
• Select objects (MBOs, workflows, scripts).
• Export the package.

2. In the target environment:

• Import the package.
• Apply changes and validate functionality.

5. API Security for REST & SOAP Web Services

APIs allow external systems to interact with Maximo, requiring proper security controls.

5.1 API Authentication Methods

• OAuth 2.0:

  • Requires a valid access token for API calls.

  • Example: Retrieving a token:

    curl -X POST -d "grant_type=password&username=maximo&password=pass" https://maximo.example.com/oauth/token
    

• API Key Authentication:

  • Used for internal applications that require access to Maximo’s APIs.
  • Configure API Keys in Integration → API Security.

5.2 Enforcing Access Control

• CORS Rules (Cross-Origin Resource Sharing)

  • Restricts which external websites can call Maximo APIs.

  • Example: Allow only trusted domains:

    Access-Control-Allow-Origin: https://trusted-company.com
    

• Restrict API Data Access (Object Structures)

  • Example: Allow only active work orders to be accessed:

    workorder.status = 'ACTIVE'
    

5.3 API Logging & Auditing

• Enable API logging to track unauthorized access attempts.
  • Found under: System Configuration → Logging.
  • Set Integration Logs to DEBUG for troubleshooting API security issues.

Summary

To fully configure Maximo for performance, security, and manageability, administrators must understand:

1. System Properties Management

• Optimize database queries, background tasks, and concurrent users.
• Adjust properties such as:
  • mxe.db.fetchResultLogLimit
  • mxe.maxconcurrentlogins
  • mxe.report.birt.disableReportSecurity

2. Maximo Business Objects (MBO) Management

• Configure Lazy Loading and MBO Relationships to improve performance.
• Create custom MBOs using Database Configuration.

3. Electronic Signature & Audit Logs

• Use eSignatures for secure approvals.
• Enable audit logs to track changes and meet compliance requirements.

4. Migration Manager (Configuration Deployment)

• Use Migration Packages to transfer configurations across environments.
• Ensure consistency between TEST and PROD.

5. API Security (REST & SOAP)

• Implement OAuth 2.0 and API Keys for authentication.
• Enforce CORS rules to restrict API access.
• Enable API logging to track security events.