Login Connection Strings

The ArcFM Solution supports a wide variety of connection possibilities. For details on login connection strings, refer to the ArcGIS help topic Database Connections in ArcMap. The following table provides the supported platform, authentication type and connection type as well as the required parameters. All connections displayed in the table below are supported by the ArcFM Solution.

ArcFM supports two types of authentication: database and operating system. Database authentication (DBMS) requires the user to enter their user name and password when logging into an ArcFM application. Operating system authentication (OSA) uses the user's Windows login name and password.

IMPORTANT: Do not include the @ symbol in your ArcFM password. It is not supported and causes the login to fail.

All Process Framework logins (e.g., Session Manager, Workflow Manager, Process Framework Admin tool) support both types of authentication. When logging in, you can select the authentication type.

The ArcGIS help discusses Connecting to an Enterprise Geodatabase or Database from the Catalog Tree.

Supported Databases

ArcFM products support Oracle, SQL, FGDB, PGDB, PostgreSQL, and Postgre databases. For a detailed list of supported databases and versions for each ArcFM product, see the myArcFM Supported Versions article.

IMPORTANT:

PostgreSQL:
- PostgreSQL is supported using psqlODBC, which is the official PostgreSQL OBDC Driver.
- PostgreSQL connections are case sensitive.
File Geodatabases:
- Neither Designer nor Process Framework may be used with a file geodatabase.
Oracle:
- The pattern for SDE Oracle direction connection is <server_name>:<listener_port>/ <service_name> (for example, yankees.miner.com:1521/orca.yankees). Because 1521 is the default listener port, yankees.miner.com/orca.yankees would also work.
- When creating an Oracle database connection, use ONLY the tns name, for example orca.yankees, not sde:oracle11g:orca.yankees. The latter form can lead to inconsistent behavior.
- The TNS name must always be consistent. TNS names such as "orca.yankees" and "yankees" can reference the same instance on the same server, but they can also reference different instances. It is critical that all users have a consistent TNS name to reference a particular geodatabase.
- Configure the sqlnet.ora file to specify the path adapters to be used for resolving names. For example: NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)

In ArcCatalog, when you Add Database Connection, a dialog appears with connection fields.

The table below provides examples of what each Database Platform is looking for in the connection fields.

IMPORTANT: Regarding the Database field, this drop-down populates with values after you type the Instance and authenticate with an appropriate User Name and Password. Once the drop-down is populated, click the Database name.

Database Platform	Connection Type	Connection Parameters (Instance)	Authentication Type	Owner of Default
Oracle/ArcSDE Enterprise	TNSNAMES	Instance = <tns_name>	OSA/Database	SDE
Oracle/ArcSDE Enterprise	EZCONNECT	Instance = <server_name>:<listener_port>/ <service_name>	OSA/Database	SDE
SQL Server/ArcSDE Enterprise	N/A	Instance = <server_name>\<instance_name>	OSA/Database	SDE or DBO
PostgreSQL	Direct Connect	Instance = sde:postgresql:server, Database = databasename	DBMS	SDE
Personal Geodatabase (Access)	N/A	Database file path = D:\data\Minerville.mdb	N/A	N/A
File Geodatabase*	N/A	Database folder path = D:\data\Minerville.gdb	N/A	N/A

* Process Framework may not be used with a file geodatabase.