Soleslayer Generating Checkout Request Key
What is Vendor Key?
- An SSH key is an access credential for the SSH (secure shell) network protocol. This authenticated and encrypted secure network protocol is used for remote communication between machines on an unsecured open network. SSH is used for remote file transfer, network management, and remote operating system access.
- Before you generate an SSH key, you can check to see if you have any existing SSH keys. Generating a new SSH key and adding it to the ssh-agent → After you've checked for existing SSH keys, you can generate a new SSH key to use for authentication, then add it to the ssh-agent. Adding a new SSH key to your GitHub account →.
The vendor key is a keyword provided by SAP or the third party Add-on vendor, to retain an existing Add-on Software component version during a system switch upgrade or an enhancement package installation. The Add-on retained must be functionally and technically compatible with the target release.
Create and add your SSH key pair. It is best practice to use Git over SSH instead of Git over HTTP. In order to use SSH, you will need to: Create an SSH key pair; Add your SSH public key to GitLab. Creating your SSH key pair. Go to your command line. Follow the instructions to generate your SSH key pair. Adding your SSH public key to GitLab.
While for system switch upgrades it is very uncommon that an Add-on version is retained, the introduction of the enhancement package concept demanded the Add-on to either release a compatible version or to test the compatibility and release the existing Add-on version on the new enhancement packages.
In an enhancement package installation there is a different handling of Add-ons based on NW only (NW-Add-on) and on Add-ons based on applications (Application-Add-on). While for NW-Add-ons the compatibility is by definition, Application-Add-ons must provide either a new release or allow the compatibility by delivering an ACP (Attribute Change Package).
If the import Conditions of the Addon still fit to the target either by compatibility definitions or import conditions enhanced with an ACP -NO Vendor Key is required .
When do I need a Vendor Key?
System Switch Upgrades:
It is very likely that no vendor key has to be provided to customers if the upgrade is a system switch upgrade with a major change of the basis release (e.g. basis 640 to 700). Note that Notes and Add-on Support Packages may not be applied on the target release with the kept Add-on version.
You can purchase one from somewhere like GoDaddy or you can get a free certificate with. With a self-signed certificate, users will get a warning on their first visit to your site that is using an untrusted certificate. If you just need a self-signed cert for personal use or testing, continue and learn how to sign your own certificate.OpenSSL is the tool used in this tutorial.
Enhancement Package installation up to target SAP basis 701 (incl.):
Vendor keys have to be provided for compatible Add-ons during an installation of an enhancement package if the release of the application component specified by the Add-on as import condition changes (e.g. SAP_APPL 600 -> 604). Add-ons requiring NW components only are treated as compatible and no vendor key has to be provided.
Enhancement Package installation as of target SAP basis 702 (incl.):
No Vendor key shall be necessary for any type of Add-ons (incl. application Add-ons) delivered by SAP. NW Add-ons are treated as compatible and application Add-ons can either be enabled by delivering a new Add-on version, or they can be allowed on the new release by an ACP (Attribute Change Package).
With the new strategy, Vendor keys are no longer required
KEEP VERSION
Starting with target release 702 onwards ,you can retain the SAP addon using the KEEP VERSION. This is possible due to
Sole Slayer Generating Checkout Request Key West
• Use of ACP to enhance Import conditions:
For Application Addons,the import conditions of the Addon can be enhanced to support the target release using an ACP .Thus if the ACP for the Addon that makes it compatible with the target release is present in EPS/in then the preselected option of KEEP Version must be selected in IS_SELECT.For MOPZ enabled Add-on product versions , the Addon is handled during MOPZ XML creation ,so the ACP would be downloaded and present in EPS/in. As a consequence the Addon will not appear in IS_SELECT phase.
• Use of compatibility Definitions :
For Netweaver Addons,the preselected option KEEP VERSION in IS_SELECT will be selected when the import conditions satisfy the target constellation due to NW compatibility definitions. For eg. A pure NW addon based on NW 700 will automatically be compatible with target constellation NW 701,NW 702 without a Vendor key and without an ACP
Soleslayer Generating Checkout Request Key West
eg. During an upgrade of NW 700 with SLL-NFE 100 -> NW 702 . SLL-NFE 100 (based on 700 ) can be kept on the target release 702 without a Vendor key due to NW compatibility definitions .
The Vendor key process is no longer in use, and ACP packages are required (only in exceptional cases)
RELATED NOTES:
- Note1301301 - Release Strategy for SAP Best Practices Package ABAP
- Note 1262124 - Vendor Keys for Add-ons released with ERP Enhancemnt Packages
- Note1589409- Vendor key handling as of enhancement package 2 of NW 7.0
- Note1324996 - Vendor keys for manufacturers of ABAP add-ons(for 3rd party Addons)
- Note 1324910 - SAP upgrade with add-ons of third parties