FIM standalone install asks for sql url/port with Derby
Originally Published: 2015-10-08
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
Authentication with SSH tools fails on Solaris asks for a password instead of passcode Number of Views RSA Customer Frequently Asked Questions FAQs: FireEye Tooling Disclosure SolarWinds Advisory Number of Views RSA Customer Frequently Asked Questions FAQs: Kaseya VSA Advisory Number of Views Frequently Asked Questions for the Admin MFA Trial Number of Views FIM console not asking for administrative logon after applying hotfix Number of Views
Trending Articles
Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA Authentication Manager Upgrade Process RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager Patch Updates How to implement SAML SSO Authentication with Microsoft Azure Active Directory and RSA Identity Governance & Lifecycle
Don't see what you're looking for?
