Configuring a logical port with SOMANAGER (SAP NetWeaver Release 7.1 and higher)
- Start the transaction SOAMANAGER.
- Click the Web service configuration link.
- Select Object type as the first search criterion and enter the search term Consumer proxy.
- Select Object name as the second search criterion and enter the search term IATCCONNECTORBF.
Click Search. - In the list of search results, the consumer proxy with the internal name /AEB/CO_02IATCCONNECTOR_BF and the name IATCConnectorB is displayed.
- In the entry, click on the link in the Internal name column.
- In the consumer proxy details displayed below, select the Configurations sheet and click Create – Manual configuration.
- Enter a name of your choice for the logical port and its description. Note that the port name must not be longer than 30 characters. When you are finished, click Next.
- In the Consumer security step, either select No authentication for an HTTP connection or User ID and password for an HTTPS connection. This includes all connections to the AEB data center. Specify the user ID in the format of <user in the target system>@<client of the target system> and the password matching the user.
- When you are finished, click Next.
- In the HTTP settings step, enter the values from the “HTTP settings” table
- When you are finished, click Next.
- In the SOAP log step, enter the values from the “SOAP log” table.
- Click Finished to save the configuration of the logical port. The logical port should be displayed with the Active status in the list of logical ports for the consumer proxy. Otherwise, activate the port manually using the Activate button.
If the search for the consumer proxy does not return any results, refer to note 2772510 in SAP's Online Service System (OSS).
HTTP settings
Field name | Value | Explanation |
|---|---|---|
Log | HTTP or HTTPS | To be selected according to the desired connection type. |
Host | Server name of target system | For connections with the AEB data center, the server name is always rz3.aeb.de |
Port | Port under which the target system can be accessed | For HTTPS connections, the port is 443 |
Path | /<Pathname target system>/servlet/bf/ATCConnectorBF Example: /test2cai/servlet/bf/ATCConnectorBF | Ask your AEB representative if you do not know the path name of the target system. |
Data of the proxy computer | Name, port and login for the proxy server | If a proxy must be used, enter the relevant access data for the proxy here and in the other fields |
Execute local call | No local system call | |
Transport binding type | SOAP 1.1 | |
Max. waiting time WS consumer | 0 | |
Optimized XML transfer | none | |
Compressing the HTTP message | Active | |
Compressing the response | True |
SOAP log
Field name | Value |
|---|---|
Message ID log: | Suppress ID transfer |
Scope of data transfer | Minimal data transfer |
Transfer log | Transfer via HTTP header |
A logical path created for proxy class /AEB/CO_02IATCCONNECTOR_BF should never be defined as default port since additional AEB add-ons in the system require their own logical port with this class, for example.
The test of the port using the Ping function in SOAMANAGER is not reliable. Instead, use the connection test of the add-on (transaction /n/AEB/CT).
When hosting in SAP's private cloud ("RISE"), it is necessary to have the URL of the target system included in the list of permitted URLs. To do this, create a ticket with SAP.