1 Introduction

The Administration Guide describes how to administrate the installed Agile e6.2.1.0 components.

Note: For information about security, please refer to the Security Guide for Agile e6.2.1.0.

1.1 About Agile e6.2.1.0 Administration

An Agile e6.2.1.0 application defines a particular hardware and software configuration that allows Agile e6.2.1.0 to work with an Oracle database and Oracle WebLogic Server.

To administer the Agile e6.2.1.0 application, you can create and manage Agile e6.2.1.0 applications. For every created Agile e6.2.1.0 application, information is stored on the EDM Server that specifies how to connect to the database, locate data, and which Oracle WebLogic Server is to be used.

When you install an EDM Server, the installation program automatically creates a default application which is configured during the installation, and the application name is associated with the database.

It is also possible to create additional applications within the same installation thus, it is not necessary to maintain separate installations for different purposes. A single Agile e6.2.1.0 installation often includes separate applications for various purposes, such as testing for testing purposes before creating the actual working applications, development, production, and education.

The applications created for an installation can be associated with the same, or with different databases (e.g. a multi-application system, in which development and test applications, and their respective databases co-exist with a production application and its database). In general, it is required to have a separate production infrastructure to avoid the risk of loss of production by changing something in e.g. the development application.

1.2 About Agile e6.2.1.0 Business Services Administration

When you create an Agile e6.2.1.0 application, the Business Services component will be installed/deployed on your Oracle WebLogic Server for each new application. The Business Services comprise of the Workflow Module, Permission Manager, and Product Configurator.

1.2.1 Overview of the Workflow Module

To include Workflow processes in an Agile e6.2.1.0 application, optional configuration parameters can be defined for the processes within the overall Agile e6.2.1.0 application definition. For more information, refer to the chapter Administering Agile e6.2.1.0.

Note: For further information on using the Workflow module, refer to the Agile e6.2.1.0 Online Help > Using Agile e6 > Product Data Management > Workflow.

1.2.2 Modifying Configurations without the Administration Client

Any file or configuration modification made without the Administration Client will be lost when changing the application values with the Administration client again, except when using the component based J2EE installation.

If you want to install/deploy the Agile e6.2.1.0 J2EE components with a separate user, or on a separate server, different from the one used for the "native" Agile e6.2.1.0 installation, it is necessary to also perform a separate Agile e6 installation of the J2EE components with a separate user, or on a separate server.