000031449 - FIM standalone install asks for sql url/port with Derby

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000031449
Applies ToRSA Federated Identity Manger (FIM) 4.2.1
DERBY Database

 
IssueCustomer trying to get a simple standalone install of FIM 4.2 on WAS.  The install script requires the DB FQDN and Port. 
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?
ResolutionIn case of Standalone and derby, no need to specify any FQDN or Port pointing to the internal DB (Derby) as everything is in same instance
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

Attachments

    Outcomes