Access web content via a servlet
Overview
Users can access content displayed via the Web Content Manager servlet by connecting to a URL. A servlet delivered website should be used when you don't need to use any WebSphere Portal based features such as authoring tools.
Access a web page using a servlet
The following URL structure is used to connect to a web page:
http://[HOST]:[PORT]/wps/connect/[PATH]?srv=Non-ascii characters can not be used in the query string section of URLs. For this reason, it is best not to name Web Content Manager items using Non-ascii characters if you plan to use URLs to call Web Content Manager items.
- [PATH] can be the path to a site area or content item. This must be entered for all types of content including components. In the case of components, this is the path to the site area or content item that the component is displayed with.
- srv= is either cmpnt or page.
Service option Details srv=cmpnt Retrieve a component from either the component library or from a site area or content item. You must also specify the following:
- source=
- This determines where the component is being sourced from. This is either:
- library
- sitearea
- content
- cmpntname=[componentname]
- This is the name of the component being retrieved.
srv=page Retrieve a content item. As srv=page is returned as default, this can be omitted from the URL. The presentation template to use when displaying this content is specified by adding:
presentationtemplate=library/presentationtemplatename
Examples:
- URL to content:
http://[HOST]:[PORT]/wps/connect/[PATH]Examples:
- http://host:10039/wps/connect/sitearea/content
- http://host/wps/wcm/myconnect/path/?contentIDR=xyz
contentIDR equals content UUID and can can be found by opening content item and showing hidden fields.
- URL to content with a presentation template defined:
http://[HOST]:[PORT]/wps/connect/[PATH]?presentationtemplate=[libraryname/presentationtemplatename]Example:
http://host:10039/wps/connect/sitearea/content?presentationtemplate=library/presentationtemplate
URL to a library component:
http://[HOST]:[PORT]/wps/connect/[PATH]?srv=cmpnt&source=library&cmpntname=[componentname]Example:
http://host:10039/wps/connect/sitearea/content?srv=cmpnt&source=library&cmpntname=component
URL to a content component:
http://[HOST]:[PORT]/wps/connect/[PATH]?srv=cmpnt&source=content&cmpntname=[componentname]Example:
http://host:10039/wps/connect/sitearea/content?srv=cmpnt&source=content&cmpntname=component
Apply custom caching and expiring parameters
Like any other URL request made to a Web Content Manager Server, custom caching and expiring parameters can be added to a request.
- Example:
http://[HOST]:[PORT]/wps/connect/[PATH]?CACHE=SITE&EXPIRES=REL+9000sIn this example, the content being retrieved via URL will be saved in the Basic Site Cache, and expired after 9000 seconds (two and half hours).
Parent: Deliver web content