How the portal implements the remote PUMA REST service

The previous topics describe the general part of the remote REST service for PUMA Interface. This interface can be implemented by different providers that can be based on different backend systems or user repositories and provide their own input and output formats. The implementation of the interface described here is the one based on HCL WebSphere Portal v8.5.

The implementation described here uses ATOM (refer to RFC 4287) and the ATOM Publishing Protocol as basic input and output format to wrap the resource representations described by the schema in the general part. Additionally, using the remote REST service for PUMA requires that you consider some special aspects described in this section.

• URL path segment for virtual portals
  
• Identifiers used in the Portal Implementation
  
• Access Control Checks
  
• Use ATOM/APP as input and output format
  
• Switch for tunneling of HTTP methods
  
• HTTP caching
  
• Context root and authentication mechanism
  
• Lookup facility in the portal
  

Parent Remote REST service for PUMA