Below is a summary of the steps on how to install the SAP Cloud Connector on openSUSE and make a connection from SAP Netweaver ABAP to the SAP Cloud Platform (SCP).
Install the software
- Download the latest version of the SAP Cloud Connector from SAP Development Tools.
- Start your instance of SAP Netweaver using startsap ALL.
- Extract the zip file and install the cloud connector using the rpm command.
rpm -i com.sap.scc-ui-2.10.2-1.x86_64.rpm
- Check the status of the cloud connector.
pravin@vhcalnplci:~> sudo service scc_daemon status
[sudo] password for root:
* scc_daemon.service – LSB: LJS Daemon
Loaded: loaded (/etc/init.d/scc_daemon; bad; vendor preset: disabled)
Active: active (exited) since Tue 2018-01-16 12:08:26 AEDT; 26min ago
Process: 3323 ExecStart=/etc/init.d/scc_daemon start (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 512)
Jan 16 12:08:25 vhcalnplci systemd: Starting LSB: LJS Daemon…
Jan 16 12:08:25 vhcalnplci scc_daemon: Starting scc_Daemon
Jan 16 12:08:25 vhcalnplci su: (to sccadmin) root on none
Jan 16 12:08:25 vhcalnplci su: pam_unix(su:session): session opened for user sccadmin by (uid=0)
Jan 16 12:08:25 vhcalnplci scc_daemon: [1B blob data]
Jan 16 12:08:25 vhcalnplci scc_daemon: osgi>
Jan 16 12:08:26 vhcalnplci scc_daemon: osgi>
Jan 16 12:08:26 vhcalnplci scc_daemon: scc_Daemon started.
Jan 16 12:08:26 vhcalnplci systemd: Started LSB: LJS Daemon.
Jan 16 12:08:44 vhcalnplci scc_daemon: Cloud Connector 2.10.2 started on https://localhost:8443 (instance role is undefined)
- Open the SAP cloud connector logon page by using https://localhost:8443.
- Enter username Administrator (case-sensistive) and password (initial password is manage).
- You will be asked to type a new password.
- For Installation Type, choose Master.
- Click on save.
- Enter the Region Host, Subaccount, Display Name, Subaccount User and Password. Ensure Location ID is empty.
- If everything is ok, you will get the following screen.
Check connection in SAP Cloud Platform Trial Account
- In SAP Cloud Platform, click on Connectivity->Cloud Connectors.
- The green connected message shows that you have successfully connected SCP to the on-premise ABAP server.
The next step is to expose your on-premise system with the proper access control.
Expose the ABAP back-end using Access Control
- Open the SAP Cloud Connector admin cockpit.
- Click on Cloud To On-Premise and Select Access Control.
- Enter the following information:
- Back-end Type – ABAP System
- Protocol – HTTPS
- Internal Host – localhost and Internal Port – 44300
- Virtual host – s4h and virtual port – 443
- Principle type – Kerberos
- Check Internal Host – on
- You must also specify Accessible Resources. For URL path, enter /sap/ and choose Path and all sub-paths.
- In the SCP trial account, check Connectivity->Cloud Connectors. The exposed system should be visible now.
Create Destination on SAP Cloud Platform
We need to create a destination with the data below so that SAP Web IDE can refer to the back-end system.
The property WebIDEUsage has 4 usages:
- odata_abap (for oData from abap system; allows service to appear in Service Catalog in SAP Web IDE.
- dev_abap (for extending SAPUI5 applications)
- ui5_execute_abap (for executing SAPUI5 applications from ABAP system)
- bsp_execute_abap (for working with fact sheets)
Detailed description of the usages can be found here.
Check the connection of the destination.
Now, the SAP Netweaver ABAP server is available from SCP via the virtual host
http://s4h:443. It can be used for oData access.
Detailed step-by-step guidance can be viewed from openSAP.