Skip to Content
Author's profile photo Former Member

Creation of an SLD connection from ABAP backend to AEX SLD

All ABAP backend systems involved in a PI/AEX integration scenario need to be connected to the SLD. There are a lot of guides and overviews available on SCN how this is done. However, I wanted to create a complete overview in my blog since the existing blogs are still missing the one or the other detail I was looking for during my first SLD connection setup.

The following sections describe the SLD connection of an ABAP backend system to an AEX (Java-Only) 7.31 which also hosts the SLD (same hostname).

I. Overview

The main steps which need to be performed to set up a proper SLD connection are the following:

1st step: Definition of the SLD access data (hostname and user) which should be used to connect to the SLD on AEX

2nd step: Setup of the SLD data supplier connection

3rd step: Check of SLD connection

II. Detailed Setup Description

1st Step: Definition of access data:

The settings in transaction SLDAPICUST define where the ABAP system goes to read SLD data from if required. These settings have nothing to do with writing ABAP system data to the SLD. This part is setup in the 2nd step (transaction RZ70).

     a. Start transaction SLDAPICUST

     b. Select access via HTTP, enter an Alias, the hostname of the SLD (AEX), port and the user to be used to

        connect to the SLD (standard SLD users are automatically created during installation of the SLD): 

        IMPORTANT: In older ABAP stacks, the HTTP option of RZ70 is not available yet. In this case only connection

                               via RFC (former connection) is possible.

                               In this case please refer to the SAP Help for further details how to set this up.

         

     c. Enter the password for the used SLD user by clicking on the “Passwort” button.

     d. Test the connection by clicking on the “Test” icon. A green status should be displayed. If this is not the case,

         check again the hostname, port, user and password which you entered to connect to the SLD.

        

2nd Step: Setup of the SLD data supplier connection

The data provided in in transaction RZ70 define where the ABAP system is writing SLD system data to. It doesn’t define where the ABAP SAP system reads SLD data. This is defined in transaction SLDAPICUST (see step 1).

As soon as the data is provided in transaction RZ70, the system automatically creates two RFC connections SLD_UC and SLD_NUC in transaction SM59 which are used to connect to the SLD. If these connections are manually deleted you can automatically recreate them by saving the settings again in transaction RZ70.

     a. Start transaction RZ70

     b. Enter the gateway hostname and the gateway service name. If you don’t know the correct values, choose the

         same as available in SLD at (see below screenshot):

         http://<SLD hostname>:<port>/sld
         => Administration => Details => Data Suppliers

         

        Enter the values in transaction RZ70:

         

     c. Start data collection:

         For immediate data collection click the start button, otherwise schedule a background job for regular data

         collection.

3rd Step: Check of SLD connection

     a. Start transaction SLDCHECK

     b. The SLD needs to open in a browser window and all status value need to be green

        

        



Assigned tags

      10 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      HI,

      I have installed SAPPO 7.4 and trying to connect ECC6.0 EHP5 SP14 with PO.

      IN transaction SLDAPICUST, I can't see the option to select access via HTTP.

      SO Do I need to create SAPSLDAPI RFC of type T.

      Please suggest.

      Thanks,

      Roohi

      Author's profile photo Former Member
      Former Member
      Blog Post Author

      Hello Roohi,

      Yes correct. Choose type T.

      Best Regards

      Harald

      Author's profile photo Former Member
      Former Member

      Thanks Harald,

      I created RFCs and Jcos .. it worked.. 🙂

      Author's profile photo Harish Babu
      Harish Babu

      Hi Harald,

      What is the exact value to be entered in the RZ70 to write to the SLD. Do we have to enter the same as in SLD -> Administration -> Details -> Data Suppliers or we have to add something else there?

      I felt this line a bit ambiguous that " if you don't know the correct values, choose the same as available in the SLD".

      Regards

      Harish Babu

      Author's profile photo Former Member
      Former Member
      Blog Post Author

      Hi Harish,

      Correct. You have to enter the same values as in SLD -> Admin. -> Details -> Data Suppliers (gateway host and gateway port)

      I meant if you don't know which gateway host/port to be entered here, check the SLD.

      Best Regards

      Harald

      Author's profile photo Marcos Cristiano Ickert
      Marcos Cristiano Ickert

      Hi Harald Bitzer, nice post.

      We upgraded our PI to version 7.4 and after that, we cannot run RZ70 as expected for. Show us this error:

      tail -20 dev_rfc9

      **** Trace file opened at 20141204 114123 BRST, by disp+work

      **** Versions SAP-REL 742,0,17 RFC-VER U 3 1521276 MT-SL

      ======> CPIC-CALL: 'ThSAPOCMINIT', communication rc: CM_PARAMETER_ERROR (cmRc=19), taskhandler rc: TP_REG_ACCESS_DENIED (thRc=748)

      Internal error, session terminated

      ABAP Programm: RSRFCPIN (Transaction: SM59)

      User: DDIC (Client: 001)

      Destination: SLD_NUC (Handle: 2, DtConId: 54800D2C358331A8E10000000A010408, DtConCnt: 0, ConvId: ,)

      EPP RootContextId: 9C8E991A1D881ED49EF3E7F0906C6F9E, ConnectionId: 00000000000000000000000000000000, ConnectionCnt: 0

      EPP TransactionId: 54800D29358331A8E10000000A010408

      Error RFCIO_ERROR_SYSERROR in /bas/742_REL/src/krn/rfc/abrfcpic.c : 1726

      CPIC-CALL: 'ThSAPOCMINIT', communication rc: CM_PARAMETER_ERROR (cmRc=19), taskhandler rc: TP_REG_ACCESS_DENIED (thRc=748)

      Internal error, session terminated

      DEST =SLD_NUC

      HOST =%%RFCSERVER%%

      PROG =SLD_NUC

      GWHOST =<SOLMAN_SERVER>

      GWSERV =sapgw01

      Have you ever seen this error before?

      Thanks

      Marcos

      Author's profile photo Former Member
      Former Member
      Blog Post Author
      Author's profile photo Former Member
      Former Member

      Hi ,

      If your issue is not resolved yet then try adding

      gw/acl_mode =0 parameter in your SCS profile for PI 7.4 JAva stack.

      and restart system.

      Thanks,

      Roohi

      Author's profile photo Jens Schwendemann
      Jens Schwendemann

      This will deactivate security. Not recommended .

      Author's profile photo Former Member
      Former Member

      Hi,

        I followed through this blog and i was able to connect my ECC 6 EHP 7 (the data supplier) to PO 7.4 (the SLD server).

        Suggestion from Roohi was very key for it work for me.

        Great blog.

      regards,

      BO