5.8. Defining Connections to Other Repositories

Engineering Knowledge Manager

User's Guide | Chapter 5: Customizing EKM for Your Own Use |

5.7. Setting the Alert Frequency |  | Chapter 6: Object Types and Properties
Prev |  | Next

## 5.8. Defining Connections to Other Repositories

Some features in EKM require or allow access to other repositories:

- Expand Search

- Connection to a URL

- Running jobs in distributed mode

For example, if your EKM administrator has configured a multi-region deployment with Master/Slave workspaces, as described in Running Jobs in a Distributed Environment, you will be automatically signed in to the Master server when you sign in to a Slave server so that you can access the data in the Master repository. Similarly, if you sign in to the Master server and submit a job to a Slave workspace, you will be signed in to the Slave workspace at that time. By default, the credentials used to sign in to a Slave workspace are used to sign in to the Master workspace, and vice versa. If those credentials are not valid for the workspace being accessed, then you will be need to specify a credential override for that workspace, as shown in Authentication in a Master/Slave Setup.

You can use the Connections feature to capture sign-in credentials for other repositories. When you define connections, user names and passwords are validated and saved so that you can be automatically signed in to those repositories when you need to access them.

To define connections:

1. Click the user profile drop box on the title bar and select Connections.

2. To add a connection in the Connections dialog box, click .

3. In the Name field, optionally specify a name for identifying the repository. If you do not specify a name, one will be generated using the format `hostname`:`workspace`.

4. Specify the Server URL using the format `hostname`.`domain`:`port`, as shown in the example below. The available workspaces on the specified server are automatically displayed in the Workspace drop list. Select the workspace that you want to access.

   If the Server URL is not the URL of the current EKM server, then you must specify the User Name, and Password required to sign in to that server. If the Server URL is that of the current EKM server, you do not need to specify your User Name and Password because you are already signed into the current server.

   Note:

   - The Server URL entered must be for an EKM Server version 17.0 and above.

   - If the Server URL entered is for a secured EKM Server (`https://`) that uses a self-signed certificate, you must import the certificate into Java's keystore on the current EKM server. Otherwise, the current EKM server’s Java will not trust the certificate that you are using to secure the server, and will therefore not create a secure connection. For details, see Importing a Self-signed Certificate into Java’s Keystore in the EKM Installation Guide.

   - EKM cannot validate a connection’s credentials if the connection is currently open in Workbench. The connection will remain displayed in the Connections dialog box and appear as an available connection when accessing other repositories, but you will be prompted for sign-in credentials when you attempt to use it.

For information about the Expand Search feature, see Expanding a Search to Other Repositories. For information about creating a URL object, see Creating a Connection to a URL.

Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.

Prev | Up / Contents | Next

Release 18.2 - © ANSYS, Inc. All rights reserved.