Restricted and reserved names for application domains

Technote (troubleshooting)


Problem(Abstract)

Names of application domain can conflict with the names of system-defined, top-level directory. When there is a conflict, unpredictable results can occur.

Resolving the problem

System-defined, top-level names and other names are reserved. If you use a reserved names as an application domain name, unpredictable results can occur. A common result is the inability to access directories.


When you create an application domain, a subdirectory of this name is created in the default domain in the following directories:

  • local:
  • store:
  • temporary:
  • logstore:

If you have the fixedname file in the local: directory ( local:///fixedname) in the default domain, you cannot have the fixedname application domain. If you create the fixedname domain, the appliance creates a directory in the same place as this file. This is the conflict.

The following names are reserved. Do not to use them as application domain names, folder names, or file names.
  • .backtrace.reason
  • .jrte.properties
  • .memstats_b4reload
  • audit
  • b2bdocs
  • backtrace.sent
  • backtraces
  • capture.pcap
  • documentcache
  • error-report.txt.gz
  • export
  • extended-backtrace
  • ffdc-cache-usage
  • ffdc-logcapture
  • ffdc-nbleakreport-first
  • ffdc-nbleakreport-last
  • ffdc-packetcapture
  • ffdc-services-memory
  • ftp-response
  • image
  • internal-state.txt
  • jrte
  • log
  • policyframework
  • probe
  • pubcert
  • sharedcert
  • tmp
  • unpack
  • webgui

In addition to these specific names:
  • Do not use an application domain name that matches a file or directory name.
  • Do not create application domain names with the same name as the Directory property of a storage volume.

Rate this page:

(0 users)Average rating

Document information


More support for:

IBM DataPower Gateways
General

Software version:

3.8.2, 4.0.1, 4.0.2, 5.0.0, 6.0.0

Operating system(s):

Firmware

Software edition:

Edition Independent

Reference #:

1639172

Modified date:

2013-06-28

Translate my page

Machine Translation

Content navigation