Searching SAP PI/PO message content with module development

Facebooktwittergoogle_pluslinkedintumblr
internet search conceptI was talking with a fried around searching content and how easy it would be to implement your own search solution.
After taking a look at search APIs, such as Amazon’s, and having long discussions with a friend, I came across this useful page: https://www.searchify.com/documentation/java-client
I thought it would be a good project to start my development and be able to develop better solutions for searching. It would be fun to see how easy it is be to integrate this with the SAP PI/PO/XI module framework.
Spoiler: It is way too easy. 
As a seasoned PI consultant, I wanted to create an archiving solution that would make a developer’s work easier. Specifically, I wanted to create an archiving module that would store a lot of metadata on the file, while also adding a useful search function to it. This is how www.piarchiving.com was born, it is no longer being maintained because there is other solutions. Some of the newer user-defined message search modules also have different search criteria for text and so does HANA.

After gathering my ideas, I had created a module. In only takes one hour to learn and implement the code in an SAP PI module.

To get started, you need to add the API URL that should be used. The next step is to create and add the Index. After these steps, the content should be put into the text field and uploaded. A step-by-step explanation is shown in my video, with examples on how to find message IDs after the completion of keyword-based searches.


This is an easy application for those who wish to search through all of their content using Searchify in a PI/PO context. It is good for scenarios where you don’t have a HANA instance to save and search through messages.

It is also quite inexpensive, at only $59 per month which will not let you run much servers.
If this was to be used in a real scenario, there should be a focus on creating more stable code and an asynchronous process. Obviously, a better front end would also be needed.

For a more in-depth explanation, watch my video at:
The code is the following
Facebooktwittergoogle_pluslinkedintumblr

Comments are closed.