6.9.2 Managing files when storing static files directly in the web server's directory
When the File Management/Registration menu is not displayed in the Operational Content Editing Window, you will have to store static files directly in a directory on the web server. The File Management/Registration menu in the Operational Content Editing Window can store only one static file at a time; therefore, if you want to store multiple static files on the web server in the batch mode, it is easier to store them directly in the web server's directory.
The following subsections provide notes on storing static files directly in the web server's directory.
- Organization of this subsection
(1) How to select a storage directory
When you place in an Operational Content a static file that has been stored in a directory on Navigation Platform's web server, you specify the relative path of the static file. This path is relative to Navigation-Platform-installation-directory\PP\uCPSB\httpsd\htdocs. Therefore, we recommend that you store image files in a directory that is close to the htdocs directory.
Once you have stored static files, notify the Content Manager, the Content Creator (when JP1/Base is used for user authentication), and the Content Editor of their paths relative to the contents storage directory.
(2) Limitations to file names and directory names
Do not create any file or a directory with a name beginning with ucnp other than the ucnpuserstaticfiles directory directly under the Navigation-Platform-installation-directory\PP\uCPSB\httpsd\htdocs contents storage directory on Navigation Platform's web server. The name ucnp is reserved by the Navigation Platform system. If a file or a directory is created with this name, the operation is not guaranteed.
In addition, do not edit any directory or file that is located in a directory whose name begins with ucnp other than the ucnpuserstaticfiles directory. If such a file or a directory is edited, the operation is not guaranteed.