Connect to NetWeaver ABAP instance running inside Docker

Let the world know ...Tweet about this on Twitter
Twitter
Share on Google+
Google+
0Share on Facebook
Facebook
0Email this to someone
email
Share on LinkedIn
Linkedin

This blog will help you to connect to your SAP NetWeaver ABAP instance running inside a Docker container. For how to get NetWeaver running inside a Docker container, please see my blog Docker for SAP NetWeaver ABAP 7.5x Developer Edition.

SAPGui

Open SAPGui and create a new connection.

Give a name for the connection and click on tab Advanced. I use NPL Docker. Activate expert mode and give the correct connection String. Check to which port the message server port is mapped to by Docker. Inside the container, the port is 3200, and in my case, the external port is 32771. Therefore, the connection String is:

Connection String: conn=/H/localhost/S/32771

Note: the port information is specified when you start the container. As an alternative, you can use Kitematic to see the port mapping.

Save and connect to NetWeaver.

The users and passwords can be found in the readme.html of the extracted SAP NW ABAP 751 download. Standard users are SAP* and Developer.

HTTP Access

You can test if access to your new SAP system is working via HTTP by calling the ping service: http://localhost:32769/sap/public/ping

For this to work, first activate the ping service in SICF.

When you get the response “Server reached.” you can start using the HTTP access.

SAP WebGui

For general WebGui activation, you can see my previous blog “Activation of SAP WebGui”. Here is a short version of this guide. As in the previous HTTP service access, the same procedure must be followed to have access to NPL via WebGui.

Activate the service webgui

To activate the SAP WebGui service, activate the node:

/sap/bc/gui/sap/its/webgui

Activation of public resources

You also need to activate the public service that contains the HTML files (JS, etc):

/sap/public/bc/its

Note

It is not sufficient to only activate the webgui node. The app is using additional resources that are available under /sap/public/bc/its. If this node is not activated, you’ll get an error message when logging in to webgui.

Therefore, for SAP WebGui to load the node /sap/public/bc/its must be activated too.

Activate the node its and its subnodes. Select Activate Service.

Activate with all sub nodes nodes (second Yes).

Result

After activating these two nodes, access to WebGui should work. To test this, call the URL http://localhost:32769/sap/bc/gui/sap/its/webgui After logging in, you should see the SAP Menu.

Let the world know ...Tweet about this on Twitter
Twitter
Share on Google+
Google+
0Share on Facebook
Facebook
0Email this to someone
email
Share on LinkedIn
Linkedin

SAPGui Maximum runtime exceeded

Let the world know ...Tweet about this on Twitter
Twitter
Share on Google+
Google+
0Share on Facebook
Facebook
0Email this to someone
email
Share on LinkedIn
Linkedin

Systems you work with have a timeout parameter. You may be logged on or an anonymous user, in both cases the system creates a session for you and controls its lifetime. This is not to remind you to get your work done rapidly, but mostly to ensure that a long living session is not eating up too much resource (so, short, yes, it is to ensure you get your work done rapidly). The timeout period for a session depends on your system. Normal time is between 10 minutes to 30 minutes. In a SAP NetWeaver ABAP system, the time is set by default to 10 minutes, or 600 seconds. The counter is reset each time a commit is issued by the running ABAP program.

It can, however happen that you reach a timeout.

What to do? I have to say that my system was a little bit busy. I restarted my dev system and all went back into normal. As an alternative, you can change the timeout parameter. How to do this and why you should not do this is explained in SAP Note 25528.

  • Profile parameter: rdisp/max_wprun_time
  • Tx: RZ10 (permanent change)
  • Tx: RZ11 (only until next restart)
Let the world know ...Tweet about this on Twitter
Twitter
Share on Google+
Google+
0Share on Facebook
Facebook
0Email this to someone
email
Share on LinkedIn
Linkedin

FND – 62 – Create outbound destination for content publisher

Let the world know ...Tweet about this on Twitter
Twitter
Share on Google+
Google+
0Share on Facebook
Facebook
0Email this to someone
email
Share on LinkedIn
Linkedin

The configuration steps to be executed on the HUB system (FND) are detailed at SAP Help.

  1. Maintaining Inbound bgRFC Queue on the Hub System SAP Help
  2. Create outbound destination for content publisher SAP Help

This document explains how to execute step 2.

When a mobile user subscripes for push notification, he/she basically informs SAP Gateway to receive updates on a collection. As Gateway handles subscriptions in a pretty abstract way, the user needs to inform some information during the subscription process. One of these informations is the communication channel. This channel corresponds to a HTTP destination created at the HUB system.
SAP Help

A user subscribing will pass the following channel information to Gateway: urn:sap-com:channel:<CHANNEL_NAME>/<unique_ID_of_device

The first part (urn:sap-com:channel) is used by OData as a keyword to filter and extract the name of the channel. The channel name is a HTTP destination created in SM59. I’ll use SMP_PUSH. This implies that you can have several push destinations for a single SAP Gateway system.

No SPRO activity

All activities are done on the SAP Gateway HUB (FND) system.

  1. Create HTTP Destination
  2. Transaction SM59


  3. New Destination


  • RFC Destination: SMP_PUSH
  • Connection Type: G


  1. Go to tab “Technical Settings”
  • Target host: Host of SMP 3 (smp3.tobias.de)
  • Service No: HTTP Port of SMP 3 (8080, depends on your configuration)
  • Path Prefix: Prefix used by SMP 3 for push notifications (/Notification/)


  1. Go to tab “Logon & Security


  • User: SMP Push user (smppush)
  • Password: password of SMP Push user
  1. Save
  2. Test destination

Let the world know ...Tweet about this on Twitter
Twitter
Share on Google+
Google+
0Share on Facebook
Facebook
0Email this to someone
email
Share on LinkedIn
Linkedin

FND – 61 – Maintaining Inbound bgRFC Queue on the Hub System

Let the world know ...Tweet about this on Twitter
Twitter
Share on Google+
Google+
0Share on Facebook
Facebook
0Email this to someone
email
Share on LinkedIn
Linkedin

The configuration steps to be executed on the HUB system (FND) are detailed at SAP Help.

  1. Maintaining Inbound bgRFC Queue on the Hub System SAP Help
  2. Create outbound destination for content publisher SAP Help

This document explains how to execute step 1.

“SAP NetWeaver Gateway uses inbound queues to reliably send information to a consumer (Such queues are used by various services. For example, the Notification Content Publisher). These inbound queues use bgRFC (Background Remote Function Call) technology.”
SAP Help

No SPRO activity

All activities are done on the SAP Gateway HUB (FND) system.

  1. Creating RFC Destination for Inbound Queue
    1. Transaction SM59


    2. Create new connection


  • RFC Destination: IWFND_ODATA_PUSH.
  • Connection Type: 3


  1. Go to tab “Special Options
  • Transfer Protocol: Classic with bgRFC.


  1. Save
  2. Test RFC destination


    Result


     

  1. Registering RFC Destinations for Inbound Queue
    1. Transaction: SBGRFCCONF


    2. Go to tab “Define Inbound Dest.
    3. Create


  • Inb. Dest. Name: IWFND_ODATA_PUSH


  1. Save.


     

  2. Go to tab: “Scheduler: Destination
  3. Create


  • Type: Inbound


  • Destination: IWFND_ODATA_PUSH


  1. Save

Let the world know ...Tweet about this on Twitter
Twitter
Share on Google+
Google+
0Share on Facebook
Facebook
0Email this to someone
email
Share on LinkedIn
Linkedin

FND – 5 – Activate SAP NetWeaver Gateway

Let the world know ...Tweet about this on Twitter
Twitter
Share on Google+
Google+
0Share on Facebook
Facebook
0Email this to someone
email
Share on LinkedIn
Linkedin

The configuration steps to be executed on the HUB system (FND) are detailed at SAP Help. The steps are for the OData Channel Service for backend system.

  1. Basic configuration activities: SAP Help
    • Set profile parameters to support SSO2 SAP Help
    • Activate ICF Services Blog / SAP Help
  2. User & Authorization SAP Help
  3. SAP Gateway to Consumer (FND to SMP3) SAP Help
    1. Creating a bgRFC destination for outbound queues Blog SAP Help
    2. Registering bgRFC destination for the oubound queue Blog SAP Help
    3. Creating bgRFC supervisor destination Blog SAP Help
  4. SAP Gateway to SAP Backend (FND to BEP) SAP Help
    1. Create RFC on SAP Gateway (FND) to SAP backend (BEP) Blog SAP Help
    2. Define trust between SAP Gateway and SAP backend (FND <-> BEP) Blog SAP Help
    3. Configure SAP backend system (BEP) to accept assertion ticket from SAP Gateway Blog SAP Help
    4. Configure SAP Gateway (FND) to accept assertion ticket from SAP backend (BEP) BlogSAP Help
    5. Configure SAP system alias for applications BlogSAP Help
  5. Activate SAP NetWeaver Gateway SAP Help

This document explains how to execute step 5.

The final step is to activate the SAP Gateway functionality. SAP Help

SPRO: SAP Reference IMG and navigate to:  SAP NetWeaver Gateway OData Channel Configuration Activate or Deactivate SAP NetWeaver Gateway


  1. Execute the activity. Confirm the dialog to activate SAP Gateway
  2. Result:

Let the world know ...Tweet about this on Twitter
Twitter
Share on Google+
Google+
0Share on Facebook
Facebook
0Email this to someone
email
Share on LinkedIn
Linkedin

FND – 42 – Define trust between SAP Gateway and SAP backend

Let the world know ...Tweet about this on Twitter
Twitter
Share on Google+
Google+
0Share on Facebook
Facebook
0Email this to someone
email
Share on LinkedIn
Linkedin

The configuration steps to be executed on the HUB system (FND) are detailed at SAP Help. The steps are for the OData Channel Service for backend system.

  1. Basic configuration activities: SAP Help
    • Set profile parameters to support SSO2 SAP Help
    • Activate ICF Services SAP Help
  2. User & Authorization SAP Help
  3. SAP Gateway to Consumer (FND to SMP3) SAP Help
    1. Creating a bgRFC destination for outbound queues SAP Help
    2. Registering bgRFC destination for the oubound queue SAP Help
    3. Creating bgRFC supervisor destination SAP Help
  4. SAP Gateway to SAP Backend (FND to BEP) SAP Help
    1. Create RFC on SAP Gateway (FND) to SAP backend (BEP) SAP Help
    2. Define trust between SAP Gateway and SAP backend (FND <-> BEP) SAP Help
    3. Configure SAP backend system (BEP) to accept assertion ticket from SAP Gateway SAP Help
    4. Configure SAP Gateway (FND) to accept assertion ticket from SAP backend (BEP) SAP Help
    5. Configure SAP system alias for applications SAP Help
  5. Activate SAP NetWeaver Gateway SAP Help

This document explains how to execute step 4.2.

A trust relationship between IWFND and BEP is needed to allow for SSO.
SAP Help

No SPRO activity.

Transaction SMT1


Trust relationship wizard opens


Inform a RFC destination: ECCCLNT001 (created in previous step)


Click continue. Basic connection checks are done

Continue

Continue

Complete

Let the world know ...Tweet about this on Twitter
Twitter
Share on Google+
Google+
0Share on Facebook
Facebook
0Email this to someone
email
Share on LinkedIn
Linkedin

FND – 41 -Create RFC on SAP Gateway (FND) to SAP backend (BEP)

Let the world know ...Tweet about this on Twitter
Twitter
Share on Google+
Google+
0Share on Facebook
Facebook
0Email this to someone
email
Share on LinkedIn
Linkedin

The configuration steps to be executed on the HUB system (FND) are detailed at SAP Help. The steps are for the OData Channel Service for backend system.

  1. Basic configuration activities: SAP Help
    • Set profile parameters to support SSO2 SAP Help
    • Activate ICF Services SAP Help
  2. User & Authorization SAP Help
  3. SAP Gateway to Consumer (FND to SMP3) SAP Help
    1. Creating a bgRFC destination for outbound queues SAP Help
    2. Registering bgRFC destination for the oubound queue SAP Help
    3. Creating bgRFC supervisor destination SAP Help
  4. SAP Gateway to SAP Backend (FND to BEP) SAP Help
    1. Create RFC on SAP Gateway (FND) to SAP backend (BEP) SAP Help
    2. Define trust between SAP Gateway and SAP backend (FND <-> BEP) SAP Help
    3. Configure SAP backend system (BEP) to accept assertion ticket from SAP Gateway SAP Help
    4. Configure SAP Gateway (FND) to accept assertion ticket from SAP backend (BEP) SAP Help
    5. Configure SAP system alias for applications SAP Help
  5. Activate SAP NetWeaver Gateway SAP Help

This document explains how to execute step 4.1.

A RFC connection between SAP Gateway HUB and SAP backend is needed so that the HUB system can communicate with BEP. Without this, the OData services exposed at Gateway won’t work, as they cannot map the services (BAPIs) to a backend.
SAP Help

SPRO: SAP Reference IMG and navigate to:  SAP NetWeaver Gateway OData Channel Configuration Connection Settings SAP NetWeaver Gateway to SAP System Manage RFC Destinations

This open transaction SM59

  • Create

  • Give a name for the RFC destination, like <SID>CLNT<Client>
  • RFC Destination: ECCCLNT001 (example)
  • Connection type: 3
  • Inform a description
  • Go to tab “Technical Settings
    • Load balancing: Yes or No, depending on landscape
    • Target host: host name of SAP backend (BEP) system
    • System number: system number of SAP backend (BEP) system

  • Go to tab “Logon & Security
    • Client: cliente of BEP system
    • Current User: Yes
    • Trust Relationship: Yes


  • Go to tab “Special Options
    • Transfer Protocol: Classic with tRFC


  • Save
Let the world know ...Tweet about this on Twitter
Twitter
Share on Google+
Google+
0Share on Facebook
Facebook
0Email this to someone
email
Share on LinkedIn
Linkedin

FND – 33 – Creating bgRFC supervisor destination

Let the world know ...Tweet about this on Twitter
Twitter
Share on Google+
Google+
0Share on Facebook
Facebook
0Email this to someone
email
Share on LinkedIn
Linkedin

The configuration steps to be executed on the HUB system (FND) are detailed at SAP Help. The steps are for the OData Channel Service for backend system.

  1. Basic configuration activities: SAP Help
    • Set profile parameters to support SSO2 SAP Help
    • Activate ICF Services SAP Help
  2. User & Authorization SAP Help
  3. SAP Gateway to Consumer (FND to SMP3) SAP Help
    1. Creating a bgRFC destination for outbound queues SAP Help
    2. Registering bgRFC destination for the oubound queue SAP Help
    3. Creating bgRFC supervisor destination SAP Help
  4. SAP Gateway to SAP Backend (FND to BEP) SAP Help
    1. Create RFC on SAP Gateway (FND) to SAP backend (BEP) SAP Help
    2. Define trust between SAP Gateway and SAP backend (FND <-> BEP) SAP Help
    3. Configure SAP backend system (BEP) to accept assertion ticket from SAP Gateway SAP Help
    4. Configure SAP Gateway (FND) to accept assertion ticket from SAP backend (BEP) SAP Help
    5. Configure SAP system alias for applications SAP Help
  5. Activate SAP NetWeaver Gateway SAP Help

This document explains how to execute step 3.3.

The supervisor destination for bgRFC receives the configuration settings for the bgRFC scheduler and also starts or stops the schedulers as required.
SAP Help

SPRO: SAP Reference IMG and navigate to:  SAP NetWeaver Gateway OData Channel Configuration Connection Settings SAP NetWeaver Gateway to Consumer Create bgRFC Supervisor Destination

This open transaction SBGRFCCONF

  1. Go to tab “Define Supervisor Dest.
  2. Create

  • Destination Name: BGRFC_SUPERVISOR
  • User name: user name

  1. Save
  2. Select “Generate Password
  3. Save

Let the world know ...Tweet about this on Twitter
Twitter
Share on Google+
Google+
0Share on Facebook
Facebook
0Email this to someone
email
Share on LinkedIn
Linkedin

Gateway – Activate ICF Services

Let the world know ...Tweet about this on Twitter
Twitter
Share on Google+
Google+
0Share on Facebook
Facebook
0Email this to someone
email
Share on LinkedIn
Linkedin

Gateway exposes services via HTTP, therefore the Gateway services must be activated on the NetWeaver ABAP system. As HTTP services are run by ICF, they are controlled by transaction SICF. The services to be activated for Gateway system that d not care about compatibility mode for SP02 are

  • /sap/public/opu
  • /sap/opu/odata

More information: SAP Help

These services are activated by activating the corresponding node and all sub elements.

Sap/public/opu

  1. Go to transaction SICF
  2. Execute and navigate to sap/public/opu

  3. Select Activate Service
  4. Select Yes

  5. Node is activated

/sap/opu/odata

  1. Go to transaction SICF

  2. Execute and navigate to sap/opu

  3. Select Activate Service
  4. Select Yes

  5. Node is activated

  6. Make sure that the handler for /sap/opu/odata is /IWFND/CL_SODATA_HTTP_HANDLER

Let the world know ...Tweet about this on Twitter
Twitter
Share on Google+
Google+
0Share on Facebook
Facebook
0Email this to someone
email
Share on LinkedIn
Linkedin