Develop > Presentation layer > Customize IBM Sales Center

Troubleshoot: IBM Sales Center customization

This section related to troubleshooting while using IBM Sales Center customization.

User interface customization

When troubleshooting a user interface customization, try the following suggestions:

• In the plugin.xml file, check for any misspellings, especially in the id and reference id values.

• In the configurator file, called config.ini, check for misspellings and remove any white space at the end of each line. Remember that all values are case-sensitive.

• Ensure that you specify the location of the config.ini file by extending the com.ibm.commerce.telesales.configurator extension point.

• Isolate the problematic plug-in by systematically preventing plug-ins from running when opening the IBM Sales Center client.

  To prevent a plug-in from running:

  1. In the IBM Sales Center development environment, click Run > Run.

  2. On the Run panel, click the Plug-ins tab.

  3. Select Choose plug-ins and fragments to launch from the list.

  4. In the Available plug-ins and fragments window, deselect the plug-ins that you do not want to run.

  5. Click Apply.

  6. Click Run, and the IBM Sales Center client opens

User-defined data customization: Viewing the contents of a BOD

When passing custom data between the WebSphere Commerce Server and IBM Sales Center client, sometimes the data does not display as expected. Verify the BOD files really contain the custom data by viewing the contents of the BODs.

To view the contents of a BOD:

1. Within the IBM Sales Center development environment, click Run > Run.

2. On the Arguments tab, make note of the Workspace Data Location. By default the location is WCDE_INSTALL /mscworkspace/runtime-workspace. This is the location in which the BOD files will be stored.

3. On the Tracing tab,

   1. Click Enable tracing for the selected plug-ins.

   2. In the Plug-ins that support tracing list, select com.ibm.commerce.telesales.core.impl plugin and check all the debug check boxes in the right frame.

   3. Click Run.

4. When the IBM Sales Center client opens, follow the instructions above to test the changes by searching for a manufacturer part number.

5. In the file system, navigate to the Workspace Data Location you examined. By default the location is WCDE_INSTALL /mscworkspace/runtime-workspace. Within this directory, navigate to the debug/bodmessages directory. All BODs exchanged between the client and the server are stored in this directory.

6. Locate the appropriate BOD file. Each file name contains the name of the command that generates the BOD and a timestamp, for example the ShowElectronicCatalog command's BOD will be called wc.ShowElectronicCatalog_ timestamp .xml, where timestamp is the time when the BOD was created.

7. In the file, find the <wc:UserData> tag. For example, the manufacturer part number is passed from the server to the client: <wc:UserData> <wc:UserDataField name="manufacturerPartNumber">myMFPartNumber</wc:UserDataField> </wc:UserData>

8. Remember to disable tracing in the Tracing tab when you no longer need to view the BOD.

Server-side command customization

The IBM Sales Center client uses the same commands as the WebSphere Commerce Server. Therefore, customizations made to the WebSphere Commerce Server will surface in the IBM Sales Center client. For example, assume you customize the order process by implementing the ExtOrderProcessCmd interface. When a customer places an order through the store front, the OrderProcess command runs and then the ExtOrderProcess command runs. In the same way, when a CSR submits an order from the IBM Sales Center client, the OrderProcess command runs and then the ExtOrderProcess command runs.

Related tasks

Debug the IBM Sales Center development environment

Enable tracing in the IBM Sales Center development environment

Plan a customization to the IBM Sales Center

+

Search Tips   |   Advanced Search