E-IB: Best Practices in Gateway Setup to Minimize PeopleTools Version Dependency between Integrated Peoplesoft Environments
Last updated on MAY 02, 2017
Applies to:PeopleSoft Enterprise PT PeopleTools - Version 8.48 and later
Information in this document applies to any platform.
***Checked for relevance on 02-MAY-2017***
When PeopleSoft environments on different PeopleTools releases or patch levels are integrated to each other, the setup must ensure that no gateway is trying to connect to an app server whose PeopleTools release is higher than the gateway's. One of the ways to achieve this is to use a single shared gateway, using the one on the highest PeopleTools release among the participants. However in such configuration on each upgrade/maintenance cycle you must start from the environment whose gateway is shared as common, otherwise the data flow to the first upgraded/patched environment might be broken, or you would have to switch to use as shared another gateway which becomes the new highest PeopleTools release, and to reconfigure all other environments accordingly. Both options, having to follow certain upgrade/patching order or having to reconfigure all environments to use another shared gateway, are inconvenient.
Is there a best practice to have a gateway configuration that could be stable and do not depend on the order in which you upgrade or patch the integrated environments?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms