About the XML configuration interface

About the XML configuration interface

+
Search Tips | Advanced Search

Overview

The XML configuration interface (xmlaccess) allows you to...

Export an entire portal configuration or parts of a configuration, for example specific pages, to an XML file
Re-create the exported configuration from such a file on another portal

The XML configuration interface command line client connects to the server using an HTTP or HTTPS connection. It is therefore possible to configure the portal remotely.

Limitations

A complete XML export of a portal configuration is not sufficient to re-create the portal. You also need...

WAR files for your portlets
Any additional file resources, such as theme files, if they are not part of the standard portal installation

The XML configuration interface is not designed to deal efficiently with large volumes of data. For a backup and restore solution on a production server you should rely on low-level database and file system backups.

Access and security considerations

To use the XML configuration interface, have the...

manager role on the virtual resource XML_ACCESS
security administrator role on the virtual resource PORTAL.

Basically you need to be a super administrator who can perform any action.
When you use an HTTP connection, the user and password are sent to the server unencrypted, therefore you should only connect to the XML configuration interface from inside a protected intranet where you can be sure that the HTTP connection is not compromised. In all other networks configure SSL and use a secure HTTPS connection to connect to the XML configuration interface.

Overall structure of the XML input and output

There are two main types of requests that can be sent to the XML configuration interface:

Export requests

Export complete or partial portal configurations into XML. Does not modify the configuration of the portal. Results in a response file.

Update requests

Modify the configuration of a portal according to the values found in the XML script.
the

A third request type is available for preparing the deletion of orphaned data:

export-orphaned-data requests

Export the complete portal configuration into XML, including orphaned data. Results in a response file.

Requests to and responses from the XML configuration interface use the same XML format. An export request generates an XML response that contains all the configuration data required to re-create the exported configuration part. This means that you can...

export a portal configuration
save the XML output file
send it to another portal to re-create the same configuration there

Use the XML schema for the XML format that WebSphere Portal provides for reference, located in...
portal_server_root/base/wp.xml/shared/app/wp.xml.jar

Unpack the JAR file and you will find the file with the XML schema under the path com/ibm/wps/command/xml/PortalConfig_1.4.xsd.
An XML request contains the following:

Mandatory portal section that describes the parts of the portal configuration to be exported or updated
Optional status section that indicates the success or failure of the requested operation. During the import of configuration data the XML processing ignores this section of the XML input file.

Representation of a portal configuration in XML

The XML hierarchy that is found under the portal section in the XML request file represents the structure of a portal as an XML tree. This tree contains resources in the portal, such as portlets or pages, and their configuration data. The XML hierarchy of all supported portal resources is shown in the following table:

XML element Description
portal Main element of every XML request
global-settings Global portal settings
services-settings Global portal settings for portal services
language Languages that are defined in portal
action Actions that can be used to create action sets
virtual-resource Virtual resources that have associated access control settings
user Users defined in the portal user management system
group Groups defined in the portal user management system
markup Markups that can be supported by portal pages
client Client devices (browsers) that the portal knows about
event-handler Definitions of event handlers that can react to events in the portal
skin Visual appearance settings that can be applied to user interface elements
theme General visual settings that can be applied to the user interface
wsrp-producer Producer of Web services as defined in the consumer portal
wsdl-url The URL to the Producer's WSDL document
service-description-url The URL to the Producer's service description
markup-url The Producer's markup URL
registration-url The Producer's registration URL
portlet-mgt-url The Producer's portlet management URL
portlet-app Portlet applications that are defined in the remote Web module
portlet Portlets that are defined in the remote portlet application
web-app Web modules containing portlets
url The WAR file that contains the Web application
context-root The context root that is assigned to the Web application of the portlet application in the predeployed EAR file (reference: application.xml)
display-name The name that is assigned to the application in the predeployed EAR file (reference: application.xml)
servlet Servlets that are defined in the Web module
portlet-app Portlet applications that are defined in the Web module
portlet Portlets that are defined in the portlet application
content-node Elements of the portal content tree (pages or labels)
supported-markup The markups that are supported by this content node
allowed-portlet The portlets that are allowed on this page
component Layout components of pages
component Subcomponents in the structure of the page
portletinstance Occurrences of a portlet on a page with customized settings
cross-page-wire Property broker wiring between two portlet instances.
The wire tag is deprecated with WebSphere Portal V6.1, as it supports property broker wiring between two portlets on the same page only.
Use the cross-page-wire tag as it supports property broker wiring between portlets on the same page and on different pages.
credential-segment Segments for storing credentials in the credential vault
credential-slot Slots in a credential segment that hold a credential
url-mapping-context User defined URLs that map to pages in the portal
user-resource Export and delete a specific user resources.
policy-node Policies that are defined in the portal
application-role Application role is a named set of authorization roles that can be assigned to users or groups.

Depending on the content of an XML request, these resources can be created, modified, deleted or exported. An XML request can contain any number of such resource definitions. It can therefore create hundreds of new resources in one step or modify only a single configuration setting of one existing resource.

Parent topic
The XML configuration interface

Related concepts
Portal administration tools

Related tasks
Set up SSL
Delete orphaned data

Related reference
Changes to the XML configuration interface for this version of portal
XML configuration reference
Sample XML configuration files

Related information
Work with the XML configuration interface

XML element	Description
portal	Main element of every XML request
global-settings	Global portal settings
services-settings	Global portal settings for portal services
language	Languages that are defined in portal
action	Actions that can be used to create action sets
virtual-resource	Virtual resources that have associated access control settings
user	Users defined in the portal user management system
group	Groups defined in the portal user management system
markup	Markups that can be supported by portal pages
client	Client devices (browsers) that the portal knows about
event-handler	Definitions of event handlers that can react to events in the portal
skin	Visual appearance settings that can be applied to user interface elements
theme	General visual settings that can be applied to the user interface
wsrp-producer	Producer of Web services as defined in the consumer portal
wsdl-url	The URL to the Producer's WSDL document
service-description-url	The URL to the Producer's service description
markup-url	The Producer's markup URL
registration-url	The Producer's registration URL
portlet-mgt-url	The Producer's portlet management URL
portlet-app	Portlet applications that are defined in the remote Web module
portlet	Portlets that are defined in the remote portlet application
web-app	Web modules containing portlets
url	The WAR file that contains the Web application
context-root	The context root that is assigned to the Web application of the portlet application in the predeployed EAR file (reference: application.xml)
display-name	The name that is assigned to the application in the predeployed EAR file (reference: application.xml)
servlet	Servlets that are defined in the Web module
portlet-app	Portlet applications that are defined in the Web module
portlet	Portlets that are defined in the portlet application
content-node	Elements of the portal content tree (pages or labels)
supported-markup	The markups that are supported by this content node
allowed-portlet	The portlets that are allowed on this page
component	Layout components of pages
component	Subcomponents in the structure of the page
portletinstance	Occurrences of a portlet on a page with customized settings
cross-page-wire	Property broker wiring between two portlet instances. The wire tag is deprecated with WebSphere Portal V6.1, as it supports property broker wiring between two portlets on the same page only. Use the cross-page-wire tag as it supports property broker wiring between portlets on the same page and on different pages.
credential-segment	Segments for storing credentials in the credential vault
credential-slot	Slots in a credential segment that hold a credential
url-mapping-context	User defined URLs that map to pages in the portal
user-resource	Export and delete a specific user resources.
policy-node	Policies that are defined in the portal
application-role	Application role is a named set of authorization roles that can be assigned to users or groups.