Maximo Calibration records do not migrate when upgrading to version 7.5

Resolving The Problem

When upgrading Maximo Calibration to 7.5, specific steps are required to manually migrate Calibration information. The following data must be first be exported from the existing deployment.

- Saved Calibration queries and default queries.
- Calibration security groups
- Calibration customized applications
- Calibration bookmarks

The data is then imported back into the deployment after the upgrade is complete.

This information applies only to Maximo Calibration data migration after a successful upgrade to Maximo Asset Management 7.5. No other industry solutions require these migration steps.

EXPORTING

Before you begin ensure you have the Maximo Integration Framework configured.

Exporting IBM Maximo Calibration bookmarks

IBM® Maximo® Calibration bookmarks are not preserved when upgrading to
version 7.5. Use the IBM Maximo Enterprise Adapter to export custom bookmarks
and re-import them to applications.

Before you begin ensure you have the Maximo Integration Framework configured.

1. Log in to Maximo Asset Management.
2. Create object structure.
a. From the Start Center, select Go To > Integration > Object Structures.
b. Insert a new record using the following details:
Object Structure
MXQUERY
Description
Query table definition
Consumed By
INTEGRATION
c. From Source Objects for MXQUERY, click New Row, and specify QUERY for
the Object field, and then save the record.
d. Optional: Select Action > Exclude / Include Fields and choose the
persistent and non-persistent fields to be included or excluded from this
object.
3. Create publish channels.
a. From the Start Center, select Go To > Integration > Publish Channels.
b. Insert a new record using the following details:
Publish Channel
MXQUERYInterface
Description
QUERY
Object Structure
MXQUERY
c. Save the record.
d. Select Action > Enable Event Listener .
4. Create enterprise services (for inbound).
a. From the Start Center, select Go To > Integration > Enterprise Services.
b. Insert a new record using the following details:
Enterprise Service
MXQUERYInterface
Description
QUERY
Object Structure
MXQUERY
c. Save the record.
5. Create external systems.
a. From the Start Center, select Go To > Integration > External Systems.
b. Filter results by the default external system value, EXTSYS1.
c. Change the property value for PRETTYPRINT to 1.
d. From the Publish Channels tab, click New Row, select the
MXQUERYInterface publish channel, and then select Enabled.
e. From the Enterprise Services tab, click New Row, select the
MXQUERYInterface enterprise service, and then select Enabled.
f. Save the record.
6. Export data by PLUSC tables.
a. From the Start Center, select Go To > Integration > External Systems.
b. Filter results by the default external system value, EXTSYS1.
c. Select the Publish Channels tab, filter channels by MXQUERYInterface, and
then click Data Export.
d. In the Export Condition field, add where app = ’PLUSCASSET’. An XML file
with all records is generated in the folder defined for IBM Maximo
Enterprise Adapter. You can rename the XML file to make it easier to
identify when re-importing the file after the upgrade is complete.
e. Repeat the export process for the following applications:
PLUSCJP
PLUSCLOC
PLUSCPM
PLUSCTLINV
PLUSCTOOL
PLUSCWT
PLUSDSPLAN

Exporting IBM Maximo Calibration application definitions for groups

Maximo Asset Management groups lose permission to IBM Maximo Calibration
applications when upgrading to version 7.5. Use the IBM Maximo Enterprise
Adapter to export authentication data, modify it, and then re-import the data back
into Maximo Asset Management.

1. Log in to Maximo Asset Management.
2. Create object structure.
a. From the Start Center, select Go To > Integration > Object Structures.
b. Insert a new record using the following details:
Object Structure
MXAPPLICATIONAUTH
Description
Applicationauth table definition
Consumed By
INTEGRATION
c. From Source Objects for MXAPPLICATIONAUTH, click New Row, and
specify APPLICATIONAUTH for the Object field, and then save the record.
d. Optional: Select Action > Exclude / Include Fields and choose the
persistent and non-persistent fields to be included or excluded from this
object.
3. Create publish channels.
a. From the Start Center, select Go To > Integration > Publish Channels.
b. Insert a new record using the following details:
Publish Channel
MXAPPAUTHInterface
Description
APPLICATIONAUTH
Object Structure
MXAPPLICATIONAUTH
c. Save the record.
d. Select Action > Enable Event Listener .
4. Create enterprise services (for inbound).
a. From the Start Center, select Go To > Integration > Enterprise Services.
b. Insert a new record using the following details:
Enterprise Service
MXAPPAUTHInterface
Description
APPLICATIONAUTH
Object Structure
MXAPPLICATIONAUTH
c. Save the record.
5. Create external systems.
a. From the Start Center, select Go To > Integration > External Systems.
b. Filter results by the default external system value, EXTSYS1.
c. Change the property value for PRETTYPRINT to 1.
d. From the Publish Channels tab, click New Row, select the
MXAPPLICATIONAUTHInterface publish channel, and then select Enabled.
e. From the Enterprise Services tab, click New Row, select the
MXAPPLICATIONAUTHInterface enterprise service, and then select Enabled.
f. Save the record.
6. Generate a list of PLUSC tables that require data export.
a. Open an SQL editor compatible with your database.
b. Connect to the database and issue the following SQL statements:
select groupname,app,count(*) from applicationauth where app
like ’PLUSC%’ group by groupname,app order by groupname;
7. Export data by PLUSC tables.
a. From the Start Center, select Go To > Integration > External Systems.
b. Filter results by the default external system value, EXTSYS1.
c. Select the Publish Channels tab, filter channels by
MXAPPLICATIONAUTHInterface, and then click Data Export.
d. In the Export Condition field, add where groupname in ('groupname’) and
app like 'PLUS%'. An XML file with all records is generated in the folder
defined for IBM Maximo Enterprise Adapter. You can rename the XML file
to make it easier to identify when re-importing the file after the upgrade is
complete.
e. Repeat the export process for the list of groups you generated earlier.

Exporting IBM Maximo Calibration customized application definitions

Customized Maximo Asset Management application definitions are lost when
upgrading to version 7.5. You must export authentication data and then re-import
the data back into Maximo Asset Management after the upgrade is complete.

This solution pertains to Maximo Asset Management 7.1 with base service
fix pack 7.1.1.9 and Calibration 7.1.2. If you have other industry solutions or
add-ons installed, you cannot use this method for preserving customized
application definitions.

Pre-upgrade application name Post-upgrade application name
PLUSCASSET ASSET
PLUSCJP JOBPLAN
PLUSCLOC LOCATION
PLUSCMASPM MASTERPM
PLUSCMSITE MULTISITE
PLUSCPM PM
PLUSCTLINV TOOLINV
PLUSCTOOL TOOL
PLUSCWT WOTRACK


1. From the Start Center, select Go To > System Configuration > Platform
Configuration > Application designer.
2. Filter applications by PLUSC%.
3. Export application definition data.
a. Select the first application, PLUSCASSET, click Export Application definition,
and save the data in a file called PLUSCASSET_custom.xml.
b. Using a text or XML editor, open the PLUSCASSET_custom.xml file for editing.
c. Add the presentationset opening element directly after the XML header
and the presentationset closing element at the end of the file.
. . . . . . <\presentationset>
d. Save the PLUSCASSET_custom.xml file.
4. Repeat the application definition data export process for the remainder of
PLUSC% applications.
PLUSCJP
PLUSCLOC
PLUSCMASPM
PLUSCMSITE
PLUSCPM
PLUSCTLINV
PLUSCTMPLT
PLUSCTOOL
PLUSCWT
5. Change directory to install_home\tools\maximo\internal, create a new
directory called calibration, and save all of the XML files you created when
you exported application definition data.
6. Download the presentation sets attached to this document and unzip them in
the calibration directory.
7. Change directory to install_homemaximo\tools\maximo\internal and run the
mxdiff command.
mxdiff.bat -bdefault_application_definition.xml -mdefault_application_definition.xml
-tapplication_definition_diff.mxs
For example:
mxdiff.bat -bcalibration\PLUSCASSET_orig71.xml -mcalibration\PLUSCASSET_custom.xml
-tcalibration\PLUSCASSET_diff.mxs
8. Repeat the file comparison process for the remainder of application definition
XML files.

IMPORTING

Before you begin ensure you have successfully upgraded to v7.5.

Importing IBM Maximo Calibration bookmarks

IBM Maximo Calibration bookmarks are not preserved when upgrading to version
7.5. You must re-import the IBM Maximo Calibration bookmarks you saved before
the upgrade.

Edit the XML files you generated before the upgrade for IBM Maximo Calibration
applications. Edits include renaming the application node names contained in the
files.

Pre-upgrade application name Post-upgrade application name
PLUSCASSET ASSET
PLUSCJP JOBPLAN
PLUSCLOC LOCATION
PLUSCMASPM MASTERPM
PLUSCMSITE MULTISITE
PLUSCPM PM
PLUSCTLINV TOOLINV
PLUSCTOOL TOOL
PLUSCWT WOTRACK

1. Using a text or XML editor, open one of the IBM Maximo Calibration
application XML files you exported before the upgrade.
2. Replace the PublishMXQUERY opening and closing elements with SyncMXQUERY
elements.
Change

<?xml version="1.0" encoding="UTF-8"?>
<PublishMXQUERY xmlns="http://www.ibm.com/maximo&quot; event="0">
. . .
</PublishMXQUERY xmlns="http://www.ibm.com/maximo&quot; event="0">
to
<?xml version="1.0" encoding="UTF-8"?>
<SyncMXQUERY xmlns="http://www.ibm.com/maximo&quot; event="0">
. . .
</SyncMXQUERY xmlns="http://www.ibm.com/maximo&quot; event="0">

3. Using information from the Table 2 table, update the pre-upgrade application
name with the corresponding post-upgrade application name contained within
the APP element.
For example, change

PLUSCASSET . . .
to
ASSET . . .
4. From the Start Center, select Go To > Integration > External Systems.
5. Filter results by the default external system value, EXTSYS1.
6. Select the Enterprise Services tab, filter channels by MXQUERYInterface, and
then click Data Import.
7. Click Browse, select the updated XML file, and then click OK. The import task
is sent to the process manager. When the crontask completes, the query is
updated and available.
8. Repeat these steps for all of the IBM Maximo Calibration application XML files
you exported before the upgrade. During the import process, you might
encounter warnings or errors that refer to invalid field values or deprecated
objects. You must resolve these errors and reimport the file with no errors.

Importing IBM Maximo Calibration application authentication information

IBM Maximo Calibration application authentication information is not preserved
when upgrading to version 7.5. You must re-import the IBM Maximo Calibration
application authentication information you saved before the upgrade.

Edit the XML files you generated before the upgrade for IBM Maximo Calibration
applications. Edits include renaming the application node names contained in the
files.

Pre-upgrade application name Post-upgrade application name
PLUSCASSET ASSET
PLUSCJP JOBPLAN
PLUSCLOC LOCATION
PLUSCMASPM MASTERPM
PLUSCMSITE MULTISITE
PLUSCPM PM
PLUSCTLINV TOOLINV
PLUSCTOOL TOOL
PLUSCWT WOTRACK


1. Using a text or XML editor, open the APPLICATIONAUTH application XML file you
exported before the upgrade.
2. Replace the PublishMXAPPLICATIONAUTH opening and closing elements with
SyncMXAPPLICATIONAUTH elements.
Change

<?xml version="1.0" encoding="UTF-8"?>
<PublishMXAPPLICATIONAUTH xmlns="http://www.ibm.com/maximo&quot; event="0">
. . .
</PublishMXAPPLICATIONAUTH xmlns="http://www.ibm.com/maximo&quot; event="0">

to

<?xml version="1.0" encoding="UTF-8"?>
<SyncMXAPPLICATIONAUTH xmlns="http://www.ibm.com/maximo&quot; event="0">
. . .
</SyncMXAPPLICATIONAUTH xmlns="http://www.ibm.com/maximo&quot; event="0">

3. Using information from the Table 3 table, update the pre-upgrade application
name with the corresponding post-upgrade application name contained within
the APP element.
For example, change
PLUSCASSET . . .
to
ASSET . . .
4. From the Start Center, select Go To > Integration > External Systems.
5. Filter results by the default external system value, EXTSYS1.
6. Select the Enterprise Services tab, filter channels by MXAPPAUTHInterface, and
then click Data Import.
7. Click Browse, select the updated XML file, and then click OK. The import task
is sent to the process manager. When the crontask completes, the query is
updated and available.
8. Repeat these steps for all of the IBM Maximo Calibration groups you exported
before the upgrade.

Importing IBM Maximo Calibration customized application definitions

Customized IBM Maximo Calibration application definitions are not preserved
when upgrading to version 7.5. You must re-import the IBM Maximo Calibration
customized application definitions you saved before the upgrade.

Edit the XML files you generated before the upgrade for IBM Maximo Calibration
applications. Edits include renaming the application IDs and modify control values
contained in the files.

Pre-upgrade application name Post-upgrade application name
PLUSCASSET ASSET
PLUSCJP JOBPLAN
PLUSCLOC LOCATION
PLUSCMASPM MASTERPM
PLUSCMSITE MULTISITE
PLUSCPM PM
PLUSCTLINV TOOLINV
PLUSCTOOL TOOL
PLUSCWT WOTRACK

1. Modify MXS files.
a. Copy all MXS files you created earlier when you compared application
definition XML files into the install_home\maximo\tools\maximo\en\script
directory.
b. Using a text or XML editor, open the PLUSCJP_diff XMS file, rename the
application ID and modify control values using the post-upgrade
application names, and then save the file.
Change
. . .
to
. . .

c. Change directory to install_home\maximo\tools\maximo\internal and run
the runscriptfile command.

runscriptfile -fPLUSCJP_diff

The differences for this application are now imported.
2. Repeat the MXS file modification and import process for all remaining XMS
files.
3. Rebuild the Maximo EAR file, deploy it to the server, and then start the
application server.