Skip to end of metadataGo to start of metadata

Contents

To configure a consumer to access a particular service, you need to create and configure one or more logical ports.
A logical port is created for a specific consumer proxy to access one particular binding on the provider system.
You can create more than one logical port for the same consumer proxy. However, each logical port can point to only one binding.

Concept

May 19, 2018 - Enabling redirect to External URLs in a Portal integrated. Technical ID lpd_start_url with the prefix com.sap.pct.erp.common. “NavigationService.redirect.recieved exception when calling to redirectors with URL”. The NavigationRedirector provides a method to retrieve redirected node names. A re-director must be registered in a means that recognizes the prefix of the navigation target.

The logical port is based on the WSDL document generated for a binding. The WSDL document describes how to access the binding, and includes the URLs for all the bindings defined for a service.

Prerequisites

You can create a logical port based on a WSDL document or manually.

To use the WSDL based configuration the binding WSDL has to be used, not the design time WSDL. The binding WSDL can only be generated after a binding was created for the provider in transaction SOAMANAGER.

Depending on the way you choose to create a logical port, you need the following information:

Method to Create a Logical Port

What You Need to Know

Based on the WSDL document for a service

  • The URL that points to the WSDL document for the service.
    This is the URL for the binding that was generated for the Web service provider.
  • The access parameters for the WSDL document
    (Alternatively, you have the WSDL document stored as a file.)

Manually
If a WSDL document is not available, you need to create a logical port manually.

  • The URL of the binding
  • The configuration settings that the provider expects

Procedure

  1. From the main screen of SOA Manager, go to the Service Administration tab.
  2. Select Web Service Configuration.
  3. In the Search by menu, choose Consumer Proxy.
  4. In the Search Pattern field, specify a consumer proxy or a search string.
    Here, we will use CO_SRT_TEST_PROVIDER.
  5. Select the row with the consumer proxy and choose Apply Selection.
    Design-time information about the consumer proxy is displayed.
  6. Go to the Configurations tab.
    An overview of logical ports is displayed if any have been created.
  7. To create a new logical port, choose Create.
    A dialog box is displayed.
  8. Specify the following information for the new logical port.
    Here, we will use the name CO_SRT_TEST_PROVIDER2.
  9. Select the configuration type WSDL-Based Configuration.
    For WSDL-Based Configuration, the system extracts the binding URL from the WSDL document for the service.

  10. Specify the WSDL access settings.
    Here, use Via HTTP access. Additionally, you need to specify the path to the WSDL document and a user and password.

    The user for WSDL Access needs to be authorized to access the WSDL in the system you are working in.


    For URL for WSDL Access, you need the URL for the binding generated for the Web service provider.

  11. Choose Apply Settings.
    A dialog box displays overview of bindings that could be used for this logical port.
  12. Select the appropriate binding for your logical port.
  13. Choose Apply Settings.
    The logical port is now created in memory.

  14. If an authentication method is used, go to the Consumer Security tab and specify a user and a password.

    The user must have runtime access and application authorization.

  15. Save.
    The new logical port with the default settings is created and displayed in the overview.
  16. Optionally, you can check whether the logical port can access the binding by selecting the consumer proxy and choose Ping Web Service.

Result

Url

You now have created a logical port which can be used in your application to send a SOAP message to the respective Web Service Provider.

Example Application Code Snippet

To invoke a Web Service you could use the following code snippet as an example:

data lr_consumer_proxy type ref to co_my_consumer_proxy.

' instantiate consumer proxy
CREATE OBJECT lr_consumer_proxy
EXPORTING
logical_port_name = 'MY_LOGICAL_PORT_NAME'.

' invoke WebService operation
lr_consumer_proxy->my_webservice_operation( ... ).

Sap

Quick Testing

It's also possible to test the Consumer Proxy without creating a program, using transaction SE80. Follow these steps to trigger a test-call:

  1. Go to transaction SE80 and display the Consumer Proxy object (Edit Object > Enhanced Options > Enterprise Services > Client Proxy).
  2. Click on the Test (F8) button.
  3. On the selection screen specify the Logical Port and select the Method.
  4. Click on Execute (F8).
  5. With the XML Editor (Ctrl+F2) you can edit the input values of the request XML.
  6. To trigger the call, click on Execute (F8).

SAP Logon / SAP GUI

TRBL A1: SAP Logon: Partner vhcalnplci:sapdp00 not reached

If you SAP Logon cannot reach the SAP NetWeaver AS ABAP installation, please check the following:

  1. Check if SAP NetWeaver AS ABAP system is running.

  2. Verify that all dispatcher and Gateway processes have been started as described in Week 1 - Unit 6. All the processes should be in GREEN state.

  3. If one of the process is in state YELLOW, stop your SAP NetWeaver AS ABAP system as described in Week 1 - Unit 6 and start it again as described in step above.

  4. Check the the firewall is turned off in openSUSE Linux.
  5. Switch to the running Oracle VM VirtualBox where your Linux VM runs.
  6. Open YaST and enter your root password of the Linux image.
  7. Search for Firewall. You should select Disable Firewall Automatic Starting and Stop Firewall Now.
  8. Click Next and Finish to save the changes.
  9. Check if you have done the correct port forwarding configurations.
  10. Check if you have added the port forwarding from the SAP logon in your host OS, to the Guest OS as described in Week 1 - Unit 6.

TRBL A2: Local browser can’t access S/4HANA

If you in browser window in your host OS, you cannot access the SAP NetWeaver AS ABAP system which runs in your Guest VM. You are trying to access links for example, S/4 Fiori Launchpad or HTTPS S/4 Fiori Launchpad.

  1. Check if SAP NetWeaver AS ABAP system is running.
  2. Verify that all dispatcher and Gateway processes have been started as described in Week 1 - Unit 6. All the processes should be in GREEN state.
  3. If one of the process is in state YELLOW, stop your SAP NetWeaver AS ABAP system as described in Week 1 - Unit 6 and start it again as described in step above.
  4. Check if you have added the port forwarding from the SAP logon in your host OS, to the guest OS as described in Week 1 - Unit 6.

TRBL A3: SAP Fiori Launchpad link not working in SAP GUI

If you in browser window in your host OS, you cannot access the SAP S/4HANA system which runs in your Guest VM. You are trying to access links for example, S/4 Fiori Launchpad or HTTPS S/4 Fiori Launchpad.

  1. Check if SAP S/4HANA system is running.
  2. Verify that all dispatcher and Gateway processes have been started as described in Week 1 - Unit 6. All the processes should be in GREEN state.
  3. If one of the process is in state YELLOW, stop your SAP S/4HANA system as described in Week 1 - Unit 6 and start it again as described in step above.
  4. Check if you have added the port forwarding from the SAP logon in your host OS, to the Guest OS as described in Week 1 - Unit 6.
  5. Replace the address in the above URL to localhost and access the above SAP S/4HANA Fiori Launchpad link again.
  6. You could also add an entry in your host OS for resolving vhcalnplci.dummy.nodomain to 127.0.0.1. We recommend to replace the links to localhost instead of adding an entry in your hosts file.

  7. Sample entry in your host OS for resolving the launchpad links.

TRBL A4: SAP Logon / SAP GUI: Null pointer exception when running ABAP transaction within Eclipse

In Eclipse, you could open the ABAP project in ABAP in Eclipse but when you try to run the transactions within Eclipse, you get a null pointer exception.

  • You have installed a older version of Java GUI (SAP Logon) in your Mac OS and have Configuration file and SAP UI Landscape configuration file which was not deleted when you uninstalled old SAP Logon and installed the latest version.
  • Remove these two settings files in the Java GUI and click Save.

TRBL A5: How to unlock the user DEVELOPER in AS ABAP?

Javascript Url Redirect

You can unlock the locked user DEVELOPER with another user named SAP* that already exists by default:

  1. Open SAP GUI and log on with a backend user which is not locked. You can use here SAP* with password Appl1ance. Again how to do do that is described here: week 1 - unit 6 - step 6.2.2 Add SAP NetWeaver to SAP GUI and Log On For Windows
  2. In the opened SAP GUI window enter SU01 in the field right to the green Enter icon in the window toolbar in the upper left corner.
  3. Click green Enter icon to open transaction window User Maintennance: Initial Screen.
  4. In the User field enter DEVELOPER.
  5. Click the Lock/Unlock toobar icon.
  6. In the opened dialog you can read that the user DEVELOPER is locked. Click the Unlock icon in that window.
  7. After the DEVELOPER user is unlocked you should be able to log on also with DEVELOPER user to the backend system as described in week 1 - unit 6 - step 6.2.2 Add SAP NetWeaver to SAP GUI and Log On For Windows.

SAP NetWeaver AS ABAP / S/4HANA backend system

Redirect Url Html Code

TRBL B1: What is the password to access SAP NetWeaver AS ABAP?

You are trying to logon to your SAP NetWeaver AS ABAP system in your SAP Logon but cannot login to the ABAP system.

Check if you are trying with the correct ABAP user : developer and password : Appl1ance. See the steps described in Week 1 - Unit 6 - Install SAP GUI Client.

TRBL B2: SAP NetWeaver AS ABAP installation fails

You tried to install the ABAP from the install script which you downloaded from https://tools.hana.ondemand.com/#abap following Week 1 - Unit 6 - Install SAP GUI Client. If the installation finishes with message “Installation successful”, you can ignore the warnings which the script prints in the process of installation.

The installation script fails and stops with errors. The following could be reasons for the script to be fail:

Note: If the ABAP installation fails for whatever reason, you need to revert to the clean state of only with OpenSUSE installation. Revert to the snapshot state Initial Installation Snapshot and re-do the installation steps after this snapshot state.

  1. Check if you have partially downloaded or partially extracted the ABAP installation files as you will run into installation errors. Check the warning as described in Week 1 - Unit 6.
  2. Check if host name is set correctly as described in Week 1 - Unit 6.
  3. Check if your virtual machine has enough memory - 6 GB (4 GB is enough but the replication job in Week 4 works without failures with 6 GB) and enough hard disk space (80 GB) as described in Week 1 - Unit 6.
  4. Check if you have enough disk space in home drive. If you create 2 parititions in your Linux OS, home drive has smaller space though you have allocated 80 GB.

  5. Check if during the OpenSUSE installation, if you have unchecked the checkbox so that you have only one partition.

  6. To check the free space available in your home drive, switch to your running virtual machine Linux instance.
  7. Open the console application Konsole (KDE Application Menu and navigate to System > Konsole).

  8. Type the command df -h and check how much free space is available in your home drive. The free space in your home drive should at least be 35 GB.

  9. Check if uuidd is installed and started as described in Week 1 - Unit 6.
  10. Check if install.sh set to executable and if Installation started as root as described in Week 1 - Unit 6.
  11. The ABAP installation script also fails if you chose a weak password. The installation script accepts a weak password, but fails in a later stage.
  12. Choose a strong password of at least 8 characters with at least one number, one capital letter, one lowercase letter.
  13. If the installation script fails for another reason, you may try to revert to the snapshot state Initial Installation Snapshot and re-do the installation steps.

TRBL B3: SAP NetWeaver AS ABAP Slow

  • Any transcation/action called in the SAP NetWeaver AS ABAP for the first time triggers compilation of the relevant function modules. Subsquent call/action should be of normal speed.
  • As the VM is quite small: Please have some patience, second call usually will be faster. You can try to increase the RAM memory size to 6 GB and try again.
  • You need to stop the Virtual machine instance to increase the memory size.
  • Click on Settings and increase the memory size to 6 GB.

TRBL B4: SAP NetWeaver AS ABAP does not start

  • Check if UUIDs service is started as described in Week 1 - Unit 6.

TRBL B5: Developer key not accepted

  • Check if you have installed the DEMO license in your ABAP system as described in Week 1 - Unit 6.

TRBL B6: SAP S/4HANA system not running or crashed

  1. Stop the SAP NetWeaver SAP NetWeaver AS ABAP backend system and the VM as described in Week 1 - Unit 6.
  2. Start the VM andSAP NetWeaver SAP NetWeaver AS ABAP system as described in Week 1 - Unit 6.

SAP System Landscape Transformation Replication Server (SLT)

see Troubleshooting - SLT

Posted on  by  admin