on 07-23-2014 11:53 AM
Hi experts,
currently I'm not quite sure how to handle our system upgrade of our PI system. Currently we are running PI 7.31 Double Stack and we are planning on upgradeing our system to 7.40 SP07. We have three system landscape installed and one SLD. We have allready updated our test-system to 7.40 SP07. But as the metadata was loaded from the SLD of our productive system (not patched yet) there has not been any update of the software component version.
Currently our system looks like this
PI PROD | 7.31 | Main SLD 7.31 |
PI QUAL | 7.40 | Import from PI Dev - 7.31 |
PI DEV | 7.31 | Import from SCV from PI Prod |
Therefore the communication channel currently stll have the component version 7.31 on our PI Qual, even it has PI 7.40 SP7:
Do we need to Update all of our communiction channels after we have upgraded the producitve sld? As this is our productive system can we keep the old versions of the adapter?
regards
Christian
Hello Christian,
It is recommended that the SAP BASIS Software Component, available in the ESR, should always be at the same release and SP level as the PI system itself. It should be either manually imported into the ESR or imported by running the relevant Configuration Wizard after the upgrade/SP upgrade etc. This SWCV, which is imported into the ESR, contains the Adapter metadata (not by importing from SLD).
See note 1575249 How to check the patch level of the PI Basis content.
"Do we need to Update all of our communiction channels after we have upgraded the producitve sld? As this is our productive system can we keep the old versions of the adapter?"
- There is no specific requirement to update the communication channels to the new 7.4 upgraded version. This requirment will only arise if you need to use some new functionality which will only be available with the lastest 7.4 Adapter metadata.
- If the old versions of the adapter metadata are meeting your business requirements, then I don't see any problems with keeping the old versions.
Regards
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just to close the question:
We didn't need to update the metadata of the used adapter for the update of the NW-release. After the upgrade I deployed the new SAP BASIS core coponent and used the Integration Directory Migration Tool to update the metadata. The handling of the tool is described under:
http://help.sap.com/saphelp_nw74/helpdata/en/f1/544ad104f6494c9eb0a8a87a601549/frameset.htm
regards
Christian
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.