3.4.3 Constraints on accessing the network drives (in Windows)
In Windows, the access to the network drives by the component software listed in the following table is restricted. The following table describes the constraints for the component software.
Also, note that the access to the network drives is restricted for a program started from a service depending on the Windows specifications.
|
Component software |
Constraints |
|---|---|
|
Component Transaction Monitor |
When you use a Windows service to start Component Transaction Monitor, do not specify a network drive path in the CTMSPOOL environment variable. |
|
HTTP Server |
The network drives cannot be accessed from the HTTP server. |
|
Performance Tracer |
When you use a Windows service to start Performance Tracer, do not specify a network drive path in the PRFSPOOL environment variable. |
|
Reliable Messaging |
Do not specify the files and directories on a network drive in the following Reliable Messaging configuration properties:
|
|
TPBroker |
Do not specify a network drive or the files on a network drive in the environment variables and properties used with the ORB functionality. |
|
HiRDB/Single Server Version 10 |
The network drives are not connected when the power is input, so HiRDB Embedded Server Version 8 cannot be started by using a Windows service. For this reason, do not install HiRDB/Single Server Version 10 or set up the database environment on a network drive. |