Configuring for integration

Edit online

Maximo IT is a highly configurable product and with minimal technical skills, users can add new fields, make screen changes, restrict values of attributes, and integrate with other products.

The following Maximo IT solution blocks are used to integrate Maximo IT with ManageIQ.

Note: The following solution blocks of Maximo IT support ManageIQ Integration without doing any java level code changes. After making these changes in the configuration, re-deployment of Maximo IT is not required. There is no downtime to achieve the goal.
  1. Automation Scripts

    Automation scripts are small, targeted pieces of code that can extend the product. The Automation Scripts application is used to create scripts to automate tasks based on the events, or attributes of a business object, or based on actions or custom conditions. For more details, refer to section Automating routine application tasks.

    The advantage of using an automation script is the deployment process. Unlike Java customization that can take hours to deploy for the clustered environment and makes developing and testing longer, automation scripts can be added, modified, or disabled without any downtime.

    To run the automation script, the following components must be defined:

    • A launch point
      A launch point defines the execution context for an automation script, for example when a business object is updated, or a value is entered into a field. Few types of launch points are supported, and the automation scripts application provides a separate wizard application for creating each type of launch point.
    • Variables and corresponding binding values
      You can specify the variables that determine how information is passed into or received from an automation script in the wizard applications. Variables are not mandatory, but when you use variables it simplifies the code and makes it easier to reuse the code.
    • Source code
      You can write source code in an external application and import it into the automation scripts application.
  2. Endpoint Configuration
    An endpoint and its associated handler route the outbound messages to an external system. The combination of an endpoint and handler specifies the transport protocol to use, such as HTTP or web service and provides the communication data required to reach the destination, such as a URL. For more details, refer Endpoints and handlers.
    • Create an endpoint to identify the target location and the transport mechanism that the integration framework or deployment manager uses to publish data, or to invoke a service.
    • Add a handler to an endpoint record to specify how to route outbound data to a specific endpoint location. You can also add a handler to define the data format that is used in the data transfers.
    • HTTP Handler is used by providing the metadata information for ManageIQ Integration.
  3. Service Request Catalog module

    The Service Request Catalog module contains applications that enable you to manage the Offering Catalog, view catalog requests, view offerings, and catalogs, and more. For more details, refer Service Request Catalog module.

  4. Offering Application

    You create new offerings and modify existing offerings in the Offerings application. The offerings application can be used to design your offering in the Offerings application, including: classifying offerings; defining offering attributes and conditional options; specifying the presentation type for your offering (default or custom); and defining the approval and fulfillment options for your offering. For more details, refer Offerings application.

  5. Catalogs Application

    You use the Catalogs application to create catalogs, add offerings to a catalog, remove offerings from a catalog, and manage the lifecycle of a catalog. Catalogs can contain one or more offerings, and catalogs are used by the Offering Catalog and Self Serve to allow users to search for and order offerings and services. For more details, refer Catalogs application.

  6. Domains application

    As an administrator, you use the Domains application to add domains or to modify existing ones to fit with your business practices. The Domains application contains a single table window, Domains, that you use to add, view, change, and delete domains. For more details, refer Managing domains.

    Adding a domain in the Domains application is only part of the process of adding a working domain to the system. After adding domains, additional tasks might be required, depending on the domain and how you want the system to display it. You can use the Classifications application, the Database Configuration application, or the Application Designer application to complete these tasks.

For further configuration procedures, follow below sections.