Terminator Component (SAP Library - SAP Enterprise Portal Development Kit (PDK))

Terminator Component

The Terminator component sends HTTP request to servers, to terminate the registered sessions.

Basic functionality

The Terminator component receives a HTTP request (either get or post), with the parameter TermString, TermString contains escaped URLs concatenated with an ampersand (&).The special characters must be escaped (see JavaScript functions escape/unescape) so that the URLs are transmitted correctly.

Format of the parameter TermString:

escaped(escaped(URL1)+"&"+escaped(URL2)+"&"+...escaped(URLn))

The Terminatorcomponent splits und unescapes the TermString parameter into single URLs and sends for every of them one single HTTP post request to the target system (usually ITS).

The Portal uses by default the Portal component DSMTerminator as Terminator component. You can customize this component or define another component or Portal component as Terminator component.

Configuring the DSMTerminator component

The default Terminator Portal component DSMTerminator can be customized by changing the properties of the iView.

DSMTerminator Properties

Property	Description
validationEnabled=<true\|false>	The DSMTerminator component sends requests to the servers it is told to. With this property you can define, if the URL is validated before it is sent. If the property is set to true, every URL will be validated against the trustedHost and restrictedHost list.
trustedHosts=<host_name_list>	This semicolon separated list specifies the hosts to which the DSMTermination component is allowed to connect. A host entry can also be specified as pattern with one wildcard (). Example: .myfirm.com;*yourfirm.com
restrictedHosts=<host_name_list>	This semicolon separated list specifies the hosts to which the DSMTermination component is not allowed to connect. A host entry can also be specified as pattern with one wildcard (). Example: .badfirm.com;*anotherbadfirm.com
cookieThroughEnabled=<true\|false>	Allows that cookies from the incoming requests are passed on to the all requested destinations. This is required when you integrate components based on the BSP (Business Server Pages).

The DSMTerminator component can also be used standalone by specifying the URL of the DSMTerminator component (<Portal_URL>/irj/servlet /prt/portal/prtroot/DSMTerminator.default ) with following parameters:

DSMTerminator Parameter

Property	Description
TermUrl=<String>	Optional parameter specifies all URLs to which the requests should be distributed. If the parameter not specified or empty, no request is distributed.
Autoclose=<positive_Number>	Optional parameter that specifies the delay before the External Window (used for browsers with no Java support) is closed. If not specified, the External Window will not be closed.
Filter=<NOCOPY \| ESCAPE \| COPY>	Optional parameter that specifies how the single responses returned after the request distribution should be handled by the DSMTerminator component, when the final (collective) response is assembled. COPY The single responses are copied into the collective response. ESCAPE Is similar to COPY but all special characters will be converted (escaped) so that the string is properly displayed on the HTML page. NOCOPY The single responses are not copied into the collective response. If the parameter is not specified, the NOCOPY option is selected.

Using Another Terminator Component

You can define another Portal component or an external script or process specified by full qualified URL (for example, servlet or ASP) as Terminator component. The specified component has to implement the basic functions of a Terminator component. See chapter EPCF Configuration for more details.