How to replace an Access Fulfillment Express (AFX) Connector jar file that has been uploaded to an AFX connector template in RSA Identity Governance & Lifecycle

RSA Product Set: RSA Identity Governance & Lifecycle 
RSA Version/Condition: 6.8.1 P20+, 6.9.1 P07+, 7.x
 

RSA Identity Governance & Lifecycle AFX Connectors require various third party files to be uploaded into RSA Identity Governance & Lifecycle in order to function. RSA Identity Governance & Lifecycle supplies many of these files by default. However, there are certain files that RSA is prohibited from distributing. These files needs to be provided by the customer. These files are uploaded by  going to the AFX > Connector Templates > {connector template name} > File Content tab and pressing the appropriate Upload File button in the Loaded column. Once the file has been uploaded the status changes to Loaded.

Occasionally, an uploaded jar file may need to be replaced. There could be several reasons for this such as:

• Wrong version of the jar file was loaded
• Corrupt version of the jar file was loaded
• Newer version of the jar file now supported
• There is an unidentified problem with the existing jar file
• Jar file did not come from a reputable source 

There is a button labeled Clear in the user interface (AFX > Connector Templates > {connector template name} > File Content ) in the Loaded column when a file has been uploaded to an AFX connector template. This button can be used to remove or clear out the existing jar file that was uploaded so a new jar file with the same name may be uploaded. Note that any files loaded by RSA Identity Governance & Lifecycle cannot be removed or cleared (no button).
 

Example:

The example below is of the Sybase AFX connector template and the customer is required to provide the jconn3.jar file. Once loaded the Clear button is available to remove the uploaded file which can then be replaced with another file of the same name by uploading that file.