The ObjectStore Windows installation and setup system is responsible for creating and maintaining the environment ObjectStore requires in order to operate properly. If you want to replace the standard tool, you must maintain the proper environment.
Installation
Installation requires that various directories and files be created or copied to the user's system, that the system environment be modified to point to the files, and that various entries (most described in more detail in Setup in this chapter) be established in the registry or in system services databases. Also, installations that include a Server generally require that the Server be initialized. This is also described in Setup.
Licensing options
The standard ObjectStore installation system has eight licensing options. Depending on the option selected, the installation system determines whether or not to install
Optional components
In addition to variations based on licensing options, the installation system allows the following components to be installed or omitted:
Directories
Though some of the entries described in Chapter 3, API Reference, appear to allow a variety of target directories to be used for elements of an ObjectStore installation, in practice everything should be installed in various directories under a single OS_ROOTDIR. The directory structure should be as follows:
OS_ROOTDIR \
bin
binsngl
doc \
pscript
etc
examples
include
lib
While the contents of most of the directories are self-evident, the etc and binsngl directories need some explanation.
The OS_ROOTDIR and OS_TMPDIR values need to be set in the system environment section on Windows NT, to ensure that they are available for the Server and Cache Manager when they run as services.
Registration data in the registry
The standard ObjectStore installation sets a variety of values in the registry concerning product registration. These values are used by the install and setup system and might not be needed for a VAR installation. Most values are stored in
HKEY_LOCAL_MACHINE\SOFTWARE\Object Design Inc.\ObjectStore.4.0\Registrationbut one is stored in
HKEY_CURRENT_USER\Software\Object Design Inc.\ObjectStore.4.0\RegistrationNote that ObjectStore.4.0 refers to the server generation, not to the current ObjectStore release number, and is used for both Release 4.x and 5.x.
Values stored in HKEY_LOCAL_MACHINE include
See OS_GetRegistration and OS_SetRegistration in Chapter 3, API Reference, for information about using these functions to retrieve and set these values.
Setup
Setup operations are typically performed on a preexisting (or just created) ObjectStore installation. Setup operations generally involve
HKEY_LOCAL_MACHINE\SOFTWARE\Object Design Inc.\ObjectStore.4.0\ServerIndividual parameters are stored using value names that correspond to the parameter name (for example, "Authentication Required"). All values are stored as strings (REG_SZ).
Note that you can use the OS_GetServerParameter and
Creating or modifying RAWFS partition information
Partition information is also stored in the registry, under the same key:
HKEY_LOCAL_MACHINE\SOFTWARE\Object Design Inc.\ObjectStore.4.0\ServerThe RAWFS might contain multiple components, named Partition0, Partition1, ..., PartitionN. Partitions must start from number 0 and no gaps are allowed in the sequence. Each partition descriptor has the following format:
<type> <path> <expandability>
where
<type> is either FILE (Windows NT or 95) or PARTITION (Windows NT only).
<path> is the name of a file system file (for FILE) or a partition name in the form
\\.\A:or a physical drive name in the form
\\.\PhysicalDrive1<expandability> is either EXPANDABLE or NONEXPANDABLE. Only file system files can be EXPANDABLE. Partitions and physical drives are always NONEXPANDABLE.
If you specify a file system file, the installation must create the file. The Server overwrites the contents of the file during initialization, but it does not create the file if it does not exist. If a file system file is designated NONEXPANDABLE, the installation must also presize the file before initializing the Server.
Note that you can use the OS_SetupRawfs entry, described in Chapter 3, API Reference, to run the standard RAWFS setup dialog and update the registry.
Note also that most changes in RAWFS configurations require you to reinitialize the Server. The only exception is when you add a new component (file, partition, or disk) to an existing RAWFS. You can do this without reinitializing.
Initializing or reinitializing the Server and Server log file
You must reinitialize the ObjectStore Server following an installation or following most changes to a RAWFS configuration. You can use the entry OS_InitLog, described in Chapter 3, API Reference, to initialize the Server. Note that there are several entries in the registry that are relevant to Server initialization under the key
HKEY_LOCAL_MACHINE\SOFTWARE\Object Design Inc.\ObjectStore.4.0\ServerThey are
Use the entry OS_InitLog, described in Chapter 3, API Reference, to initialize the Server and set the relevant values in the registry.
Setting up the Server and Cache Manager as system services
You can use the entry OS_UpdateStartup, described in Chapter 3, API Reference, to set up system services. This task requires two steps. First, you must update the system services databases. Then set the Auto Start Server value in the registry under
HKEY_LOCAL_MACHINE\SOFTWARE\Object Design Inc.\ObjectStore.4.0\ServerNote that system service updating follows different rules on Windows NT, which supports substantive system services, and Windows 95, which does not.
The following paragraphs characterize the components and sequence of an ObjectStore installation and setup.
Components of Installation and Setup
The major ObjectStore-supplied components for the installation and setup are SETUP.INS, OS_SETUP.DLL, and OSCP437.DLL. SETUP.INS is the main InstallShield application program. OS_SETUP.DLL provides a wide variety of ObjectStore-specific support routines, and OSCP437.DLL is a resource DLL supplying English-language resources used by OS_SETUP.DLL. OS_SETUP.DLL and OSCP437.DLL are supplied in object form. SETUP.INS is derived from the source files SETUP.RUL and
OS_SETUP.H that are supplied with this VAR kit. OS_SETUP.DLL and OSCP437.DLL
Chapter 3, API Reference, describes the available entries in
OS_SETUP.DLL. You should use these entries when modifying the ObjectStore installation or when creating your own installation and setup. The VAR kit might contain a text file with updates for the API documentation included in Chapter 3, API Reference.
The OSCP437.DLL is used internally by OS_SETUP.DLL and should not need to be changed unless the installation is to be performed in a language other than English. Contact Object Design Technical Support for assistance if a non-English system is required.
SETUP.INS: SETUP.RUL and OS_SETUP.H
SETUP.INS is the control program for ObjectStore install, setup, and uninstall. It was generated by the InstallShield compiler from the source files SETUP.RUL (that contains code) and OS_SETUP.H (that contains definitions for the various strings displayed by InstallShield) and for a variety of constants used by SETUP.RUL.
See Chapter 4, SETUP.RUL Routines, for specific information about how these routines work.
Uninstall
Using uninstall results in the removal of all the various pieces of the ObjectStore installation from the system. This typically means the removal of
Updated: 03/26/98 21:57:20