Migrating your IBM Websphere Commerce Version 8 site security
Manually migrate your site security from your IBM Websphere Commerce Version 8 production environment to your HCL Commerce Version 9 production environment.
Important:
If you are using local authentication on the WebSphere Commerce Search server, ensure that the session key is synchronized between the WebSphere Commerce and WebSphere Commerce Search servers. You must copy the new session key to the WebSphere Commerce Search server whenever it is changed on the WebSphere Commerce server.
It is highly recommended that you change the session key at the same time you change the merchant key. According to PCI specification, the merchant key should be changed at least annually.
Procedure
-
If you enabled AES encryption on your IBM Websphere Commerce Version 8 database and file system,
migrate your encryption settings files to your HCL Commerce Version 9 production
environment.
-
If you used the Key Locator Framework (KLF) in your IBM Websphere Commerce Version 8 production
environment, migrate your key provider customizations. For more information about the KLF, see Key Locator Framework (KLF).
-
Open your IBM Websphere Commerce Version 8
WC_eardir/xml/config/wc-server.xml file, and look for the
KeysConfigFile
parameter. This parameter points to a separate custom key configuration XML. - Open your custom key XML file.
- The custom files that are referenced in this keys XML file must be copied to the same directories on your HCL Commerce Version 9 production environment, and then deployed through your CI/CD pipeline, which is covered in one of the last steps when you migrate your production environment.
-
Open your IBM Websphere Commerce Version 8
WC_eardir/xml/config/wc-server.xml file, and look for the
- Migrate any other custom security files that were part of your IBM Websphere Commerce Version 8 production security solution by copying the files to your HCL Commerce Version 9 production environment.