Persistent storage and user files
IBM® Maximo® Real Estate and Facilities persistent storage retains data that must survive pod restarts, rescheduling, and application upgrades. In Kubernetes and OpenShift environments, persistent storage is implemented by using Persistent Volume Claims (PVCs) that are configured during application activation.
Maximo Real Estate and Facilities requires persistent storage for 3 types of data:
-
User files include application data, uploaded files, integration data, and business content. User files are stored in the /home/wiotp/userfiles directory and contain data that must persist across deployments. The userfiles directory contains multiple directories for different types of data. See User files directories for a complete list.
-
Log files include application logs, Object Migration logs, integration logs, and diagnostic information. Log files are stored in the /home/wiotp/log directory. Configure log retention and rotation policies to manage storage usage. For more information about logs, see Reviewing Maximo Real Estate and Facilities pod and container logs.
-
Configuration files include property files and other configuration data that the application uses at run time. Configuration files are stored in the /home/wiotp/config directory. For information about configuration files, see Properties files.
User files directories
The /home/wiotp/userfiles directory contains directories for many types of application data. The following table summarizes the purpose of the /home/wiotp/userfiles directories.
| Subdirectory | Purpose | Priority | Auto-created |
|---|---|---|---|
| input |
Batch input files for Data Integrator processing. The default /home/wiotp/userfiles/input directory is created by the CreateBatchProcess.sh script. For related properties and directory settings, see Uploading data with batch uploads. Starting in Maximo Real Estate and Facilities 9.2, batch file locations are managed by the operator. Starting in Maximo Real Estate and Facilities 9.2, if you enable S3 object storage, batch file locations are managed by the object storage integration. See Configuring S3 object storage. |
Critical | Yes |
| processing |
Files being processed by Data Integrator. The default /home/wiotp/userfiles/processing directory is created by the CreateBatchProcess.sh script. For related properties and directory settings, see Uploading data with batch uploads. Starting in Maximo Real Estate and Facilities 9.2, batch file locations are managed by the operator. Starting in Maximo Real Estate and Facilities 9.2, if you enable S3 object storage, these file locations are managed by the object storage integration. See Configuring S3 object storage. |
Critical | Yes |
| output |
Data Integrator output files. The default /home/wiotp/userfiles/output directory is created by the CreateBatchProcess.sh script. Copy files if you need to retain the results for reference. For related directory settings, see Uploading data with batch uploads. Starting in Maximo Real Estate and Facilities 9.2, batch file locations are managed by the operator. Starting in Maximo Real Estate and Facilities 9.2, if you enable S3 object storage, these file locations are managed by the object storage integration. See Configuring S3 object storage. |
Critical | Yes |
| error |
Data Integrator error logs. The default /home/wiotp/userfiles/error directory is created by the CreateBatchProcess.sh script. Copy files only for debugging or troubleshooting purposes. For related directory settings, see Uploading data with batch uploads. Starting in Maximo Real Estate and Facilities 9.2, batch file locations are managed by the operator. Starting in Maximo Real Estate and Facilities 9.2, if you enable S3 object storage, these file locations are managed by the object storage integration. See Configuring S3 object storage. |
High | Yes |
| log |
Data Integrator runtime logs. The default /home/wiotp/userfiles/log directory is created by the CreateBatchProcess.sh script. These temporary logs are created automatically. For related directory settings, see Uploading data with batch uploads. Starting in Maximo Real Estate and Facilities 9.2, batch file locations are managed by the operator. Starting in Maximo Real Estate and Facilities 9.2, if you enable S3 object storage, these file locations are managed by the object storage integration. See Configuring S3 object storage. |
High | Yes |
| images | Company logos and uploaded images. See Navigation items. For a related topic about image handling during migration, see Object types supported by Object Migration. | Medium | No |
| Company-1 | Company-specific files. For a related topic, see Tips for operating Data Integrator. | Medium | No |
| crystalreports | Crystal Reports templates, style sheets, and image resources. For related topics, see Form building and Customizing report logos. | Medium | Yes |
| birt | BIRT report designs and related resources. See BIRT reporting, BIRT report process, and Creating BIRT reports. | Low | Yes |
| resources/security | Encryption keystores and related security files | Critical | No |
| ClassLoader | Custom class loader resources such as HTML, JavaScript, and images. See Custom class loaders, Class loader development mode, and Adding resource files to class loaders. | Critical | Yes |
| skin | Style customization that control the user interface appearance. See Customizing styles, Restoring the default styles, and Importing styles and colors. | Critical | No |
| ObjectMigration | Object Migration package exports. See Object migration overview, Background uploads, Background uploads with import, Creating a file by using an export package, and Comparing all objects. | Medium | Yes |
| Translations | Custom XLIFF translation files, exported translation content, TreeGrid translation files, and related language pack content. See Storage of translation files, Changing the language in the availability section, Changing the Gantt language, Importing language packs for data and labels, Exporting data and labels for translation, and Troubleshooting import of language packs. | Critical | Yes |
| treegrid-sample | Sample TreeGrid styling files that you can copy to treegrid when you customize Gantt scheduler styling. See Styling the Gantt scheduler. | Medium | Yes |
| treegrid | TreeGrid styling customization. See Styling the Gantt scheduler, Reverting the Gantt styling, and Changing the Gantt language. | Critical | Yes |
| IntegrationObject | Integration files for outbound processing. See Example: Execution from custom tasks. For related topics, see Execution of DataConnect processes and Standard queries. | Medium | Yes |
| kettle | Pentaho Kettle ETL plug-ins. See ETL maps. For related topics, see Mechanisms to move data into tables and ETL integration process. | Medium | Yes |
Storage configuration
Persistent storage for user files, log files, and configuration files is configured during Maximo Real Estate and Facilities activation in Maximo Application Suite. You specify the storage class and size for each storage category.
- Storage class selection
- Choose a storage class that supports the required access mode and provides appropriate
performance for your workload. The storage class must support file-based storage and allow
read/write access for the Linux group. To view available storage classes in your cluster, run:
oc get storageclasses - Storage sizing
- Size storage based on your expected data volume, growth rate, and retention policies. Consider
factors such as:
- Number of users and concurrent sessions
- Volume of uploaded files and attachments
- Integration data volume
- Log retention period
- Backup and archive requirements
- S3 object storage support
- Starting in Maximo Real Estate and Facilities 9.2, you can use S3-compatible object storage for specific batch upload directories. This can reduce persistent volume storage requirements for large file uploads. For more information, see the S3 object storage configuration documentation.
For more information, see Deploying Maximo Real Estate and Facilities in Maximo Application Suite.