Bookshelf Home | Contents | Index | PDF |
Oracle Migration Tool On Demand Guide > Getting Started with Oracle Migration Tool On Demand > Considerations for Using the Oracle CRM On Demand Migration Tool Client > Considerations for Character Encoding in Configuration DataThe Oracle Migration Tool On Demand client stores and transfers configuration data in XML. This allows you to manage change through version control tools such as diff. Therefore, all serializations must follow XML formatting and encoding rules. The most commonly occurring characters that must be encoded are:
To preserve the integrity of the XML content:
For example, if you extract data containing an ampersand character, then the Oracle Migration Tool On Demand client renders the ampersand to & in the XML file. If you run the Upsert operation on the data from the XML file, then any & characters must be represented as & in the XML for the upsert to be successful To further illustrate, consider a Custom Web Tab in the UI with the following URL value containing ampersand characters: https://xxxx.yyyy.com/commerce/buyside/commerce_manager.jsp?from_hp=true&_bm_trail_refresh_=true&bm_cm_process_id=4482147&_partnerAccountId=%%%Account_Id%%%&_partnerSessionId=%%%User id%%%&_partnerSsoToken=%%%SSO Token%%%&_partnerSessionUrl=https%3A//secure-ausomxkwa.crmondemand.com/Services/Integration&BM_URL_CAPTURE_COOKIE=siebel-dev After a ReadAll operation, the same URL in the XML is remapped to the following URL value with the ampersand characters encoded as https://xxxx.yyyy.com/commerce/buyside/commerce_manager.jsp?from_hp=true&_bm_trail_refresh_=true&bm_cm_process_id=4482147&_partnerAccountId=%%%Account_Id%%%&_partnerSessionId=%%%User id%%%&_partnerSsoToken=%%%SSO Token%%%&_partnerSessionUrl=https%3A//secure-ausomxkwa.crmondemand.com/Services/Integration&BM_URL_CAPTURE_COOKIE=siebel-dev |
Oracle Migration Tool On Demand Guide, Release 36 | Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |