Use this page to view or change settings related to the
WPAR Manager.
Fields
- Shared directory
- When a WPAR is relocated a set of files is generated including
logs and the state file used to save the full context of the applications
running within the WPAR. Specify the directory where these files are
going to be generated during the relocation work flows. For system
WPARs, this directory refers to a location relative to the root directory
(/) of the WPAR itself. For application WPARs this directory refers
to a location relative to the root directory of the managed system
that is hosting the WPAR.
Note: Since files generated during relocation
must be accessible from both the departure system and the arrival
system, it is important to make sure that what you specify as the
shared directory is accessible from any system where application WPARs
are to be relocated. You can do this by mounting the shared directory
over an NFS file system in each managed system. In the case of system
WPARs this is not necessary because the shared directory refers to
a location within the WPAR's file system, which is already accessible
from both the departure and the destination systems.
Actions
- Enable debug information for relocation logs
- Enables verbose log messages for relocation operations. Only select
this option for debugging purposes as it affects performance.
- Preserve workload partition definitions after the workload partitions
have been deleted
- Preserves workload partition definitions after a system workload
partition has been deleted or an application workload partition has
been stopped. Workload partition definitions also get created and
persisted during the create workload partitions tasks if any error
occurs during the create operation. If workload partition definitions
are preserved they can be deployed at a later time on a WPAR-capable
system. If this option is not selected, no records are persisted on
the IBM® Systems Director environment
after a workload partition has been deleted from the managed system.