|
Operating
Record Builder on Windows NT
Contents
Introduction
Document Conventions
Requirements
Record Builder in a SiteSearch Environment
Starting the Record Builder Application
Using the ssadmin Interface
Shutting Down the Record Builder Application
Starting and Stopping Individual Record Builder Components
Introduction
This document
contains procedures for operating (starting up and shutting down) the
Record Builder application included with
Open SiteSearch Database Builder.
Document
Conventions
- <WebZ_root>
is the location of the environment that contains the Record Builder
application.
- Commands you
type appear in quotes, like this: "poll".
Requirements
Before
starting these procedures, complete the following tasks:
Because Record
Builder is an application included with Open SiteSearch Database
Builder, it is installed concurrently with Database
Builder.
Return
to Contents
Record
Builder in a SiteSearch Environment
In a SiteSearch environment
that includes Record Builder, a single OpServe manages both WebZ and Record
Builder. Record Builder has its own Web server port and Web server extension,
JaSSI, ZBase, and Access servers (JaSSIRB, ZBaseRB, and AccessServerRB,
respectively), and a Lock server. This is the usual configuration, although
it is possible to set up Record Builder-only environment.
The procedures in
this document assume that you are using a SiteSearch environment with
both WebZ and Record Builder.
Return
to Contents
Starting
the Record Builder Application
If you are using
the Microsoft Internet Information Server (IIS) as your Web server, it
is not possible to run WebZ and Record Builder simultaneously on a single
machine. Your options are to:
- Use Netscape as
your Web server, which allows you to run WebZ and Record Builder simultaneously
on the same machine
- Use IIS as the
Web server for a WebZ-only environment and Netscape as a Web server
for a Record Builder-only environment
- Use Netscape as
the Web server for a WebZ-only environment and IIS as the Web Server
for a Record Builder-only environment
- Use IIS as the
Web server for a WebZ-only environment on one machine and IIS as the
Web server for a Record builder-only environment on another machine
Procedure
The steps below
describe how to start the Record Builder application (and WebZ, if desired),
regardless of its Web server.
|
1. Verify
that your Web server for Record Builder is running. Refer to your
Web server's documentation for instructions about starting the Web
server.
|
| 2. Shut
down WebZ if it is currently running. |
|
3. Do you want
to restart WebZ when you start Record Builder?
- Yes.
Verify
that the Web server for WebZ is running. Refer to your Web server's
documentation for instructions about starting the Web server
- No.
Go directly to step 4.
|
|
4. Are you
using the Access component
to provide staff authentication and and authorization for Record
Builder (and WebZ, if applicable)?
|
|
5. Which
version of SiteSearch are you running?
- SiteSearch
4.1.2. From the Programs menu, select SiteSearch_4_1_2. Then
click Start SiteSearch Record Builder Batch File. This launches
the ssmgr_rb.bat file.
- SiteSearch
4.1.1. From Windows NT Explorer, execute the ssadmin.bat file:
- Move
to the <WebZ_root>\scripts directory.
- Double-click
ssadmin.bat to execute this file.
| Note: |
Executing
ssadmin_rb.bat starts the ssadmin utility, which starts the
OpServe if it is not already running. OpServe then starts the
Record Builder and WebZ servers listed in the OpServe_rb.ini
configuration file (typically JaSSIRB, ZBaseRB, AccessRB,
Lock, JaSSI, ZBase, and Access). |
|
| 6. ssadmin_rb.bat
runs in an MS-DOS window. After displaying a series of messages, the
ssadmin interface opens and you see the SSAdmin
Cmd> prompt. |
7. Use the
ssadmin poll command to
verify that the JaSSIRB, ZBaseRB, AccessRB, and Lock servers for Record
Builder and the OpServe, JaSSI, ZBase, and Access servers for WebZ
have started.
| Note: |
If
you did not start the SQL server software or configure the
Access component, the Access server shuts down immediately
after it starts up.
|
|
Return
to Contents
Using
the ssadmin Interface
The ssadmin utility
has an interface to the Operations server, OpServe, for both WebZ and
the Record Builder application. This interface allows you to monitor system
status and issue commands directly to the system components.
While you are
working in ssadmin, the command prompt changes to "SSAdmin Cmd>".
Some commonly-used ssadmin commands are:
- poll,
which lists the servers that are currently running
- help,
which lists and briefly describes all ssadmin commands
- quit,
which closes the ssadmin interface without shutting down any servers
- term,
which shuts down all currently-running servers
For detailed information
about all ssadmin commands, refer to the ssadmin
Command Reference.
Return
to Contents
Shutting
Down the Record Builder Application
The following
steps describe how to shut down the Record Builder application (and
WebZ as well if it is currently running):
|
1. In Windows
NT Explorer, execute the ssadmin_rb.bat file.
- Move to
the <WebZ_root>\scripts directory.
- Double-click
ssadmin_rb.bat to execute this file.
| Note: |
Because OpServe is already running, no servers start up when
you execute ssadmin_rb.bat this time. |
|
| 2. ssadmin_rb.bat
runs in an MS-DOS window. After displaying a series of messages, the
ssadmin interface opens and you see the SSAdmin
Cmd> prompt. |
|
3. Type
"term" at the SSAdmin Cmd> prompt and press Enter.
The OpServe terminates each of the Record Builder and WebZ servers
and returns you to the system command prompt.
Refer to
Starting and Stopping Individual Record
Builder Components for instructions about stopping a single
Record Builder or WebZ component.
| Note: |
You
need to stop the Web server and the SQL server, if applicable,
separately. Refer to the Web server and SQL server documentation
for instructions about stopping these servers. If you just
shut down WebZ as well, you also need to stop its Web server.
|
|
Return
to Contents
Starting
and Stopping Individual Record Builder Components
Use the ssadmin
start and stop
commands to start or stop individual Record
Builder components (JaSSIRB, ZBaseRB, and AccessRB). For
example, it is possible for you to stop all Record Builder servers individually
and leave the WebZ servers running.
Return
to Contents
See Also
Operating
the WebZ System on Windows NT
|