6.3 HP StoreAll Storage File System User Guide (TA768-96093, June 2013)

Table 11 Checklist for creating HTTP shares (continued)
Step
completed?
Where to find more
informationTask
Step applies
only
nl
to REST API
SharesStep
Create or select an exiting HTTP config profile through
the GUI or through the CLI (ibrix_httpconfig).
IMPORTANT: Each server can have only one HTTP
profile.
Step applies
to all HTTP
share types.
4
• CLI:“Creating HTTP
shares from the CLI”
(page 131)
• GUI: “Creating HTTP
shares from the GUI”
(page 118).
Create or select an existing HTTP virtual host through
the GUI or through the CLI (ibrix_httpvhost).
Step applies
to all HTTP
share types.
5
• CLI:“Creating HTTP
shares from the CLI”
(page 131)
• GUI: “Creating HTTP
shares from the GUI”
(page 118).
Create the HTTP share through the GUI or by using
the CLI (ibrix_httpshare).
Step applies
to all HTTP
share types.
6
• CLI: “Creating HTTP
shares from the CLI”
(page 131)
• GUI: “Creating HTTP
shares from the GUI”
(page 118)
Best practices for configuring HTTP
When configuring HTTP, follow these best practices:
• If an SSL certificate will be required for HTTPS access, add the SSL certificate to the cluster
before creating the shares. See “Managing SSL certificates” (page 174) for information about
creating certificates in the format required by StoreAll software and then adding them to the
cluster.
• When configuring a share on a file system, the file system must be mounted.
• If the directory path to the share includes a subdirectory, be sure to create the subdirectory
on the file system and assign read/write/execute permissions to it. (StoreAll software does
not create the subdirectory if it does not exist, and instead adds a /pub/ directory to the
share path.)
• Ensure that all users who are given read or write access to HTTP shares have sufficient access
permissions at the file system level for the directories exposed as shares.
• For High Availability, when specifying IP addresses for accessing a share, use IP addresses
for VIFs having VIF backups. See the administrator guide for your system for information about
creating VIFs.
Object mode shares and data retention
You can choose to create object mode API shares on regular file systems or on retention-enabled
file systems. Since the object mode API offers no functionality to manage WORM or retained files,
you would normally create them on regular file systems.
If you choose to put an object mode API share on a retention-enabled file system, and if you choose
to enable auto-commit on the file system, objects will become WORM automatically after the
auto-commit period of no filesystem activity on the object. A WORM object cannot be modified
nor replaced via the API. If a default retention period is also defined, it will also become retained
at the same time, and cannot be deleted via the API for the default retention period. Such a file
can be removed administratively using the ibrix_reten_adm CLI command.
Best practices for configuring HTTP 117