Install Oracle Express Server
Install Oracle Express Server
Install Oracle Express Server
Release 6.3.1
April 2000
Part No. A81031-01
Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris, Release 6.3.1
The Programs (which include both the software and documentation) contain proprietary information of
Oracle Corporation; they are provided under a license agreement containing restrictions on use and
disclosure and are also protected by copyright, patent, and other intellectual and industrial property
laws. Reverse engineering, disassembly, or decompilation of the Programs is prohibited.
The information contained in this document is subject to change without notice. If you find any problems
in the documentation, please report them to us in writing. Oracle Corporation does not warrant that this
document is error free. Except as may be expressly permitted in your license agreement for these
Programs, no part of these Programs may be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without the express written permission of Oracle Corporation.
If the Programs are delivered to the U.S. Government or anyone licensing or using the Programs on
behalf of the U.S. Government, the following notice is applicable:
Restricted Rights Notice Programs delivered subject to the DOD FAR Supplement are "commercial
computer software" and use, duplication, and disclosure of the Programs, including documentation,
shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement.
Otherwise, Programs delivered subject to the Federal Acquisition Regulations are "restricted computer
software" and use, duplication, and disclosure of the Programs shall be subject to the restrictions in FAR
52.227-19, Commercial Computer Software - Restricted Rights (June, 1987). Oracle Corporation, 500
Oracle Parkway, Redwood City, CA 94065.
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently
dangerous applications. It shall be the licensee’s responsibility to take all appropriate fail-safe, backup,
redundancy, and other measures to ensure the safe use of such applications if the Programs are used for
such purposes, and Oracle Corporation disclaims liability for any damages caused by such use of the
Programs.
Oracle and Personal Express are registered trademarks, and Express, Oracle7, Oracle8, Oracle8i, and
Net8 are trademarks or registered trademarks of Oracle Corporation. All other company or product
names mentioned are used for identification purposes only and may be trademarks of their respective
owners.
Contents
Preface............................................................................................................................................................ ix
Related Documentation......................................................................................................................... x
Conventions ............................................................................................................................... ............ xii
2 Pre-Installation
Getting Ready for Installation ......................................................................................................... 2-1
Viewing Additional Documentation .............................................................................................. 2-2
Identifying the Products That You Want to Install ...................................................................... 2-3
Choosing an Oracle Home ................................................................................................................ 2-5
Setting Up Express Server’s User Accounts................................................................................... 2-7
Upgrading Express Databases.......................................................................................................... 2-9
Deinstalling 6.2.x.x and Earlier Software Versions .................................................................... 2-10
iii
3 Installation
Basic Installation ............................................................................................................................... .. 3-1
Choices in a Custom Installation ..................................................................................................... 3-8
Communications ............................................................................................................................... .. 3-9
Optional Express Products .............................................................................................................. 3-11
Managing the Service Environment.............................................................................................. 3-12
Upgrading........................................................................................................................................... 3-14
Installing an Express Instance Manager Web Site ..................................................................... 3-15
Providing Documentation to the User Community ................................................................... 3-18
iv
6 Security
Restricting Access to Your Data ....................................................................................................... 6-2
Creating a Secure Express Server Instance .................................................................................... 6-2
Identities Used by Express Server ................................................................................................... 6-3
Establishing a Client’s Identity........................................................................................................ 6-4
Establishing the Session Identity .................................................................................................... 6-5
Establishing the File Owner ............................................................................................................. 6-7
Controlling Access to Files................................................................................................................ 6-8
Establishing the Base File Mode.................................................................................................... 6-11
Modifying Access Rights to Existing Files .................................................................................. 6-13
Limiting Access to the Operating System.................................................................................... 6-14
8 Monitoring Performance
Basic Tuning Guidelines ................................................................................................................... 8-1
Simulating Test Sessions................................................................................................................... 8-3
Monitoring Performance ................................................................................................................... 8-4
Tuning Performance-Related Parameters....................................................................................... 8-7
Understanding Database Paging ..................................................................................................... 8-8
How the Paging Manager Reclaims Cache Memory ................................................................. 8-10
v
Providing ODBC Support ............................................................................................................... 9-14
Defining ODBC Data Sources........................................................................................................ 9-15
Testing Your Configuration............................................................................................................. 9-19
Index
vi
Send Us Your Comments
Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris, Release
6.3.1
Part No. A81031-01
Oracle Corporation welcomes your comments and suggestions on the quality and usefulness of this
publication. Your input is an important part of the information used for revision.
■ Did you find any errors?
■ Is the information clearly presented?
■ Do you need more information? If so, where?
■ Are the examples correct? Do you need more examples?
■ What features did you like most about this manual?
If you find any errors or have any other suggestions for improvement, please indicate the chapter,
section, and page number (if available). You can send comments to us in the following ways:
■ E-mail - [email protected]
■ FAX - 781-684-5880. Attn: Oracle Express Server
■ Postal service:
OLAP Products Documentation Manager
Oracle Corporation
200 Fifth Avenue
Waltham, MA 02451-8720
USA
If you would like a reply, please give your name, address, and telephone number below.
If you have problems with the software, please contact your local Oracle Support Services.
vii
viii
Preface
Intended audience
This manual is intended for system administrators.
ix
■ Chapter 9 explains how to configure your system to access data stored in
relational databases.
■ Chapter 10 explains how to configure your system to translate to and from
other single-byte character sets.
Related Documentation
Books
This manual is part of a documentation set that also includes the following books:
■ Oracle Express Database Administration Guide — Describes the structure of
Express data and explains how to create and maintain Express databases. The
guide also explains how to configure Express databases for use with client
applications.
■ Oracle Express Programmer’s Guide to the Express Language — Explains the
programming environment for Express, the structure of Express data, the
Express language, and how to write Express programs. The guide also
illustrates programming strategies for accessing and working with data.
■ Oracle Express SNAPI Guide — Explains how to use SNAPI to connect to Oracle
Express Server or Personal Express and obtain Express data. The guide also
provides installation instructions and setup information.
■ Oracle Express Web Products Installation Guide — Explains how to install and
configure the server-side components of Oracle Express Web Agent and Oracle
Express Web Publisher.
■ Oracle Express Web Agent User’s Guide — Explains how to create an Express
application that generates and manipulates dynamic views of Express data for
display by Web browsers.
■ Oracle Express Web Agent Guide to Add-In Views— Explains how a programmer
can design and implement add-in views, which are custom view types that are
not delivered with Oracle Express Web Agent.
■ Oracle Express Relational Access Manager User’s Guide — Explains how to use
Oracle Express Relational Access Manager to enable Express applications to
access and display data from a relational database. The guide also explains
fundamental concepts pertaining to data warehouse design and optimization.
x
Help files
The documentation set for Express Server also includes the following Help files:
■ Oracle Express Instance Manager Help — Provides online Help for managing
Oracle Express Server, including starting, stopping, and managing Express
services, selecting Express modules and configuring runtime settings for
Express services, and monitoring individual Express client sessions.
■ Express Language Help — Provides online Help for the commands, functions,
options, and programs that make up the Express language.
■ Oracle Express Administrator Help — Provides online Help for creating
Express databases and configuring Express databases for use with client
applications.
■ Express Web Agent Help — Provides online Help for Express Web Agent
programs, objects, and properties, which are used to generate and manipulate
dynamic views of Express data for display by Web browsers.
■ Oracle Express Relational Access Administrator Help — Provides online Help
for defining an Express data model, building a supporting data warehouse
schema, mapping the data model to the schema, and maintaining a
corresponding Express database.
■ Relational Access Manager – Query Statistics Help — Provides online Help for
reporting statistics about runtime query activity in the data warehouse as a
means of evaluating the performance of an Oracle Express Relational Access
Manager system.
xi
Conventions
Text conventions
You will find the following text conventions in this document.
Convention Usage
Boldface text Indicates menu items, command buttons, options, field names,
and hyperlinks.
Bold text is also used for notes and other secondary information
in tables (for example, Result).
Fixed-width text Indicates folder names, file names, operating system
commands, and URLs. Also indicates examples and anything
that you must type exactly as it appears.
For example: If you are asked to type show eversion, you
would type all the characters exactly as shown in the
fixed-width font.
Italic text Indicates variables, including variable text. Variable text is used
when dialog boxes or their components are unlabeled or have
labels that change dynamically based on their current context.
The wording of variable text does not exactly match what you
see on your screen.
Italic type is also used for emphasis, for new terms, and for titles
of documents.
Underlined text Indicates a default value in descriptions of Express language
syntax.
UPPERCASE text Indicates Express commands and objects and acronyms.
Mouse usage
Always use the left mouse button unless you are specifically instructed to use the
right mouse button.
The term “left mouse button” refers to the dominant button. If you have
reconfigured your mouse to reverse the functions of the left and right buttons, then
you will need to use the reverse button when you follow the procedures in this
manual.
xii
Formats for key combinations and sequences
Key combinations and key sequences appear in the following formats.
xiii
xiv
1
Introducing Oracle Express Server
Chapter summary
This chapter explains basic system concepts that apply to Oracle® Express Server 6
(hereinafter referred to as “Express Server”). All subsequent chapters in this manual
assume that you understand these basic concepts.
List of topics
This chapter includes the following topics:
■ System Overview
■ The Client Side
■ Understanding Services
■ Understanding the Express Service Environment
■ Understanding Installations and Instances
■ Understanding Connections and Sessions
System Overview
Modular architecture
Express Server is implemented as a collection of dynamically linked, shareable
libraries that are known as modules. Some of these modules are required for any
working instance of Express Server. Others support optional features and are
required only if you want to support those features.
Express services
Each instance of Express Server runs as a service. On Unix systems, Express services
have their own service control environment.
Express language
The Express language is sometimes called an SPL (Stored Procedure Language).
Express language programs are equivalent to the stored procedures of a Relational
Database Management System (RDBMS). The Express language is documented in
the Express Language Help and the Oracle Express Programmer’s Guide to the Express
Language.
Command processing
Client applications send scripts of Express language code to the server. Express
Server processes this code and returns the results to the client. The results can
include Express data. Client applications might or might not provide user access to
the Express language.
1-2 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
The Client Side
Understanding Services
What is a service?
A computer service provides a basic capability to a community of users. A service is
defined by:
■ The type of capability it offers
■ A set of configuration parameters
Configuration parameters distinguish one service from another that offers the same
capabilities.
A print service exemplifies the concept of a service. A print service allows users to
send documents to be printed. Print services are distinguished from each other by
such parameters as format (Postscript, PCL, and so on), accessibility (which users
are allowed to use a printer), and other characteristics, such as physical location.
System administrators create and control services. An administrator can start and
stop a service, and can change its parameters. An administrator can also configure a
service to start automatically when a computer is booted.
1-4 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Understanding the Express Service Environment
The daemons
The primary components of the Express service environment are several Unix
processes that are always running. These daemon processes implement the service
control management of Express Server instances. They support the activities you
initiate from Express Instance Manager: the starting, stopping, creating, destroying,
and configuring of Express services.
Most of the daemons run under the root identity and handle specific functions that
must be performed by the root user.
Master daemon
The Express service environment master daemon, xsdaemon, serves as the anchor
point for the Express service environment. The master daemon is installed on all
Unix platforms and runs as root.
The master daemon performs the following functions:
■ Sets up the rest of the service environment
■ Starts supporting daemons/processes
■ Starts Express Server instances that are configured to start automatically
■ Starts manual Express Server instances when requested
■ Provides interprocess connections between supporting processes
■ Intercepts and handles errors and abnormal terminations from Express Server
instances and supporting processes
■ Provides for the graceful termination of running Express Server instances,
supporting processes, and interprocess communications during environment
shutdown
■ Provides support for Oracle Express Instance Manager
Authentication daemon
The Express service environment authentication daemon, xsauthn, allows Express
services to authenticate clients in a shadow password file. The authentication
daemon runs as root.
Authorization daemon
The Express service environment authorization daemon, xsauthz, sets the access
permissions to files created by Express Server so that both the user who created the
file and the identity under which Express Server runs have the necessary access
rights. The authorization daemon runs as root.
1-6 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Understanding Installations and Instances
Agent daemon
The Express service environment agent daemon, xsagent, acts as the intermediary
between Express services, the oes.key configuration file, and Express Instance
Manager. The configuration agent daemon runs as the Installation User.
Overview
An Express service is an instance of Express Server that is derived from a given
Express Server installation. Each Express service has its own module list and its
own configuration settings.
Default services
The default Express service is defined by the installation process. It uses the
identifiers that are normally expected by Express clients. For example, most Express
applications by default try to connect to an Express service on port 12287. Only one
service can have this identifier, and it is the default for all SNAPI clients.
What is a connection?
A connection is a conversation between a client process and an instance of Express
Server. The connection may be managed by SNAPI, XCA, or Express Web Agent.
What is a session?
Whether a client connection is initiated through SNAPI, XCA, or the Web, Express
Server identifies a session for its interaction with that client. The session provides a
logical context in which Express Server executes Express language code.
A session usually exists within the context of a client/server connection. Ordinarily,
each client’s session is private. That is, Express Server ensures that it is not affected
by the activities of other clients. For example, one client might want two decimal
places displayed in all reports while another might require four, so Express Server
ensures that each session has its own setting for the number of decimal places.
Session sharing
In some circumstances, two related clients might need to work within the same
session. To make this possible, Express Server may be configured to support the
sharing of sessions. When an Express service is configured to support session
sharing, its clients can call an Express language function to make their sessions
shareable.
1-8 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
2
Pre-Installation
Chapter summary
This chapter describes the decisions that you need to make before installation, and
how to set up your system so that the installation is successful.
List of topics
This chapter includes the following topics:
■ Getting Ready for Installation
■ Viewing Additional Documentation
■ Identifying the Products That You Want to Install
■ Choosing an Oracle Home
■ Setting Up Express Server’s User Accounts
■ Upgrading Express Databases
■ Deinstalling 6.2.x.x and Earlier Software Versions
Computer configuration
The product release notes specify both the minimum and the recommended
configuration. Verify that your computer meets or exceeds these hardware
requirements and is running under a supported operating system. Running Express
Server on outdated and underpowered computer hardware will result in poor
Pre-Installation 2-1
Viewing Additional Documentation
Pre-installation checklist
You must perform the following tasks, as described in this chapter, before installing.
Task Instructions
Identify Oracle home. The owner of Oracle home is “Choosing an Oracle Home” on
the Installation user, under whose identity you will page 2-5
install Express Server. You also need to perform some
installation steps under the “root” or “super user”
identity, so be sure you know the password.
Create accounts for the various roles that Express “Setting Up Express Server’s User
Server plays: the DBA role, Initialize role, and Default Accounts” on page 2-7
role.
Upgrade existing Express databases. “Upgrading Express Databases” on
page 2-9
Stop any existing Express services. “Stopping the service
environment” on page 2-10
Finding documentation
Instructions for viewing documentation on the installation CD are available in the
readme.txt file on the Oracle OLAP Express Server CD.
2-2 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Identifying the Products That You Want to Install
Pre-Installation 2-3
Identifying the Products That You Want to Install
Software dependencies
The following table identifies software that is required for a software package on
the Server CD to work.
2-4 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Choosing an Oracle Home
Pre-Installation 2-5
Choosing an Oracle Home
down the Express service environment before installing Express Server, even if its
components are installed in a different Oracle home.
2-6 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Setting Up Express Server’s User Accounts
OLAP home
OLAP home is the path under Oracle home where OLAP products are installed on
the host. During installation of Express Server, Installer identifies OLAP home as
the olap subdirectory of Oracle home.
Environment–variable descriptions
The Oracle–specific environment variables defined during installation are listed in
the following table.
Pre-Installation 2-7
Setting Up Express Server’s User Accounts
Installation user
To install any Express products, you must log into your Unix system as the
Installation user. The Installation user owns all the installed files. The home
directory of the Installation user is typically, but does not have to be, Oracle home
for Express Server.
The oes.key file, which is the repository for all parameter settings for Express
services, is owned by the Installation user. The xsagent daemon, which accesses
the oes.key file on behalf of the Express Agent and Express Server, runs as the
Installation user.
DBA user
Each Express service runs as the DBA user. All files created by Express services will
be owned, at least initially, by the DBA user for that service.
The DBA user must have full access to all directories in which the Express service
will create databases and other files.
Initialize user
The optional Persistent Session runs as the Initialize user. A Persistent Session is a
special session that is active as long as the Express service is running. It is a
mechanism for periodically executing scripts of Express language commands.
The Initialize user must have the file system and shell privileges that are needed for
the Express language commands that are executed by the Persistent Session.
Default user
Anonymous sessions run as the Default user. An anonymous session is one for
which the client does not provide a user name and password. The default security
for Express Server allows anonymous sessions, but more stringent security schemes
that are available in Express Server do not allow them.
The Default user must have the file system and shell privileges that are needed by
anonymous Express sessions. Typically, the access rights of the Default user are
limited.
2-8 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Upgrading Express Databases
Pre-Installation 2-9
Deinstalling 6.2.x.x and Earlier Software Versions
Related information
For the syntax of the EXPORT and IMPORT commands, search for them in Express
Language Help.
2-10 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Deinstalling 6.2.x.x and Earlier Software Versions
Pre-Installation 2-11
Deinstalling 6.2.x.x and Earlier Software Versions
2-12 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
3
Installation
Chapter summary
This chapter explains how to install Express Server and its administration tools and
utilities.
List of topics
This chapter includes the following topics:
■ Basic Installation
■ Optional Express Products
■ Choices in a Custom Installation
■ Communications
■ Managing the Service Environment
■ Upgrading
■ Installing an Express Instance Manager Web Site
■ Providing Documentation to the User Community
Basic Installation
Installation 3-1
Basic Installation
3-2 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Basic Installation
Result: The results vary depending on your installation choice and previously
installed software.
4. If you chose a Custom installation, you see the Available Product Components
page.
Scroll through the list and select the components that you want to install. For
descriptions of these products, refer to “Choices in a Custom Installation” on
page 3-8.
To select language support:
a. Click the Product Languages button.
Result: You see the Language Selection dialog box.
b. Select a language.
c. Click OK.
5. If Oracle Application Server 4.x is detected on your computer, you see the
Application Server Configuration page.
Refer to the Oracle Express Web Products Installation Guide for installation
instructions.
6. If the Installer detects an existing installation of Express Server in a different
Oracle home, you see the Oracle Express Server Base Components page. To
allow older installations to continue operating, select Yes.
The older Express service environment will be disabled, but the new Express
service environment, which runs in the current Oracle home, will have the
configuration settings for both old and new Express services.
7. Review the Summary page to verify that the installation includes the
components that you wish to install. Then click Install.
Result: You will be prompted to run the root.sh script in Oracle home.
8. To run the root.sh script:
a. Open a new command window.
b. Log in as root with a command such as this:
su -
c. Change directories to Oracle home with a command such as this:
cd /home/oracle
Installation 3-3
Basic Installation
Tip: You may want to follow a Typical, Minimum, or Complete install with a
Custom install, if your installation requires additional optional modules. Check
the table in “Installation of optional modules” on page 3-6.
3-4 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Basic Installation
Installation 3-5
Basic Installation
3-6 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Basic Installation
Installer components
Oracle Universal Installer is installed automatically on your computer. The Oracle
Home Selector is installed also, which is useful for changing the default Oracle
home.
Installation 3-7
Choices in a Custom Installation
Types of choices
When you perform a custom installation, you make selections from a list of
available product components. These components are organized into the following
groups:
■ Optional Express Server modules, as described in “Optional modules” on page
3-9.
■ Oracle Express Server Configurations, as described in “Communication
configurations” on page 3-9.
■ Optional Express Products, as described in “Optional Express Products” on
page 3-11.
■ Installer Components, which include the Home Selector.
3-8 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Communications
Optional modules
The optional modules offered during Express Server custom installation are
described in the following table.
Module Description
Oracle Express Shell Enables users to execute operating system commands from
Command within Express Server.
Oracle Express Initial Enables Express Server to support automatic execution of
Session Express scripts on startup, shutdown, or at periodic intervals.
Also called the Persistent Session.
Oracle Express Test Enables multi-session testing of Express Server using an input
Engine Facility file of Express commands.
Oracle Express SQL Enables users to execute SQL commands from within Express
Server. It must be used with Oracle Express Call Interface or
Oracle Express Database Connection modules.
Oracle Express Database Used with the Express SQL module, enables communication
Connection with ODBC data sources.
Oracle Express Call Used with the Express SQL module, enables communication
Interface with Oracle relational databases such as Oracle8.
Oracle Express External Enables Express sessions to invoke functions defined in
Call Support external libraries.
Oracle Express Exports counter objects that can be used to monitor Express
Performance Monitor services in the Windows NT Performance Monitor.
Communications
Communication configurations
Express Server supports several types of communications. Your installation must
include one or more of them, depending upon the communication requirements of
your client applications.
Installation 3-9
Communications
Protocol Description
Oracle SNAPI Server Provides the server-side component of client-server
communications for Express applications such as Oracle
Sales Analyzer.
Oracle SNAPI Server Remote Extends SNAPI Server support to Unix platforms.
Operations
Oracle Express Communications Provides peer-to-peer communications between two
Architecture instances of Express.
Oracle Express Web Agent Enables Express Web applications to communicate with
Server Express Server.
Oracle Express Web Agent Extends Web support to Unix platforms.
Remote Operations
3-10 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Optional Express Products
Users of these applications can access Express multidimensional data from any
computer platform, without installing additional client software.
Express Web Agent is used by Oracle Express Web Publisher and the Web
components of other Express applications.
In order to run Express Web Agent applications, you must have a Web listener
installed and configured according to the instructions in the Oracle Express Web
Products Installation Guide.
Overview
The various installation options for Express Server differ primarily in the optional
components that are installed along with Express Server and Express Instance
Manager. Using the following descriptions, you can decide which of these
components you need to install.
Software dependencies
The following table identifies the dependencies among the Express components.
You can install components individually in a custom installation.
Installation 3-11
Managing the Service Environment
Introduction
The express.sh script controls the Express service environment. If you run it
without arguments to the command, like you did when first installing Express
Server, you can reset various options. Or, you can stop and start the Express service
environment using existing options.
3-12 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Managing the Service Environment
Installation 3-13
Upgrading
Upgrading
Service identifiers
All versions of Express Server use the same default identifiers. If you are running
more than one version of Express Server on a host (such as the current production
version plus the newly installed 6.3 version) you must decide which service will use
the default identifiers. This is the service that client applications will connect to
automatically.
You must modify all other services to use different identifiers. Problems will result
if you try running multiple versions of Express Server using the same identifiers.
All versions of Express Server and Personal Express, including versions of Express
earlier than 6.0, use 6543 as the default port for XCA connections. You cannot
change the port number for Express 5.x. Therefore, if you want to continue to
support Release 5, then you must configure all Release 6 services on that host to use
different XCA port numbers.
3-14 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Installing an Express Instance Manager Web Site
■ Log into the service in Express Instance Manager and look at the State page of
the Instance sheet. It shows the build number of Express Agent.
Database aliases
Express Server reads only the database aliases defined in its own Oracle home,
therefore it cannot read the database aliases created for versions of Express Server
earlier than Release 6.3. To recreate your database aliases, use the Net8 Easy
Configuration Utility that is installed in the same Oracle home as your new version
of Express Server.
Overview
One of several ways that you can run Express Instance Manager is through a Web
browser. To make this method available, you must create a Web site so that Express
Instance Manager files are available to the Web listener.
After you have created this Web site, you can run Express Instance Manager from
any machine where the browser has been configured properly, without installing
Installation 3-15
Installing an Express Instance Manager Web Site
the Express Instance Manager files locally on each machine. Instructions for
configuring a browser and viewing the Web site are provided in “Starting Express
Instance Manager in a browser” on page 4-3.
Web Browser
Instance
CO
Manager
RB
Files
A
an
d
So
ck
et
Co
m
m
un
ica
tio
ns
Express
Server
3-16 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Installing an Express Instance Manager Web Site
Prerequisites
To follow the instructions for installing an Express Instance Manager Web site, you
must fulfill the following prerequisites:
■ You must have administrative rights to the Web server.
■ You must know where to set up a Web site that is accessible to the Web server.
■ You must know how to configure the Web server.
Installation 3-17
Providing Documentation to the User Community
b. Choose Properties.
Result: You see the Properties page.
c. Set Access Permissions to Read.
d. Set Applications Settings Permissions to None.
5. Configure your browser as described in “Starting Express Instance Manager in
a browser” on page 4-3.
Online manuals
Users connecting to Express Server should have access to the online manuals on the
installation CD, particularly those concerned with the Express language and
application development. The manuals are provided as Acrobat PDF files and are
located in the doc subdirectory of the Oracle Express Server CD.
You can make these manuals available to users by copying the DOC directory from
the installation CD to a central directory on the server host to which all users have
access. You can provide the Acrobat Reader as well, or tell users how to download it
from the Web. Users can then copy the documentation to their client workstations.
Online Help
The doc subdirectory of the Oracle Express Server CD also contains the following
Help files:
■ Express Language Help (explang.hlp)
■ Express Web Agent Help (xwagent.hlp)
You can provide users with access to these Help files in the same way that you
provide access to the PDF files. Users can copy the Help files to their client
workstations. They can use the Microsoft Help viewer provided with Windows NT,
Windows 98, or Windows 95 to access these Help systems.
Related information
For more detailed instructions, refer to “Viewing Additional Documentation” on
page 2-2.
3-18 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
4
Administering Express Server
Chapter summary
This chapter explains how to start, stop, and configure existing Express services,
and create additional services using Oracle Express Instance Manager.
List of topics
This chapter includes the following topics:
■ Running Express Instance Manager
■ Navigating in Express Instance Manager
■ Starting a Service
■ Stopping or Pausing a Service
■ Changing Configuration Parameter Settings
■ Modifying the Module List
■ Modifying Express Server User Identities
■ Managing Express Sessions
■ Viewing Status Messages
■ Creating New Services
■ Choosing a Service Discovery Mode
■ Using Oracle Enterprise Manager
Overview
Express Instance Manager is the primary tool for administering Express Server.
Using Express Instance Manager, you can:
■ Start and stop Express services
■ Add and remove optional modules from an Express service
■ Change the configuration parameters that control the behavior of an Express
service
■ Create new Express services and remove existing services
■ Change the user identities under which Express Server runs
■ View system log files that record status messages from Express Server
Express Instance Manager is a Java tool that uses CORBA and socket
communications. Services running on computers throughout the network register
with CORBA, and then they are accessible as local services. Users must be able to
provide the required credentials before accessing any information about a particular
service.
Related information
For information about administering Express services in batch mode, refer to
Chapter 5.
Modes of operation
The following table identifies the different ways of running Express Instance
Manager.
4-2 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Running Express Instance Manager
Service discovery
Express Instance Manager has two modes for discovering Express services:
■ Manual mode — Express Instance Manager provides a Discover Nodes dialog
box in which you can identify a specific Express service. You may see this
dialog box at startup, or you can choose Discover Nodes from the Service menu
after Express Instance Manager starts.
■ Name factory mode — Express services are registered in the Visigenic Name
Factory, and Express Instance Manager locates a name factory using the
Visibroker Smart Agent. When you start Express Instance Manager, you
automatically see all of the Express services that have registered with that name
factory.
Express Instance Manager uses Name Factory mode if it is available; otherwise, it
uses manual mode. Manual mode is always available and is the normal mode of
operation.
Express Agent must be running on the computer where the Express service that you
want to manage is installed. The master daemon in its default configuration runs
Express Agent. Express Agent provides all administrative services to Express
Instance Manager.
For information about controlling the mode that Express Instance Manager runs in,
refer to “Choosing a Service Discovery Mode” on page 4-29.
Supported browsers
The following browsers are supported for use with Express Instance Manager on
Windows NT, Windows 98, and Windows 95:
Netscape Navigator 4.0.5 and later
Microsoft Internet Explorer 4.x
4-4 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Running Express Instance Manager
to separate the property name from its value. The following table describes the
various properties.
Property Value
DebugLevel= The following keywords control the level of detail of the debug
statements when DebugToLogFile=true:
■ PROD — Production
■ DBG — Debug
■ VDBG — Verbose debug
DebugToLogFile= A value of true or false, which controls whether debug
statements are written to the log file.
DiscoverOnStartup= A value of true or false, which controls whether the Discover
dialog box appears when Express Instance Manager starts up
and cannot connect to a name factory.
GeneralTimeOut= The number of milliseconds allowed for any general operation,
including user interface operations, performed in Express
Instance Manager before timing out. The default value is 40000
ms (40 seconds). Only numeric values are acceptable. Any
non-numeric characters will invalidate the setting.
NodeList= A list of host names separated by commas (,) or new-line
characters (\n). Express services on these hosts will be listed in
Express Instance Manager.
SocketTimeOut= The number of milliseconds allowed for any socket operation
performed in Express Instance Manager before timing out. The
default value is 20000 ms (20 seconds). Only numeric values are
acceptable. Any non-numeric characters will invalidate the
setting.
Related information
For more information about Express Instance Manager Help, search for the
following topic: “Using Express Express Instance Manager Help.”
4-6 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Navigating in Express Instance Manager
The following table identifies the settings. Separate multiple values with
semicolons. For information about defining and setting system variables, refer to
the documentation for your operating system.
Setting Description
-IORPort=portno Specifies the port number used by Express Instance Manager for
the Discover Nodes dialog. The default port is 6789 and can be
changed if another process is using this port.
-LogOutput=level Controls the amount of information provided in the logs to the
following levels:
■ PROD — Production
■ DBG — Debugging
■ VDBG — Verbose debugging
-NoNameServices Prevents Express services from being discovered in Name
Factory mode. For additional information, refer to “Choosing a
Service Discovery Mode” on page 4-29.
width of the Navigator by dragging its right edge. The page that is displayed on the
right side of the window adjusts automatically to fit the available space.
4-8 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Starting a Service
user name and password. If you cannot provide valid login credentials for that
computer, you cannot access any information about an Express service.
After you have identified yourself, you can expand and collapse the setting lists for
that service without providing your credentials again.
When you select a list item for a particular service, the sheet to the right of the
Navigator changes. For example, when you select Instance, you see the Instance
sheet. It consists of two pages, the State page and the Properties page. You can
switch between the two by clicking on the tabs at the top of the sheet.
Related information
For further information, search for the following topics in Express Instance Manager
Help:
“Discovering Services”
“Exiting Express Instance Manager”
“Selecting a Service to Configure”
Starting a Service
4-10 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Starting a Service
Troubleshooting Tips
Express Server sends messages to system log files to help you diagnose any
problems. You can access these log files through Express Instance Manager. For
information about viewing these files, refer to “Viewing Status Messages” on page
4-24.
Failure to start is typically caused by a problem in the parameter settings. The
following are some of the most common causes:
■ The paging parameters are set inappropriately for the computer’s processors.
For information about changing these settings, refer to “Understanding
Database Paging” on page 8-8.
■ More than one instance of Express Server is configured with 16-bit SNAPI. You
must remove the Direct Call module from at least one of them. (This problem
applies only to earlier versions of Express Server. 16-bit SNAPI is not supported
in Release 6.3.1.)
■ The first directory specified in the ServerDBPath setting (an I/O Management
parameter) does not contain express.db. Modify this setting so that the
Express Server service subdirectory is first.
■ The ServerDBPath setting specifies an invalid directory. Check your changes to
this setting for typographical errors or other mistakes.
■ The password for the DBA role as specified in Express Instance Manager is
different from the password recognized by the operating system for the DBA
user account.
■ The current primary Oracle home is not the Express Server installation
directory. If you changed Oracle home after installing Express Server, you must
change it back. After starting Express Server, you can change the primary
Oracle home as necessary.
Related information
For information about starting instances of Express Server, search Express Instance
Manager Help for the following topics:
“Customizing Express Server Initialization”
“Express Server Startup Parameters”
“Logging Into and Out of a Service”
“Starting a Service”
4-12 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Changing Configuration Parameter Settings
Related information
For information about stopping instances of Express Server, search Express Instance
Manager Help for the following topics:
“Customizing Express Server Termination”
“Stopping a Service”
For information about shutdown options, click Help on the State page, as shown in
“Figure: State page of the Instance sheet” on page 4-10.
The following are some common reasons for changing the default settings:
■ You want to add directories to Express Server’s search path so that client
applications do not need to specify the full path for Express databases. The
search path is particularly critical for locating the databases for Web
applications. You need to change the setting of ServerDBPath.
■ Express Server is running on a single-processor computer, but the default
paging settings are optimized for a dual-processor computer. You should
change the settings of FreePageHighCount and FreePageLowCount, as
described in “Understanding Database Paging” on page 8-8.
■ You want to improve performance. You should modify the settings described in
“Understanding Database Paging” on page 8-8.
■ You want to tighten security, because the default settings provide only a
minimum level of security. You must modify the settings described in
Chapter 6.
■ Some of the Express database files are quite large, so you need to identify
additional disk drives where Express can create temporary files and extension
files (described in Chapter 7). You must modify the settings for
SessionTempFilePath and ExtensionFilePath.
■ You want to run more than one instance of Express Server on a single computer.
Only one instance can run under the default identifiers, so you must modify the
identifiers for the additional instances. The following are some reasons for
running multiple instances:
■ You want to run a beta version of Express Server in addition to a released
version on the same computer.
■ You want to configure two instances of the same version to provide
appropriate services to two different user groups.
■ You want to run Express Server and Personal Express on the same
computer.
Important: Express client applications use the default identifiers to make a
connection to Express Server unless they are configured to do otherwise. If you
configure an Express service with non-default identifiers, you must inform
everyone in the target user community of the change so that they can include
the new identifiers in their connection descriptions.
■ You want to provide support for additional languages. You must specify the
localization settings, as described in Chapter 10.
4-14 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Changing Configuration Parameter Settings
■ If the Express service will support shell operations, then you might need to
modify the ShellPath parameter. The default path is usr/bin/sh.
4-16 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Modifying the Module List
Related information
If you want information about a specific parameter, then search Express Instance
Manager Help for that parameter by name.
If you want help changing the parameter settings, then search Express Instance
Manager Help for the topic “Changing a Configuration Parameter.”
Adding modules
Choices that you make during installation determine whether or not a module is
installed on your computer. If a module has been installed but is not currently
included in the module list, you can simply add it to the list using Express Instance
Manager.
If you did not install support for an option that you now want to provide, then you
need to rerun the installer and add that support in a custom installation.
Removing modules
The module list should contain all the modules that are needed to provide the
necessary level of support for your client applications. However, you can
unnecessarily slow performance by loading modules that provide unused features.
For example, if an Express service does not need to support ODBC or XCA, you can
remove the ODBC and XCA modules from the module list. Check the list provided
in “Installation of optional modules” on page 3-6, or check the list of modules
provided in Express Instance Manager, to see if there are modules that should be
removed.
Before removing a module, make sure that you know exactly what features it
provides and whether another module is dependent on it. Multiple modules
provide support for SNAPI, Express Web Agent, and SQL. You may be able to
remove a module that extends one of these communication options in a way that
your installation does not need. However, if you remove the wrong module, you
may completely disable that option.
Unless disk space is scarce, you do not need to delete module files. You can simply
remove them from the module list. Then, if you want to restore that functionality
later on, you can add the module back onto the list.
Module dependencies
The following table identifies dependencies among communications modules.
4-18 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Modifying the Module List
Related information
For more information about SQL configurations, refer to Chapter 9.
For more information about SNAPI configurations, refer to the Oracle Express
SNAPI Guide.
For more information about Web configurations, refer to the Oracle Express Web
Products Installation Guide.
Related information
For more information about a specific module, search Express Instance Manager
Help for the module by name. Or, in Express Instance Manager, display the General
page for modules. Select a module from the list, click Properties, and then click
Help.
For more information about managing the module list, search Express Instance
Manager Help for the following topics:
“Adding a New Module”
“Removing a Module”
“Viewing Module Properties”
4-20 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Modifying Express Server User Identities
Introduction
Express Server takes the identity of a user to perform up to three roles: the DBA
Role, the Initialize Role, and the Default Role. These roles require different access
permissions; therefore, Express Server uses a different user identity for each role.
These “users” are defined by the operating system’s administrative facilities the
same way as any other user accounts. On Unix systems, you must manually set up
these accounts prior to installation.
Using Express Instance Manager, you can change the credentials that Express
Server offers to the operating system to use these identities. These credentials must
correspond to a valid user name and password.
Related information
For more information about roles, search for the following topics in Express
Instance Manager Help:
“DBA Role Sheet: General Page”
“Default Role Sheet: General Page”
“Initialize Role Sheet: General Page”
4-22 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Managing Express Sessions
Related information
For more information, search for the following topics in Express Instance Manager
Help:
“Remove Sessions from ServiceName Dialog Box”
“Sessions Sheet: General Page”
“Terminating a Session”
“Viewing Session Information”
Overview
Express Server sends information to several log files to help you monitor operations
and troubleshoot any problems. Most of these files are available through Express
Instance Manager. You can change the level of detail of these log files by changing
the configuration of either Express Instance Manager or Express Agent. Refer to
4-24 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Viewing Status Messages
Message Description
main() entered. Indicates that the Express Server service has begun
initialization.
Express Server KERNEL - Indicates that the Express Server service is
Application event log initialized for initializing and writing messages to the event log.
Express Server KERNEL.
Express Server KERNEL - Thread Indicates that the Express Server service is
waiting for service done event. initialized and ready to process client connections.
Express Server KERNEL - Service Indicates that the Express Server kernel has started
done event satisfied. shutdown operations.
Express Server KERNEL - Service Indicates that the Express Server kernel has
done event signaled. concluded shutdown operations.
4-26 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Creating New Services
In some specific cases of authentication and authorization failure, a log file named
xsbufdump.log is created. In this event, you should contact your Oracle technical
service representative.
Related information
For more information about log files, search for these topics in Express Instance
Manager Help:
“EventLogPath Setting”
“OverWriteEventLog Setting”
“Viewing Event Logs”
Choosing a tool
Express Instance Manager provides two methods for creating a new service:
■ Create creates a new service with default configuration parameters. Initially, no
modules are on the module list. You must add the required modules, as well as
any optional modules, before you can start the service.
■ Create Like creates a new service with parameter settings and a modules list
that duplicates an existing service. This existing service can be either the same
version or a different version of Express Server.
4-28 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Choosing a Service Discovery Mode
■ Check the value of WakeUpSPLScript. Only one service can run the batch
file for Batch Manager, since it opens a database with write access.
■ If you used Create, you must add all of the required modules and whatever
optional modules provide features that you want. Refer to Express Instance
Manager Help for a list of required and optional modules.
Related information
For further information about creating new services, search Express Instance
Manager Help for the following topics:
“Copying a Service”
“Copying Service Settings”
“Creating a Service”
Two modes
Express Instance Manager has two modes of operation, as described in “Service
discovery” on page 4-3:
■ Manual mode
■ Name Factory mode
If you, like most administrators, manage just a few Express services, Manual mode
is the most convenient. It is available for all methods of running Express Instance
Manager.
If you manage a large number of Express services, you may find Name Factory
mode to be more convenient. However, you might find that the list of services
displayed in Express Instance Manager varies from one session to the next. This can
occur when services are installed on several subnets, or when multiple name
factories exist on the network.
computers on your network that are using this software, Express Instance Manager
may automatically locate a name factory on startup.
To prevent use of Name Factory mode, set the system variable OES_EA_STARTUP to
-NoNameServices, as described in “Express Agent startup parameters” on page
4-6.
4-30 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Using Oracle Enterprise Manager
Related information
For more information about Oracle Enterprise Manager, see Oracle Enterprise
Manager Help.
4-32 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
5
Setting Up Batch Jobs
Chapter summary
This chapter introduces facilities you can use to set up batch jobs that manage
Express services and execute Express language commands.
List of topics
This chapter includes the following topics:
■ Tools for Running Batch Jobs
■ Introduction to the Command-Line Utilities
■ Targeting an Express Service
■ Using the Command-Line Service Manager
■ Using the Command Processor
■ Scheduling Jobs in Oracle Enterprise Manager
■ Using a Persistent Session
■ Using Batch Manager
Overview
You may want to schedule Express services to start or stop at specific times or run
scripts of Express language commands at specific times. To do this, you can use one
or more of the following administrative facilities:
■ Oracle Express Server Command-Line Service Manager
■ Oracle Express Server Express Command Processor
■ Oracle Enterprise Manager
■ Persistent Session
■ Oracle Express Batch Manager (hereinafter referred to as “Batch Manager”)
These tools, which are summarized below, are explained in detail in subsequent
sections of this chapter.
5-2 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Introduction to the Command-Line Utilities
Manager to schedule jobs that invoke the administrative utilities oesmgr and
oescmd.
Persistent Session
The Persistent Session, an optional feature of Express Server, is a special session that
is active as long as the Express service is running. Within the Persistent Session, you
can schedule scripts of Express language commands to run at startup and
termination of the Express service, and at periodic intervals while the service is
active.
Note: The Persistent Session is sometimes called the Initial Session.
Batch Manager
Batch Manager is a graphical utility that runs on a Windows desktop. You can use it
to create, monitor, and control batch processes within Express Server. It is available
on the Express Client CD.
Overview
The Express Server command-line administration utilities, oesmgr and oescmd,
are operating system commands. They can be invoked from within scripts and from
the Unix command line.
You can schedule and launch scripts that contain oesmgr and oescmd commands
using the following facilities:
■ The Unix cron facility
■ The job-scheduling facility within Oracle Enterprise Manager
File location
The oesmgr and oescmd programs are installed during the installation of Express
Server. The following are sample path names:
/home/oracle/olap/bin/oesmgr
/home/oracle/olap/bin/oescmd
Redirecting output
The oesmgr and oescmd utilities write text output to stdout and stderr, which
are typically defined as the screen. This implementation allows you to redirect
output to a file, pipe it to another program, or capture and interpret output in a
script.
If the output consists of multiple lines of text, then the end-of-line character will be
represented in the native format. On Unix, the end-of-line character is LF.
All text output from oesmgr and oescmd is in English US ASCII format. All text
output returned from Express is in the language (character set) used by that Express
Server instance.
Default services
The command-line utilities connect to the local default instance of Express Server
unless you target another instance by specifying its binding string in the command
syntax.
Binding strings
A binding string uniquely identifies a process on a network. It has the following
general format.
[UUID@]transport:host[endpoint]
The components that you specify in the binding string vary, depending on the
location of the service and the service identifier.
5-4 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Targeting an Express Service
Component Description
uuid Identifies a particular instance of Express Server. The UUID is specified
in the ServerObjectID configuration setting.
transport Describes the Remote Procedure Call (RPC) transport used to
communicate with Express Server.
hostname Identifies the computer where the instance of Express Server is running.
endpoint An IP port number for Oracle Remote Operations.
Transport descriptions
You can specify the following value for the transport component of the binding
string.
Transport Description
ora_ro_tcp Oracle Remote Operations RPC, used for Unix-to-Unix and
Unix-to-Windows connections.
Component Unix
uuid No
transport Yes
hostname Yes
endpoint oescmd: Yes
oesmgr: No
Overview
You can run the Command-Line Service Manager interactively or as a batch
command processor. By using it interactively, you can access its online Help
facilities, which provide you with the information you need to formulate complete
and syntactically correct commands. After you know the exact syntax of the
commands you want to use, you can issue them in a batch environment.
5-6 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Using the Command-Line Service Manager
Command-line syntax
To manage Express services in batch mode, specify the full operation in a single
command. The input to oesmgr consists of a series of options followed by one or
more commands.
oesmgr [-v] [-b target] [-u userID] [-p password] [-i] [-h] [-t timeout] [-s]
command1; command2...
Description of options
The command-line options target a specific Express service and specify command
runtime characteristics, such as redirection of input and error handling. The
oesmgr command-line options are described briefly in the following table. For
more detailed explanations, use the oesmgr Help facility.
Description of commands
The oesmgr service-management commands specify the type of service
management you want to perform, such as stopping, starting, and pausing the
service. The oesmgr commands are described briefly in the following table. For
more detailed explanations, use the oesmgr Help facility.
Handling errors
The oesmgr utility returns a status code that indicates whether or not it
successfully completed execution. You can write a batch program that traps the
status code and proceeds conditionally, based on the type of error, rather than
simply terminating.
The error messages are sent to stdout, which is typically the screen, but you can
redirect this output to a log file for later analysis.
Tip: Use -i option if you want oesmgr to ignore errors rather than terminating.
The following table identifies oesmgr error codes.
5-8 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Using the Command Processor
Overview
You can use the Express Command Processor either interactively or in batch mode
to execute Express language commands.
Command-line syntax
To process Express commands in batch mode, specify the full operation in a single
command. The input to oescmd consists of a series of options followed by one or
more Express language commands, as shown by the following syntax.
oescmd [-b target] [-u userID -p password] [-i]
[Express_command1; Express_command2 ...]
Descriptions of options
Use the oescmd command-line options to target a specific Express service and to
specify runtime characteristics, such as redirection of input and error handling.
The oescmd command-line options are described in the following table.
Handling errors
The oescmd utility returns a status code that indicates whether or not it
successfully completed execution. You can write a batch program that traps the
status code and proceeds conditionally, based on the type of error, rather than
simply terminating.
The error messages are sent to stdout, which is typically the screen, but you can
redirect this output to a log file for later analysis.
Tip: Use -i option if you want oescmd to ignore errors rather than terminating.
The following table identifies oescmd error codes.
5-10 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Scheduling Jobs in Oracle Enterprise Manager
Related information
For information about the Express language, refer to Express Language Help and
the Oracle Express Programmer’s Guide to the Express Language.
Overview
You can set up jobs in Oracle Enterprise Manager that invoke the Express Server
command-line administration utilities oesmgr and oescmd.
These jobs can invoke the utilities on either Unix or Windows NT. When running on
Unix, the utilities can target Express services on other Unix platforms.
General requirements
You can schedule jobs that use oesmgr and oescmd in Oracle Enterprise Manager,
provided that you have met the following general requirements:
■ There is a working installation of Oracle Enterprise Manager on your Windows
NT machine.
Unix requirement
If the utilities will run on a Unix host, then you must create a shell script for them.
Within the script, set the library path so that the utilities can find the shared
libraries that they require.
The libraries required by oesmgr and oescmd on Unix are listed in the following
table.
5-12 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Scheduling Jobs in Oracle Enterprise Manager
password of docguest. The oesmgr utility will return the status of an Express
service named ExpSrv630.
#!/usr/bin/ksh
LD_LIBRARY_PATH=/home/oracle/lib${LD_LIBRARY_PATH+
:LD_LIBRARY_PATH}
export LD_LIBRARY_PATH
/home/oracle/olap/bin/oesmgr -b olapsun -u guest
-p docguest status ExpSrv630
Overview
Using a Persistent Session, you can schedule scripts of Express language commands
to run upon startup and termination of the Express service and at periodic intervals
while the service is active.
5-14 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Using Batch Manager
Event logs
Events generated by the Persistent Session’s startup and shutdown scripts are
recorded in the service event log OESevent.log.
You can specify whether or not Express Server will record events generated by the
wakeup script in the event log. If you are using the WakeUpMilliseconds setting to
execute your wakeup script frequently, then you should ensure that the
SPLScriptLogging setting is set to NO. Otherwise, the event log will quickly be
filled with script-related events.
Related information
For more information about the Persistent Session, search for the following topics in
Express Instance Manager Help:
“Express Server Startup Parameters”
“Persistent Session Module”
“Running Scripts Periodically”
“ShutdownSPLScript Setting”
“SPLScriptLogging Setting”
“StartupSPLScript Setting”
“Viewing Event Logs”
“WakeUpMilliseconds Setting”
“WakeupSPLScript Setting”
Overview
You can use Batch Manager to formulate and schedule batch jobs within Express
Server. Batch Manager can run as a standalone client product, or integrated into
Oracle Express Administrator or Relational Access Administrator. All of these
products that can be installed from the Oracle OLAP Express Client CD.
You can use Batch Manager to schedule and launch the following types of jobs:
■ Build a database or perform a series of commands by running a script file of
Express commands.
■ Build databases for Oracle Sales Analyzer with the data loader.
■ Build a database with Relational Access Manager.
■ Attach a database and use an Express command to manipulate the data in that
database.
■ Run a data-reader program that has been defined within Oracle Express
Administrator.
■ Enter specifications to run a data rollup program that has been defined within
Express Administrator.
Batch Manager does not require a continuous connection to Express Server.
Related information
For more information, see Batch Manager Help.
5-16 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
6
Security
Chapter summary
This chapter explains how to control client access to Express services and files
created by Express services, particularly databases.
List of topics
This chapter includes the following topics:
■ Restricting Access to Your Data
■ Creating a Secure Express Server Instance
■ Identities Used by Express Server
■ Establishing a Client’s Identity
■ Establishing the Session Identity
■ Establishing the File Owner
■ Controlling Access to Files
■ Establishing the Base File Mode
■ Modifying Access Rights to Existing Files
■ Limiting Access to the Operating System
Security 6-1
Restricting Access to Your Data
Web access
If you are planning to deploy Express Web applications, you probably want to take
extra security precautions. Refer to the Oracle Express Web Products Installation Guide
for a discussion of security issues specific to the Web.
6-2 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Identities Used by Express Server
The most stringent security measures can be implemented only when Express
Server is being accessed exclusively by SNAPI clients.
Related information
For information about configuring multiple instances of Express Server, refer to
“Creating New Services” on page 4-27.
Security 6-3
Establishing a Client’s Identity
Related information
For information about Express user identities, search for the following topics in
Express Instance Manager Help:
“Defining User Roles in Express”
“DBA Role Sheet: General Page”
“Default Role Sheet: General Page”
“Initialize Role Sheet: General Page”
“Working With User Roles in Express”
What is authentication?
Authentication is the process whereby an Express service determines the identity of a
client.
The Express service establishes a connection only if it can identify a valid user
account that conforms to the security requirements for that service.
6-4 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Establishing the Session Identity
Overview
You can configure Express Server so that users must identify themselves with a user
name and password before initiating a session. Express Server attempts to
authenticate the information that the user supplies with the user database that is
maintained by the operating system.
Express Server can be configured with several levels of authentication, ranging from
open access to authentication upon each exchange of packets. It is configured
initially with open access. You can change the settings that affect security by
specifying values for the settings on the Security page of Express Instance Manager.
Access requirements
Under the default security settings of Express Server, individual users do not need
to supply their own credentials. If a client provides authentication credentials,
Express Server uses them; if not, the client session operates under the identity of the
Default User. The client session has all of the access rights that are granted to that
user ID and the groups to which that user ID belongs, regardless of whether the
user ID is his or her own or that of the Default User.
Access is denied to a user who supplies:
■ A user name that is not in the user database
or
■ An incorrect password
A user who attempts to log in without offering credentials is either given access as
the Default User or rejected, depending on the RequiredSecurityLevel configuration
setting.
Security 6-5
Establishing the Session Identity
Level Description
NONE Clients do not need to provide an identity, as long as a Default User has been
defined on the host computer. A client who does not specify a user ID and
password automatically assumes the identity of the Default User.
If a client specifies a Windows NT domain user ID or a host user ID, Express
Server uses the ID to establish an identity for the client.
This level provides the least security.
You must define a Default User in Express Instance Manager.
HOST Clients must explicitly identify themselves with a valid user ID and password
(and optionally an NT domain name). The ID can be a host user ID that is set
up on the computer running Express Server, or it can be a Windows NT
domain user ID.
This level is fairly secure.
You do not need to define a Default User.
Validating an ID
All Express Server sessions are initiated under a user identification that is known to
the operating system. On Unix, the user ID is defined on the host machine or
network.
Password encryption
Express Server can be configured to require that passwords be encrypted, which
improves security but precludes connections by clients that do not encrypt
passwords. The following table shows the availability of password encryption for
different types of client communications.
6-6 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Establishing the File Owner
Related information
Search for the following topics in Express Instance Manager Help:
“EncryptStoredPasswords Setting”
“RequirePasswordEncryption Setting”
“RequiredSecurityLevel Setting”
“RequiredAuthenticationLevel Setting”
Default owner
Express Server instances, running as a DBA User, create databases and other types
of files. Since Unix files are created under the ownership of the controlling process
ID, the DBA User would normally own all the files that are created by Express.
However, Express services can be configured to use either the session identity or the
DBA identity as the file owner. By default, the file owner is the session identity. The
specified user owns all the files that are created during sessions with this Express
service.
Security 6-7
Controlling Access to Files
FileOwner Parameter
The following table identifies the settings for the FileOwner configuration
parameter, which you can set using Express Instance Manager.
What is authorization?
Authorization is the process whereby Express services regulate clients’ access to files,
such as databases and EIF files, and to database objects, such as variables and
dimensions.
Express sessions need to interact with the file system. At the minimum, they need to
be able to read from Express databases. They may also need to perform tasks such
as creating and updating databases, exporting and importing EIF files, writing to
log files, and reading data from external file formats.
Session-level authorization
You can control clients’ access to files and other resources on the host by restricting
the access rights associated with their session identity. The permissions associated
with the session identity govern access to files of all types: files created by Express
(databases, EIF files, log files), and external files (files accessed via such Express
features as data reader or SHELL commands).
Ensure that the Default User, as well as any other account that will be used as a
login account, has the necessary level of access rights. For example, the Default User
6-8 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Controlling Access to Files
might only require read access to one directory containing Express databases.
Another user account might require write access to a specific directory where
sessions will create new databases.
Express-level authorization
The Express language supports its own security mechanisms. Express security
applications, which execute within the context of Express sessions, can establish
access criteria for Express databases and database objects.
Express security applications use the following features of the Express language:
■ PERMIT commands — Control access to databases and database objects
■ PERMIT_READ and PERMIT_WRITE programs — Specify permission when a
database is attached
■ SYSINFO function — Returns the session identity or its groups (USER and
GROUP keywords) so that permissions can be based on the user’s identity.
Security 6-9
Controlling Access to Files
Because Express Server runs under the identity of the DBA User, and Unix uses the
process user ID to control access to files, the DBA user must have access to any file
that Express may need to open. At the same time, each session has a user ID and
Express uses the session user ID to control access files, so that each session user
must have access to any files that the session may need to open. When Express
creates a file, it ensures that the file has permissions that allow it to be reopened by
the session user who created it. To do this, Express must grant access to two users:
the DBA user and the session user.
With ACLs, Express can grant access rights to a specific user who is not the owner.
Without ACLs, Express can only grant access rights to a group of users. This can be
a security breach since it allows everyone in a group to access data that might be
intended for access by a single user.
The following table shows how access rights are granted so that both the DBA User
and the user who created the file have access rights.
Desupporting ACLs
Solaris systems support ACLs and by default Express Server will use ACLs to
regulate access. However, you can control whether ACLs are used by setting the
AcceptACLs parameter in Express Instance Manager.
6-10 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Establishing the Base File Mode
File-level authorization
Access to a file depends not only on the identity of the process that is seeking
access, but also on the mode of the file itself. In Unix systems, all files have an
associated file mode that specifies how different categories of users can access the
file.
The file mode specifies access rights for the file’s owner, the file’s associated group,
and for all other users.
File modes
Each Unix file has a mode that governs access to the file. The mode specifies read,
write, and execute permission for the file’s owner, for members of the file’s group,
and for anyone else (the “world”).
The mode is generally represented as a three-digit octal number, with a distinct
digit for the owner, the group, and the world. Each octal digit represents three
binary digits (bits). Each bit specifies an access type: read, write, or execute.
Security 6-11
Establishing the Base File Mode
6-12 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Modifying Access Rights to Existing Files
The following table shows how the same DefaultMode setting produces different
access rights, depending on whether or not ACLs are enabled.
Related information
For more information about the “DefaultMode” setting, search Express Instance
Manager Help.
For more information about file mode settings, refer to the Unix man page for
chmod.
Overview
Once Express Server has created a database, or any type of file, there is no
mechanism within Express Server or Express Instance Manager to modify the file’s
associated access rights. If you need to change the permissions associated with a file
created by Express Server, then you must use Unix commands.
Security 6-13
Limiting Access to the Operating System
Important: If you specify a chmod command for a file that has an ACL, the results
may be unexpected. The chmod command does not work properly on files that have
ACLs.
Related information
For more information about ACLs, refer to the man pages for chmod, setfacl and
getfacl.
6-14 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Limiting Access to the Operating System
Related information
For more information about the Express SHELL, DEFINE EXTCALL, and EXTARGS
commands, search for these topics in Express Language Help.
Security 6-15
Limiting Access to the Operating System
6-16 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
7
Managing Express Databases
Chapter summary
This chapter describes how Express databases are implemented within the file
system. It also explains how to set the database search path and tune the use of
database extension files and temporary files.
List of topics
This chapter includes the following topics:
■ Understanding Express Database Files
■ Accessing Databases
■ Setting Search Paths
■ Managing Temporary Files
■ Managing Extension Files
Overview
The basic organizational unit of Express is the database. An Express database is a
cache in which clients create and store the objects that support multidimensional
analysis. Express objects include dimensions, variables, relations, models, and
programs. An Express program is equivalent to a stored procedure.
Internal organization
The internal organization of Express databases is controlled by Express
applications. These applications use Express language commands to create new
databases and create and manipulate objects within databases.
External organization
Externally, Express databases are controlled by the operating system’s file system.
Depending on its size and on whether or not it is currently in use, an Express
database might consist of one or several files.
Types of files
Express Server manages databases by creating and using the following types of
files.
7-2 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Accessing Databases
Related information
For more information, see the following:
■ Oracle Express Programmer’s Guide to the Express Language
■ Oracle Express Database Administration Guide
■ The “DATABASE command” topic in Express Language Help
Accessing Databases
Overview
Which databases a session can attach depends on several factors, including:
■ The access rights of the Session User
■ The access rights of the DBA User
■ The permissions that are associated with the directory in which a database
resides
■ The file mode and access control list for the database
■ Whether the Session User or DBA User is the owner of a database
■ Whether or not the database is currently attached in another session and, if so,
how it is attached
Although the Session User may be designated as the file owner, the DBA is always
the initial file owner when the file is first created, before the authorization daemon
changes the ownership.
Database sharing
In order for two separate instances of Express Server to have the same database
open simultaneously, the database file must be flagged as read–only at the
operating system level.
When attaching a database, a session can request one of the following attach modes.
7-4 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Setting Search Paths
Related information
For more information about database access rights, search for the following topics
in Express Instance Manager Help:
“DefaultModeSetting”
“FileOwner Setting”
their own search paths for main database files and extension files by setting the
appropriate Express language options.
The following table summarizes the configuration settings that set the default paths
for all sessions and the Express language commands for overriding these defaults.
File Type Search Path for Service Search Path for Session
Main database file ServerDBPath setting DBSEARCHPATH option
Database extension files ExtensionFilePath setting DBEXTENDPATH option
EXPTEMP files SessionTempFilePath setting DBTEMPPATH option
GLOBTEMP files GlobalTempDBPath setting NA
Related information
For more information, search Express Instance Manager Help for the following
topics:
“ExtensionFile Path Setting”
“GlobalTempFilePath Setting”
“ServerDBPath Setting”
“SessionTempFilePath Setting”
Search Express Language Help for the following topics:
“DBEXTENDPATH Option”
“DBSEARCHPATH Option”
“DBTEMPPATH Option”
7-6 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Managing Temporary Files
Overview
Express Instance Manager provides several settings that you can use to control how
an Express service will handle temporary database files.
Related information
For more information, see Express Instance Manager Help and the “DATABASE
Command” topic in Express Language Help.
7-8 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Managing Extension Files
Related information
For more information, see Express Instance Manager Help and the “DATABASE
command” topic in Express Language Help.
7-10 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
8
Monitoring Performance
Chapter summary
This chapter provides information about performance monitoring and tuning.
List of topics
This chapter includes the following topics:
■ Basic Tuning Guidelines
■ Simulating Test Sessions
■ Monitoring Performance
■ Tuning Performance-Related Parameters
■ Understanding Database Paging
■ How the Paging Manager Reclaims Cache Memory
What is tuning?
Express Server has numerous user-settable parameters that affect the way that it
behaves. The optimal settings for some of these parameters is dependent on the
hardware configuration of the computer. The default settings might be right for
most hardware configurations, but will not be right for all of them.
If you are satisfied with the performance of Express Server, then you can assume
that the default settings are appropriate for your system. If you are not satisfied,
then you should investigate whether the settings can be optimized for your system.
8-2 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Simulating Test Sessions
the command OUTFILE TEST.#, then 10 separate output files would result, named
TEST.0, TEST.1, and so forth.
Monitoring Performance
8-4 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Monitoring Performance
Resource Command
Shared Memory ipcrm - m
Semaphores ipcrm - s
For more information, see the man pages for ipcs and ipcrm.
7. In the Counter box, you will see a list of Express Server counters. Select a
counter, and choose Add. You can add as many counters to the chart as you
want.
8. Choose Done to return to the main window.
9. To save your chart definition, follow these steps.
a. From the File menu, choose Save Chart Settings As to display the
Performance Monitor - Save dialog box.
b. In the File Name box, type a name for the chart.
c. Select the drive and directory where you want to save the chart.
d. Choose OK to return to the main window.
10. From the File menu, choose Exit.
Performance counters
Performance counters are updated upon completion of a transaction with the
Express service. A Test Engine script is treated as a single transaction: Sending the
script, executing it, and receiving the results.Following are descriptions of the
Express Server counters.
8-6 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Tuning Performance-Related Parameters
Related information
For more information about Windows NT Performance Monitor, see Windows NT
Performance Monitor Help, especially the following topics:
“Working with Alerts”
“Working with Charts”
“Working with Log Files”
“Working with Reports”
Introduction
There are numerous configuration parameters that affect performance. The
following information provides a brief introduction to them.
SessionManagement parameters
Check the following parameters:
■ ThreadPoolMax — Affects the number of threads available for SNAPI and Web
sessions
■ ThreadPoolMin — Affects the number of threads available for SNAPI and Web
sessions
■ MaxSessions — The maximum number of simultaneous sessions
■ XCAQueueDepth — The maximum number of simultaneous requests for XCA
connections
WebAgent parameter
Check the MaxWebSessions parameter. MaxWebSessions specifies the maximum
number of simultaneous Web sessions.
8-8 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Understanding Database Paging
Related information
For further information about the default setting of PageBufferCount and its
relationship with other parameters, search Express Instance Manager Help for the
topic “PageBufferCount Setting.”
Two threads
The Paging Manager uses the services of two optional, dedicated threads to reclaim
cache memory:
■ The collector thread maintains a reserve of free page buffers in the page pool.
■ The ModifiedPageWriter thread flushes modified pages to disk.
8-10 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
How the Paging Manager Reclaims Cache Memory
Related information
For further information about changing these parameters, search Express Instance
Manager Help for the following topics:
“CollectorThreadCount Setting”
“FreePageHighCount Setting”
“FreePageLowCountSetting”
specify determines the time (in milliseconds) that the Modified Page Writer thread
sleeps after writing a modified database page to disk. When the Modified Page
Writer thread wakes up, it writes another page to disk.
Related information
For more information about updating and concurrent access to Express databases,
refer to the following:
■ Oracle Express Programmer’s Guide to the Express Language
■ The topics “UPDATE command” and “DATABASE command” in Express
Language Help
8-12 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
9
Supporting Access to Relational Databases
Chapter summary
This chapter describes the software components and configuration settings you
need to establish a connection between Express Server and a relational database.
List of topics
This chapter includes the following topics:
■ Choosing a Connection Method
■ Setting Up a Connection
■ Configuring Express Server
■ Setting Environment Variables
■ Setting Up Oracle Communications
■ Selecting and Installing an ODBC Driver
■ Providing ODBC Support
■ Defining ODBC Data Sources
■ Testing Your Configuration
Connection options
Express Server supports two types of connections to relational databases:
■ OCI
■ ODBC
Definition: OCI
The Direct Oracle Call Interface (OCI) is an application programming interface
(API) that allows applications such as Express Server to issue SQL statements to an
Oracle relational database management system (RDBMS). The OCI gives Express
Server the ability to perform the full range of operations that are possible with
relational systems such as Oracle8.
Definition: ODBC
ODBC is Microsoft’s Open Database Connectivity interface. It is a Windows
convention for accessing files and databases.
Availability of options
The connection you can use depends on the type of relational database you wish to
access.
For connections to Oracle relational databases, OCI offers substantial benefits over
ODBC, because you have access to the special features of Oracle, without the
restrictions that are imposed by an ODBC driver. In addition, a direct connection is
always faster and more reliable.
Limitations of ODBC
Because the ODBC convention supports only standard SQL, ODBC drivers do not
support the nonstandard, special features that might be available in a particular
RDBMS. In addition, Express imposes further restrictions with an ODBC
connection, because of the differences among the various RDBMS. For example,
Express does not support multiple-statement transaction processing through an
ODBC connection; all changes are committed immediately.
9-2 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Setting Up a Connection
Related information
For information on accessing relational data from within Express, see the Express
Language Help system and the Oracle Express Programmer’s Guide to the Express
Language.
Relational Access Manager is an OLAP client application that you can use with
Express Server. Relational Access Manager enables Express Server to access,
manipulate, and display data that is stored in a relational database. For more
information, see the Relational Access Manager Help system and the Oracle Express
Relational Access Manager User’s Guide.
Setting Up a Connection
Introduction
Once you have identified the type of connection that you need to set up, you must
install and configure the various components that make up that connection.
Oracle8
Express Server
or
OCI Module
9-4 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Setting Up a Connection
ODBC Module
ODBC Administrator
ODBC Driver
9-6 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Configuring Express Server
Verification methods
You can verify the configuration in the following ways:
■ Open an interactive session with Express Server and issue the following
command.
show sql.dbmslist
This variable identifies the available types of SQL support.
■ Open an interactive session with Express Server and issue the following
command.
show eversion
Check the resulting list of modules.
■ Open Instance Manager and examine the list of modules for your instance of
Express Server.
Required modules
Express Server must have the following modules in its module list.
Related information
For information about the SQL.DBMSLIST and EVERSION options, search the
Express Language Help system for these topics.
For information about configuring Express Server, search the Instance Manager
Help system for the following topic: “Providing SQL Support.”
Startup scripts
The environment variables that are used by Express are set by a Shell script named
$OLAP_HOME/express.prm. This script is run by the startup script for Express
Server. The express.prm script ensures that whenever Express Server is running,
the environment variables are set correctly.
OCI requirements
The following environment variables must be set for Express to establish OCI
connections to an Oracle relational database.
Note: If you have installed a number of different Oracle products, then your system
might have more than one directory defined as ORACLE_HOME. Ensure that
$ORACLE_HOME is defined in express.prm as the Oracle home directory of
Express Server. Additional information about multiple Oracle homes is located in
“Choosing an Oracle Home” on page 2-5.
9-8 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Setting Up Oracle Communications
RDBMS-specific variables
For information about additional environment variables that must be set for your
relational database, refer to MERANT DataDirect ODBC Drivers Help in the chapter
on the particular driver you are configuring. The MERANT manual is provided as
an Acrobat file on the installation disk for Express Server. It is also installed with
the ODBC drivers as $OLAP_HOME/odbc/doc/odbchelp.pdf.
For example, the “Sybase Drivers” chapter describes the appropriate setting for the
SYBASE environment variable.
Introduction
To communicate with an Oracle relational database, you must set up a Net8
connection.
Net8 is the communications software that is used by Oracle relational database
management systems. It is provided on the installation media with Oracle relational
server and client products.
If you are accessing a non-Oracle relational database, then you will need to perform
equivalent procedures to the ones described here, using the communications
interface that is provided for that product.
Net8 requirements
You must have installed Net8 on the same machine where Express Server is
installed. Typical and Complete installations of Express Server include Net8.
Express Server uses this installation of Net8 client, regardless of whether there are
other versions installed on your computer.
Net8 has both a server component and a client component. The Net8 client installed
with Express Server should be able to run with whatever version of the server
component is installed on your Oracle8 or Oracle7 host computer. Do not install
another version of Net8 client in the Oracle home used by Express Server, because
you will get unpredictable results.
9-10 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Selecting and Installing an ODBC Driver
You can use the Oracle Net8 Easy Configuration utility to modify tnsnames.ora.
Oracle Corporation recommends that you use the Easy Configuration utility instead
of editing tnsnames.ora directly.
If you have another installation of Net8 and want to use previously defined
database aliases, then copy tnsnames.ora to the Oracle home used by Express
Server. Then, be sure to use the version of the Oracle Net8 Easy Configuration
utility located in the Oracle home for Express Server.
For information about Oracle home, refer to “Choosing an Oracle Home” on page
2-5.
Introduction
Your satisfaction with your ODBC connection is greatly influenced by your choice
of driver. Some drivers are supplied by the database vendor, while others are
supplied by third-party vendors. Different vendors might provide drivers for the
same relational database management system that offer very different levels of
speed, reliability, and conformance with ODBC conventions.
Recommended drivers
ODBC support in Express Server is developed and tested using MERANT
DataDirect ODBC drivers. Remember that you should use an OCI connection
instead of ODBC when you are connecting to an Oracle relational database.
9-12 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Selecting and Installing an ODBC Driver
Levels of conformance
Different drivers for the same relational database can vary significantly in their level
of conformance with the ODBC conventions. There are two areas in which the level
of conformance can be measured:
■ ODBC API
■ ODBC SQL grammar and data types
Within these two areas, the level of conformance can impose restrictions on the
types of SQL statements and syntax that you can use in communicating with a
relational database. When evaluating the suitability of a particular driver, you must
look at the driver’s conformance level in both areas.
Related information
For more information about ODBC, refer to the Microsoft ODBC Programmer’s
Reference and SDK Guide.
Supported databases
Drivers are provided for the following types of databases:
Oracle
dBase
DB2
Informix
OpenIngres
Sybase
SQL Server
Text
9-14 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Defining ODBC Data Sources
Before editing odbc.ini for the first time, make a backup copy using a command
such as this one.
cp odbc.ini odbc.bak
You can modify odbc.ini using any text editor, such as vi or emacs.
Structure of odbc.ini
The odbc.ini file initially contains the following section labels. Note that in this
sample file, there is a label for each type of data source. When you are through
editing the file, there should be a label for each defined data source.
[ODBC Data Sources]
[dBase]
[Sybase]
[Sybase11]
[Oracle7]
[Oracle8]
[Informix]
[DB2]
[UDB2]
[OpenIngres]
[OpenIngres20]
[Text]
[MS_SQLServer7]
[ODBC]
9-16 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Defining ODBC Data Sources
Database=odbc
ServerName=SYBASE
WorkstationID=id
LogonID=odbc01
Password=odbc01
OptimizePrepare=2
SelectMethod=1
Be sure that each section label matches an entry in the [ODBC Data Sources] section.
For example, if you created entries in that section for Sybase11 and Sybase10, you
make entries as shown here.
[Sybase10]
Driver=%ODBCHOME%/lib/OEsyb15.so
Description=Sybase10 on OurOtherMachine
.
.
.
[Sybase11]
Driver=%ODBCHOME%/lib/OEsyb15.so
Description=Sybase11 on ThisMachine
.
.
.
Do not change the Driver setting. During installation, ODBCHOME is defined in the
file so that its value accurately identifies the location of the driver. (ODBCHOME is
defined as $ORACLE_HOME/odbc.)
All of the other settings are provided only as examples of the values you might
provide. For information about providing the correct values for these settings, refer
to MERANT DataDirect ODBC Drivers Help under the chapter on the particular
driver you are configuring.
Note: Oracle Corporation recommends that you do not provide values for the
LogonID and Password settings. Providing this information in a text file
compromises the security of your relational database. In most cases, Express Server
requires this information at connect time, regardless of whether or not it is provided
in odbc.ini.
9-18 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Testing Your Configuration
Introduction
To make sure that your communications are set up correctly, you must open
communications with the relational database. Express does not test the
configuration until it receives a SQL CONNECT command.
You can use the facilities of the Express client software you are using or issue
Express commands, as shown in the following examples. Refer to the SQL
command entry in the Express Language Help system for additional syntax options.
9-20 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
10
Supporting Single-Byte Character
Translation
Chapter summary
This chapter explains how to configure Express services to translate single-byte
character data between formats that are used by external data sources and the
format that is used internally by Express.
List of topics
This chapter includes the following topics:
■ Understanding Character Sets
■ When to Configure Your System
■ How to Configure Your System
■ Determining the Character Sets
■ Creating Translation Tables
■ Instructing Express to Use the Tables
■ Sample Translation Tables
10-2 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
When to Configure Your System
Overview
Whether or not you need to configure Express services for single-byte character
translation depends on how the services will be used. For each Express service, you
will need to consider such questions as:
■ Will clients connect using SNAPI, XCA, or the Web?
■ On what platforms will clients run?
■ Will clients load data into Express from relational databases? Where will the
relational databases reside?
■ Will clients load data into Express from files? Where will the files reside?
Express Analyzer. When you start up the Oracle RDBMS and view the original
data, the Pound Sterling characters are properly displayed.
This situation does not signal loss of data or database corruption. Rather, it is a
symptom of different internal and external character sets.
10-4 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
How to Configure Your System
External
I/O Description Data
File I/O Express commands, such as FILEREAD, INFILE File
EIF operations Express IMPORT and EXPORT commands EIF file
XCA XCA communications Partner
session
SNAPI SNAPI communications Windows
client
SQL Express SQL command RDBMS
Additionally, you can specify translation tables for upper- and lowercase letters in
the DefaultCaseTranslateTable setting.
Note: With the single exception of the DefaultCharacterSet setting, all the settings in
the Locale sheet of Instance Manager are for specifying single-byte character
translation tables. The DefaultCharacterSet setting is for systems based on multibyte
characters only.
10-6 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Determining the Character Sets
do
_hexvalue = extchars(_hexdigit, intpart(_i / 16) + 1, 1)
_hexvalue = joinchars(_hexvalue, extchars(_hexdigit, -
rem(_i, 16) + 1, 1))
show joinchars(’glyph for byte value \\x’ _hexvalue -
’ = ’ convert(_i byte))
_i = _i + 1
doend
END
10-8 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Creating Translation Tables
10-10 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Creating Translation Tables
6. In the external character set, locate the character in the first cell and note its
hexadecimal position, which always begins with the letter “x,” such as x00.
The following figure shows the at symbol (@) at position x00 in the external
character set.
7. In the internal character set, locate the corresponding character and note its
hexadecimal position, such as xE1.
The following figure shows the at symbol (@) at position xE1 in the internal
character set.
8. In the inbound translation table, find the cell that corresponds to the position
you noted in Step 6 and write the position from Step 7. For example, in cell 00 of
the inbound table, write xE1.
10-12 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Creating Translation Tables
9. In the outbound translation table, find the cell that corresponds to the position
you noted in Step 7 and write the position from Step 6. For example, in cell E1
of the outbound table, write x00.
The following figure illustrates this correspondence.
10. Repeat Steps 6 through 9 for each character in the external character set.
Tips: For some characters in the external character set, you might not find
exactly the same character in the internal character set. In such cases, select a
character in the internal character set that can be a substitute for the character in
the external character set.
Generally, the outbound table should be an exact “inverse” of the inbound
table, so that characters that are brought into Express and then are written out
again are unchanged by this “round-trip.”
10-14 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Instructing Express to Use the Tables
10. Use Administrator or the Connection Utility to validate the values of _XLTID
and _XLTABLE.
11. Stop the Express service.
12. Using operating system commands, make the express.db file read-only.
10-16 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Instructing Express to Use the Tables
The following table shows how translation tables may be specified for various I/O
activities within Express.
Session
Express I/O Service Default Default Command
SQL DefaultSQLTranslateTable _XLTSQL
SNAPI DefaultSNAPITranslateTable _XLTAPI
EIF Pipeline in XCA DefaultEIFTranslateTable _XLTEIF COMSET
XLTTABLE
Text file in XCA DefaultFileTranslateTable _XLTFILE
TRANSPORT
Input from XCA DefaultXCATranslateTable _XLTXCA COMSET
RETRIEVE XLTTABLE
Input from XCA DefaultXCATranslateTable _XLTXCA COMSET
EXECUTE XLTTABLE
FILEREAD, FILEPUT, DefaultFileTranslateTable _XLTFILE FILESET
INFILE, OUTFILE, and XLTTABLE
so on
EIF files with IMPORT DefaultEIFTranslateTable _XLTEIF
or EXPORT
DIF or PRN files with DefaultFileTranslateTable _XLTFILE
IMPORT
DIF files with EXPORT DefaultFileTranslateTable _XLTFILE
Note: The Express IMPORT and EXPORT commands never use translation tables
when used with the following types of worksheet files: WKS, WK1, WRK, or WR1.
Related information
For more information about identifying translation tables for Express Server, search
the Instance Manager Help system for parameters on the Locale sheet.
For more information about identifying translation tables for individual Express
sessions, see the Express Language Help system.
Overview
The sample translation table pairs provided in this section are not intended as
complete solutions. You may refer to them as models and adapt them as needed.
ANSIOEM
This pair of tables is the reverse of OEMANSI (shown earlier in this chapter).
if not isvalue(_xltid ’ANSIOEM’)
then maintain _xltid add ’ANSIOEM’
_xltable(_xltid ’ANSIOEM’) = joinlines(-
joinchars( -
’\x00\x01\x02\x03\x04\x05\x06\x07\x08\x09\x0A\x0B\x0C\x0D\x0E\x0F’-
’\x10\x11\x12\x13\x14\x15\x16\x17\x18\x19\x1A\x1B\x1C\x1D\x1E\x1F’-
’\x20\x21\x22\x23\x24\x25\x26\x27\x28\x29\x2A\x2B\x2C\x2D\x2E\x2F’-
’\x30\x31\x32\x33\x34\x35\x36\x37\x38\x39\x3A\x3B\x3C\x3D\x3E\x3F’-
’\x40\x41\x42\x43\x44\x45\x46\x47\x48\x49\x4A\x4B\x4C\x4D\x4E\x4F’-
’\x50\x51\x52\x53\x54\x55\x56\x57\x58\x59\x5A\x5B\x5C\x5D\x5E\x5F’-
’\x60\x61\x62\x63\x64\x65\x66\x67\x68\x69\x6A\x6B\x6C\x6D\x6E\x6F’-
’\x70\x71\x72\x73\x74\x75\x76\x77\x78\x79\x7A\x7B\x7C\x7D\x7E\x7F’-
’\x5F\x5F\x2C\x9F\x2C\x2E\x2B\xD8\x5E\x25\x53\x3C\x4F\x5F\x5F\x5F’-
’\x5F\x60\x27\x22\x22\x07\x2D\x2D\x7E\x54\x73\x3E\x6F\x5F\x5F\x59’-
’\xFF\xAD\x9B\x9C\x0F\x9D\xDD\x15\x22\x63\xA6\xAE\xAA\x2D\x72\x5F’-
’\xF8\xF1\xFD\x33\x27\xE6\x14\xFA\x2C\x31\xA7\xAF\xAC\xAB\x5F\xA8’-
’\x41\x41\x41\x41\x8E\x8F\x92\x80\x45\x90\x45\x45\x49\x49\x49\x49’-
’\x44\xA5\x4F\x4F\x4F\x4F\x99\x78\x4F\x55\x55\x55\x9A\x59\x5F\xE1’-
’\x85\xA0\x83\x61\x84\x86\x91\x87\x8A\x82\x88\x89\x8D\xA1\x8C\x8B’-
’\x64\xA4\x95\xA2\x93\x6F\x94\xF6\x6F\x97\xA3\x96\x81\x79\x5F\x98’)-
joinchars( -
’\x00\x01\x02\x03\x04\x05\x06\x07\x08\x09\x0A\x0B\x0C\x0D\x0E\xA4’-
’\x10\x11\x12\x13\xB6\xA7\x16\x17\x18\x19\x1A\x1B\x1C\x1D\x1E\x1F’-
’\x20\x21\x22\x23\x24\x25\x26\x27\x28\x29\x2A\x2B\x2C\x2D\x2E\x2F’-
’\x30\x31\x32\x33\x34\x35\x36\x37\x38\x39\x3A\x3B\x3C\x3D\x3E\x3F’-
’\x40\x41\x42\x43\x44\x45\x46\x47\x48\x49\x4A\x4B\x4C\x4D\x4E\x4F’-
’\x50\x51\x52\x53\x54\x55\x56\x57\x58\x59\x5A\x5B\x5C\x5D\x5E\x5F’-
’\x60\x61\x62\x63\x64\x65\x66\x67\x68\x69\x6A\x6B\x6C\x6D\x6E\x6F’-
’\x70\x71\x72\x73\x74\x75\x76\x77\x78\x79\x7A\x7B\x7C\x7D\x7E\x7F’-
’\xC7\xFC\xE9\xE2\xE4\xE0\xE5\xE7\xEA\xEB\xE8\xEF\xEE\xEC\xC4\xC5’-
’\xC9\xE6\xC6\xF4\xF6\xF2\xFB\xF9\xFF\xD6\xDC\xA2\xA3\xA5\x50\x83’-
’\xE1\xED\xF3\xFA\xF1\xD1\xAA\xBA\xBF\xAC\xAC\xBD\xBC\xA1\xAB\xBB’-
’\xA6\xA6\xA6\xA6\xA6\xA6\xA6\x2B\x2B\xA6\xA6\x2B\x2B\x2B\x2B\x2B’-
10-18 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Sample Translation Tables
’\x2B\x2D\x2D\x2B\x2D\x2B\xA6\xA6\x2B\x2B\x2D\x2D\xA6\x2D\x2B\x2D’-
’\x2D\x2D\x2D\x2B\x2B\x2B\x2B\x2B\x2B\x2B\x2B\xA6\x5F\xA6\xA6\xAF’-
’\x61\xDF\x47\x70\x53\x73\xB5\x74\x46\x54\x4F\x64\x38\x66\x65\x6E’-
’\x3D\xB1\x3D\x3D\x28\x29\xF7\x98\xB0\xB7\xB7\x76\x6E\xB2\xA6\xA0’))
if not isvalue(_xltid ’THIN2PND’)
then maintain _xltid add ’THIN2PND’
_xltable(_xltid ’THIN2PND’) = joinlines(-
joinchars( -
’\x00\x01\x02\x03\x04\x05\x06\x07\x08\x09\x0A\x0B\x0C\x0D\x0E\x0F’-
’\x10\x11\x12\x13\x14\x15\x16\x17\x18\x19\x1A\x1B\x1C\x1D\x1E\x1F’-
’\x20\x21\x22\x23\x24\x25\x26\x27\x28\x29\x2A\x2B\x2C\x2D\x2E\x2F’-
’\x30\x31\x32\x33\x34\x35\x36\x37\x38\x39\x3A\x3B\x3C\x3D\x3E\x3F’-
’\x40\x41\x42\x43\x44\x45\x46\x47\x48\x49\x4A\x4B\x4C\x4D\x4E\x4F’-
’\x50\x51\x52\x53\x54\x55\x56\x57\x58\x59\x5A\x5B\x5C\x5D\x5E\x5F’-
’\x60\x61\x62\x63\x64\x65\x66\x67\x68\x69\x6A\x6B\x6C\x6D\x6E\x6F’-
’\x70\x71\x72\x73\x74\x75\x76\x77\x78\x79\x7A\x7B\x7C\x7D\x7E\x7F’-
’\x5F\x5F\x2C\x9F\x2C\x2E\x2B\xD8\x5E\x25\x53\x3C\x4F\x5F\x5F\x5F’-
’\x5F\x60\x27\x22\x22\x07\x2D\x2D\x7E\x54\x73\x3E\x6F\x5F\x5F\x59’-
’\xFF\xAD\x9B\x9C\x0F\x9D\xDD\x15\x22\x63\xA6\xAE\xAA\x2D\x72\x5F’-
’\xF8\xF1\xFD\x33\x27\xE6\x14\xFA\x2C\x31\xA7\xAF\xAC\xAB\x5F\xA8’-
’\x41\x41\x41\x41\x8E\x8F\x92\x80\x45\x90\x45\x45\x49\x49\x49\x49’-
’\x44\xA5\x4F\x4F\x4F\x4F\x99\x78\x4F\x55\x55\x55\x9A\x59\x5F\xE1’-
’\x85\xA0\x83\x61\x84\x86\x91\x87\x8A\x82\x88\x89\x8D\xA1\x8C\x8B’-
’\x64\xA4\x95\xA2\x93\x6F\x94\xF6\x6F\x97\xA3\x96\x81\x79\x5F\x98’)-
joinchars( -
’\x00\x01\x02\x03\x04\x05\x06\x07\x08\x09\x0A\x0B\x0C\x0D\x0E\xA4’-
’\x10\x11\x12\x13\xB6\xA7\x16\x17\x18\x19\x1A\x1B\x1C\x1D\x1E\x1F’-
’\x20\x21\x22\x23\x24\x25\x26\x27\x28\x29\x2A\x2B\x2C\x2D\x2E\x2F’-
’\x30\x31\x32\x33\x34\x35\x36\x37\x38\x39\x3A\x3B\x3C\x3D\x3E\x3F’-
’\x40\x41\x42\x43\x44\x45\x46\x47\x48\x49\x4A\x4B\x4C\x4D\x4E\x4F’-
’\x50\x51\x52\x53\x54\x55\x56\x57\x58\x59\x5A\x5B\x5C\x5D\x5E\x5F’-
’\x60\x61\x62\x63\x64\x65\x66\x67\x68\x69\x6A\x6B\x6C\x6D\x6E\x6F’-
’\x70\x71\x72\x73\x74\x75\x76\x77\x78\x79\x7A\x7B\x7C\x7D\x7E\x7F’-
’\xC7\xFC\xE9\xE2\xE4\xE0\xE5\xE7\xEA\xEB\xE8\xEF\xEE\xEC\xC4\xC5’-
’\xC9\xE6\xC6\xF4\xF6\xF2\xFB\xF9\xFF\xD6\xDC\xA2\xA3\xA5\x50\x83’-
’\xE1\xED\xF3\xA3\xF1\xD1\xAA\xBA\xBF\xAC\xAC\xBD\xBC\xA1\xAB\xBB’-
’\xA6\xA6\xA6\xA6\xA6\xA6\xA6\x2B\x2B\xA6\xA6\x2B\x2B\x2B\x2B\x2B’-
’\x2B\x2D\x2D\x2B\x2D\x2B\xA6\xA6\x2B\x2B\x2D\x2D\xA6\x2D\x2B\x2D’-
’\x2D\x2D\x2D\x2B\x2B\x2B\x2B\x2B\x2B\x2B\x2B\xA6\x5F\xA6\xA6\xAF’-
’\x61\xDF\x47\x70\x53\x73\xB5\x74\x46\x54\x4F\x64\x38\x66\x65\x6E’-
’\x3D\xB1\x3D\x3D\x28\x29\xF7\x98\xB0\xB7\xB7\x76\x6E\xB2\xA6\xA0’))
STRAIGHT
This is an invisible map. It simply puts the character 65 to 65, 66 to 66, and so on. It
is not useful in itself, but it might be handy as a template for creating other tables.
10-20 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Sample Translation Tables
THIK2PND
These translation tables are similar to STRAIGHT, but they map both the internal
character codes 9C and A3 to external character code 9C.
10-22 Oracle Express Server Installation and Configuration Guide for Sun SPARC Solaris
Index
Symbols B
_XLTABLE variable, 10-9 backslash characters, 5-11
_XLTAPI option, 10-16 batch jobs, 5-2, 5-11, 5-14, 5-16
_XLTCASE option, 10-16 Batch Manager, 3-7, 3-11, 3-12, 5-16
_XLTEIF option, 10-16 bin directory, 3-7, 4-30
_XLTFILE option, 10-16 binding strings, 5-4 to 5-5
_XLTID dimension, 10-9 browsers
_XLTSQL option, 10-16 Instance Manager interface, 3-16
_XLTXCA option, 10-16 supported by Instance Manager, 4-4
btmxxx directory, 3-7
A
access rights
C
DBA User, 2-8, 7-4 cache, 8-8
file owner, 6-9, 7-4 Call Interface module, 3-9
ACLs (Access Control Lists), 6-9 to 6-11 character sets
Acrobat Reader, 2-2 ANSI, 10-2
administration utilities ASCII, 10-2
See also Command-Line Service Manager, Express configuration, 4-16
Command Processor, Instance Manager single-byte, 10-2, 10-4
file location, 3-8 translation, 10-3, 10-7
installing, 3-7 translation tables, 10-5, 10-6
ANSI character set, 10-2, 10-3 CHDIR command, 7-5
Application Event Log, 4-26 chmod command, 6-14
ASCII character set, 10-2 client support files, 3-8, 3-11
authentication, 6-4 clients, 1-3
authentication daemon, 1-6, 4-26, 6-7 See also Express clients
authorization code pages. See character sets
defined, 6-8 collector thread, 8-10
file-level, 6-11 CollectorThreadCount setting, 8-10
within Express, 6-9 command-line administration utilities. See
authorization daemon, 1-6, 4-26, 6-10, 7-4 administration utilities
Command-Line Service Manager
Index-1
description, 5-2 DATABASE CREATE command, 7-2
file location, 3-8 database files
installing, 3-7 See also extension files, temporary files
libraries, 5-12 location, 7-5
running interactively, 5-6 owner, 7-4
syntax, 5-7 to 5-8 remote, 6-11
targeting a service, 5-4 to 5-5 search paths, 7-5
commands size, 7-2, 7-7
operating system, 4-15 types, 7-2
common directory, 3-8 database list, 7-3
communications transports databases
installing support, 3-9 defined, 7-1
specifying in a binding string, 5-5 files composing, 7-2
verifying, 4-11 pages, 8-9
complete installation, 3-6 paging performance, 8-6, 8-8
composites, 2-9 performance, 2-9
computer configuration, 2-1 sharing, 7-4
COMSET command, 10-16 upgrading, 2-9
configuration DBA User, 2-7, 2-8, 4-21, 6-7, 6-12
hardware requirements, 2-1 DBEXTENDPATH option, 7-6, 7-9
optional modules list, 3-9 DBSEARCHPATH option, 7-6
configuration agent, 1-7, 4-26 DBTEMPPATH option, 7-6
configuration parameters DBWAITTIME option, 7-5
changing, 4-13 to 4-17 Default User
database paging, 8-9 access rights, 2-8, 6-8
default settings, 4-14 defined, 2-7, 2-8
for improved performance, 8-7 to 8-12 password, 4-21
locating by task, 4-16 session identity, 6-6
connect string (SQL), 9-10 DefaultCaseTranslateTable setting, 10-16
connection options (SQL), 9-2 DefaultEIFTranslateTable setting, 10-5, 10-16
connections, 1-8 DefaultFileTranslateTable setting, 10-5, 10-16
See also SNAPI, XCA, Express Web Agent DefaultMode setting, 6-12
Corba Session Manager, 4-23 DefaultSNAPITranslateTable setting, 10-5, 10-16
crash recovery, 7-8 DefaultSQLTranslateTable setting, 10-5, 10-16
custom installation, 3-6, 3-8 to 3-12 DefaultXCATranslateTable setting, 10-5, 10-16
deinstalling, 2-10 to 2-11, 3-5
dependencies
D
among components, 3-11
daemons, 3-7 among software products, 2-4
database access directory structure, 3-7
attach modes, 7-4 Discover Nodes option, 4-3
concurrent users, 8-8 disk assignments, 4-14
file modes, 6-12 to 6-13, 7-3 documentation, 2-2 to 2-3, 3-18, 4-6
database aliases, 3-15, 9-10
Database Connection module, 3-9
Index-2
E targeting a service, 5-4 to 5-5
troubleshooting with event logs, 4-25
EBCDIC character set, 10-2 Express Server clients. See clients
EIF files, 2-9, 10-7
Express service environment
EIF operations, 10-5
components, 1-5
eim directory, 3-8 daemons, 1-5, 3-7
eim_webstage.zip file, 3-17
initializing, 3-13
eim.sh script, 4-3
log files, 4-25
environment variables, 9-8 managing, 3-12 to 3-13
escape characters, 5-11
overview, 1-5 to 1-7
esextend directory, 3-8
stopping, 2-10
estemp directory, 3-8 version check, 3-14
event log, 4-25, 5-15, 8-9
Express services
event messages, 4-26
creating, 4-27
EventLogPath setting, 4-25 default identifiers, 1-7
exception handling, 4-16
defined, 1-7
EXPORT command, 2-9
implemented in Unix, 1-5 to 1-7
Express Agent, 3-15, 4-3, 4-26 locating in Instance Manager, 4-29
Express Batch Manager. See Batch Manager
multiple instances, 4-14
Express Command Processor
targeting, 5-4 to 5-5
file location, 3-8 viewing lists, 4-8
installing, 3-7
Express SPL. See Express language
libraries, 5-12
Express Web Agent
running interactively, 5-9 configuration, 4-17
scheduling jobs in Oracle Enterprise described, 3-11, 3-12
Manager, 5-11
file location, 3-8
syntax, 5-10 Help system, 3-18
targeting a service, 5-4 to 5-5 installation dependencies, 2-4, 3-11
Express Connection Utility, 4-11
modules, 4-19
Express Instance Manager. See Instance Manager Express Web Publisher, 1-3, 3-8, 3-11, 3-12
Express language express_vb.sh script, 4-30
command processing, 4-11
express.db database, 4-11, 7-6, 10-9
defined, 1-2 express.prm script, 3-15, 4-30, 9-8
Help system, 3-18 express.prm.old script, 3-15
scripts, 8-3
express.sh script, 2-11, 3-13, 3-15
security, 6-9 EXPTEMP database, 7-2, 7-7
Express modules. See specific modules EXTCALL objects, 3-9, 6-14
Express scripts. See scripts
extension files, 7-5, 7-9
Express Server location, 3-8
deinstalling, 2-10 removing, 2-11
installing, 3-2
ExtensionFilePath setting, 7-6, 7-9
sessions, 1-8 External Call Support module, 3-9
starting, 4-9 external function calls, 6-14
stopping, 2-11, 4-12
Index-3
F installation
file locations, 3-7
failed connection error, 3-2 Oracle home, 2-5
failure to start, 4-11
prerequisites, 2-2
file I/O, 10-5
product choices, 2-3
file modes, 6-11, 6-12 user accounts, 4-21
See also access rights
installation options
FileOwner setting, 7-3
custom choices, 3-8
FILEQUERY function, 6-14 dependencies among products, 2-4
files
described, 3-6
disk assignments, 4-14
Oracle8 support files, 9-3
location, 3-7, 4-16 product descriptions, 2-3
FILESET command, 10-16
SQL support, 3-9, 9-3
FreePageHighCount setting, 8-6
installation procedures
FreePageLowCount setting, 8-6 administration utilities, 3-7
Express Server, 3-2
G Instance Manager, 3-4
starting Installer, 3-1
GLOBTEMP databases, 7-2
installation user, 2-7, 2-8
GPSBtreeMax setting, 8-12
Installer
GPSBTreeMiss setting, 8-12
incompatibilities, 2-10
installing, 3-7
H Oracle home support, 2-5
hardware requirements, 2-1 running, 3-1
help systems, 3-18, 4-6 Instance Manager
HOST security level, 6-6 basic usage, 4-2 to 4-9
described, 4-2
diagram of browser access, 3-16
I file location, 3-8
identifiers for services, 4-16 installation options, 2-3
identities installing, 3-4
default, 4-21 installing Web site support, 3-15 to 3-18
Web user, 6-5 navigation, 4-7
impersonation, 4-21 service discovery, 4-3, 4-29
IMPORT command, 2-9 starting from a browser, 4-3
INFILE command, 10-16 starting from Oracle Enterprise Manager, 4-31
Initial Session module, 3-9 starting from X Windows, 4-3
Initial Session. See Persistent Session startup properties, 4-4
initialization, 4-17 instances. See Express services
Initialize User Intersolv ODBC drivers, 9-3, 9-8
See also Persistent Session InvisibleEXPTEMP setting, 7-8
access rights, 2-8 I/O mechanisms, 10-5
default identity, 4-21 IV_GLS_LCDIR environment variable (SQL), 9-9
defined, 2-7 IV_GLS_REGISTRY environment variable
required privileges, 5-14 (SQL), 9-9
Index-4
J N
Java plug-ins, 3-17, 4-4 name factory mode, 3-13, 4-3, 4-30
JInitiator, 4-4 Net8 communications, 3-15, 9-9
job scheduling, 5-11 Netscape Navigator, 4-4
network transports, 5-5
node lists, 4-5
K
kernel messages, 4-26
O
OCI
L configuration diagram, 9-4
library search path, 9-9 definition, 9-2
localization, 4-16 installing support, 3-9, 9-3
log directory, 3-8 ODBC
log files, 3-8, 4-5, 4-7, 4-25 configuration diagram, 9-5
login identities, 6-5 definition, 9-2
installing support, 3-9, 9-3
M restrictions, 9-2
ODBC drivers
main database file, 7-2, 7-5 conformance levels, 9-13
malfunction recovery, 7-8 definition of tiers, 9-12
manual mode, 4-3, 4-29 environment variables, 9-8
manuals, 3-18 installation, 9-14
master daemon, 1-5, 1-6, 3-14, 4-3, 4-26 supported, 9-11
MaxIOStreams setting, 8-8 ODBCHOME environment variable, 9-9
MaxSessions setting, 8-8 ODBCINI environment variable, 9-9
MaxWebSessions setting, 8-8 oecxx directory, 3-8
memory management, 4-16 OES_EA_STARTUP system variable, 4-6, 4-30
Microsoft Internet Explorer, 4-4 OES_VBAGENT environment variable, 3-13
Microsoft Internet Information Server (IIS), 3-17 OES_VBAGENT system variable, 4-30
minimum installation, 3-6 oescmd. See Express Command Processor
ModifiedPageWriter thread, 8-10 oesevent.log file, 4-25, 5-15, 8-9
ModifiedPageWriterSleep setting, 8-10, 8-12 oes.key configuration file, 1-5, 1-7, 2-8, 3-15, 4-26
module lists, 4-17 to 4-20 oesmgr. See Command-Line Service Manager
modules OLAP clients. See clients
defined, 1-2, 4-17 olap directory, 3-7
ODBC, 9-6 OLAP home, 3-7, 3-15
optional, 3-9, 9-6 OLAP_HOME environment variable, 2-7
SNAPI, 4-19 Open Database Connectivity. See ODBC
SQL, 4-18, 9-6 OpenWindows graphical interface, 3-2
Web Agent, 4-19 operating system commands, 4-15
multiple services, 4-27 optimization, 2-9, 4-18
ORA_NLS33 environment variable, 9-8
Oracle Application Server, 2-7, 3-3, 3-17
Index-5
Oracle Enterprise Manager configuration settings, 8-7
defined, 4-30 database paging, 8-8 to 8-12
integrating Instance Manager, 2-4, 2-7, 4-30 module list, 4-18
setting up batch jobs, 5-2, 5-13 monitoring, 8-3, 8-4
Oracle Express Administrator, 1-3 tuning, 4-16
Oracle Express Analyzer, 1-3 Performance Monitor
Oracle Express Batch Manager. See Batch Manager counters, 8-6
Oracle Express Instance Manager. See Instance installing support, 3-9
Manager procedure for using, 8-5
Oracle Express modules. See specific modules using, 8-4 to 8-7
Oracle Express Objects, 1-3 performance monitor daemon, 1-7
Oracle Express Spreadsheet Add-In, 1-3 Performance Monitor module, 3-9
Oracle Express Web Agent, 3-11 permissions. See access rights
Oracle Express Web Publisher. See Express Web PERMIT command, 6-5, 6-9
Publisher Persistent Session, 2-8, 4-21, 5-3, 5-14 to 5-15, 8-7
Oracle Financial Analyzer, 1-3 Persistent Session User. See Initialize User
Oracle home, 2-5 to 2-6, 3-7 Personal Express, 1-3, 3-10, 4-14
Oracle Personal Express. See Personal Express port numbers, 3-13, 3-14, 4-7
Oracle Sales Analyzer, 1-3 pre-installation checklist, 2-2
Oracle SNAPI Client. See SNAPI processor configuration, 4-14
Oracle Universal Installer. See Installer product descriptions, 2-3
Oracle Web Listener Components Package. See Web product release notes, 2-2
Listener Components Package
ORACLE_HOME environment variable, 2-7, 9-8
R
ORACLE_SID environment variable, 9-8
Oracle8. See relational database access ramxxx directory, 3-7
orainst. See Installer RDBMS. See relational database access
oratab file, 2-6 Relational Access Manager, 1-3, 3-7, 3-8, 3-11, 3-12,
osnxxx directory, 3-7 9-3
OUI. See Installer relational database access, 9-1 to 9-19
OverWriteEventLog setting, 4-25 installing support, 2-6
owaxxx directory, 3-8 release notes, 2-2
owpxxx directory, 3-8 remote administration utilities. See Instance
Manager
Remote Operations, 3-10
P Remote Procedure Call (RPC) protocol, 3-10
page pool, 8-8 removing products, 3-5
PageBufferCount setting, 8-6 RequiredSecurityLevel setting, 6-5
Paging Manager, 8-8, 8-10 roles, 4-21 to 4-22
paging performance, 4-16 root.sh script, 3-3, 3-13, 4-30
parameters. See configuration parameters runInstaller program, 3-2
password encryption, 6-6
passwords, 4-11
PDF reader, 2-2
performance
Index-6
S SHELL command
installing support, 3-9
schedules for jobs, 5-11 security considerations, 6-14
scripts
Shell Command module, 3-9
in applications, 1-2
ShellPath setting, 4-15
periodic execution, 5-14 shutdown options, 4-13
running in Oracle Enterprise Manager, 5-11
shutdown parameters, 4-17
scheduling, 4-17
ShutdownSPLScript setting, 5-14
starting, 5-3 SNAPI
stopping initialization, 5-15
described, 10-5
search paths
file location, 3-7
databases, 7-5 installation options, 2-4
library, 9-9
installing support, 3-10
modifying, 4-14
modules, 4-19
security remote operations, 3-10
configuration settings, 4-17, 6-5
socket communications, 3-10, 4-5
Express language support, 6-9
software dependencies, 3-11
Express Server features, 6-2 SPL. See Express language
host identity, 6-6
SPLScriptLogging setting, 5-15
levels of, 6-4
SQL
operating system, 6-2 modules, 4-18
ServerDBPath setting, 4-11, 7-5, 7-6
SQL access, 9-1 to 9-19
ServerObjectID setting, 5-5
connecting, 9-5
service directory, 3-8, 4-11 database aliases, 3-15
service discovery, 4-7, 4-29 environment variables, 9-8
service discovery modes, 4-3, 4-5
Express configuration requirements, 9-6
service environment. See Express service installing support, 3-9
environment localization issues, 10-5
service identifiers, 3-14, 4-14, 4-16
paging issues, 8-9
services software dependencies, 3-11
See also Express services SQL module, 3-9
defined, 1-4
SQL*Net. See Net8 communications
listing for Instance Manager, 4-5 startup failure, 4-11
Session User, 6-7, 6-8, 6-12 startup parameters, 4-17
sessions
StartupSPLScript setting, 5-14
configuration parameters, 4-17 status messages, 4-24 to 4-27
current number of, 8-7 SYSINFO function, 6-5, 6-9
defined, 1-8
system messages, 4-26
Persistent Session, 5-3, 5-14 to 5-15 system recovery, 7-8
sharing, 1-8 system requirements, 2-2
terminating problem, 4-23
working directory, 7-5
SessionTempFilePath setting, 7-6, 7-7 T
shadow password file, 6-7 TempFileExtendSize setting, 7-7
TempFileMinimumCount setting, 7-7
Index-7
temporary files W
described, 7-2
location, 3-8, 7-5 WakeUpMilliseconds setting, 5-14, 5-15
WakeUpSPLScript setting, 5-14
managing, 7-7
Web access. See Express Web Agent
removing, 2-11
termination Web Agent. See Express Web Agent
Web communications, 4-17
controlling, 4-17
Web Listener Components Package, 2-4
procedure, 4-12
session, 4-23 Web listener configuration, 3-3
Web listener configuration files, 3-8
Test Engine
Web Publisher. See Express Web Publisher
installing support, 3-9
running, 8-3 to 8-4 Web servers, 3-17
Windows NT
Test Engine Facility module, 3-9
Performance Monitor. See Performance Monitor
ThreadPoolMin setting, 8-8
timeout delay, 4-5
tnsnames.ora configuration file, 9-10 X
tools directory, 3-8
XCA (Express Communications
transactions, 4-13
Architecture), 3-10, 10-5
translation tables, 10-5 to 10-6, 10-8 to 10-21
XCAQueueDepth setting, 8-8
transports, 5-5
Xlib error, 3-2
troubleshooting
xsagent daemon, 1-7
log files, 4-24
xsagent.log file, 4-25
startup, 4-11
xsauth.log file, 4-25
TWO_TASK environment variable, 9-8
xsauthn daemon, 1-6
typical installation, 3-6
xsauthz daemon, 1-6
xsbufdump.log file, 4-27
U xsdaemon master daemon, 1-5, 3-14
uninstalling. See deinstalling xsdaemon.log file, 4-25
xsdpmon daemon, 1-7
upgrading
xsdpmon.log file, 4-25
Express databases, 2-9
general issues, 3-14 X-Windows graphical interface, 3-2
user accounts, 2-7 to 2-8
user identities, 6-5
user roles, 4-21 to 4-22
UUID. See service identifiers
V
Visibroker Smart Agent, 3-13
Visigenic Smart Agent, 4-29
Index-8