Concepts and Architecture 

Use

The principle of the Web services in the portal is shown in the graphic below. You can easily enable a Web service to run in the portal.

For the emitter and for the receiver, the SOAP message is not directly handled by the portal service. It is all wrapped by the PRT. The portal service of the requestor is wrapped by the open tool (PAR plug-in) from the WSDL file to the external Web service. Each access to the SOAP service is then converted by the runtime to a SOAP message. The answer is waited for and when it arrives, the process can continue. All the changes made by the open tool are done before the PAR file is created. There is no intervention by the open tool in the runtime sequence.

On the other hand, for the provider, the WSDL file of the SOAP service within the portal is generated by the open tool (PAR plug-in). When a SOAP message is received, the message is interpreted by the runtime and redirected to the specified portal service. This is done if the security is respected.

Principle of the Web Services in the Portal

The main architectural aspects of the portal Web services are:

Main Architecture Aspects