+

Search Tips   |   Advanced Search

Changes to xmlaccess.sh for this version of WebSphere Portal

Learn about the changes that were made to the XML configuration interface from earlier versions to current versions of IBM WebSphere Portal. This information can be useful to you if you migrate the WebSphere Portal from one version to a later version.


Changed XML schema

The XML schema is updated for new versions of WebSphere Portal as required. Make sure the XML scripts specify the correct version of the XML schema according to the version of the portal installation. For example, for portal v8.5 specify the current version of the XML schema as follows: 

   <?xml version="1.0" encoding="UTF-8"?>
   <request
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:noNamespaceSchemaLocation="PortalConfig_8.5.0.xsd"
    type="export | update">
     . . . configuration . . .
   </request>

The different versions of WebSphere Portal use the following syntax definitions for xmlaccess.sh:

WebSphere Portal Version XML schema
v7.0.0 7.0.0
v7.0.0.2 7.0.0_2
v8.0.0 8.0.0
v8.5 8.5.0

  1. Backward compatibility: The later XML schemas are backward compatible with earlier supported versions of WebSphere Portal. We can run XML scripts from earlier portal versions that IBM supports under a later version of the portal. For example, we can run an XML script based on the PortalConfig_7.0.0.xsd under portal v8.5. In such cases a warning message is written to the output script, which informs that a previous version of the XML schema was used.

  2. Schema file naming convention: If the XML schema is enhanced by updates, a new version of the xsd file with a new file name is created according to the following naming convention:

    • Start with portal V 6.0.1 the schema file name includes the portal version number as follows: PortalConfig_portal_version_number.xsd. Example: PortalConfig_7.0.0.xsd.

    • If the schema is enhanced during a portal version, the name includes additional ID information to ensure unique schema file names: PortalConfig_portal_version_number_id.xsd. Example: PortalConfig_7.0.0_2.xsd.


New XML resources in WebSphere Portal v8.5

In WebSphere Portal v8.5 the following new resource tags have been introduced:

New XML configuration interface tags in portal v8.5 Tag specifies the following type of portal resource
device-class a device class
global-target-settings a section containing the cross-page wire settings set as global targets
target a global target
For more details about this tag refer to the XML configuration interface reference.


New XML attributes in WebSphere Portal v8.5

This section lists the attributes that have been added to WebSphere Portal for v8.5.

  • A new boolean flag system has been introduced for content-mapping tags.

  • We can now set parameter sections for task nodes.

  • A new attribute target-portletdefinitionref has been introduced on cross-page-wire items,


Removed XML resources in WebSphere Portal v8.5

The following XML resource is no longer supported in portal v8.5:

  • event-handler


Set the project scope in WebSphere Portal v8.5

The managed pages feature enables us to edit portal resources, such as pages, in the scope of a project. By working in a project, we can create, update, and approve pages in a draft state, without affecting the live server. We can specify a project scope for actions performed with xmlaccess.sh command by including the object ID of the project in the URL. See XML configuration interface and managed pages for details.


Parent xmlaccess.sh

Related reference:

XML configuration interface and managed pages