Logical Ports for Web Services
As of SAP NetWeaver 7.0 SP14 and SAP NetWeaver 7.1, new logical ports are no longer transportable objects. If you generate, or regenerate, a proxy class, eCATT no longer generates the logical port ECATTDEFAULT.
Instead, the system divides the end point URL from the generation process into the following parts:
Target system describing parts
These are stored in HTTP destination and compared with the current target system.
Service addressing parts
These are stored in the WEBSERVICE command interface in the field PATH_SUFFIX.
The fields PROTOCOL, HOST_NAME, PORT, and Path from the end point URL are compared with the corresponding fields of the destination of the maintenance target system. If there is a difference, the system creates a new HTTP destination and assigns it to a new target system. This is entered in the system data container currently in use. This target system is assigned to the WEBSERVICE command in the script.
In addition, the system stores the complete end point URL in the command interface in the field END POINT for reference. When you choose Update Interface, the system extends the command interface structure to include the field END POINT.
Execution
Executing with Old Proxy Classes and Existing Old Logical Ports
If the specified logical port was created during the original generation, it still exists in the old form and can be used correspondingly.
If it is to be changed to the execution logic, the logical port is copied and this copy is used in the altered form.
Executing with Old Proxy Classes and Existing New Logical Port
If eCATT has not generated any logical ports for the proxy class, you can enter one in the command interface in the field LOGICALPORT-NAME.
The logical port must exist. You can create a logical port in the transaction SOAMANAGER, for example.
Executing with Newly Generated Proxy Classes
In current Releases the system does not generate logical ports for new proxy classes.
If no LOGICALPORT-NAME is specified in the command interface, the system generates a new logical port at execution.
In the process, the target system describing data from the HTTP destination is passed into the information for the logical port in PROTOCOL, HOST_NAME, and PORT.
The PATH_SUFFIX is passed to the PATH in the logical port. The SAP client is taken from the HTTP destination and is appended to the PATH in the logical port as an additional suffix &sap-client=nnn.
Furthermore, the USERNAME from the logon data of the HTTP destination is passed to the logical port. As it is not possible to transfer the password from the HTTP destination, eCATT has developed a method for password handling.
Password Handling for Logical Ports
You can store a password for every target system with a HTTP destination in the eCATT maintenance function for system data. You can get a list of the HTTP destinations using the pushbutton HTTP Password. The client and the user are displayed for each HTTP destination and you can enter or delete a password.
When you enter a password, it is encrypted and stored in a separate table. This password is used solely during the execution of eCATT Webservices to address the logical port.
Deleting Logical Ports
New logical ports are deleted after execution as well as the old copied logical ports.
Supplementary for the eCATT Log
Currently, only the name of the currently generated logical port is displayed in the eCATT log.