How browser extensions can make our life much easier: a real case applied to Google Chrome and SAP PI
It’s a lot of fun to have your consulting company dealing with many customers, each of those having two or three different PI layers.
But what if you started to save all these Integration Builder pages to your bookmarks? Well, unless you are a “SXMB_IFR boy” (and if you are this weblog isn’t just for you I think) the result is a deep folders structure in your browser with probably a three or four click actions to open your favourites integration builder pages of the day.
So what’s the alternative?
If you are a Chrome user and you want to make a little coding to build up your own extension, here it is a simple and fast solution in few steps that can open the door for new useful ideas.
Let’s see briefly the architecture of our extension:
We need three things to have our extension ready to use:
- The HTML file that will contains all the logic to build up our view;
- The list of information that we need (in this case in a XML file): all the integration builder urls for the purpose of this blog.
*1. Manifest.json: the stone tablet of our extension*
This file is the manifest that let us import our extension in Google Chrome. Create a new folder which will contain all of our extension stuff – I will name it G#PI-QuickLoader.<!–
–>3. List.xml: the information we want to share inside our extension</p><p>Here I haven’t so much to say: I choose an XML file to store all URLs information, but you can have whatever technology you like.</p><p>
<textarea cols=”44″ rows=”14″><?xml version=”1.0″ encoding=”UTF-8″ standalone=”yes” ?>
</textarea></p><p> </p><p>The final step
A. Put all the icons and the HTML file inside our folder. Our folder will look like this:
B. Open chrome extensions page (chrome://extensions), go into “developer mode”, and choose “Pack Extension”
If the operation will succeed you’ll have two files in output:
– CRX File : It’s the real extension. You can send it to your friends/colleagues or upload it to the Chrome Web Store;
– PEM File: it’s the private key. Don’t lose it because you need it to update the extension or upload the extension to the Chrome Web Store.
Here it is! Our extension is ready to use. We can see the final result in the image below (please sorry for chrome italian language):
Note that we can spread this extension inside our company to have a single point of configuration for all PI consultants, and of course… it’s time to clean your bookmarks!