About Registration
If at some point you have to move an engine unit to a new node, you do not have to manually
Registration in Production Environments
At a production site removed from a development environment, registration can only be performed using iIS process management tools. In a production environment it is more likely that registrations will be batched, rather than performed one at a time as in a development environment. It is also more likely that library distributions will be registered with a number of engines, rather than a single test engine.
Before performing registrations in such situations, however, you have to first transfer iIS library distributions to the production environment. Use the following steps:
➤To transfer iIS library distributions to a production environment
1.Make sure that developers have generated all relevant iIS library distributions using either the File > Distribute command in the process development workshops or the MakeConductorDistribution Conductor Script command.
2.Copy the iIS library distributions located on the central server node in the development environment to your distribution medium.
The distributions are found in the following directory: FORTE_ROOT/appdist/environment_ID/distribution_ID
where, environment_ID is the name of the active iPlanet UDS development environment. Copy the contents of the distribution_ID directory and the required cl# directory structure beneath it. For information on the structure of library distributions, see the iPlanet UDS System Management Guide.
3.Transfer the iIS library distributions from your distribution medium to the central server node in the production environment.
The distributions should be placed in the FORTE_ROOT/appdist/environment_ID/
directory, where, environment_ID is the name of the active iPlanet UDS production environment.
Chapter 5 Managing Registrations 141
