ObjectStore Installation and License for Windows

Chapter 1

Overview of ObjectStore Installation

ObjectStore Release 5.1 does not support pre-Release 5.0 persistent relocation mapping (prm) format. If you have pre-release 5.0 databases, or if you used the earlier (standard prm) format in your release 5 databases, you must upgrade using the ObjectStore Release 5.0 utility osupgprm before you can use ObjectStore Release 5.1 with these databases.

ObjectStore Release 5.1 Product Modules

ObjectStore Release 5.1 for Windows comprises the ObjectStore database engine and three interfaces - the C++, the Java, and ActiveX interfaces -and the Component Server Framework software. The ObjectStore database engine is bundled with the C++ interface. The Java and ActiveX interface installation is optional.

The first screen you see after inserting the CDROM in the drive is a menu that provides a button corresponding to each interface and an Exit button.

You must install ObjectStore C++ and the database engine first. Complete the C++ installation according to instructions in the remaining chapters in this book. Once this installation is complete, you can initiate installation of the Java and ActiveX interfaces as well as the Component Server Framework from the buttons in the main menu.

Installation Summary

Here are generalized steps for installing ObjectStore:

       x:\ODI\ostore\doc\Index.htm
where x: is equivalent to the root of the CDROM.

If you intend to install the DEBUG or DDEBUG build of ObjectStore Release 5.1, see the instructions for such an installation in the ObjectStore C++ Interface Release Notes, Chapter 3, Platform-Specific Considerations section Platform-Specific Considerations.

Considerations in Configuring ObjectStore

About rawfs components
ObjectStore Release 5.1 for Windows NT and Windows 95 supports storage of rawfs databases for compatibility with previous releases and existing installations. Most installations find file databases more convenient, and can ignore rawfs configuration. However, if you are going to take advantage of the ObjectStore Release 5.1 high-availability features, configuring rawfs disk partitions or physical disks is a necessity. Refer to ObjectStore Management for more information about managing the rawfs and high availability.

When you configure rawfs components, you can choose one of the following options:

Creating and editing rawfs components
 When you use rawfs databases, you specify a set of rawfs components. Each file component can be expandable or of a fixed size. Disk partitions and physical disks are always fixed.

You must create these partitions before initializing the Server and using rawfs databases. Otherwise you must reinitialize after creating the Server partitions.

Neither disk partitions nor physical disks contain a file system. If you choose to use rawfs databases in disk partitions or physical disks, you should create the raw partitions before you initialize the Server.

The Server partition takes at least 2.5 MB of disk space, and must be placed on a local hard drive. After you initialize the partitions, you cannot shrink them without losing data. However, you can expand partitions or add more partitions whenever you want.

Initializing the Server
After you have created rawfs components, initialize the Server. This creates the root directory in an empty rawfs.

There is a small performance advantage if you put the log file on a physical disk separate from your database partitions and file databases.



[previous] [next]

Copyright © 1998 Object Design, Inc. All rights reserved.

Updated: 04/08/98 13:04:31