Restrictions to names for URL mapping contexts

The following restrictions apply to the names that you can give to URL mapping contexts.

  1. A label of a context must be unique in the scope of its parent context. This means that no two sibling contexts can have the same label.
  2. When creating a URL mapping or creating or modifying a page, make sure that URL mappings and friendly URLs in your portal do not match, partially overlap, or otherwise interfere with each other. For example, do not use strings such as home, ibm, ibm.com, and do not use strings that have been used as URL mappings or friendly URLs in your portal already. Otherwise infinite browser redirect loops might occur, sometimes without an error message. To determine such strings, create an export from your portal by using the XML configuration interface and scan the exported XML result output file for the string that you want to use for your URL mapping or for your friendly URL. By default, the portal ensures that the friendly URL name that you enter is unique. However, this enforcement does not include derived pages with an inherited friendly name and siblings that are moved in by a personalization rule.
  3. Users can map contexts to all portal pages for which they have the User role.
  4. As the labels are later used to create the URL, the label can only contain characters that are in the set of unreserved URL characters. For more information see Unreserved characters.
  5. The label of a root context must not share its partial or full name string with a portal URL identifier. Example: If the identifier is name, then a root context must not be na or vice versa. For more information see Defining the identifier for portal URLs.
  6. The maximum length of a label is restricted to 255 characters.
  7. A label must not have the same name as URL codecs that are used in the portal. Here is a lists of codec names that are currently used in the portal and therefore reserved:
    base64xml
b0,    b0_1,   b0_2,   b0_3,  b1,    b2, b3, 
c0,    c0_1,   c0_2,   c1,    c2,    c3, c4,  c4_1, c4_2, c4_3,  c5, c6, c7, 
cxml,  cxml_1, cxml_2, cxmld, kcxml,
d0,    d1,     d2,     d3,    d4,    d5, dl2, dl3,  dl4,  delta
kcxml, nm1,    nm2,    nm3,   nm4,   pw, resource,  sel,  vp,    wml