XML configuration interface and managed pages

We can use xmlaccess.sh to manipulate managed pages just as we can for other portal resources.

Project scope

When using the XML configuration interface with managed pages, processing occurs either completely within a project or completely outside a project.

When you import a published page and specify a project scope, the page is created as a draft page in the project.

Important: We cannot export a draft page and then import that page as a draft in another project.

To run the xmlaccess command from within a project, specify the project either with the project name or with the object ID of the project. The command uses the following format, depending on how you identify the project:

xmlaccess -in input_file -url http://hostname:port_number/wps/config/$project/project_name

xmlaccess -in input_file -url http://hostname:port_number/wps/config/$project/project_object_id

For example:

• xmlaccess -in Export.xml -url http://www.example.com:10039/wps/config/$project/myproject

• The following command must be entered all in one line:

  • xmlaccess -in Export.xml -url

  • http://www.example.com:10039/wps/config/$project/

  • Z6QReDeN9E86O46P9CGJMK633P8JMG6J1P8MM47MPD6MMCC63PI3IL6GPD63R46J1

AIX Linux Solaris note: You might need to precede the percent sign ($) with a backslash (\) to prevent $project from being interpreted as an environment variable. For example:

xmlaccess -in Export.xml -url http://www.example.com:10039/wps/config/\$project/myproject

Use transaction processing with xmlaccess.sh

Because managed pages are stored in the Portal Site library in Web Content Manager, each page has corresponding objects in the JCR database. Be aware of this relation when creating, updating, or deleting managed pages with xmlaccess.sh. If xmlaccess processing is interrupted, it can result in a mismatch between the page state and database state.

To ensure that page and database information for a managed page remain synchronized, use the transaction-level attribute of the request element in the XML file. For more information about using the transaction-level attribute, see XML configuration reference.

Example:

<request 
    type="update" 
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
    xsi:noNamespaceSchemaLocation="PortalConfig_8.0.0.xsd"
    transaction-level="resource">

Parent: Administer managed pages