(Glue-2405) SNP Java Connector Setup

Owned by SNP
May 21, 2024
4 min read

This guide will show you how to perform the setup (SM-Latest) Java Connector Setup.

After you have imported transports for SNP Reuse Library, SNP GLUE, and SNP Java Connector continue with the prerequisites for the setup of SNP Java Connector:

  1. Create JAVA_CONN RFC (SM59):

    1. Connection type: TCP/IP Connection.

    2. Activation type: Registered Server Program.

    3. Fill in Program ID (e.g.): JAVA_CONN.

  2. Creation of Technical SAP user for ABAP->JCO RFC Communication:

    1. In transport, you are provided with a template role with name /DVD/JCORFC (if you decide to use the role shipped in transport, please do not forget to generate the profile in transaction PFCG).

    2. Create System user, with role /DVD/JCORFC.

  3. Granting access for external program JAVA_CONN to SAP gateway

    1. Check SMGW > GoTo > Expert Functions > External Security > Maintenance of ACL files whether external programs are allowed (=* or ProgramID).

Once you are done with the prerequisites follow these steps:

  1. Enter the SNP Java Connector management via transaction /DVD/JCO_MNG:

    1. A pop-out window will appear explaining the difference between Local and Standalone SNP JCO deployment. Choose Deploy local JCO,

  2. You will be redirected to the main page of SNP JCO management.

  3. Double-click on the JCO you want to configure and then click on the Edit button.

  4. The toolbar will change and provide you with new options, click on Fill default values. We will explain the feature in the following steps.

  5. In the JCO management, you can see several tabs (General, Config, Libraries, Advanced):

    1. In the General tab, fill in the RFC destination, you have created in prerequisites.

    2. In the Config tab, you will need to populate the field for RFC user which you have created in prerequisites.

    3. In the Libraries tab, newest package of libraries is selected by Fill default values functionality.

    4. In the Advanced tab, you will see the biggest advantage of Fill default values feature, all parameters are pre-filled with values for Standard deployment. Optionally, you can adjust Log4j log level to the Trace level for more detailed logs and Log4j log deletion parameter to set log retention based on your preferences.

  6. Click on the save button in the SAP GUI toolbar.

  7. Navigate back to the General tab and click the Restart button:

    1. You can follow the steps of the first start of JCO in the bottom left corner of JCO.

  8. The first start can take a little bit longer, because of the deployment of the libraries package on the operating system of the SAP application server is happening.

  9. Successful start will be marked with a green tick next to the restart button.

     

Verification of functionality

Option 1:

  1. Go to transaction SM59 and perform a connection check on RFC which is used for SNP JCO.

  2. If your JCO is working properly result of the test should look like this:

 

Option 2:

  1. Go to transaction SMGW.

  2. In the menu click on GoTo >Logged on Clients.

  3. In the list, you should see (based on the Connection count parameter in the Advanced tab of JCO management) 10 records of Registered programs with names you have entered in the RFC destination configuration.

     

If both tests are successful, you are ready to proceed with the creation of storage connections to your target of choice.