| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Upgrading: Step 4: Update midm.xml |
|
About the Upgrade Paths to Sun Master Index
Upgrading From eView Studio to Sun Master Index (Repository)
To Upgrade to Sun Master Index (Repository)
Migrating to Service-Enabled Sun Master Index
Step 1: Create the Service-Enabled Master Index
Step 2: Migrate any Custom Plug-ins
Step 3: Update the Object Definition
Step 5: Update the Master Controller
Step 6: Update the Matching and Standardization Configuration
Step 7: Update Query Definitions
Step 8: Update the Survivor Calculator
Step 9: Update Field Validations
Step 10: Validate the Configuration Files
Step 11: Update Match and Standardization Engine Files
Step 12: Upgrade the Database Connection and Security
Step 13: Finalizing the Upgrade
Step 14 (Optional): Update the Master Index API in Client Projects
The upgrade from the Enterprise Data Manager file in the Repository-based project to
midm.xml in the service-enabled project is partially automated. A few updates to the
text need to be performed manually, but the bulk of the update is
done through the Configuration Editor.
midm.xml.midm.xml in the service-enabled application.edm element near the top of the file, change the name
of the element from “edm” to “midm”, and change “sbyn:SeeBeyond/eView/schema/EDM.xsd" to "schema/midm.xsd". Be sure
to change both the opening and closing edm tags.
These are the lines you need to change:
<edm xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="sbyn:SeeBeyond/eView/schema/EDM.xsd"> ... </edm>
When you are done, the lines should look like this:
<midm xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="schema/midm.xsd"> ... </midm>
The Configuration Editor appears.
Note - This change is just to enable the Save command so you can
save midm.xml in the new format. For example, you can change the
data type for one of the fields and then change it back to
its original value.
midm.xml again, and perform the following steps:max-length element with a value of
-1. If you find fields with this value, change it to the correct
value.
Tip - An easy way to check for these values is to right-click in
the text of the file and then click Validate XML. If you get
errors similar to The value '-1' of element 'max-length' is not valid., click on the error and the cursor will move
to the errant text in the file.
reports element and all of its contents, and then replace it with the
following text. <reports>
<root-object>Person</root-object>
<tab-name>Reports</tab-name>
<screen-id>6</screen-id>
<display-order>5</display-order>
<search-pages/>
<search-result-pages/>
<subscreen-configurations>
<subscreen>
<enable>true</enable>
<root-object>Person</root-object>
<tab-name>Potential Duplicate Report</tab-name>
<report-name>Potential Duplicate</report-name>
<screen-id>0</screen-id>
<display-order>5</display-order>
<search-pages/>
<search-result-pages>
<search-result-list-page>
<search-result-id>0</search-result-id>
<item-per-page>10</item-per-page>
<max-result-size>2000</max-result-size>
<field-group>
<description/>
<field-ref>Person.FirstName</field-ref>
<field-ref>Person.LastName</field-ref>
<field-ref>Person.SSN</field-ref>
<field-ref>Person.DOB</field-ref>
<field-ref>Person.Gender</field-ref>
</field-group>
</search-result-list-page>
</search-result-pages>
</subscreen>
<subscreen>
<enable>true</enable>
<root-object>Person</root-object>
<tab-name>Deactivated Record Report</tab-name>
<report-name>Deactivated</report-name>
<screen-id>1</screen-id>
<display-order>1</display-order>
<search-pages/>
<search-result-pages>
<search-result-list-page>
<search-result-id>0</search-result-id>
<item-per-page>10</item-per-page>
<max-result-size>2000</max-result-size>
</search-result-list-page>
</search-result-pages>
</subscreen>
<subscreen>
<enable>true</enable>
<root-object>Person</root-object>
<tab-name>Merged Transaction Report</tab-name>
<report-name>Merged</report-name>
<screen-id>2</screen-id>
<display-order>0</display-order>
<search-pages/>
<search-result-pages>
<search-result-list-page>
<search-result-id>0</search-result-id>
<item-per-page>10</item-per-page>
<max-result-size>2000</max-result-size>
<field-group>
<description/>
<field-ref>Person.FirstName</field-ref>
<field-ref>Person.LastName</field-ref>
<field-ref>Person.SSN</field-ref>
</field-group>
</search-result-list-page>
</search-result-pages>
</subscreen>
<subscreen>
<enable>true</enable>
<root-object>Person</root-object>
<tab-name>Unmerged Transaction Report</tab-name>
<report-name>Unmerged</report-name>
<screen-id>3</screen-id>
<display-order>2</display-order>
<search-pages/>
<search-result-pages>
<search-result-list-page>
<search-result-id>0</search-result-id>
<item-per-page>10</item-per-page>
<max-result-size>2000</max-result-size>
</search-result-list-page>
</search-result-pages>
</subscreen>
<subscreen>
<enable>true</enable>
<root-object>Person</root-object>
<tab-name>Updated Record Report</tab-name>
<report-name>Update</report-name>
<screen-id>4</screen-id>
<display-order>3</display-order>
<search-pages/>
<search-result-pages>
<search-result-list-page>
<search-result-id>0</search-result-id>
<item-per-page>10</item-per-page>
<max-result-size>2000</max-result-size>
<field-group>
<description/>
<field-ref>Person.FirstName</field-ref>
<field-ref>Person.SSN</field-ref>
<field-ref>Person.Address.AddressLine1</field-ref>
</field-group>
</search-result-list-page>
</search-result-pages>
</subscreen>
<subscreen>
<enable>true</enable>
<root-object>Person</root-object>
<tab-name>Activity Report</tab-name>
<report-name>Transaction Summary</report-name>
<screen-id>5</screen-id>
<display-order>4</display-order>
<search-pages>
<simple-search-page>
<screen-title>Weekly Activity</screen-title>
<report-name>Weekly Transaction Summary Report</report-name>
<search-result-id>0</search-result-id>
<search-screen-order>1</search-screen-order>
<field-group/>
</simple-search-page>
<simple-search-page>
<screen-title>Monthly Activity</screen-title>
<report-name>Monthly Transaction Summary Report</report-name>
<search-result-id>0</search-result-id>
<search-screen-order>2</search-screen-order>
<field-group/>
</simple-search-page>
<simple-search-page>
<screen-title>Yearly Activity</screen-title>
<report-name>Yearly Transaction Summary Report</report-name>
<search-result-id>0</search-result-id>
<search-screen-order>3</search-screen-order>
<field-group/>
</simple-search-page>
</search-pages>
<search-result-pages>
<search-result-list-page>
<search-result-id>0</search-result-id>
<item-per-page>10</item-per-page>
<max-result-size>2000</max-result-size>
<field-group/>
</search-result-list-page>
</search-result-pages>
</subscreen>
<subscreen>
<enable>true</enable>
<root-object>Person</root-object>
<tab-name>Assumed Matches Report</tab-name>
<report-name>Assumed Match</report-name>
<screen-id>6</screen-id>
<display-order>6</display-order>
<search-pages/>
<search-result-pages>
<search-result-list-page>
<search-result-id>0</search-result-id>
<item-per-page>10</item-per-page>
<max-result-size>2000</max-result-size>
<field-group>
<description/>
<field-ref>Person.FirstName</field-ref>
<field-ref>Person.LastName</field-ref>
<field-ref>Person.SSN</field-ref>
</field-group>
</search-result-list-page>
</search-result-pages>
</subscreen>
</subscreen-configurations>
</reports> field-ref
elements, replacing the value of the root-object elements, and configuring the items
per page and maximum result size for each report.root-object elements. In each empty root-object element
you find, insert the name of the parent object. For example:<root-object>Person</root-object>
midm.xml by right-clicking in the text and selecting Validate XML.