3.2. Configuration Options

Engineering Knowledge Manager

Getting Started Guide | Chapter 3: Configuring and Initializing EKM |

3.1. Initialization Options |  | Chapter 4: Using EKM
Prev |  | Next

## 3.2. Configuration Options

Here are some configuration changes that you can make before starting the EKM server. You can make these changes at any time in the future as well. Some changes may also require that you migrate your old data model to a new one. For details, see Migrating Workspaces in the EKM Administration Guide.

- Define server settings: You will need to define additional server settings in ekm.xml if you want to integrate with RSM for batch job submission.

  For details, see Configuring EKM Server Settings in the EKM Administration Guide.

- Define custom types: You will need to define custom types if you want to do the following:

  - Add metadata or custom actions to existing types provided by EKM

  - Allow EKM to recognize new file types and specify metadata for these new types

  - Allow users to create custom containers or custom analysis projects

  For details, see Defining Custom Types in the EKM Administration Guide.

- Define metadata and report extractors for third-party file formats: This is required if you want to extract metadata or reports from file formats that EKM does not support. You will need to define applications that will perform the extraction. For details, see Custom File Formats in the EKM Administration Guide.

- Define custom applications: This is required if you want to capture best practice or procedures. You will need to define both the back end (scripting logic) and front end (user interface) of the application. For details, see Scripts and Journals in the EKM Administration Guide.

- Define process templates: This is required if you want to define a process involving multiple users or a set of activities that cannot be defined using a custom application. For details, see Defining Process Templates in EKM Studio in the User’s Guide.

- Define object lifecycles: This is required if you want to track the maturity level of any object type as it moves through its lifecycle. You will need to define the stages involved, permissions applicable at each stage, and any review processes required to complete a stage change. For details, see Defining and Configuring Lifecycles in the EKM Administration Guide.

- Define Queues for Remote Simulation: This is required if you want to execute or run simulation jobs from within EKM. To make this possible, EKM must be synchronized with ANSYS RSM. For details, see Managing Queues in the EKM Administration Guide.

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.