To simplify things we will use for both releases Exchange Infrastructure 3.0 and Process Integration 7.0 thename Process Integration (PI). From an architectural point both releases does not show significantdifferences (beside of HA specific facts).The following graphic shows the components that make up the SAP Process Integration. The SAP ProcessIntegration consists of the following functional components: Integration Builder, Integration Repository,Integration Directory, Integration Server, Integration Engine, Business Process Engine, Adapter Engine,Runtime Workbench (RWB) and System Landscape Directory (SLD)Most of these components have to exchange information during runtime of the Process Integration. Thus, itis essential that each component can be accessed and that the communication between them is set upcorrectly. However, major changes of the PI infrastructure, especially when applying patches or whenchanging hostnames in the context of a High Availability setup, are potentially critical for the correctcollaboration of the PI components.Therefore we recommend to carry out a set of simple checks that test the basic communication pathsbetween the PI components and strive to ensure a smooth runtime after a software patch or HA setup.These checks are divided into 2 groups: the first group is meant to be carried out by everyone and requireslittle to no knowledge about PI. The second group of checks is addressed to PI experts, e. g. developers orPI system administrators, and require a basic understanding of the Process Integration.