Index

A B C D E F G H I J L M O P R S T U V W X

Numerics

10g Release 3 (10.1.3)

see Oracle Application Server 10g Release 3 (10.1.3)

A

admin_client.jar

management tasks you can perform, 5.5

using to manage OC4J instances and clusters, 5.5

administration OC4J instance

installing as part of a 10.1.3 cluster, 2.2.3.1

administration username

see oc4jadmin

admin.jar

replaced by admin_client.jar in a managed environment, 5.5

utility for standalone OC4J environments only, 3.3.2

adminstrator account

setting the default password, 2.2.3.1

when creating a new OC4J instance, 2.2.3.3

setting the default password for a cluster, 2.2.3.1

Advanced Installation Mode, 2.2.3.1

Ant

see Apache Ant

Apache 1.3 Web Server, 2.1.3.2, 2.2.3.2

Apache Ant

location in 10.1.3 Oracle home, 2.1.1, 2.2.1

project Web site, 2.1.3.4, 2.2.1, 2.2.3.5

using to rebuild the FAQApp EAR file, 2.1.3.4, 2.2.3.5

application clustering

configuring during deployment of FAQApp, 2.2.3.6

configuring in 10.1.3, 5.3.2

for session state replication, 5.3

replication methods available in 10.1.3, 5.3.2

Application Server Control Console

browsing the JNDI context, 3.8.4

displaying, 2.1.3.3

managing JNDI MBeans, 3.8.2

new version for 10.1.3, 1.1

using to manage OEMS JMS, 3.5.3

B

Basic Installation Mode, 2.1.3.1

C

Cluster Topology page, 2.1.3.3, 2.2.3.3, 2.2.3.4

using to view a 10.1.3 cluster, 5.1

viewing members of a cluster on, 2.2.3.1

cluster-config

deprecated element in server.xml, 5.3.1

cluster-island

deprecated attribute of the web-site element in the Web site configuration file, 5.3.1

clusters

configuring with a multicast address during installation, 2.2.3.1

differences between 10.1.3 and previous releases, 5.1

installing and configuring for 10.1.3, 2.2.3.1

setting the administrator password for, 2.2.3.1

using the cluster topology instead of an OracleAS Farm, 5.1

using the cluster topology page in 10.1.3, 5.1

verifying the installation and configuration of, 2.2.3.1

CMP Entity Beans

configuring to use Oracle TopLink, 3.10.1

co-existence

with previous application server releases, 4.1

com.evermind packages

deprecated security features for 10.1.3, 3.9.1

compatibility

between 10.1.3 and previous releases, 6

connection caching mechanism

for data sources, 3.3.1

connection URL

for JDBC connections, 2.1.3.3

context factories

for JNDI, 3.8.1

createinstance command, 5.4

using to create the FAQApp group, 2.2.3.3

verifying the new OC4J instance, 2.2.3.3

D

data sources

configuring for FAQApp, 2.1.3.3

configuring in a clustered environment, 2.2.3.4

considerations when redeploying applications on 10.1.3, 3.3

converting data-sources.xml to new 10.1.3 format, 3.3.2

JDBC-OCI drivers

using with 10.1.3, 3.3.3

managed data sources, 3.3.1

native data sources, 3.3.1

new connection caching mechanism for 10.1.3, 3.3.1

new features for 10.1.3, 3.3.1

potential problems during application deployment, 2.1.3.5

database transaction coordinator

replaced by two-phase commit (2pc) coordinator in 10.1.3, 3.6.1

data-sources.xml, 2.1.3.3

converting to new 10.1.3 format, 3.3.2

document-literal message format

when developing database Web services, 3.4.3

dosasprivileged-mode

deprecated security feature in 10.1.3, 3.9.1

E

EJB

see Enterprise Java Beans

End of Installation Screen, 2.1.3.1

Enterprise Java Beans

considerations when deploying applications on 10.1.3, 3.10

Example Connection Pool

configuring before deployment of the FAQApp application, 2.1.3.3

configuring for a group, 2.2.3.4

F

FAQ database schema

for the FAQApp sample application, 2.1.3.3

FAQApp

configuring application clustering for, 2.2.3.6

creating a group for, 2.2.3.3

deploying in a clustered environment, 2.2

overview, 2.2.2

procedure, 2.2.3

starting point, 2.2.1

deploying on a 10.1.3 clustered environment, 2.2.3.6

deploying to a single 10.1.3 instance, 2.1

overview, 2.1.2

procedure, 2.1.3

starting point, 2.1.1

location on OTN, 2.1.1

rebuilding the FAQApp EAR file, 2.1.3.4

required database schema, 2.1.3.3

screen shot of successful deployment on 10.1.3, 2.1.3.6

testing after deployment, 2.1.3.6, 2.2.3.7

troubleshooting, 2.1.3.5

FAQApp.ear

locating in the 9.0.4 or 10.1.2 Oracle home, 2.1.3.4, 2.2.3.5

location after using Apache Ant, 2.1.3.4, 2.2.3.5

rebuilding with required JSP libraries, 2.2.3.5

faq/dist/

in the FAQApp working directory, 2.2.3.5

faq/dist/

in the FAQApp working directory, 2.1.3.4

faq/lib/

in the FAQApp working directory, 2.2.3.5

faq/lib/

in the FAQApp working directory, 2.1.3.4

G

Group Administration page

using in 10.1.3, 5.2.1

Group page

using in 10.1.3, 5.2.1

groups

compared to OracleAS clusters, 5.2

configuring data sources for, 2.2.3.4

created automatically based on OC4J instance name, 5.2.2.3

creating a group, 2.2.3.3

differences from OracleAS Clusters, 5.2.2

important considerations when creating, 2.2.3.3

performing administration tasks on a group, 5.2.1

restarting, 2.2.3.4

H

httpd.conf, 1.2, 2.1.3.2, 2.2.3.2

I

installation options

Advanced Installation Mode, 2.2.3.1

Basic Installation Mode, 2.1.3.1

Integrated Web Server, J2EE Server and Process Management

installation type, 2.2.3.1

Integrated Web Server, J2EE Server and Process Management installation type, 2.2.3.1

islands

no longer supported in 10.1.3, 5.3.1

J

J2EE Application Deployment API (JSR-88), 3.1

JAAS mode

for security authorization, 3.9.1

Java 2, Enterprise Edition (J2EE) 1.4, 1.1

Java Management Extensions (JMX)

support for, 1.1

Java Messaging Service (JMS)

considerations when deploying application on 10.1.3, 3.5

nomenclature changes for 10.1.3, 3.5.1

see also Oracle Enterprise Messaging Service (OEMS) JMS, 3.5.1

Java Naming and Directory Interface (JNDI)

browsing the JNDI context in the Application Server Control Console, 3.8.4

considerations when deploying applications on 10.1.3, 3.8

deprecated context factories, 3.8.1

MBeans available in the Application Server Control Console, 3.8.2

new package names for initial JNDI context factories, 3.8.1

performing inter-application JNDI lookups, 3.8.3

Java Transaction API (JTA)

considerations when deploying applications on 10.1.3, 3.6

database transaction coordinator

replaced by two-phase commit (2pc) coordinator in 10.1.3, 3.6.1

support for two-phase commit (2pc) coordinator, 3.6.1

transaction propagation support, 3.6.2

JAX-RPC 1.1 specification, 3.4.2

jazn-data.xml

replaced by system-jazn-data.xml in 10.1.3, 3.9.1

JDBC

connection URL, 2.1.3.3

data source, 2.1.3.3

JDBC Resources

accessing from the OC4J Administration page, 2.1.3.3

configuring for a group, 2.2.3.4

setting the connection URL, 2.2.3.4

JDBC-OCI Drivers

using with 10.1.3, 3.3.3

JDK1.4

OracleAS JAAS Provider requirement, 3.9.1

JMS

see Java Messaging Service (JMS)

JMS Connector

resource adapter for OEMS JMS, 3.5.2

jms.xml

changes in 10.1.3, 3.5.4

JMX

see Java Management Extensions (JMX)

JNDI

see Java Naming and Directory Interface (JNDI)

jndi.properties

setting the oracle.j2ee.rmi.loadBalance property, 3.7.2

JSP

including standard tag libraries in an application EAR file, 2.1.3.4

new location of standard tag libraries, 3.2.2

rebuilding the FAQApp with, 2.2.3.5

standard tag libraries

jstl.jar, 2.2.3.5

standard.jar, 2.1.3.4, 2.1.3.4, 2.2.3.5

JSR-88

see J2EE Application Deployment API

jstl.jar

including in application EAR file before deployment, 2.1.3.4, 2.2.3.5

new location in 10.1.3, 3.2.2

L

load balancing

RMI requests, 3.7.2

loadbalancer.jar

no longer supported in 10.1.3, 5.3.1

M

managed data sources, 3.3.1

middle tiers

installing 10.1.3 middle tiers in an existing application server environment, 4.1

multicast discovery address

specifying during installation, 2.2.3.1

valid range, 2.2.3.1

O

OC4J

see Oracle Containers for J2EE

OC4J instances

creating, 5.4

oc4jadmin, 2.1.3.1

setting the default password, 2.1.3.1, 2.2.3.1, 2.2.3.1

when creating a new OC4J instance, 2.2.3.3

OEMS JMS

see Oracle Enterprise Messaging Service (OEMS) JMS

OJMS

see Oracle Enterprise Messaging Service (OEMS) JMS

OPMN

see Oracle Process Manager and Notification Server

opmnctl reload command

when creating a new OC4J instance, 2.2.3.3

opmn.xml

reloading when creating a new OC4J instance, 2.2.3.3

Oracle Application Server 10g Release 3 (10.1.3)

definition, 1.1

differences between 10.1.3 and previous releases, 5

installing, 1.2

installing a cluster, 2.2.3.1

installing in an existing application server environment, 4.1

key features, 1.1

redeploying existing J2EE applications on, 3

summary of changed features, 5.6

typical upgrade, 1.2

understanding the upgrade to, 1

version compatibility, 6

Oracle Containers for J2EE

new version for 10.1.3, 1.1

restarting the OC4J instance, 2.1.3.3

Oracle Enterprise Messaging Service (OEMS) JMS, 3.5.1

changes to jms.xml in 10.1.3, 3.5.4

creating connection factories and destinations, 3.5.3

Database option, 3.5.5

In-Memory and File-Based options, 3.5.2, 3.5.5

JAR files required when redeploying on 10.1.3, 3.5.5

Managing with Application Server Control, 3.5.3

redeploying a JMS application on 10.1.3, 3.5.4

Oracle HTTP Server

applying site-specific configuration settings, 1.2

in a clustered environment, 2.2.3.2

using existing installations with 10.1.3, 4.3

Oracle Internet Directory

using as an application security provider, 3.9.3

Oracle Process Manager and Notification Server, 5.1

new version for 10.1.3, 1.1

reloading when creating a new OC4J instance, 2.2.3.3

Oracle Technology Network

location of FAQApp sample application, 2.1.1

Oracle TopLink

configuring CMP Entity Beans to use Oracle TopLink, 3.10.1

considerations when deploying applications on 10.1.3, 3.10

upgrading TopLink Workbench projects, 3.10.2

OracleAS Farm

equivalent cluster topology in 10.1.3, 5.1

OracleAS Identity Management

compatibility with 10.1.3 middle tiers, 6

using as a security provider, 4.2

using with 10.1.3 middle tiers, 4.2, 6

OracleAS Infrastructure

using with 10.1.3 middle tiers, 4.2

OracleAS JAAS Provider, 3.9.1

OracleAS JMS

see Oracle Enterprise Messaging Service (OEMS) JMS

OracleAS Metadata Repository

not required for 10.1.3, 4.2

not required in 10.1.3, 6

OracleAS Single Sign-On, 3.9.3

configuring for deployed applications, 4.2

using to authenticate Web services, 4.2

using with 10.1.3 middle tiers, 4.2

OracleAS Web Cache

using as a reverse proxy for 10.1.3, 4.4

OracleASjms

resource adapter for OEMS JMS, 3.5.2

OracleDS data source

configuring, 2.1.3.3, 2.2.3.4

oracle.j2ee.rmi.loadBalance

system property for RMI load balancing, 3.7.2

orion-ejb-jar.xml, 3.10.1

OTN

see Oracle Technology Network

P

password

setting the default administrator password

during installation, 2.2.3.1

for a cluster, 2.2.3.1

when creating a new OC4J instance, 2.2.3.3

principals.xml, 3.9.1

converting to new 10.1.3 JAAS security model, 3.9.2

R

readme.txt, 2.2.3.1

for 10.1.3 installation details, 2.1.3.3

Real Application Clusters (RAC)

when using data sources for 10.1.3, 3.3.1

redeploying applications on 10g Release 3 (10.1.3), 3

data source considerations, 3.3

general considerations, 3.1

classloading and shared library support, 3.2.1

new location of JSP tag libraries, 3.2.2

overview, 3.1

Web services considerations, 3.4

Remote Method Invocation (RMI)

applying compatibility patches for 10.1.3, 3.7.1

configuring secure connections with RMIS and SSL, 3.7.4

considerations when deploying applications on 10.1.3, 3.7

new implementation of ORMI tunnelling through HTTP, 3.7.3

new system property for configuring ORMI request load balancing, 3.7.2

RPC-encoded message format

when developing database Web services, 3.4.3

runas-mode

deprecated security feature in 10.1.3, 3.9.1

S

security

application realm, 3.9.1

com.evermind packages deprecated for 10.1.3, 3.9.1

considerations when deploying applications on 10.1.3, 3.9

converting principals.xml to new JAAS security model, 3.9.2

external realm, 3.9.1

jazn-data.xml, 3.9.1

new consolidated JAAS mode, 3.9.1, 3.9.1

OracleAS JAAS Provider requirements, 3.9.1

significant changes for 10.1.3, 3.9.1

system-jazn-data.xml, 3.9.1

using OracleAS Identity Management as a security provider, 4.2

XMLUserManager security class, 3.9.1

Security Assertion Markup Language

using to authenticate Web services, 4.2

security provider

using Oracle Internet Directory, 3.9.3

session state replication

configuring with 10.1.3 application clustering, 2.2.3.6

SQL

responding to SQL error messages during application deployment, 2.1.3.5

standard.jar

including in application EAR file before deployment, 2.1.3.4, 2.2.3.5

new location in 10.1.3, 3.2.2

step-by-step examples

upgrading to 10.1.3, 2

system-jazn-data.xml, 3.9.1

T

TopLink

see Oracle TopLink

toplink-ejb-jar.xml, 3.10.1

tunnelling

for RMI through HTTP, 3.7.3

two-phase commit (2PC) coordinator

for Java Transaction API (JTA), 3.6.1

U

upgrade

documentation roadmap for, 1.3

step-by-step examples, 2

to 10g Release 3 (10.1.3)

understanding, 1

typical upgrade to 10.1.3, 1.2

USE_JAAS

deprecated security feature in 10.1.3, 3.9.1

UserManager

custom security classes, 3.9.1

V

verifying new OC4J instances, 2.2.3.3

W

Web services

considerations when assembling from Java Classes in 10.1.3, 3.4.2

considerations when redeploying on 10.1.3, 3.4

developing database Web services in 10.1.3, 3.4.3

Web Services Assembler

new version (wsa.jar) for 10.1.3, 3.4.1

WebServicesAssembler.jar

compatibility with new wsa.jar, 3.4.1

wsa.jar

compatibility with WebServicesAssembler.jar, 3.4.1

new Web Services Assembler for 10.1.3, 3.4.1

using to develop database Web services, 3.4.3

X

XMLUserManager security class

converting to new JAAS security model, 3.9.2

support in 10.1.3, 3.9.1