 |
 |
|
 |
 |
|
 |
 |
 |
If your organization already has created an enterprise database on Oracle or Microsoft SQL Server and you have an active user account, you can use an enterprise repository connection file (*.rserp) to connect with it. You can create this file yourself or use a file that has been created by someone else. Once this file is created, it can be used to connect to the database and to import from or export to the database.
To create a connection file, choose File > New > Enterprise Repository Connection File.
This command creates a Synthesis repository connection file (*.rserp) that is stored locally on your computer; the file contains all of the necessary information for connecting to the enterprise database.
Enter a name for the connection file, then choose the database type and version (i.e., Microsoft SQL Server 2005 or 2008, or Oracle 10 or 11).
For SQL Server databases, enter the server name and database name. Select the Use impersonation check box if you want the new connection file to impersonate a Windows user account with a SQL Server login that can be shared by multiple users. This connection file can then be distributed to any user who does not have his/her own individual SQL Server login and is not part of a Microsoft Active Directory® group that has a login. (See SQL Server Logins or Using Windows Impersonation.)
For Oracle databases, enter the port, host and service identifiers and the database schema. Your Windows login credentials are used for access to the database; enter your Windows password.
If you have used the connection file recently, choose File > Recent and then select the file in the Recent Repositories list.
Otherwise, choose File > Open Repository and then browse for the *.rserp file.
If you are unable to connect to an enterprise repository, you may be encountering any of the following issues:
No access to the repository. If you have not been given access to the repository, you will see a message stating that your account in the repository is not active or not assigned to at least one security group. You will need assistance from someone who can create and update user accounts (see Managing User Accounts).
Windows authentication failed. If your Windows login (domain and username) is different from what was specified for your user account, you will see a message to connect using alternative credentials. You will need assistance from someone who can enable the use of alternative credentials for your user account.
Cannot connect to the server or login failed. Server-related issues may occur for several reasons, and you may see various messages pertaining to the situation. Common issues are:
You do not have a network connection or you may have entered the incorrect database name (i.e., Synthesis repository name) or server name in the connection file.
The server may not be configured to allow remote connections, has certain firewall settings or is experiencing other issues. In this case, you will need to contact the IT support group responsible for the server.
In SQL Server databases, a login issue may occur if your username is not associated with a SQL Server Login. (See SQL Server Logins or Using Windows Impersonation.)
© 1992-2016. ReliaSoft Corporation. ALL RIGHTS RESERVED.
 |
E-mail Link |