Remote Model SPI REST service
The Remote Model SPI provides access to portal models through REST services. It allows you to obtain and modify portal resources that are exposed by some of the models of the model SPI remotely, that is from clients that are outside the JVM of the server. This is achieved by means of REST services.
The Remote Model SPI supports the following models:
Note that the Remote Model SPI currently does not support the following models:
- ContentModel
- Obtain and modify the content topology and the properties of content nodes such as pages, labels, and content URLs.
- NavigationModel
- Obtain the navigation topology only, as the navigation model is implied by the structure of the content model.
- LayoutModel
- Obtain and modify the layout of a page, that is the topology of layout elements of a page, and the properties of layout elements such as layout containers and layout controls.
- PortletModel
- Obtain, create, update, and delete portlets.
- UserModel
- Obtain and modify user and group information.
- LanguageList
- MarkupList
- SkinList
- ThemeList
The Remote Model SPI uses feeds in the Atom Syndication Format in conjunction with the Atom Threading Extension to expose model resources, and the HTTP-based Atom Publishing Protocol (APP) to modify portal resources. With the Remote Model SPI as a REST service, use the following HTTP verbs:
- To obtain model information: HTTP GET
- To modify existing model information: HTTP PUT
- To create model resources: HTTP POST
- To delete model resources: HTTP DELETE
Parent topic
Model SPI overview
Related concepts
Sub packages of the Model SPI
Feeds for REST services
Obtaining a model from the portal
Related reference
Model SPI samples
Related information
Obtaining the object ID for a page or portlet