Portal administration tools
Portal admin tools include:
The ReleaseBuilder uses xmlaccess.sh for staging purposes. For example, move a portal configuration from a test system to a production system. The portal provides several administration tools for limited purposes, documented in the context where they can be used. For example, SLCheckerTool, used to delete orphaned data.
Security considerations
A master administrator can delegate work to subadministrators. For example, the master administrator can delegate the responsibility and rights for different administrative tasks to different departments in the same business.
Access permissions are implemented as user rights on actions related to portal resources, not on the resources themselves.
Administration portlets
Tasks:
- Configure individual portal resources.
- Configure individual portal resources, together with their dependent resources. For example, derived pages.
- Give subadministrators limited access rights on selected portal resources.
- Deploy custom developed artifacts, such as portlets, themes, or skins.
xmlaccess.sh
Batch processing interface for portal configuration updates, allowing us to export an entire portal configuration or parts of a configuration to an XML file. We can then re-create the exported configuration from such a file on another portal. xmlaccess.sh connects to the server using an HTTP connection, so we can use it remotely.
xmlaccess.sh users do not need access permission for the portal resources processed by the XML request. They only need the access permission for the virtual resource XML_ACCESS. Access rights are not required for the portal resources updated by the XML configuration interface.
Use xmlaccess.sh for the following tasks:
- Transfer or migration between workstations
- Back up of the portal configuration
- Overview of the portal configuration.
- Cloning of a portal. Use the object ID generation mode.
- Copy parts of a configuration, such as specific pages, from one portal to another.
- Transfer portal configurations from one installation to another.
- Create a portal configuration file by XML export.
- Install extra resources on a portal.
- Complete recurring administration tasks in an automated and reproducible manner.
Use is limited for:
- Delegating administrative tasks.
- Limiting administrative tasks to a particular user or to particular portal resources.
The XML configuration interface is also used for release staging. See ReleaseBuilder.
Portal Scripting Interface
Command-line tool that delegates administration in the same manner as the administration portlets. Access permissions on portal resources are required. Portal Scripting Interface allows implicit derivation during administrative work. When a portal resource is modified, the Portal Scripting Interface creates the derivations of that resource in the same process. The Portal scripting interface offers only a subset of the functionality of the portal administration portlets.Tasks we can perform...
- Make fine-tuned changes to a portal configuration.
- Transfer configuration updates without disturbing the production portal:
- Create configuration updates for the portal, and the script for running these updates.
- A test team tests the script and the configuration.
- After approval, script and configuration are uploaded to production portal.
- An operator team processes the scripts that update the production portal.
See
Parent AdministeringRelated concepts:
ReleaseBuilder
Configuration Wizard
Updates using ReleaseBuilder
Related information
Technotes for administration tools