3.6 Mapping URLs with WebUrlMapPlugin

Content Server uses Oracle WebLogic Server, which has a built-in Web server, to filter pages through a Web browser. User requests are authenticated in Oracle WebLogic Server and communicated with Content Server.

The WebUrlMapPlugin component enables you to map shortened URLs to other URLs in Content Server using a substitution script for the mapping, which also enables you to map long URLs to abbreviated versions. The WebUrlMapPlugin component is installed (enabled) by default with Content Server.

This section covers these topics:

3.6.1 Script Construction

The shortened URLs that you can create generally use the following format:


The actual mapping process is based on the part of the URL that follows the host name portion. To resolve the shortened URL, Content Server compares the prefix to those in the list of defined WebUrlMapPlugin entries. If a match exists, Content Server uses the map script that corresponds to the matching prefix to display the applicable document or Content Server page. For more information about the suffix, see "Supported Variables for Referencing".

To construct a URL mapping entry using the WebUrlMaps Screen, you must establish a prefix and define the corresponding map.

  • Prefix

    The prefix portion of the mapping entry is any abbreviation you want to use to identify URLs of a certain form. For example, if you want your short URL to return the dynamic conversions of documents, you can use idc as your prefix (for example, the abbreviated form of dynamic converter).

    When you create your prefix, do not enter a slash (/) character at the beginning of it because Content Server removes the first slash from the incoming URL before the prefix test is performed.


    Include a slash (/) at the end of your URL map prefix. Otherwise, your mappings can apply to many more URLs and interfere with standard Content Server operations.
  • Map

    The map portion of the mapping entry is the Idoc Script code that Content Server uses to resolve the shortened URL. You can use substitution tags (<!--$variable-->) in the map portion. Examples include:

    • <!--$cgipath-->

    • <!--$internetuser-->

    • <!--$suffix-->

    These substitution tags are variables that refer to the applicable parameters of a URL.

    Simple 'if' constructions are also supported. For example, the following script segment performs a test to determine whether a value exists and is not empty:

    <!--$if myconfigvar-->something<!--$endif-->

3.6.2 Supported Variables for Referencing

The map portion of the URL mapping entry uses the following standard variables for referencing:

  • The CGI path

    This is the current CGI path of the Oracle WebLogic Server Web server filter's configured master Content Server. The Web server filter Oracle WebLogic Server is configured to provide both communication and security for this Content Server. A typical example is /idcm1/idcplg.

  • The 'suffix' parameter

    The value of the suffix variable (<!--$suffix-->) is derived from the part of the URL that follows the preliminary mapping 'prefix' and before the question mark (?). Any slashes (/) at the beginning of the suffix are removed before being substituted into this variable. For example, in the following URL, 'dc' is the mapping prefix followed by the suffix.


    After removing the slash, mydocumentname is used as the value for the suffix variable that is used as a substitution tag in the map portion of the mapping entry. Also, the suffix variable does not include any CGI parameters. Therefore, in the following URL, mydocumentname is still used as the suffix variable's value.


    To enforce the slash separation between the prefix and suffix, add the slash at the end of your prefix abbreviation.

  • Any plugin variable

    For example, you could use the construct <!--$internetuser--> to substitute for the user ID of the currently logged-in user.

  • Any CGI parameter

3.6.3 Add/Edit URL Mapping Entries

To add or edit URL mapping entries:

  1. Select the Administration tray, then click WebUrlMapPlugin.

    The WebUrlMaps Screen is displayed.

  2. Enter the appropriate values in the Prefix and Map fields to edit the existing mapping entries, or define new entries, or both.

  3. Click Update.

    The screen refreshes and the Prefix and Map field values are saved. If all of the displayed fields are populated, two additional Prefix and Map field pairs are displayed after the screen is redisplayed.


    The WebUrlMapPlugin feature is designed to support hundreds of mapping entries. However, be aware that thousands of mapping entries will impact performance of the Web server.

3.6.4 Mapping Examples

The following examples demonstrate mapping scripts and techniques. Info Update Form

You can define a Web URL mapping script that enables you to create a shortened URL to generate the Info Update Form for existing content items. You can write the mapping script to allow users to enter any identification variable for a particular document. For example, all URLs with the following format:


can be mapped to the URL:


To map URLs, define the following Web URL map entry using the WebUrlMaps Screen:

  • Prefix:

  • Map:

    <!--$cgipath-->?IdcService=GET_UPDATE_FORM<!--$suffix-->&myparam=<!--$myparam--> Dynamic Conversion

Dynamic Converter must be installed for this URL mapping example to work.

You can define a Web URL mapping script that enables you to create shortened URLs to various dynamic conversions of documents. For example, all URLs with the following format:


can be mapped to the URL:


To map URLs, define the following Web URL map entry using the WebUrlMaps Screen:

  • Prefix:

  • Map:

    <!--$cgipath-->?IdcService=GET_DYNAMIC_CONVERSION&dDocName=<!--$suffix-->&RevisionSelectionMethod=LatestReleased CGI parameters

You can also directly reference CGI parameters. For example, URLs with the following format:


can be mapped to the URL:


To map URLs, define the following Web URL map entry using the WebUrlMaps Screen:

  • Prefix:

  • Map: