However, some sites require (or desire) the ability to have both secure and unsecure connections to the CV via Web services. To implement this requires two different Pterm/Lterm 'Listener' pairs, one for each type connection; and they can both be on the same Line. These Pterms can be named whatever you like; TCPWSRV is just the default name we provide and suggest, to make it's purpose easily recognizable. The Port number for each TCPIP 'Listener' must be specified in the sysgen definition, and must be unique. The port-number/host-name (or IP address) combination must be unique across the LPAR. This means that a port assigned to a listener pterm cannot be shared across CVs within the same LPAR. However, these 'listener' Pterms can share the same task code if you like, or they can each have a unique task code. The main reason why different task codes might be desired is in case a site would like to specify different limits for each one.
For the secured connection the Listener Pterm will be used for the inbound connection, and this must be specified in your PAGENT policy if you have employed that; PAGENT is a CISCO tool that runs on a CISCO router and directs traffic. This is equivalent to the ATTLS (Application Transparent Transport Layer Security).
At run-time, the Web Services client will need to specify which port it wants to use- the secure or unsecure one.
When implementing Web Services across multiple IDMS CVs, each CV (running on the same LPAR) must have a unique Listener Port. The combination of HOST-NAME and Port-Number must be unique across the network.