Technical Articles
SAP Process Integration Test Tool (PIT) – First Steps
For an Overview about the PIT Tool please read the Blog
Process Integration Test Tool shipped with sap process orchestration
The PIT Tool is a framework with which you can setup automatic tests for process integration scenarios. The main idea is that successfully processed messages are extracted from the runtime of either an SAP Process Integration or a SAP Process Orchestration system (sources system). Those messages are stored in the PIT system’s data base and can later be replayed on a different system (target system). The replayed messages are gathered from the target system after the run. The results can be compared against the reference messages from the source.
In this very first version we can collect messages on the source side from “classical” PI dual stack scenarios, Integrated Configuration Objects (ICO) and Integration Flows. On the target side we support ICOs and Integration Flows.
Prerequisites
Sources System
- System has at least PI/PO 7.31 SP 17 or PI/PO 7.50 SP6 with patch level according to SAP Note 2650265
- SAP Notes 2650265, 2739354 and 2707854 are installed on the systems
- Only successfully processed messages are extracted
- Log with Payload is enabled for all three stages (BI, MS, AM) – that means logging shall be enabled for a particular scenario – SAP Help – how to turn the logging on
Target System
- Target system is PI-AEX or PO with at least 7.50 SP 14 with the latest Kernel Patch level
- For setting up the PIT tool at the target system, the CTC called PI Test Tool Target can be carried out. The following parameters will be set:
- Injector application com.sap.aii.pit.injector.app is deployed and running, and application property pit.injector.enabled = true
- For synchronous messages an HTTP destination should exists, which points to PIT and property pit.injector.response.destination.name contains the name of the destination (retrieve the response of the sync message) Default destination name PIT_SYSTEM need a user with the action pit_resp_retriever
Test Tool (PIT) System
- the PIT system is PI-AEX or PO with at least 7.50 SP 14 with the latest Kernel Patch level
- The configuration is done via CTC PI Test Tool
- JobHandlerJob is planned
- A HTTP or RFC destination is created in NWA for each system which shall be connected to PIT (HTTP and RFC in case of a Dual Stack Sources System)
The Configuration and the Test Run Starts will be done in the NetWeaver Developer Studio (NWDS)
Entry point in NWDS
Open the Perspective SAP Process Integration Test
Open preferences “SAP Process Integration Test” and define connection to PIT Tool system.
Now you are able to connect to the PIT System.
Now you can start to configure the Landscape.
Please have in your mind that each system that you connect to the PIT Tool System needs an http destination and each connected PI Dual Stack system also an RFC destination. This should be created in the NWA before maintaining the Test Systems in the PIT Test System Browser.
Don`t use the destination PIT_SYSTEM for this connection. It is a destination on the target system pointed to the PIT System for synchronous messages only.
Then you can start to add and to configure the test systems
You have a few possibilities for the Authentication Mechanism.
for more information please take a look at the SAP Help – Create Test System
The same system can be used as sources, PIT and target systems depending on the use case as long as it is a Java ( PI-AEX or PO) System with NW 7.50 SP14. In the migration use case, source and target system are different, in the regression use case however source and target may be the same.
Starting with SP15 the Decentral Adapter Engine is supported.
It can be loaded from the SLD or maintained manually.
After having setup the test landscape in your PIT System, you can start creating the first Test Case. For this, please check out the following blog.
SAP Process Integration Test Tool (PIT) – Create and Execute a Test Case
Hello Elke,
In your blog you said the following :
System has at least PI/PO 7.31 SP 17 or PI/PO 7.50 SP6 with patch level according to SAP Note 2650265
--> Do it mean that the source system can't be anPO 7.40 ?
It is not clear which release for the “Source System” is supported by the tools as I understood from your sentence 7.31 or 7.50 and not 7.40….?
It should be supported as from 7.XX to 7.XX but here as you mentionned only 2 release with an "or" I'm confused.
Thanks in advance for the clarification
Dominique./
Hi,
You can use as Source system all 7.31 SP 17 and higher.
You can use all 7.40 System with the equivalent SP from 7.31. SP17 - this is Java SP12 and SPS14 and higher.
You can use all 7.50 Systems 7.50 SP06 and higher.
Best Regards,
Elke Döring
HI Elke,
As this is a new tool i want to use it but before that i need some clarity.
Thanks,
Satish.
Hi Satish,
Best Regards,
Elke
Hi Elke,
thanks for the nice blog, this is a tool with really great potential.
A question though. Following your instructions, I am looking for the PIT perspective in NWDS 7.50 but it looks like it does not exist. Is there a specific version we need to have? Currently have downloaded 7/5/012/0009,
Regards,
Markos
Hi Markos,
The PIT client is implemented as an NWDS Plug-In.
You have selected the new perspective
(SAP Process Integration Test Tool) in the NWDS, as described here: Understanding User Interface.
You need at least a NW 7.50 SP14 version.
Best Regards,
Elke Döring
Hi Elke,
Thanks for this blog. These seems to be powerful tool especially for migration/regression tests.
We are currently on PO 7.5 SP11. I can see the option of test tool in NWDS perspective (using 7.5 SP14 version) but when I try to connect to this perspective, I get an error as 'Login failed, you are not authorized).
I know that its not supported by SP11 but will it not even allow us to use this perspective on SP11? Could it be problem with roles?
Thanks,
Varinder
Hi Elke,
just for clarify: do we need PO or is PI enough?
In you description you write that Source, Target and Test-Tool System must be PO or PI-AEX. But the link says "shipped with Process Orchestration" ??
So: PI-AEX (Single-Stack) is enough?
What about licenses? Do we need a special license for the Test-Tool-System?
Thanks,
Rene
Hi Varinder,
The PIT Software is shipped with NW 7.50 SP14 only. So you can't use it on SP11.
Hi Rene,
A PI-AEX is enough for the Test Tool and the Target.
As Source Systems you can also use PI Systems and also older version of it.
Best Regards,
Elke
HI Elke ,
Even i am using NWDS 7.5 SP15 i am getting same issue .
while trying to connect PIT i am getting "Login failed you are not authorized" . Is it required below roles need to add on my user before login PIT ?
SAP_PIT_TEST_DEVELOPER, SAP_PIT_LANDSCAPE_ADMINISTRATOR
Regards
Ramanjaneya Reddy
Hi
I am having the same issue, but realized that it's because the source server is not reachable in the network of my PIT server. So the error message is unfortunately misleading.
Furthermore, the role SAP_PIT_ADMINISTRATOR (on another suitable *pit* role like the Test Developer) is necessary on the test server in order to connect from NWDS .
Best Regards,
Philippe
Hi Elke,
I am using NWDS 7.5 SP14 but getting error as " Cannot create a new test system. Details: 'pwctrl' can not be mapped as a property or an annotation. [HTTP/1.1 400 Bad Request]". Do you please suggest if i am missing something here?
Thanks,
Gaurav Kant
Hi Gaurav,
please make sure that the latest patchlevels of the PIT Server and NWDS are installed on your system. If the issue persists even with the latest patch, please open a ticket for that issue in component BC-XI-PIT.
Kind regards,
Jan
Hello SAP team,
Can you please clarify on below:
Regards,
Naresh
Hi Naresh,
1. the Source Systems can be at least PI/PO 7.31 SP 17, PI/PO 7.40 SP12 or PI/PO 7.50 SP6 with patch level according to SAP Note 2650265
2. The Messages sended to the Target System can be seen in the normal message monitor. They have all the Connection Name PITTEST
3. the Messages triggered by the PIT Tool have the same live cycle as all other PI/PO messages
4. no
Best Regards, Elke
Hi Elke, This is a nice tool.
Can PIT be used for testing interface migration to CPI? Can CPI be configured as the Target System? If not, do you have it on your product roadmap?
Thanks
Nishant
Hi Nishant,
The tool can not be used with CPI as a target system. We can check if we can get it to the roadmap.
Best Regards,
Elke Döring
Hello Elke,
When I tried to create Test system, I get the below error:
I am using PO7.5, SP17. Same NWDS version is used.
Thanks
Shyamalima
Hi Shyamalima,
Please open a incident at SAP (BC-XI-PIT) in case you have error messages.
Best Regards,
Elke
Hello Elke,
We do not use NWDS for our PI Environment. However we are on PO 7.5 SP-17. Can we use NWDS only for the purpose of PIT or is it possible to PIT without NWDS and at Browser level only?
//Narender R.
Hello Narender R.
For the full funtionality of the PIT Tool you need to use the NWDS.
But you can of course use it olny for the PIT.
Best Regards,
Elke
Hello Elke,
Really thanks for the prompt response.
Please help me with below info:
//Narender R
Hi Narender,
Best Regards,
Elke Döring
Hello Elke,
I am unable to collect payload for classical scenario from source PI system(7.4 dual stack) getting below error notification. However, I am able to retrieve the payloads for ICO scenario from the same system.
Note :Both RFC and HTTP destinations are created in test system to connect to source. LOGGING is enabled in IE and BI,MS and AM is enabled in global setting of Adapter engine for payload logging.
Please help me with below error, is there any setting missing.
Error_PIT
Hello,
Please open a ticket for component BC-XI-PIT and attach the default trace to this ticket.
Best regards
Anna Winterholler
Hello ,
We are configuring PIT Tool and while creating Test case getting below error . Error Fetching Integrated Configurations. Any idea on this?
Regards,
Shradha
Hi Shradha,
Without any error message it is only guessing.
Please check the user roles for the user in the system destination with help of the documentation:
https://help.sap.com/viewer/adce595d012841ceb85db272fbd9e5f5/7.5.22/en-US/f20ede28717443539e13315d1a726b05.html
me be the role api_display_710 is missing.
Otherwise - please open a ticket for component BC-XI-PIT and attach the default trace to this ticket.
Best Regards,
Elke
Hi,
try to create a new destination again and use "provide authentication for each operation" + "always authenticate with this user" - everywhere, it solved this issue for me. Looks like SPS22 issue... worked before just fine.
Regards,
Marek
Hi,
We have configured PIT and were able to load test data, but upon running of the test case we are getting the following error.
Test Execution Failure: Failed to inject msg: javax.ejb.EJBAccessException: ASJ.ejb.005045 (Failed in component: sap.com/com.sap.aii.pit.injector.app, BC-XI-PIT) ASJ.ejb.003001 Principal: 'username' (authentication method: password), policyContextID: sap.com/com.sap.aii.pit.injector.app*com.sap.aii.pit.injector.ejb.jar, permission.name: MessageInjectorV1Impl, permission.actions: inject,ServiceEndpoint,com.sap.aii.pit.ws
We have enabled the injector application com.sap.aii.pit.injector.app . It is deployed and running and the property pit.injector.enabled is set to 'true'.
Please let me know how we can resolve this issue.
PS: I am attaching the screenshot of the error as well for reference.
Priyank
Hi Priyank,
Please check the authorization of the user - it needs the role SAP_PIT_INJECTOR: see the details at the docu
If this don't solve it pease open a ticket at BC-XI-PIT.
In this we need the landscape description, der Error message and please put also the Default trace in.
Best Regards,
Elke
Hi Elke
We are trying to configure the new PIT Tool on PO 7.5 Single stack at SP22. We have done the configurations as per standards but while retrieving messages from source system when we click on count, the system does not fetch anything and goes on retrieving forever without giving any error. Any insights on this would be highly appreciated.
Hi,
For me this looks like a network issue - but this is only a guess.
You can check the authorisation of all involved users.
https://help.sap.com/viewer/adce595d012841ceb85db272fbd9e5f5/7.5.22/en-US/f20ede28717443539e13315d1a726b05.html
You can also try to have a small time frame to collect only a few messages.
If this don't help - please create a a ticket at BC-XI-PIT.
Best Regards,
Elke
We try to import a message from a decentral adapter engine. But no messages will be found although the ICO is configured correct. Same we tried with a ICO in the central adapter engine here it works. I can't find any error messages in log file. What is the problem?
Hello Marcus,
please check if the HTTP destination to the Decentral Adapter Engine is configured correct:
Best regards
Anna
Hi Elke,
We use SAP PI 7.5 SP05, Dual Stack, in our environments (DEV, Q&A and PRD).
We also have an installation of SAP PO 7.5 SP15 in our environments (DEV, Q&A and PRD).
Below is a drawing illustrating our current Landscape:
Current Landscape
Our intention is to migrate the SAP PI 7.5 SP05 environments to the SP24 for SAP PI 7.5 (Dual Stack), using the SAP PIT that is available in SAP PO 7.5 SP15.
Below is a drawing of how we intend to use the SAP PIT tool to migrate the integrations from SAP PI 7.5 SP05 to SAP PI 7.5 SP24.
SAP PIT use
Based on the scenario described above, here are some of our questions:
At last, but not least, could you provide us with more material about the SAP PIT tool, please?
Thank you in advance for any clarification you can give me!
Hi José,
Please take a look at the SAP Online Help - What Is SAP Process Integration Test Tool for the information of the function the PIT Tool has, SAP Online Help - Chapter Technical Prerequisites for the information with release and SP the PIT Tool covers and at the note 3022858 for the information about the use of the Dual Usage Type as a target.
To created test cases on the PIT System you have to use the NWDS bases UI. The Web UI is only a UI for the tester itself and not for the test development. But this is also described in the Online
Best Regards, Elke