11 Architecture

This section contains the following topics:

• Section 11.1, "Client Tier"

• Section 11.2, "Application Tier"

• Section 11.3, "Database Tier"

Figure 11-1 shows the logical Oracle Health Sciences Data Management Workbench (Oracle DMW) architecture that is described in the following sections.

Figure 11-1 Oracle Health Sciences Data Management Workbench Architecture

Description of ''Figure 11-1 Oracle Health Sciences Data Management Workbench Architecture''

11.1 Client Tier

There are two ways to set up a client, depending on the type of user:

Most Users Oracle DMW who do not write custom programs for transformations and validation checks, require the following on their personal computers:

• A Web browser

• Java Virtual Machine (JVM)

Administrators require JVM to use any of the Oracle Forms screens related to security, including setting up user accounts, and to run the post-installation jobs.

Programmers Users who write custom programs in an integrated development environment from Oracle LSH require additional software:

• One or more integrated development environments such as SAS PC, SQL*Plus, SQL Developer, or Informatica PowerCenter client.

• Oracle LSH plug-in for launching Integrated Development Environments (IDEs)

• WinZip

• Web browser

11.2 Application Tier

Oracle DMW has two distinct application tiers:

11.2.1 Oracle Life Sciences Data Hub Application Tier

In addition to standard Oracle Applications components, Oracle LSH's application tier includes the following:

Oracle LSH Application Server The Oracle LSH Application Server renders the user interface using the Oracle Applications Framework and handles the communication between the user interface and the database using the Java Runtime Environment.

Oracle LSH Distributed Processing (DP) Server The Oracle LSH DP Server handles the communication between Oracle LSH and the external processing systems required to support the IDEs.

Processing Systems XML Publisher is required for internal Oracle LSH processing. The other systems are required only if you are developing Oracle LSH Programs in those technologies:

• SAS executes user-developed SAS Programs.

• Informatica PowerCenter executes user-developed Informatica programs.

11.2.2 Oracle Health Sciences Data Management Workbench Application Tier

The Oracle DMW-specific application tier requires Oracle WebLogic Server and Oracle Applications Developer.

11.3 Database Tier

Oracle DMW uses the Oracle LSH database tier , which includes:

Oracle Enterprise Edition RDBMS All of Oracle LSH's database tier components use the Oracle Enterprise Edition database server and database.

Oracle Applications Schema The Oracle Applications Schema is the schema installed as part of the Oracle Applications installation. It contains the Oracle LSH schema.

Oracle LSH Database Server and Schema These include Oracle LSH's business logic in PL/SQL packages, internal Oracle LSH tables and views, security, adapters, and APIs; as well as Oracle LSH user-developed metadata tables and packages.

Oracle Warehouse Builder (OWB) Oracle LSH uses the OWB Java Server and schema for running and tracking internal and external jobs. Oracle LSH uses the following custom OWB operators:

• The OWB PL/SQL operator communicates with SQL*Plus, which runs many of Oracle LSH's internal processes as well as user-developed PL/SQL Programs.

• The OWB Workflow operator communicates with Oracle Workflow.

• The OWB Distributed Processing (DP) Server operator communicates with external processing engines to run jobs in external technologies.

Oracle Thesaurus Management System (TMS) Oracle LSH's classification system is based on TMS.