Portal Operations

Portal operations focus on reliable login, predictable rendering, safe permissions, and quick diagnosis of template or configuration problems.

Deployment Components

A portal installation typically depends on:

• the portal application
• DMS client and session handling
• access manager for login
• portal configuration values
• portal page and box objects
• customer-specific templates
• static assets such as CSS, JavaScript, images, and logos
• optional SSO or OpenID Connect configuration

Important Configuration Areas

Common configuration values include:

Configuration	Purpose
portal_prefix	URL prefix for the portal app.
pb_root	Public root URL used for generated links.
pb_entry_page	Default entry page after login or logout.
pb_toplevel	Root object for main navigation.
pb_empty_page	Fallback page when no page ID is provided.
login_page_url	Portal login page or external login URL.
pb_anonymous_user	Technical user for anonymous access.
pb_anonymous_password	Encrypted password for the anonymous user.
pb_required_boxes	Folder or object containing required boxes.
pb_boxes_folder_name	Name of the page-specific box folder.
pb_content_folder_name	Name of the page-specific content folder.
pb_zone_mapping	Mapping from business zone names to template zones.
portal_use_sso	Enables legacy SSO redirect.
portal_sso_login_url	External SSO login URL.

The exact set of values differs per installation.

Startup Checks

After deployment or configuration changes, check:

• the portal app starts without license errors
• the configured prefix resolves
• the anonymous user can be refreshed
• the entry page exists
• the login page exists
• required template files exist
• the configured required boxes object exists
• DMS license checks pass

Runtime Checks

For functional testing, use at least these scenarios:

• open the public entry page without a session
• log in as a normal portal user
• log in as a portal administrator
• open a page with boxes
• open a page with no boxes
• open a document link
• open a protected document link without permission
• test search
• test logout
• test an expired session

Logging

Useful log messages include:

• login redirects and failed login attempts
• invalid or expired sessions
• slow box templates
• missing page or object IDs
• access denied errors
• template include errors
• DQL or SQL query errors

Slow box templates are logged when rendering takes noticeably long. This helps identify expensive queries or heavy customer-specific templates.

Performance

Portal performance usually depends on:

• number of boxes per page
• DQL and SQL queries inside boxes
• result limits
• template include depth
• document preview and content access
• session and permission lookups

Keep page boxes focused. Prefer filtered lists with explicit limits over broad queries.

Backup and Recovery

Portal configuration is split between files and DMS objects. A full recovery plan should include:

• repository and customer template files
• customer configuration files
• DMS database backup
• filestore backup
• exported portal page and box objects if available
• SSO/OIDC configuration

Release Checklist

Before releasing portal changes:

• review changed templates
• validate routes used in e-mails
• test local and SSO login if both are enabled
• check page and box ACLs
• confirm translations
• verify documents cannot be accessed by unrelated users
• check browser console for JavaScript errors
• test on a representative customer role