Configuring for integration
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 solution blocks are used to integrate Maximo IT with JIRA.
-
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 section Automating routine application tasks.
The advantage of using automation script is the deployment process. Unlike Java customization that can take hours to deploy for 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 pointA 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 point are supported, and the automation scripts application provides a separate wizard application for creating each type of launch point.
- Variables and corresponding binding valuesYou 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 codeYou can write source code in an external application and import it into the automation scripts application.
-
Endpoint ConfigurationAn endpoint and its associated handler routes 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 JIRA Integration.
-
Application Designer
The application designer tool helps the user to create the XML for each application, without using the XML.
Applications in Maximo IT are stored as an XML document in the database. This XML is then rendered by the Maximo to show the different applications that are available. A palette with all the available elements is available and you can add the elements to the application by dragging and dropping to the desired place. Apart from the application itself, you can also edit the dialogues related to the application, signature options, toolbar, and select action menu.
The Control Palette in the designer has the all list of elements that can be added to any application. The application will be split in sections, and in the sections you can add tables, text boxes, buttons, images, hyperlinks, and other elements. After adding the elements, you must change the properties of each element as necessary.
-
Database configuration
Use the database configuration application to create or change objects and attributes, and customize the database. An object is a self-contained software entity that consists of both data and functions to manipulate data. Most applications are associated with one main object and other related objects. For more details, refer Database Configuration application.
When you use the database configuration application, interact at the business object level. Internally, the application determines the actions to take on the database tables to support the needs of the business objects.
You can add MBOs and the attributes to the existing MBOs. Attributes can be non-persistent, even if the parent MBO is itself persistent. In the Attribute section, set the type of the attribute, default value, class, domain, and more features as necessary.
Although domain is a separate application, it is used with attributes. Setting domains to attributes will help to show and validate the attribute data against a specific set of data. From the database configuration, you can also set default values to the attributes, set auto-numbering, and set if an attribute is required or not.
-
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.