Enabling object access for selected files

Use the following steps to objectize files under all the containers associated with the unified file and object access storage policy under an account

In a unified file and object access environment, if you want to access files created from file interfaces such as POSIX, NFS, or CIFS through object interfaces such as curl or swift, you need to make these files available for the object interface. For making these files available for the object interface, the ibmobjectizer service, once activated, runs periodically and makes newly created files available for the object interface. You can also use the mmobj file-access command to selectively enable files for access through the object interface.

The purpose of this command is to make certain files available to object sooner (or immediately) than when the objectizer would have made them available. This command does not ensure synchronization between file and object data. Therefore, files deleted are not immediately reflected in the object interface. Complete synchronization is done by the ibmobjectizer service eventually.

In unified file and object access enabled filesets, files can be accessed from the object interface if you know the entire URI (including keystone account ID, device etc.) to access that file without the need for them to be objectized either using the ibmobjectizer service or the mmobj file-access command.

Note: The mmobj file-access command does not enable or disable the unified file and object access feature. It is only used to objectize files (that is enable object access for files) immediately when initiated by the administrator. Disabling object access for files is not supported.

To objectize files under all the containers associated with the unified file and object access storage policy under an account, use the mmobj file-access command as follows:
```
mmobj file-access --storage-policy sof_policy --account-name admin
```
The system displays output similar to the following:
```
Loading objectization configuration from CCR
Fetching storage policy details
Creating container to database map
Performing objectization
Objectization complete
```
This command objectizes all containers in the account admin and enables them for access through the object interface.
To objectize files under a container, use the mmobj file-access command as follows:
```
mmobj file-access --storage-policy sof_policy --account-name admin --container-name container1
```
This command objectizes all files in container1 and enables them for access through the object interface.
To objectize a file while specifying a storage policy, use the mmobj file-access command with the --storage-policy option as follows:
```
mmobj file-access --storage-policy sof_policy --account-name admin \
--container-name container1 --object-name file1.txt
```
This command objectizes file1.txt in container1 and enables it for access through the object interface.
To objectize a file, use the mmobj file-access command as follows:
```
mmobj file-access --object-path \
/ibm/gpfs0/obj_sofpolicy1/s69931509221z1device1/AUTH_763476384728498323747/cont/file1.txt
```
This command objectizes file1.txt at location /ibm/cesSharedRoot/fileset1/Auth_12345/container1/ and enables it for access through the object interface.

For more information about the mmobj file-access command, see the mmobj command.