EJPXA: com.ibm.wps.command.xml.resources.XmlCommandMessages

EJPXA0001E

An error occurred while processing the XML configuration request.
The XML configuration request was not completed successfully, because an error occurred during processing. This is a general error message, details about the cause may be indicated in the response of the XML configuration request or in the server side log files.
Check the server side logs and the response of the XML configuration request to determine the cause of the failure. Correct the cause of the failure and retry the operation.

EJPXA0002I

XML configuration request is processed in ECHO mode.
This is an information message that provides feedback on the state of the portal system.
No action is required.

EJPXA0003I

XML configuration request is logged to {0}.
This is an information message that provides feedback on the state of the portal system.
No action is required.

EJPXA0004E

Invalid authentication header {0} for XML configuration request.
This is an error message. The portal system cannot handle this condition without failing.
Correct the request and try again.

EJPXA0006E

The authentication header is missing. Authentication is required for accessing the XML configuration interface.
This is an error message. The portal system cannot handle this condition without failing.
Correct the request and try again.

EJPXA0007E

A user with ID {0} was not found in the portal.
The user ID is unknown to the system.
Enter a valid user ID.

EJPXA0008E

The user ID {0} is ambiguous: more than one user with this ID was found in the portal.
This is an error message. The portal system cannot handle this condition without failing.
Correct the request and try again.

EJPXA0010E

User {0} is not authorized to use the XML configuration interface.
The user needs sufficient authorization to use the XML configuration interface.
Correction of the condition is required.

EJPXA0011E

Authentication for user {0} failed.
The XML configuration request was not executed, because the user could not be authenticated. This is mainly caused by a typo in user name or password, or by specifying a deleted user.
Check the user name and password used for the XML configuration request. The user name and password may have been specified for example via command line or in a properties file for configuration tasks, depending on the context in which XMLAccess was used. Identify the place were user name and password are read from, enter the correct user name and/or password, and repeat your action.

EJPXA0013E

A user or group with ID {0} could not be retrieved from the portal datastore, possibly because it does not exist.
This is an error message. The portal system cannot handle this condition without failing.
Correct the request and try again.

EJPXA0016E

Wildcard specification {0} is not allowed for {1} resources.
This is an error message. The portal system cannot handle this condition without failing.
Change the specification for this resource. If you want to export all the items you might export all items, for example by using the sample script Export.xml.

EJPXA0017E

An error occurred while retrieving all {0} resources.
This is an error message. The portal system cannot retrieve all of the resources matching the wildcard specification without failing.
Try a modified specification.

EJPXA0018E

Action {0} is not allowed in {1} mode.
This is an error message. The portal system cannot handle this condition without failing.
Enter a correct action for this configuration mode.

EJPXA0019E

Resources with a {0} action may not contain nested resource definitions.
This is an error message. The portal system cannot handle this condition without failing.
Correct the request and try again.

EJPXA0020E

Resources with a {1} action may not contain nested resources with a {0} action.
This is an error message. The portal system cannot handle this condition without failing.
Correct the request and try again.

EJPXA0023E

Wildcard elements support only the following actions: {0}.
This is an error message. The portal system cannot handle this condition without failing.
Correct the request by replacing the wildcard element with a valid identificator or use another identificator to locate the item.

EJPXA0025E

The resource was not found in the portal, either because it does not exist or because you have not specified an identifying attribute in the XML input.
The XML configuration request was not completed successfully, because a resource specified in the XMLAccess input file could not be found. The object ID or another specified identifying attribute like a unique name do not match to any of the existing resources or an identifying attribute was not specified. The portal system cannot handle this condition without failing.
Check and correct the identifying attribute of the resource in the input file used for the XMLAccess request and repeat your action. Possibilities to identify the correct object ID, unique name or other identifying attribute are for example XMLAccess exports or usage of the admin UI portlets to get an overview of resources and their identifying attributes in the system.

EJPXA0026E

An error occurred while looking up the resource.
This is an error message. The portal system cannot handle this condition without failing.
Correct the request and try again.

EJPXA0027E

The XML response could not be written.
This is an error message. The portal system cannot handle this condition without failing.
Correction of the condition is required.

EJPXA0029E

The XML request does not define a schema. The root element must contain an {0} attribute.
This is an error message. The portal system cannot handle this condition without failing.
Provide a schema definition.

EJPXA0030E

The schema {0} is not valid for an XML configuration request.
This is an error message. The portal system cannot handle this condition without failing.
Provide a valid schema. A list of valid schemas can be found in InfoCenter.

EJPXA0031E

The processing code for schema {0} cannot be loaded.
This is an error message. The portal system cannot handle this condition without failing.
Correction of the condition is required.

EJPXA0033E

An error occurred while retrieving the configuration of the resource.
This is an error message. The portal system cannot handle this condition without failing.
Correction of the condition is required.

EJPXA0034E

An error occurred while loading processing code {0} for XML tag {1}.
This is an error message. The portal system cannot handle this condition without failing.
Correction of the condition is required.

EJPXA0043E

An error occurred while creating or updating the resource.
The XML configuration request was not completed successfully, because an error occurred creating or updating a resource. This is a general error message, details about the cause may be indicated in the response of the XML configuration request or in the server side log files.
Check the server side logs and the response of the XML configuration request to determine the cause of the failure. Correct the cause of the failure and retry the operation.

EJPXA0044E

An error occurred while processing the {0} tag.
This is an error message. The portal system cannot handle this condition without failing.
Correct the request and try again. Check the portal log to get more information about this error.

EJPXA0048E

The XML parser could not be created or does not support the required features. Check that you are using the correct Xerces library.
This is an error message. The portal system cannot handle this condition without failing.
Correction of the condition is required.

EJPXA0049E

Input syntax error in line {0} column {1}: the XML input does not conform to the XML schema {2}.
The XML configuration request was not completed successfully, because it did not conform to the specified XML Schema.
Correct the XMLAccess input script to conform to the XML schema and try again. Additionaly to the specified line and column number the server side log might contain details what was not conform.

EJPXA0050E

Input syntax error: the XML input does not conform to the XML schema.
This is an error message. The portal system cannot handle this condition without failing.
Correct the request and try again.

EJPXA0051E

The XML request could not be read.
This is an error message. The portal system cannot handle this condition without failing.
Correction of the condition is required.

EJPXA0053W

The resource could not be found for deletion, possibly because it was already deleted.
This is a warning message. An abnormal condition has been detected. The portal system is able to handle this condition without failing.
Check whether the resource intended to be deleted still exists. If it still exists, check whether in the XMLAccess file the resource was specified correctly, for example by object ID or unique name.

EJPXA0056E

Value {0} is not valid for attribute {1}.
This is an error message. The portal system cannot handle this condition without failing.
Provide correct attribute values.

EJPXA0057E

Action {0} is not allowed for {1} resources.
The XML configuration request was not completed successfully, because the request specified an action for a resource that is not allowed for resources of that type in general.
Correct the request by removing the resource or by choosing a different action and try again. See the information center for details concerning the resource.

EJPXA0060W

A user or group with ID {0} could not be retrieved from the portal datastore, possibly because it does not exist. Related {1} configuration data will not be updated.
This is a warning message. A user or group specified in the input file used for the XMLAccess request could not be found. Access control related updates on a resource concerning that user or group were not executed. This can be caused by specifying users or groups that do not exist or by typing errors for existing users or groups. Although the actions related to this user or group were not executed, this does not affect the continuation of the script execution.
Correct the input file used for the XMLAccess request by either specifying existing users or groups correctly or removing the related configuration data from the input file.

EJPXA0061E

The {0} resource is required for the configuration update, but was not found in the portal.
This is an error message. The portal system cannot handle this condition without failing.
Correct the request and try again.

EJPXA0062E

An error occurred while loading a {0} resource.
This is an error message. The portal system cannot handle this condition without failing.
Correction of the condition is required.

EJPXA0064E

Invalid XML structure: {0} resources must be nested in {1} resources.
This is an error message. The portal system cannot handle this condition without failing.
Correct the request and try again.

EJPXA0066E

The resource cannot be identified uniquely. More than one resource matches the attributes given in the XML input.
This is an error message. The portal system cannot handle this condition without failing.
Correct the request and try again.

EJPXA0067E

The following configuration data is needed to create a {0} resource: {1}.
This is an error message. The input file for the XMLAccess request is invalid. The portal system cannot handle this condition without failing.
Correct the request and try again.

EJPXA0068E

The following configuration data is required for a {0} element: {1}.
This is an error message. The input file for the XMLAccess request is invalid. The portal system cannot handle this condition without failing.
Correct the request and try again.

EJPXA0071E

The shadow-parentref attribute cannot specify a different element than the parent component.
This is an error message. The portal system cannot handle this condition without failing.
Correct the request and try again.

EJPXA0086E

The {0} configuration data of {1} resources cannot be modified after the resource has been created.
This is an error message. The portal system cannot handle this condition without failing.
Correct the request and try again.

EJPXA0089E

Creation of the resource failed: The resource could not be retrieved from the portal datastore.
This is an error message. The portal system cannot handle this condition without failing.
Correction of the condition is required.

EJPXA0090W

It is not possible to modify {0} resources. Existing settings are left unchanged.
This is a warning message. An abnormal condition has been detected. The portal system is able to handle this condition without failing.
Correction of the condition is recommended.

EJPXA0091E

The servletref attribute is required to create a portlet clone. If you want to deploy a WAR file without creating clones, check that the names and IDs in your WAR file descriptor match the names and IDs specified in the XML request.
This is an error message. The portal system cannot handle this condition without failing.
Correct the request and try again.

EJPXA0106E

The URL {0} is not valid.
This is an error message. The portal system cannot handle this condition without failing.
Enter a correct URL.

EJPXA0107E

The resource for the URL {0} could not be read.
The XML configuration request was not completed successfully, because the specified URL in the XML configuration input script could not be read. This can be caused by an URL, that is invalid or not accessable from server side during script execution.
Correct the URL in the XML configuration input script and repeat the action.

EJPXA0108E

The resource for the zip file {0} could not be read.
This is an error message. The portal system cannot handle this condition without failing.
Check and correct the zip file.

EJPXA0109E

The zip file {0} was not found.
This is an error message. The portal system cannot handle this condition without failing.
Check and correct the zip file name and location.

EJPXA0112E

Parameter type {0} is only allowed for {1} resources.
This is an error message. The portal system cannot handle this condition without failing.
Correct the request and try again.

EJPXA0113E

The value for parameter {0} could not be decoded. Values of binary parameters must be in Base64 encoding.
This is an error message. The portal system cannot handle this condition without failing.
Correction of the condition is required.

EJPXA0114E

You cannot specify {0} configuration data if the {1} attribute is set to {2}.
This is an error message. The portal system cannot handle this condition without failing.
Correct the request and try again.

EJPXA0115E

You must specify {0} configuration data if the {1} attribute is set to {2}.
This is an error message. The portal system cannot handle this condition without failing.
Provide the required attributes.

EJPXA0120E

It is only possible to create {0} resources in {1} resources with the secret type userid-password.
This is an error message. The portal system cannot handle this condition without failing.
Correction of the condition is required.

EJPXA0127E

It is not possible to delete {0} configuration data of {1} resources.
This is an error message. The portal system cannot handle this condition without failing.
Correct the request and try again.

EJPXA0129E

An error occurred while retrieving the resource with object ID {0}.
This is an error message. The portal system cannot handle this condition without failing.
Correction of the condition is required.

EJPXA0139E

Error accessing authorization data for {0}.
This is an error message. The portal system cannot handle this condition without failing.
Correction of the condition is required.

EJPXA0140E

Duplicate objectid attribute {0}.
This is an error message. It can occur, when in the XMLAccess input file the same object ID is specified twice for two different resources. Also it can occur, if an object ID is specified in the XMLAccess input for a resource and another resource is referenced via a unique name attribute, and the referenced resource exists already in the portal database and has the same object ID. The portal system cannot handle this condition without failing.
Check and correct the objectid attribute in the input file used for the XMLAccess request.

EJPXA0141E

No resource could be found for object ID {0}.
The XML configuration request was not completed successfully, because a resource specified in the XMLAccess input file could not be found. The object ID or another identifying attribute like unique name specified do not match to any of the existing resources. The portal system cannot handle this condition without failing.
Check and correct the objectid attribute in the input file used for the XMLAccess request. Possibilities to identify the correct object ID are for example XMLAccess exports or usage of the admin UI portlets to get an overview of resources and their object IDs in the system.

EJPXA0142E

Unique name {0} is already used in the portal.
This is an error message. The portal system cannot handle this condition without failing.
Choose another unique name.

EJPXA0143E

Symbolic object ID {0} is not defined in the XML input. In object ID generating mode, all object IDs that are referenced in the XML input, must be defined in the same XML.
This is an error message. The portal system cannot handle this condition without failing.
Correct the request and try again.

EJPXA0144E

Object ID {0} references a {1} resource, but must refer to a {2} resource.
This is an error message. The portal system cannot handle this condition without failing.
Correct the objectid attribute.

EJPXA0145E

The value {0} is not a valid object ID.
This is an error message. The portal system cannot handle this condition without failing.
Correct the objectid attribute.

EJPXA0149E

Invalid access control specification: Resources of type {0} cannot be private.
This is an error message. The portal system cannot handle this condition without failing.
Omit the private flag.

EJPXA0150E

The resource was found, but in the wrong context. In the XML input, it is contained in {0}, but in the portal it is contained in {1}.
This is an error message. The portal system cannot handle this condition without failing.
Correct the request and try again.

EJPXA0151W

The role block configuration specified for resource {0} is invalid and has been corrected automatically.
This is a warning message. An abnormal condition has been detected. The portal system is able to handle this condition without failing.
Correction of the condition is recommended.

EJPXA0153W

System resource cannot be deleted.
This is a warning message. An abnormal condition has been detected. The portal system is able to handle this condition without failing.
Correction of the condition is recommended.

EJPXA0154W

The portlet WAR file {0} contains the resource {1}, but the resource is not defined in the XML input.
This is a warning message. An abnormal condition has been detected. The portal system is able to handle this condition without failing.
Correction of the condition is recommended.

EJPXA0155E

The schema {0} could not be loaded.
This is an error message. The portal system cannot handle this condition without failing.
Use an adequate schema definition. Valid schemas can be found in the InfoCenter.

EJPXA0156E

The XML schema or external entity {0} / {1} is not defined for the XML configuration interface. You have probably specified an invalid schema for the XML request. You cannot use external entities in the XML request.
This is an error message. The portal system cannot handle this condition without failing.
Use an adequate schema definition.

EJPXA0157E

The XML schema or DTD {0} / {1} corresponds to a previous release of WebSphere Portal. You must convert your XML script to the new format.
This is an error message. The portal system cannot handle this condition without failing.
Use an adequate schema definition.

EJPXA0158W

The configuration setting {0} is not defined. Assuming default value {1}.
This is a warning message. An abnormal condition has been detected. The portal system is able to handle this condition without failing.
Correction of the condition is recommended.

EJPXA0159W

The property file {0} contains no locale specific settings with prefix {1}.
This is a warning message. An abnormal condition has been detected. The portal system is able to handle this condition without failing.
Provide locale data information.

EJPXA0160W

Circular references between {0} resources: {1}.
This is a warning message. An abnormal condition has been detected. The portal system is able to handle this condition without failing.
Correction of the condition is recommended.

EJPXA0161W

The web module {0} could not be activated. Please see previous messages for reasons and possible corrective actions.
This is a warning message. An abnormal condition has been detected. The portal system is able to handle this condition without failing.
Please see previous messages for reasons and possible corrective actions.

EJPXA0162E

Cannot move page (objectid {0}) below its own child page (objectid {1}).
This request cannot be completed, as the child page would have no parent page after the operation.
Correct the request and try again.

EJPXA0163W

Role {0} does not exist.
This is a warning message. An abnormal condition has been detected. The portal system is able to handle this condition without failing.
Correction of the condition is recommended.

EJPXA0164W

Role {0} already exists.
This is a warning message. An abnormal condition has been detected. The portal system is able to handle this condition without failing.
Correction of the condition is recommended.

EJPXA0165E

{0} is disabled.
This is an error message. The portal system cannot handle this condition without failing.
Correction of the condition is required.

EJPXA0166E

The XML Configuration Interface is currently busy with another request. Please try again later.
This is an error message. The portal system cannot handle this condition without failing.
Please try again later.

EJPXA0177I

Command line parameters: -inNew <new release input file> -inOld <old release input file> -out <output file> [-virtualPortalMode] Output contains only virtual portal specific differences [-disableLogFile] No log file is written [-logFileLocation <log output file>] The log file is written to the specified location [-debug]
This is an information message.
Supply all required parameters.

EJPXA0178E

Error during processing.
This is an error message. The execution of the ReleaseBuilder tool failed because of an error that could not be handled.
Check the ReleaseBuilder tool log to get more information about this error.

EJPXA0179E

Could not initialize services.
This is an error message. The portal system cannot handle this condition without failing.
Correction of the condition is required.

EJPXA0180E

Could not read file.
This is an error message. The portal system cannot handle this condition without failing.
Correction of the condition is required.

EJPXA0181E

I/O error on file {0}.
This is an error message. The file name specified cannot be opened.
Correction of the condition is required.

EJPXA0182E

Incorrect XML input from release configuration specified with the {0} option.
This is an error message. Release Builder cannot process the XML document.
Correction of the condition is required.

EJPXA0183E

The URL {0} does not point to a directory as required by predeployed portlets. Please adjust the URL.
This is an error indicating that the URL that was found in the input file does not point to the right target. The target for a predeployed portlet must be a directory, not a war file.
Correct the URL.

EJPXA0184E

The URL {0} does not point to a file. Please adjust the URL.
This is an error indicating that the URL that was found in the input file does not point to the right target. The target for non-predeployed portlets must be a war file, not a directory.
Correct the URL.

EJPXA0185W

The URL {0} does not point to a directory as required by predeployed portlets. You will need to adjust the URL.
This is a warning indicating that the URL that was generated for the output file does not point to the right target. The target for a predeployed portlet must be a directory, not a war file.
Correct the URL.

EJPXA0186W

The URL {0} does not point to a file. You will need to adjust the URL.
This is a warning indicating that the URL that was generated for the output file does not point to the right target. The target for non-predeployed portlets must be a war file, not a directory.
Correct the URL.

EJPXA0187E

The resource {0} already exists.
The resource to be created with the create action already exists in the portal. Use an update action instead.
Use the update action instead of create.

EJPXA0188E

Cannot create more than one root component.
The page to be created can only have one root component.
Correct the XML input.

EJPXA0189W

Cannot create object ID for user {0}. Object ID is ignored.
The user cannot be created with the object ID specified.
None.

EJPXA0190W

Cannot create object ID for group {0}. Object ID is ignored.
The group cannot be created with the object ID specified.
None.

EJPXA0191E

Illegal combination of database domains: default is {0}, resource is {1}.
The combination of database domains specified is wrong.
Check spelling of the domains.

EJPXA0192W

Database domain cannot be resolved for {0}.
The database domain for the given resource cannot be resolved. This may indicate a consistency problem in the data sources.
Contact support.

EJPXA0193W

Using default database domain {0} for {1}.
The database domain for the given resource was not specified. The default domain is used.
If this is not intentionally, please specify the correct domain.

EJPXA0194W

The key {0} is undefined for node type {1}.
The key for for that specific node type is undefined.
Check spelling of the indicated key.

EJPXA0195W

The resource with object ID [{0}] could not be found for deletion, possibly because it was already deleted.
This is a warning message. An abnormal condition has been detected. The portal system is able to handle this condition without failing.
Correction of the condition is recommended.

EJPXA0196W

The component cannot be created, because its type is "control", but it does not contain a portlet instance.
This is a warning message. Components of type "control" must contain a portlet instance. The only exception is, if a user moves a portlet on a page. In that case a shadow component of type "control" is created. This component references the original portlet instance implicitly.
Either remove this component from the XMLAccess request or add a portlet instance definition to this component.

EJPXA0197E

The resource has to be from the domain with the identifier {0}.
The resource must be from a special domain, but another domain is specified. For example, a private resource must be of domain 'cust'.
Adapt the domain of the resource in the import file.

EJPXA0198W

The URL {0} does not point to a file. Portal tries to read the file from the default location installableApps.
This is a warning message. The file can not be read from the specified location. Portal tries to find the file in the default location 'installableApps'.
Correct the URL of the web-app item.

EJPXA0199E

The attribute {0} must contain following string {1}
This is an error message. The attribute must specified in a special format.
Adapt the content of the specified attribute with the corrected value and run the xml script again.

EJPXA0200E

Cloning for this resource {0} is not allowed.
This is an error message. Cloning is not possible for such kind of resource for example a transformation-app must not be cloned.
There is no way to clone this resource. This is as designed.

EJPXA0201E

Updating a composite application is not allowed.
The composite application item can not be updated. Please delete the item first.
Please delete the item first.

EJPXA0202W

The user with the userid {0} could not be found. The resource {1} will be not created.
The user was not found in your user repository. The creation of the resource is skipped.
Create the user or remove the current resource from the input file.

EJPXA0203W

The XML configuration interface assumes that you want to create a clone. {0} is replaced by {1} so that it conforms to the required XML syntax.
If you want to create a clone, the XML script must conform to a special syntax. See the XML configuration interface sample file ClonePortlet.xml provided in the Information Center or in the installation.
If you want to create a clone, the XML script must conform to a special syntax. See the XML configuration interface sample file ClonePortlet.xml provided in the Information Center or in the installation.If you do not want to create a clone, delete the clone that was just created by the XML configuration interface. Check the XML sample file DeployPortlet.xml for the correct syntax for the deployment step.

EJPXA0204W

XML input contains redundant elements. An update action for the {0} element with objectID {1} (and parent element with objectID {2}) was not processed, because a resource with the same objectID exists already in database domain {3}.
This is a warning message. The redundant element can be removed from the input.
None.

EJPXA0205E

The authentication level for the resource {0} could not be retrieved
This is an error message. The portal system cannot handle this condition without failing.
Correction of the condition is required.

EJPXA0206E

The authentication level {0} for the resource {1} could not be stored
This is an error message. The portal system cannot handle this condition without failing.
Correction of the condition is required.

EJPXA0207W

The authentication level for resource {0} could not be stored because the StepUp function is disabled.
The StepUp function has been disabled on this server. The used XML input does include configuration changes for the StepUp feature which are ignored.
Check the provided xml input file for old auth-level-name entries or enable StepUp.

EJPXA0208W

The resource {0} is not valid for the assignment of authentication levels.
Authentication level are only applicable to CONTENT_NODE and PORTLET_DEFINITION.
Check the provided xml input file for wrong assignments.

EJPXA0209E

The corresponding URL specification was not found for defaultbinding ''{0}'' for porttype ''{1}''.
This error indicates a missing URL specification for the given defaultbinding attribute for the porttype.
Correct either the defaultbinding attribute, or provide the missing secure (respectively insecure) URL specification.

EJPXA0210E

Syntax contraints when using transformationinstances in content-node {0}.
Two transformationinstance items below the same content-node are only possible, if one has the action attribute with value 'delete', and the other one has action 'update'.
Correct the provided xml input file.

EJPXA0211E

The WSRP proxy portlet application was not found.
The WSRP proxy portlet application is required when remote portlets are integrated.
Deploy the WSRP proxy portlet application.

EJPXA0212W

The XML input for web application ''{0}'' has a different display-name ''{1}'' than the already stored version ''{2}''.
It is not allowed to change the display-name of an already installed web application.
Either remove the display-name element from the import document for the concerned web-app or assign it the same name as returned by an xml export of this web application.

EJPXA0213E

The value for static page contents could not be decoded. Values of binary content must be in Base64 encoding.
This is an error message. The portal system cannot handle this condition without failing.
Correction of the condition is required.

EJPXA0214E

The specification of a registration handle and registration properties for a new WSRP producer to create is not possible.
This is an error message. The portal system cannot handle this condition without failing.
Specify either a registration handle or registration properties, but not both.

EJPXA0215E

The servlet {0} in the XML input does not exist in the enclosing web module.
This is an error message. The portal system cannot locate the servlet {0} in the enclosing web module.
Compare the name or referenceid of servlet {0} from the XML input with the settings of the corresponding portlet.xml.

EJPXA0216W

Web Module {0} contains {1} applications. Only 1 is expected.
The specified web module contains multiple applications. Only the first application is installed or updated. Other applications that are contained in the web module will be ignored.
n.a

EJPXA0217W

Web Module {0} is a standard module. Its applications cannot be deleted.
The XML command to delete a web module is ignored, as it references a standard web module.
n/a.

EJPXA0218E

No markup was defined for the static content page.
The content page that was defined in the XML input did not specify any markup, which is not allowed.
Correct the XML input.

EJPXA0219E

No content was defined for the static content page.
The content page that was defined in the XML input did not specify any content, which is not allowed.
Correct the XML input.

EJPXA0220E

The transaction failed for the following reason: {0}
The transaction specified by the transaction-level attribute failed
Increase the transaction timeout

EJPXA0221W

The locale information for {0} of resource {1} is ignored because the mandatory attribute or subtag {2} is missing.
The locale information for one language of the resource was not created or updated, because a mandatory attribute or subtag was not specified in the XML input.
Correct the XML input.

EJPXA0222W

The URL {0} does not point to a file. Portal tries to read the file from the alternative location {1}.
This is a warning message. The file can not be read from the specified location. Portal tries to find the file at the alternative location.
Correct the URL.

EJPXA0223E

The tag <{0}> is not supported by ReleaseBuilder and may have been introduced after the export via ExportRelease.
ReleaseBuilder processed a tag that is not supported.
ReleaseBuilder only supports the subset of tags exported via ExportRelease. Ensure that the input is restricted to this subset.

EJPXA0224E

The value {0} is not valid for the attribute {1}.
The value specified for the attribute is not a valid value.
Correct the XML input using a valid value for the attribute.

EJPXA0225E

The tag {0} specifies with attribute value {1} an URI for a portal system resource, that cannot be found in the portal system.
The value specified for the attribute needs to specify an URI pointing to an existing portal system resource.
Correct the XML input by either removing the tag or by specifying an URI pointing to an existing portal system resource.

EJPXA0226E

The tag {0} specifies with attribute value {1} an URI for a portal system resource, that is located in an invalid database domain. For resources to create in database domain {2} URIs are valid for resources located in one of the following database domains {3}.
The database domain in which a resource is created determines the database domains in which resources referenced via the URI can be located in.
Correct the XML input by either removing the tag or by specifying an URI pointing to a resource located in one of the listed database domains.

EJPXA0227E

Incorrect Release Builder usage. The command line parameter {0} was specified without a required filename.
Release Builder was executed with an incorrect usage syntax.
Adjust the command to execute Release Builder by specifying the missing filename and repeat your action.

EJPXA0228E

Incorrect Release Builder usage. The command line parameter {0} is not valid.
Release Builder was executed with an incorrect usage syntax.
Adjust the command to execute Release Builder by removing the invalid parameter and repeat your action.

EJPXA0229E

A request attempt was made to a virtual portal (URL mapping ''{0}''), which does not exist.
The connection URL for the XML configuration request is incorrect. A virtual portal was addressed, which does not exist on this portal installation.
Revise the connection URL, which is specified after the '-url' command line option.

EJPXA0230W

A root folder already exists {0}. Only one root folder is allowed. The folder specified in the input xml script is ignored.
The tag in the XMLAccess script is ignored because a root folder already exists. This can happen when the community domain is shared, it is tried to create a root folder although one already exists, or the folder to create was unintentionally specified as root folder.
Review your XMLAccess input script and either remove or correct the folder element and repeat your action.

EJPXA0231I

Release Builder logs are written to {0}.
This is an information message. The logs for Release Builder are written into the specified location and can be checked in case of an error.
This is an information message. No user action is required.

EJPXA0232E

The attribute {0} is required for {1} tags if the specified action is {2}.
The XML configuration request was not completed successfully, because the request specified an action for a resource but did not provide all attributes required to execute the action.
Correct the request by adding the required attribute or by removing the failing tag and repeat your action. See the information center for details concerning the resource.

EJPXA0233W

The attribute value {0} for attribute {1} of tag {2} of resource {3} contains leading or trailing whitespaces.
This is a warning message. An abnormal condition has been detected. The portal system is able to handle this condition without failing. The XML configuration request specified an attribute value for the specified tag of the specified resource, that has leading or trailing whitespaces. The leading or trailing whitespaces may have been specified unintentionally.
Check the attribute value and if it was specified unintenionally, correct the request by removing leading or trailing whitespaces for the specified attribute value and repeat your action.

EJPXA0234E

Tags {0} with attribute value {1} for attribute {2} of resource {3} were specified multiple times, but can be specified at most once.
This is an error message. The portal system cannot handle this condition without failing. Several tags were specified with the same identifying information, and only one can be stored in the backend.
Correct the request by specifying only one tag with the specified attribute name value pair and repeat your action.

EJPXA0235W

The XMLAccess input script is specified according to the deprecated schema {0}. A recommended schema for XMLAccess requests is {1}.
This is an warning message. The portal system can handle this condition without failing. The XMLAccess input script is specified according to a deprecated schema. This warning can be avoided if the XMLAccess requests are specified according a non deprecated schema, for example, the schema recommended in the warning message.
This is an warning message. No user action is required. This warning can be avoided if the XMLAccess requests are specified according a non deprecated schema, for example, the schema recommended in the warning message.

EJPXA0236W

The {0} configuration data of {1} resources cannot be modified after the resource has been created.
This is a warning message. The portal system can handle this condition without failing. The update will be ignored.
This is a warning message. No user action is required. This warning can be avoided if the XMLAccess request only specifies update statements with which updatable data is handeled only.

EJPXA0237E

Page content for the markup {0} of static page {1} has been defined, but the required parameter {2} is missing in the content metadata.
This is an error message. The portal system cannot handle this condition without failing. The static page contains content for a certain markup, but the required parameter "com.ibm.portal.static.page.file.name.(markup)" is missing in the page metadata section. The parameter value must be the name of a file that is included in the static page content.
Correct the request by specifying a valid and repeat your action. Provide a parameter named "com.ibm.portal.static.page.file.name.(markup)" for the missing markup. This parameter must denote the file in the static content data, which contains the static page content for this markup. Then repeat your action.

EJPXA0238W

The internal URL {0} does not contain a valid object ID reference for the markup {1}.
This is a warning message. A content node of the type "internal-url" contains no reference object for at least one markup. The internal URL link is created, but the link will not be usable.
Check and correct the value of the <supported-markup> tag in the input file used for the XMLAccess request.

EJPXA0239W

The content-id attribute {0} of a system content mapping was ignored.
This is a warning message. The content-id attribute of a system content mapping for a content node was ignored, because the <request> tag of the script enabled the object id creation mode, in setting create-oids="true". The system content mapping has been successfully created, but the content id value has been determined by the system.
This is a warning message. No user action is required. To avoid this warning, remove the content-id attribute from the script.

EJPXA0240E

The resource {0} was not found in the portal, either because it does not exist or because you have not specified an identifying attribute in the XML input.
The XML configuration request was not completed successfully, because a resource specified in the XMLAccess input file could not be found. The object ID or another specified identifying attribute like a unique name do not match to any of the existing resources or an identifying attribute was not specified. The portal system cannot handle this condition without failing.
Check and correct the identifying attribute of the resource in the input file used for the XMLAccess request and repeat your action. Possibilities to identify the correct object ID, unique name or other identifying attribute are for example XMLAccess exports or usage of the admin UI portlets to get an overview of resources and their identifying attributes in the system.

EJPXA0241I

The tag {0} is no more supported in this version of WebSphere Portal. The tag is ignored.
This is an informational message. The specified xml tag is no more supported in this version of WebSphere Portal. The action is ignored.
No user action is required. To avoid this warning, remove the specified tag from the script.

EJPXA0242W

The RoleType {0} is not applicable for resource {1}. Requested change will be ignored
A RoleType provided for a Resource is not or no longer applicable. The modification will be skipped.
This is a warning message. Please check your XML input if there had been a potential typo. If there has been the Delegator RoleType been assigned to Content Nodes you do not need to perform a step as this combination is no longer valid

EJPXA0243E

Portlet instance {0} does not support the specified action {1}.
A property broker action has been referenced by an actionref attribute of a <global-settings> definition of a portlet instance, which is not supported by the portlet.
Correct the actionref attribute in the failing <global-settings> definition.

EJPXA0244E

The referenced resource {0} could not be found in the system.
The XML configuration request is referencing a resource that could not be found in the system.
Correct the XML input or make sure the referenced resource is deployed.