Professional Documents
Culture Documents
MIF-Int Controls PDF
MIF-Int Controls PDF
Introduction
The Integration Framework supports the use of Integration Controls and Processing Rules
to allow customers to control and customize their integration transaction processing
through Configuration. This document explains the configuration of Integration Controls.
Table of Contents
Overview............................................................................................................................. 2
Outbound processing ...................................................................................................... 3
Inbound processing ......................................................................................................... 4
Integration Control Definition ............................................................................................ 5
Defining Integration Controls ......................................................................................... 6
Defining a Value Control............................................................................................ 8
Defining a List Control ............................................................................................... 9
Defining a Boolean Control ...................................................................................... 10
Defining a Cross Reference (XRef) Control............................................................. 11
Enabling the Use of Controls............................................................................................ 12
Associate the control to a Publish Channel or Enterprise Service................................ 12
7/29/2013
Page 1
Overview
The Maximo* Integration Framework (MIF) provides the capability to configure
integration controls and processing rules to allow customers to customize their
integration processing without (or in addition to) using custom Java User Exit code.
Some the common uses of these features is to Set an XML tag value in an integration
message or to filter integration messages such that only certain integration messages are
sent to an external application.
The example screen shots included in this document are from a Maximo 7.5.x
environment, however, the majority of the functionality is also available in the Maximo
7.1.x versions as well.
*NOTE: All capabilities provided in the Maximo application also apply the Smart Cloud
Control Desk (SCCD) application
7/29/2013
Page 2
Outbound processing
External Application / Service
End Point
Java
JMS Queue
XSL Map
User Exit
Processing Class
User Exit
Processing Rules
MAXIMO
Customization - Optional
For outbound processing, the processing rules are executed after the integration message
(XML) is formed by the MIF based on the Object Structure definition. After the
processing rules are executed, the integration message flows through the Java and XSL
customization layers (if implemented). Integration controls can be implemented as part
of processing rules or referenced by the java customization code.
7/29/2013
Page 3
Java
Integration
Servlet
User Exit
Processing Class
User Exit
XSL Map
Processing Rules
MAXIMO
Customization - Optional
For inbound processing, the processing rules are executed after the integration message
flows through the Java and XSL customization layers (if implemented). The integration
message (XML) must be in the format defined by the Object Structure when the message
reaches the Processing Rules layer. Integration controls can be implemented as part of
processing rules or referenced by the java customization code.
7/29/2013
Page 4
7/29/2013
Page 5
7/29/2013
Page 6
When you create control and assign one or more values, the values are considered the
default values for that control. As you will see further down in this document, those
default values will be copied to the external system level where they can be used and/or
changed to values specific for an external system.
7/29/2013
Page 7
Note: there is no selection capability for the Default Value field based on the domain list.
However a validation is executed when you tab out of the field to ensure the value exists
in the Domain.
7/29/2013
Page 8
Note: there is no selection capability for the Default Value field based on the domain list.
However a validation is executed when you tab out of the field to ensure the value exists
in the Domain.
7/29/2013
Page 9
7/29/2013
Page 10
Note: there is no selection capability for the Default Value field based on the domain list.
However a validation is executed when you tab out of the field to ensure the value exists
in the Domain.
7/29/2013
Page 11
7/29/2013
Page 12
In the dialog above, you can select one or more controls to associate to the selected
Publish Channel.
Controls/Default values copied to External System
When you associate a control to a Publish Channel, this will copy the control with its
default values to any External System that has that Publish Channel configured (the
publish channel does not need to be marked as enabled at the external system level). At
the external system level is where the default values can be overridden, if needed, with
values specific to that external system.
If a control is used for multiple channels (or enterprise services), it is copied down to the
external system only once. Values of the control at the external system level apply to all
channels/services that are configured to use that control (values are not channel/servicespecific).
Controls/Default values copied to External System (2)
Another way controls can be copied to an external system is when the publish channel
(with associated controls) is added to an external system (where that control was not
already associated to the external system via another channel or service).
Changing default values of Controls
For a control that is already copied (with its default values) to an external system, if the
default values are changed (adds/deletes) in the Publish Channels and/or Enterprise
Services applications, those changes are not copied down to the external system.
7/29/2013
Page 13
The values assigned to the control apply to any use of the control on all channels/services
configured for the external system.
7/29/2013
Page 14
7/29/2013
Page 15