Testing requirements
Review the software and system requirements for using the SAP capabilities with HCL DevOps Test Integrations and APIs (Test Integrations and APIs).
SAP systems and product libraries
- SAP R/3 4.7
- SAP ECC 5.0
- SAP ECC 6.0
sapjco3.jar
, is required.sapjco3.dll
file must be present within the system path; for example, C:\WINDOWS\System32.sapidoc3.jar
, is required.sapjco3.jar
and sapidoc3.jar
must be 7.11.x. To determine the internal version, extract the JAR files and use a text editor to open META-INF/MANIFEST.MF
. The internal version is recorded in a line similar to the following: Specification-Version: 7.11.1
.You can download the SAP JCo and IDoc libraries from the SAP Service Marketplace website. The architecture of the library must be the same as that of Test Integrations and APIs. For example, if you have installed the 64-bit version of Test Integrations and APIs, ensure that you download the 64-bit Java Connector.
SAP application server requirements
Before you use Test Integrations and APIs with your SAP system, you need an SAP user ID and password that enable access to a dedicated SAP application server. You need authorization from your SAP system administrator to execute remote function calls (RFCs) and access tables in SAP. Such authorization is required to extract metadata from the Business Object Repository (BOR) so that Business Application Programming Interfaces (BAPIs) can be tested with Test Integrations and APIs.
Specifically, ensure that the following RFCs can be executed successfully from transaction SE37 in your SAP GUI: SWO_QUERY_API_OBJTYPES and SWO_QUERY_API_METHODS.
Your login parameters specify the correct language. BAPIs specific to a particular language are not retrieved if you log into SAP with a different language.