Help Center · OfficeDocs Docs
Deploy with
confidence.
The official repository guides for deploying, operating and troubleshooting OfficeDocs Suite in your private cloud.
Last updated
55 matching guides · Open on GitHub ↗
START HERE
Choose your deployment path
DOCUMENTATION INDEX
Read the guide that matches your task
Getting started
01High Availability Kubernetes DeploymentBuild a resilient OfficeDocs cluster: node topology, minimum server specifications, ACCESS_DOMAIN configuration and high-availability verification.
↗02Quick StartInstall OfficeDocs Suite for the first time: prepare the installer and release package, check the environment and verify the deployment after it completes.
↗03Resource PlanningSize an OfficeDocs deployment: application node requirements, middleware baselines and object storage planning for single-node and clustered installs.
↗04Single-Node Kubernetes DeploymentDeploy an integrated single-node OfficeDocs Suite environment on Kubernetes, and retain the acceptance materials your audit or handover will ask for.
↗Infrastructure and middleware
01OfficeDocs Suite Deployment and OperationsPlan, install, configure, operate and troubleshoot a private OfficeDocs Suite deployment, from system requirements through to incident response.
↗02System RequirementsSupported server resources, network access and deployment prerequisites for installing OfficeDocs Suite in your own private cloud infrastructure.
↗03Deployment with Dameng V8After configuration, the installer will check database login, network connectivity, and table creation permissions.
↗04Dameng V8 RequirementsPlan a Dameng DM8 deployment for OfficeDocs Suite: the server specification, operating system, parameter and network requirements the database must meet.
↗05Deploying with KafkaAfter the configuration is complete, the installer will check Kafka's network connectivity and permissions for creating topics.
↗06Kafka ConfigurationComplete the Kafka integration for a self-hosted OfficeDocs Suite deployment: the ports, topics and connection settings the message queue has to expose.
↗07Deploying with MongoDBOnce the configuration is complete, the installer will check the MongoDB network connection, connection, and authentication permissions.
↗08MongoDB ConfigurationFinish connecting OfficeDocs Suite to an external MongoDB: the network access, credentials and document database settings the deployment expects.
↗09Deployment with MySQL 8Prepare and connect MySQL 8 as the relational dependency for a self-hosted OfficeDocs Suite deployment, including requirements and connection settings.
↗010MySQL 8 RequirementsSupport master-slave high availability switching Character set: utf8mb4 Time zone: Asia/Shanghai or UTC Connections: maxconnections ≥ 1000 Connection user:...
↗011Deploying with Object StorageSet up object storage for OfficeDocs Suite document files, including bucket configuration, credentials and how the deployment consumes the endpoint.
↗012Object Storage ConfigurationOnly object storage fully compatible with the S3 protocol is supported. Huawei Cloud OBS, Alibaba Cloud OSS, Tencent Cloud COS, and AWS S3 are recommended.
↗013Deploying with RedisConfigure Redis for an OfficeDocs Suite deployment: the caching layer the collaboration services depend on, and how to wire it into the installer.
↗014Redis ConfigurationOfficeDocs uses external Redis, which is usually applied in core scenarios such as session management, distributed locks, rate-limiting counters, and...
↗Operations platform
01Operations Platform OverviewMap the OfficeDocs operations platform: suite administration for licences, tenants, users, brands and AI, plus the system services used in day-to-day ops.
↗02AI ConfigurationConfigure the AI capability inside a self-hosted OfficeDocs Suite deployment, including the model endpoint your organisation has approved.
↗03Brand CustomizationBrand customization is used to unify the brand identity and interface style of OfficeDocs Suite.
↗04License ManagementLicense management is used to obtain the server machine code for OfficeDocs Suite, create and issue licenses, and view the current license status, license...
↗05Tenant ManagementManage tenants in the OfficeDocs Suite operations platform: review system-wide totals and adjust the organisational boundaries each tenant operates within.
↗06Suite User ManagementUser management is used to view users in each tenant of OfficeDocs Suite and to enable or disable user accounts in bulk.
↗07Editor ConfigurationYou can follow the steps in this document to locate configuration items, modify feature switches or quotas, verify whether they take effect, and restore the...
↗08System ConfigurationConfigure system-wide settings in the OfficeDocs Suite operations platform, for administrators and implementers setting the platform up for the first time.
↗09Collaboration BlockingWhen Kafka experiences a backlog, and it is confirmed that the abnormal backlog is caused by a certain file, you can use this disable feature to prohibit...
↗010Document RepairSymptoms of file corruption include documents failing to open properly, error pop-ups during loading, and inability to display content.
↗011File Information SearchFile information query is used to search for basic records of files in the system based on internal file GUID or client-side file ID, making it easy to...
↗012Transcoding Event SearchThe transcoding event query function is used to quickly view recent transcoding events on the MDP backend, helping to locate and troubleshoot issues during...
↗013Advanced SettingsEdit the system custom pd-config as YAML from the OfficeDocs control panel, for advanced parameters and bulk configuration changes across a deployment.
↗014Notification ChannelsNotification channels are used to centrally manage how system alert messages are received, allowing middleware checks and other features to send failure and...
↗015gRPC ToolUse the gRPC tool in the OfficeDocs operations platform to inspect services across three target modes, from selecting an endpoint to reading the response.
↗016Kafka ToolThe Kafka tool allows users to view the cluster status, topics, messages, consumer groups, and partition information in Kafka through the Redpanda console.
↗017MongoDB ToolsMongoDB is used to view MongoDB databases, collections, and document contents in the operations platform.
↗018RDB ToolQuery relational databases from the OfficeDocs operations platform: open a connection, pick a table, run SQL and read the result set without leaving the console.
↗019Redis ToolInspect Redis from the OfficeDocs operations platform: search keys on the left, then read the value, type and TTL of the selected key on the right.
↗020Cluster ManagementThe cluster management module is a console used for operating the Kubernetes cluster of the MDP and customer interface platform, targeting three scenarios:...
↗021Configuration CenterView and modify application configuration for each OfficeDocs service, comparing the factory template against the values your deployment is running.
↗022Middleware ConfigurationMiddleware Configuration is a page in the MDP Operations Platform used to integrate with various storage and middleware in the client environment,...
↗023Real-Time LogsStream service logs from across the Kubernetes cluster to locate OfficeDocs service anomalies, failed requests and slow dependencies as they happen.
↗024Service LogsThe service logs feature is a Kibana-like log retrieval platform that can collect logs from various Pods and provides log search, query, and ratio analysis...
↗025System UpgradeUpload and apply a new OfficeDocs Suite installation package, with the pre-upgrade compatibility checks the operations platform runs before it starts.
↗026Audit LogOperation logs are used to view and track user management operations in the system, helping with troubleshooting, security audits, and change tracking.
↗027Platform User ManagementSystem user management is used to maintain user accounts in the admin backend, including creating users, editing basic information, resetting passwords,...
↗028Compatibility TestingAfter clicking "Fill Content Bucket," the bucket can automatically switch to file-contents.
↗029Container Packet CaptureCapture network traffic from running Pods to diagnose OfficeDocs connection failures, request timeouts and DNS problems inside the Kubernetes cluster.
↗030General ToolsThe General Tools page includes 7 commonly used functions: JSON formatting, format conversion, JWT decoding, timestamp conversion, machine time check, QR...
↗031Middleware CheckMiddleware check is used to verify whether system dependencies MySQL, Redis, Elasticsearch, S3, MongoDB, and Kafka can connect and read/write properly,...
↗032Static Resource MonitoringStatic resource monitoring is used to check the JS and CSS resources referenced by web pages, helping you understand the access status of resources,...
↗Troubleshooting and maintenance
01Collaborative Editing IncidentInvestigate collaborative editing symptoms in OfficeDocs Suite, from edit-link failures through node pressure to the middleware dependencies behind them.
↗02Data BackupValidate backup targets and back up the databases, object storage and configuration of a self-hosted OfficeDocs Suite deployment before you need a restore.
↗03Incident Response SOPA self-hosted incident response procedure for OfficeDocs Suite: gather evidence, contain impact, trace dependencies and verify recovery end to end.
↗04Installation TroubleshootingDiagnose failed OfficeDocs Suite installations: time synchronisation, data disk paths, dependency failures and installer access problems.
↗05Monitoring Metrics ReferenceRead the key service, node and middleware signals during an OfficeDocs Suite incident, and know which metric tells you which dependency is failing.
↗