ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

SAP JCO 3.1 causes SAP Agent not to start

book

Article ID: 199024

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic Workload Automation - Automation Engine

Issue/Introduction

The SAP agent is unable to start up, when the Java Connector version 3.1. is used, and when a very restrictive role policy is applied to the CPIC user.

 

In the SAP agent logs:

=========================================================================
20200812/092445.435 - U02004165 Connection 'SAPS4X_CONN_UC4RFC' param 'rfcSystem_name=S4X'
20200812/092445.438 - U02004999 Max. Number of RFC Connections: 'UNLIMITED'
20200812/092446.109 - U02004172 Error while calling function module 'RFC_SYSTEM_INFO'.
20200812/092446.109 -           Keine RFC-Berechtigung für Funktionsbaustein RFC_METADATA_GET.
20200812/092446.121 - U07001001 Charset used by the Agent: 'ISO-8859-15'
20200812/092647.377 - U02004172 Error while calling function module 'RFC_SYSTEM_INFO'.
20200812/092647.377 -           Keine RFC-Berechtigung für Funktionsbaustein RFC_METADATA_GET.
20200812/092848.240 - U02004172 Error while calling function module 'RFC_SYSTEM_INFO'.
20200812/092848.241 -           Keine RFC-Berechtigung für Funktionsbaustein RFC_METADATA_GET.
20200812/093049.275 - U02004172 Error while calling function module 'RFC_SYSTEM_INFO'.
20200812/093049.275 -           Keine RFC-Berechtigung für Funktionsbaustein RFC_METADATA_GET.
20200812/093250.557 - U02004172 Error while calling function module 'RFC_SYSTEM_INFO'.
20200812/093250.558 -           Keine RFC-Berechtigung für Funktionsbaustein RFC_METADATA_GET.

=========================================================================

Similar messages can be found in the RFC trace of the Java Connector. (insufficient rights for accessing the function module 'RFC_METADATA_GET.'.

If the CPIC user has superuser rights (SAP_ALL, SAP_NEW) assigned to his profile the Agent starts without problem.



Cause

SAP introduced a few changes in the JCO 3.1.x, additional rights are necessary to the CPIC user.

Environment

Java Version : 1.8.0_171 Oracle Corporation
SAP Agent: 12.2.3+build.1558087575343
Java Connector: 3.1.2 

Resolution

1. Extend the S_RFC roles of the CPIC at least to function group RFC_METADATA. Refer to this part of the documentation for guide lines:

https://docs.automic.com/documentation/webhelp/english/AA/12.3/DOCU/12.3/Automic%20Automation%20Guides/help.htm#AWA/Integration/SAPSecurityObjects.htm

 

2. Verify that the SAP note 460089 is installed

 

3..Force the java option Djco.use_repository_roundtrip_optimization=0 to the startup command of the SAP Agent

/usr/bin/java -jar -Xmx256M -Djco.use_repository_roundtrip_optimization=0 <SAP_AGENTPATH> /bin/ucxjr3x.jar

 

SAP Explanations to this parameter:

jco.use_repository_roundtrip_optimization If set to 1, the JCo repository tries to use the function module for roundtrip optimization for metadata lookups. (Default: 0)

See SAP note 1456826 regarding back-end prerequisites.

 

More information to that topic can be take from the followin link:

https://www.int13h.nl:8443/_content/SAPDocuments/JCo_API_3_0/com/sap/conn/jco/JCo.html