A customer requests that a BIN in TEST environment be moved into PRODUCTION environment This procedure explains and provides steps to do so.
Originally Published: 2012-06-29
Article Number
Applies To
The FI_BIN load validation allows for the existence of 2 BINS with same numbers in both TEST and PROD environments simultaneously.
Yet there is an over-ride giving precedence to the TEST environment.
The reason is that sometimes customer will want to do a short term test of cards in a particular BIN range so Operations will add the BIN into TEST, leaving the BIN in PROD.
There are two separate Database tables that can contain the same BIN number. So, to move a BIN from Test into Production requires an FI_BIN Loadsheet
1) FI_BIN to Delete the Test BIN entry
2) FI_Bin to add NEW the Production BIN entry
Issue
A customer requests that a BIN in TEST environment be moved into PRODUCTION environment
This procedure explains and provides steps to do so.
Notes
Note Warning if only step 2 is performed, there are now entries in both Tables for These BIN numbers and there could be errors when attempts are made to register cards in these BINS since when this condition exists, Test BIN will take the precedence.
Related Articles
Setting up on-the-fly SOAP logs in production Number of Views Change hostnames on a deployed production environment in RSA Web Threat Detection Number of Views Procedure to upgrade Java in Envision Number of Views Issue loading Server Nodes tab after RSA Identity Governance & Lifecycle 7.1.0 installation on WebSphere 9.x clustered env… Number of Views Review results are removed from the system after deleting a review definition in RSA Identity Governance & Lifecycle Number of Views
Don't see what you're looking for?
