Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Define Connection Name and Type
This topic describes how to complete a connection to a DBMS repository. It is the final stage in connecting to a repository and is common to all of the database types supported by Enterprise Architect.
Complete the repository connection steps for the type of DBMS you are using, then follow the steps below.
- the Connection Name & Type dialog displays.
- In the Name field, type a suitable name for the connection so that you can recognize it in the Recent Projects panel on the Open Project dialog.
- If required, select the Encrypt Connection String checkbox. This encrypts and hides the connection details of the database from the users that the connection string is given to.
- If required, select the Lazy Load checkbox to not load the full project view when the model is loaded. Instead, only the parts that are necessary to display the visible portion of the tree are loaded. This means that a model loads faster and users can begin work sooner, but at the expense of later small delays as Enterprise Architect loads specific portions of the model.
- If required, select the Use WAN Optimization checkbox. (To improve performance over a Wide Area Network, remote database calls can be routed through a WAN Optimizer that compresses the data returned from the repository, reducing transfer time.)
If you select this checkbox, complete the next fields (see your administrator for the correct values). Otherwise go to step 9. - In the Server field, type the network name or address of the optimizer server.
- In the Port field, type the port on which the server is running on the remote machine.
- (If available.) In the DSN field, type the data source name of the database as it appears on the remote machine.
- Click on the OK button to complete the configuration.
The material ("material" includes all pages, documents and on-line graphics) on this web site is protected by copyright law. (C) 1998-2010 Sparx Systems Pty Ltd.