Considerations for Environment Cloning

Payments stores the master encryption key and other security credentials in Oracle Platform Security Services (OPSS). When you clone an environment with another environment using methods such as production-to-test (P2T), test-to-production (T2P), test-to-test (T2T), and so on, the data from the source environment in OPSS isn’t automatically replicated to the target environment.

After cloning, system administrator must immediately perform the following actions in the target environment:

• Migrate Wallet: The payments wallet contained in the OPSS repository isn’t migrated during a P2T environment refresh. Migrate the wallet from the source to the target environment using the steps provided in Payments Wallet Migration Post P2T/T2T Refresh (Doc ID 2407678.1).
• Update Transmission Configuration: Edit transmission configuration details to ensure that they point to the right destination. If the target environment is a test environment, you must confirm that details such as host/IP, port, username, client private key file, remote directory, and so on, pertain to the test environment provided by the bank or payment gateway.

Note: Adding an end date to the transmission configuration doesn’t prevent its usage if these transmission configuration details are already associated with a payment process profile or a fund capture process profile. It is mandatory to update the transmission configuration with the correct destination details for the refreshed environment.

Important: Don’t run any payment batches in a cloned environment until you have migrated the wallet and updated the transmission configuration details. If you do run payment batches, you may accidentally send payment files to the bank’s production server.