FIM standalone install asks for sql url/port with Derby
Originally Published: 2015-10-08
Last Modified: 2023-10-06
Article Number
Applies To
DERBY Database
Issue
With a standalone FIM is derby internal with no url and port?
It is needed for a cluster install!
Is it always external with url and port?
Resolution
The Connection URL is like: jdbc:derby:rsa-fim-config/demoDB;create=true
But during installation, install script will ask for the DB FQDN and Port. We can specify default value as follows, but it will not be used.
DB_FQDN= <Standalone_Machine_fqdn>
DATABASE_PORT=1527
In case of Cluster and derby, we need to specify Admin server FQDN and Port pointing to the internal DB (Derby), as all the managed node will be pointing to same Admin server DB
The Connection URL is like: jdbc:derby://{FIM_AdminServer_FQDN}:{DB_Port}/rsa-fim-config/demoDB;create=true
For cluster during installation, the install script will ask for the DB FQDN and Port and there we can specify values as follows:
DB_FQDN= <Admin_Machine_fqdn>
DATABASE_PORT=1527
Related Articles
Cleanup WTD Incidents table (postgreSQL) Number of Views Perform a silent installation of the RSA Authentication Agent 7.3 and 7.4 for Windows Number of Views AFX fails to start on RHEL 8.4 and greater in RSA Governance & Lifecycle Number of Views RSA SecurID Authentication Agent 8.1 for PAM Installation and Configuration Guide for SUSE (French) Number of Views Users receiving emails for a deleted review result in RSA Via Lifecycle and Governance Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?
