WebSphere Commerce Developer

Identifying customizations on Management Center Version 7 Feature Pack x

If you have previously installed and enabled the Management Center feature provided in a Version 7 Feature pack, review this information. Customizations that you made to the Management Center in a lower WebSphere Commerce Version 7 Feature pack installation (Version 7 Feature Pack x, for example, Version 7 or Version Feature Pack 1) can be identified after you install a higher WebSphere Commerce version 7 Feature pack (Version 7 Feature Pack y, for example, Version 7 Feature Pack 2).

Before you begin

The Eclipse compare editor does not display line numbers by default. The lines numbers assist you in determining what location within the file, has changed. To ensure that line numbers are shown in the compare editor view, complete the following steps:
  1. Start WebSphere Commerce Developer
  2. Click Window > Preferences.
  3. Expand Workbench and select General> Compare/Patch.
  4. Select Show additional compare information in the status line.
  5. Expand Workbench and select General > Editors > Text Editors.
  6. Select Show line numbers.
Notes:
  1. Introduced in Feature Pack 1In WebSphere Commerce Version 7, the OpenLaszlo files are contained in both restricted and non-restricted directories. Files in restricted directories are considered IBM assets and files in non-restricted directories are custom assets. When enabling the Version 7 Feature Pack 1 or Feature Pack 2 Management Center feature, the files in the restricted directories are deleted from your workspace and the files in non-restricted directories are overridden by the corresponding files in Feature Pack 1 or Feature Pack 2.
  2. Introduced in Feature Pack 1Between Version 7 and Version 7 Feature Pack y, some elements have been moved to a different parent or a different file. For each moved element the comparison tool reports two entries; add element and delete element. The add element is the new location of the element and the delete element is the original location of the element.

About this task

Installing WebSphere Commerce Developer Version 7 Feature Pack y (which is a higher Version 7 Feature Pack, for example FEP2) provides a new version of Management Center which includes a compare editor.

You can use the compare editor in these situations:
  • After installing the Websphere Commerce Version 7 Feature Pack Y, you can compare:
    • Management Center changes between WebSphere Commerce Management Center Version 7 Feature Pack x (which is a lower Version 7 Feature Pack, for example FEP1) with any customizations you made in Management Center Version 7 Feature Pack x.
  • After you enable the Management Center feature from the higher Version 7 Feature Pack, you can compare:
    • Management Center changes between Version 7 Feature Pack x base with any customizations you made in Version 7 Feature Pack x base.
    • Management Center changes between Version 7 Feature Pack y base with any customizations you made in Version 7 Feature Pack y base.
The compare editor generates a report to assist you with migrating OpenLaszlo files to WebSphere Commerce Version 7 Feature Pack y.

Procedure

  1. Start WebSphere Commerce Developer
  2. Start the compare editor by completing these steps:
    1. Open the Enterprise Explorer view.
    2. Take one of the following actions:
      • Feature Pack 4Feature Pack 2Feature Pack 3Feature Pack 1Right click LOBTools and select OpenLaszlo Migration > Compare Customizations.
      • Feature Pack 5 or laterRight click LOBTools and select OpenLaszlo Migration > Launch Migration Tool.
    The compare editor runs. Click the OpenLaszlo Migration Results tab.
    OpenLaszlo Migration Results
  3. The comparison report shows the following columns:
    Filename
    The name of the file you customized in Version 7 Feature Pack x. Listed below the filename is one or more lines items represented in this format:
    Line #nn:version
    Where:
    • nn is the line number which contains a change
    • version is the feature pack version of the changed file
    Status
    A status of New is displayed in this column.
    Change type
    The type of change or customization on the base Version 7 Feature Pack x file. Examples of change types are:
    • Add, Modify, or Remove attribute
    • Modify text value
    • Add file
    • Reorder element
    • Add or Delete element
      Notes:
      1. Between Version 7 Feature Pack x and Version 7 Feature Pack y, some elements have been moved to a different parent or a different file. The comparison tool reports two entries; add element and delete element. The add element is the new location of the element and the delete element is the original location of the element. The delta details of the delete element shows the new location of the file and parent.
      2. If you modified the unique identifier (ID) value of an element, two entries are displayed; add element and delete element. The add element is the modified element and the delete element is the original feature pack file.
        For example:
        <wcfGridText name="attachmentCode" propertyName="identifier" objectPath="AttachmentGroup" editable="false" text="${attachmentResources.attachmentIdentifier.string}" width="150" />
        the unique identifier (ID) of element "wcfGridText": name
        the unique identifier (ID) value of element "wcfGridText": attachmentCode
  4. Analyze the comparison report to ensure that changes identified correspond to changes made by your development team, on the base Version 7 Feature Pack x files. Consider the following situation when reviewing the report:
    • Consider the quantity of changes listed. Use the quantity to gauge the time and effort required to migrate to WebSphere Commerce Version 7 level.
    • If you modified the unique identifier (ID) of an element, two entries are displayed; add element and delete element.
      A unique ID is used to uniquely identify an element under its parent. The values or the combinations of values must be unique under its parent instance. A null value or missing value is allowed. Unique identifiers are defined in the following ways:
      1. The element name itself is a unique identifier. For example mktExperimentValidator is a unique identifer.
      2. The element name and the value of an attribute form the unique identifier. For example <mktExperimentValidator validatorId='xyz'.../>.
      3. The element name and the combinations of values of attributes form the unique identifier.
      You are not required to use unique identifiers unless you copy a ready to use class for your own purposes. Refer to OpenLaszlo API documentation for the predefined unique identifiers.

What to do next

Refer to Migrating customized Management Center files to WebSphere Commerce Version 7 Feature Pack y.