Filter
Top Products
Maintaining an iIS Process System
Chapter 2 Setting Up an iIS Process Management System 63
3. Move the two iIS repository files (reposname.btx and reposname.btd) from
FORTE_ROOT/repos on the original Repository Server node to the same
location on the target node.
4. Modify the iPlanet UDS startup script on the server to include the rpstart
command needed to start the iIS repository server (see the iPlanet UDS System
Management Guide).
Creating a Private iIS Repository
➤ To create a private iIS Repository on a development node
1. Copy the two repository seed files (wfseed.btx and wfseed.btd) from
FORTE_ROOT/resposcpy to FORTE_ROOT/repos.
2. Rename the two files to correspond to the name of your iIS private repository.
You might have to modify the files to provide read/write access.
3. Edit the iPlanet UDS Distributed or iPlanet UDS Standalone system icons that
start iIS.
Set the -fr flag in the icon’s command line to reference the new private
repository. For more information, refer to instructions about starting the
process development environment in the iIS Process Development Guide.
Upgrading an iIS System
Upgrading an iIS system is generally straightforward: You install the new version
of iIS system software over the older version. Engine configuration files can be
used with the new version, though you might want to reconfigure engines to make
use of new engine configuration options.
The situation in which you must exercise caution, however, is if you have state or
history information in your engine database that you need to preserve across the
upgrade. If the engine database schema changes from the older version to the
newer version of iIS, you must migrate that data from the older database schema to
the new one. iIS provides Dump/Restore facilities to use for this purpose. See
“Dumping and Restoring Data” on page 126, and be sure to check all release notes.