Oracle Plug-in for Microsoft IIS Configuration and User's Guide
Release 1.0.2 for Windows

Part Number A87355-01

Library

Solution Area

Contents

Index

Go to previous page Go to next page


Preface

This manual describes how to configure and use Oracle Plug-in for Microsoft IIS.

This preface contains these topics:

Audience

Oracle Plug-in for Microsoft IIS Configuration and User's Guide is intended for users who want to access PL/SQL and Java Web components, within the Oracle database, from Microsoft Internet Information Server (IIS).

To use this document, you need to be familiar with the following:

Organization

This document contains:

Chapter 1, "Oracle Plug-in for Microsoft IIS Overview"

This chapter provides an overview of Oracle Plug-in for Microsoft IIS and describes the supported transaction types for PL/SQL and Java Web components.

Chapter 2, "Configuring Oracle Plug-in for Microsoft IIS"

This chapter describes how to register and load Oracle Plug-in for Microsoft IIS and how to access PL/SQL and Java Web components.

Chapter 3, "How to Use Oracle Plug-in for Microsoft IIS"

This chapter describes how to create PL/SQL Web components and trace component requests.

Related Documentation

For more information, see these Oracle resources:

In North America, printed documentation is available for sale in the Oracle Store at

http://oraclestore.oracle.com/

Customers in Europe, the Middle East, and Africa (EMEA) can purchase documentation from

http://www.oraclebookshop.com/

Other customers can contact their Oracle representative to purchase printed documentation.

To download free release notes, installation documentation, white papers, or other collateral, please visit the Oracle Technology Network (OTN). You must register online before using OTN; registration is free and can be done at

http://technet.oracle.com/membership/index.htm

If you already have a username and password for OTN, then you can go directly to the documentation section of the OTN Web site at

http://technet.oracle.com/docs/index.htm

Conventions

This section describes the conventions used in the text and code examples of this documentation set. It describes:

Conventions in Text

We use various conventions in text to help you more quickly identify special terms. The following table describes those conventions and provides examples of their use.

Convention  Meaning  Example 

Bold 

Bold typeface indicates terms that are defined in the text or terms that appear in a glossary, or both. 

The C datatypes such as ub4, sword, or OCINumber are valid.

When you specify this clause, you create an index-organized table.  

Italics 

Italic typeface indicates book titles, emphasis, syntax clauses, or placeholders. 

Oracle8i Concepts

You can specify the parallel_clause.

Run Uold_release.SQL where old_release refers to the release you installed prior to upgrading. 

UPPERCASE monospace (fixed-width font) 

Uppercase monospace typeface indicates elements supplied by the system. Such elements include parameters, privileges, datatypes, RMAN keywords, SQL keywords, SQL*Plus or utility commands, packages and methods, as well as system-supplied column names, database objects and structures, user names, and roles. 

You can specify this clause only for a NUMBER column.

You can back up the database using the BACKUP command.

Query the TABLE_NAME column in the USER_TABLES data dictionary view.

Specify the ROLLBACK_SEGMENTS parameter.

Use the DBMS_STATS.GENERATE_STATS procedure. 

lowercase monospace (fixed-width font) 

Lowercase monospace typeface indicates executables and sample user-supplied elements. Such elements include computer and database names, net service names, and connect identifiers, as well as user-supplied database objects and structures, column names, packages and classes, user names and roles, program units, and parameter values. 

Enter sqlplus to open SQL*Plus.

The department_id, department_name, and location_id columns are in the hr.departments table.

Set the QUERY_REWRITE_ENABLED initialization parameter to true.

Connect as oe user. 

Conventions in Code Examples

Code examples illustrate SQL, PL/SQL, SQL*Plus, or other command-line statements. They are displayed in a monospace (fixed-width) font and separated from normal text as shown in this example:

SELECT username FROM dba_users WHERE username = 'MIGRATE';

The following table describes typographic conventions used in code examples and provides examples of their use.

Convention  Meaning  Example 

[ ] 

Brackets enclose one or more optional items. Do not enter the brackets. 

DECIMAL (digits [ , precision ]) 

{ } 

Braces enclose two or more items, one of which is required. Do not enter the braces. 

{ENABLE | DISABLE} 

A vertical bar represents a choice of two or more options within brackets or braces. Enter one of the options. Do not enter the vertical bar. 

{ENABLE | DISABLE}

[COMPRESS | NOCOMPRESS] 

... 

Horizontal ellipsis points indicate either:

  • That we have omitted parts of the code that are not directly related to the example

  • That you can repeat a portion of the code

 

CREATE TABLE ... AS subquery;

SELECT col1, col2, ... , coln FROM employees; 

.

.

Vertical ellipsis points indicate that we have omitted several lines of code not directly related to the example. 

 

Other notation 

You must enter symbols other than brackets, braces, vertical bars, and ellipsis points as it is shown. 

acctbal NUMBER(11,2);

acct CONSTANT NUMBER(4) := 3; 

Italics 

Italicized text indicates variables for which you must supply particular values. 

CONNECT SYSTEM/system_password 

UPPERCASE 

Uppercase typeface indicates elements supplied by the system. We show these terms in uppercase in order to distinguish them from terms you define. Unless terms appear in brackets, enter them in the order and with the spelling shown. However, because these terms are not case sensitive, you can enter them in lowercase. 

SELECT last_name, employee_id FROM employees;

SELECT * FROM USER_TABLES;

DROP TABLE hr.employees; 

lowercase 

Lowercase typeface indicates programmatic elements that you supply. For example, lowercase indicates names of tables, columns, or files. 

SELECT last_name, employee_id FROM employees;

sqlplus hr/hr 

Conventions for Windows Operating Systems

The following table describes conventions for Windows operating systems and provides examples of their use.

Convention  Meaning  Example 

Choose Start > 

How to start a program. For example, to start Net8 Assistant, you must click the Start button on the taskbar and then choose Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.  

Choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant 

C:\> 

Represents the Windows command prompt of the current hard disk drive. Your prompt reflects the subdirectory in which you are working. Referred to as the command prompt in this guide. 

C:\oracle\oradata> 

HOME_NAME 

Represents the Oracle home name.

The home name can be up to sixteen alphanumeric characters. The only special character allowed in the home name is the underscore.  

OracleHOME_NAMETNSListener 

ORACLE_HOME and ORACLE_BASE 

In releases prior to 8.1, when you installed Oracle, all subdirectories were located under a top level ORACLE_HOME directory that by default was:

  • C:\orant for Windows NT

  • C:\orawin95 for Windows 95

  • C:\orawin98 for Windows 98

or whatever you called your Oracle home.

In this Optimal Flexible Architecture (OFA)-compliant release, all subdirectories are not under a top level ORACLE_HOME directory. There is a top level directory called ORACLE_BASE that by default is C:\oracle. If you install Oracle8i release 9.0 on a clean computer (that is, there is no other Oracle software on the computer), the default setting for the first Oracle home directory is C:\oracle\ora90. The Oracle home directory is located directly under ORACLE_BASE.

All directory path examples in this guide follow OFA conventions.

See Oracle8i Administrator's Guide for Windows for additional information on OFA compliances and for information on installing Oracle products in non-OFA compliant directories. This manual is available from Oracle Technology Network (OTN). See "Related Documentation" for information on how to access OTN. 

Go to the ORACLE_BASE\ORACLE_HOME\rdbms\admin directory.

 


Go to previous page Go to next page
Oracle
Copyright © 1996-2000 Oracle Corporation.

All Rights Reserved.

Library

Solution Area

Contents

Index