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 about database connections. 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.

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 Desktop online documentation discusses how to create database connections in ArcCatalog.

Supported Databases

Oracle 9i
Oracle 10g R2
Oracle 11g R1
Oracle 11g R2
Oracle 12c
SQL Server 2005
SQL Server 2008
SQL Server 2008 R2
SQL Server Express
SQL Server Workgroup
Personal Geodatabase (.mdb, Access 2000)
File Geodatabase (.gdb)

FGDBs: Neither Designer nor Process Framework may be used with a file geodatabase.

Oracle:

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.iowa" and "iowa" 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)

Important Notes:

Oracle and SQLServer: The server property is optional when creating direct connections in ArcCatalog. Always be consistent in using it.
Oracle only: The TNS name must always be consistent. TNS names such as "orca.iowa" and "iowa" 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.
Oracle only: Configure the sqlnet.ora file to specify the path adapters to be used for resolving names. For example: NAMES.DIRECTORY_PATH= (TNSNAMES)
Oracle Direct Connect: Both 10g and 11g are supported. The instance must match your Oracle version (e.g., Instance = sde:oracle10g or Instance = sde:oracle11g).

Platform	Authentication Type	Connection Type	Connection Parameters	Owner of Default
Oracle/ArcSDE Enterprise	OSA	Direct Connect	Instance = sde:oracle11g:/;LOCAL=tns name, Authentication = operating system, Version = project1.default or Instance = sde:oracle11g:/;LOCAL=server name/EZ connect name, Authentication = operating system, Version = project1.default	Geodatabase schema owner
Oracle/ArcSDE Enterprise	OSA	Direct Connect	Instance = sde:oracle12c:/;LOCAL=tns name, Authentication = operating system, Version = project1.default or Instance = sde:oracle11g:/;LOCAL=server name/EZ connect name, Authentication = operating system, Version = project1.default	Geodatabase schema owner
SQL Server 2005/ArcSDE Enterprise	DBMS	Direct Connect	Instance = sde:sqlserver:elmo\mssql2, Database = databasename, Authentication = database, User = <user name>, Password = <password>, Version = sde.default (depending on the configuration)	*SDE or DBO
SQL Server 2005/ArcSDE Enterprise	OSA	Direct Connect	Instance = sde:sqlserver:elmo\mssql2, Database = databasename, Authentication = operating system, Version = sde.default (depending on the configuration)	*SDE or DBO
SQL Server Express 2005/ArcSDE Personal or Workgroup	OSA	Direct Connect	Server = freewheel_sqlexpress, Instance = sde:sqlserver:freewheel\sqlexpress, Database = databasename, Authentication = operating system, Version = dbo.default	DBO
SQL Server 2008/ArcSDE Enterprise	OSA	Spatial Database	Instance = sde:sqlserver:elmo\mssql2, Database = databasename, Authentication = operating system, Version = sde.default (depending on the configuration)	*SDE or DBO
Personal Geodatabase (Access)	N/A	N/A	Database file path = D:\data\Minerville.mdb	N/A
File Geodatabase**	N/A	N/A	Database folder path = D:\data\Minerville.gdb	N/A

* The owner is SDE when using a multiple spatial database instance configuration; the owner is DBO when using a single spatial database instance configuration.

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