Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Prev | Next |
Add Database Manager
The Add Database Manager screen displays when you click on the on the 'Sparx Systems Cloud Services Configuration Client' dialog; it helps you to define a new database connection to either a local Firebird repository or a DBMS repository (via ODBC or OLE/DB).
This note is shown on the Add Database Manager screen:
'Note: The Data Source Names and network paths provided by the Data Link Properties and ODBC Data Sources dialogs are relative to this machine and may need to be modified to match those on the server.'
This means if the Cloud Services Client application is running from a remote machine (that is, not the machine running the Cloud Server) the screens that are shown by clicking on the button and are relative to the current machine and not the Cloud Server machine, so care should be taken.
By default and as a safety precaution, whenever a new Database is defined it is automatically configured to be disabled. You can enable the database during definition by selecting the 'Enabled' checkbox on the Configure Database Manager screen.
Adding New Databases
It is important to note that the Cloud Server uniquely identifies Databases by a single identifying value; this value is referred to as the database 'Alias'.
When adding a new database manager, the Alias can be specified using the 'Alias' field on the 'Add Database Manager' dialog.
If no Alias is specified, then a default Alias is determined. For:
- Firebird definitions, the 'Alias' is the filename minus the extension
- ODBC based definitions, the 'Alias' is the 'Data Source'
- Oracle OLE DB based definitions, the 'Alias' is the 'net service name'
- SQLServer OLE DB based definitions, the 'Alias' is the 'Initial Catalog'
Therefore, take care when defining database connections, to ensure that you do not create duplicate database aliases. However, if two or more database definitions do share the same alias then all Enterprise Architect clients will connect to the first database found with the requested alias.
Item |
Description |
---|---|
Firebird Database |
Sparx Systems, in the 'Introduction to Sparx Systems Cloud Services' webinar, demonstrate the Cloud Services with a Firebird database as it is so easy to set up and use, and it works extremely well with Sparx Systems Cloud service technology. Firebird is a free, open source rational database that runs on a variety of platforms. Firebird is very sophisticated and offers great concurrency, scalability and performance. It can be used in an enterprise setting and has been used in production systems, under a variety of names, since 1981. To discover more about the Firebird database, please visit this website: http://www.firebirdsql.org/en/about-firebird/ You can view the webinar by clicking on this link: https://sparxsystems.com/resources/webinar/model-repository/cloud/introduction/introduction-cloud-services.html You can define a connection to a Firebird database by entering its filename (and extension) only; for example,'MyFireBird.feap'. The Cloud Server assumes all Firebird databases physically reside under the directory %SERVICE_PATH%\Models\. The Cloud Server is, by default, installed to the folder of: ...\Program Files (x86)\Sparx Systems\Cloud Services\ In this case all Firebird models will be located at: ...\Program Files (x86)\Sparx Systems\Cloud Services\Models\ |
ODBC Database |
You can define a connection to a database under a DBMS such as MySQL or PostgreSQL, by specifying the connection string to the database. If you are running the Management Client on the same machine as the server you can:
Notes:
|
Oracle Database (via OLE DB) |
You can define a connection to an Oracle Database (via OLE/DB) by specifying the connection string to the database. If you are running the Management Client on the same machine as the server you can:
Note:
|
SQLServer Database (via OLE DB using SQL Server authentication) |
Microsoft SQL Server supports two different forms of database authentication:
The Cloud Service will work with either, but SQL Server authentication is easier to configure. Prior to defining the Cloud Service connection, define a SQL Server user with db_datareader and db_datawriter roles to the database that will act as the Enterprise Architect repository. You can define a connection to a SQLServer Database by specifying the connection string to the database. If you are running the Management Client on the same machine as the server you can:
|
SQLServer Database (via OLE DB using Windows authentication) |
Microsoft SQL Server supports two different forms of database authentication:
The Cloud Service will work with either, but Windows authentication requires some special consideration. The Cloud Server runs as a Windows Service, and by default all Windows Services run as 'Local System Account'; therefore, if Windows authentication is to be used, the Sparx Systems Cloud Service should be configured to run under a predefined network user (configured with the Windows Services console) and this network user must have access rights to the database (configured with Microsoft SQL Server Management Studio or similar). You can define a connection to a SQLServer Database by specifying the connection string to the database. If you are running the Management Client on the same machine as the server you can:
Note:
|