This blog is the result of thought process behind this thread posted recently. Although many of you might have seen some documented or undocumented process at your respective organizations, I believe there are still many clients who do not have any process in place. The blog is about the process of Decommissioning or removing the interfaces from PI landscape. This may appear easy, however, if you just start thinking about it, it can be a huge job.
A few years back, I wrote about "How clean is your Integration Directory?". It talked about keeping the Integration Directory clean. This blog is about entire PI answering the question "How".
What do we usually do?
There could be numerous reasons why you need to decommission an interface in PI. I have captured some of the reasons here however, there could be a whole bunch of other reasons. So once we decide that the interface should not be used for production flows, here are the simple steps which are normally being followed:
I recommend always doing both point 1 and 2 at the same time because then you have option to navigate and select all the inactive channels in Communication Channel Monitoring and rest assure that the channel is inactive.
Now the problem with point 3 is it is not always easy to implement. It depends a lot on the Release Management strategy of your organization. If your organization is very stringent about the transport processes in PI, you may end up waiting forever to get a delete related transport request to PI production environment. And it is not only about transports, it is also about the configurations you perform directly in production. If you can convince your Release Manager (or you can skip him), then go ahead with reading rest of the blog. :smile:
When you develop a scenario, you first design it (ESR) and then configure it (ID). However, when you go for decommission, remove configuration (ID) first and then the design (ESR) objects. This will avoid any inconsistencies in the landscape.
Improving the Decommissioning Process
If the release management process supports you, you have to start thinking what all objects or configurations associated with your interface should be removed. First, understand the current process completely. Then, start the improvement path.
Finally, the list of objects!
To fill the above created template and checklist with different objects that may be hidden across your PI implementation, you have to ask the below questions and proceed with the deletion. For each point, make sure that the object to be deleted is not reused anywhere.
General
ID
ESR
SLD
It is better to remove everything related to ESR in one single transport. I have tried to keep this list in the logical order in which I believe they should be deleted.
Conclusion:
I like to "keep it clean" and therefore like to spend some time on this topic. I know and understand that there could be several objects not listed here. The aim here is to throw some lights on the different areas in PI which may be impacted by this single interface. Enjoy cleaning! :smile:
What are your experiences with the end-of-life of interfaces?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
9 | |
8 | |
7 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 |