BPEL Admin Exceptions ORABPEL 00200 - 00234

BPEL Admin Exceptions ORABPEL 00200 - 00234
Admin Exceptions 00200 - 00234

ORABPEL-00200
severity: 10
type: error
name: SOAP server URL not specified
description: The SOAP server URL for the OraBPEL server has not been specified in the configuration file \"{0}\".

ORABPEL-00201
severity: 10
type: error
name: Caller not permitted
description: Cannot return system authentication token for caller \"{0}\".

ORABPEL-00202
severity: 10
type: error
name: Invalid domain id
description: The domain identifier \"{0}\" is not valid. Domain identifiers may start with a letter, a \"$\" or \"_\" character; domain characters (other than the first character) include a letter, a digit, a \"$\", a \"_\" or \"-\" character. Additionally, the domain identifier \"xmllib\" may not be used; this identifier is reserved.

ORABPEL-00203
severity: 10
type: error
name: Invalid domain directory
description: The domain directory \"{0}\" does not match the domain identifier \"{1}\" retrieved from the configuration files. The domain directory name must match the domain identifier.

ORABPEL-00204
severity: 10
type: error
name: Missing domain id
description: The domain descriptor at \"{0}\" does not contain a domain identifier (attribute \"id\"). The domain derives its id from the descriptor, not the directory name.

ORABPEL-00205
severity: 10
type: error
name: Domain already exists
description: A domain with identifier \"{0}\" already exists at \"{1}\". Please specify another domain identifier.

ORABPEL-00206
severity: 10
type: error
name: Domain creation error
description: An exception occurred while attempting to create the domain \"{0}\" at path \"{1} \". The exception reported is: {2}

ORABPEL-00207
severity: 10
type: error
name: Domain create directory error
description: An exception occurred while attempting to create the domain directory \"{1}\" for domain \"{0}\". Please check that the directory does not already exist.

ORABPEL-00208
severity: 10
type: error
name: Maximum number of domains exceeded
description: Failed to create the domain \"{0}\"; the maximum number of domains ({1}) has been reached.

ORABPEL-00209
severity: 10
type: error
name: Domain id not found
description: The domain identifier \"{0}\" has not been registered with the server.

ORABPEL-00210
severity: 10
type: error
name: Domain ref not found
description: The domain ref \"{0}\" has not been registered with the server.

ORABPEL-00211
severity: 10
type: error
name: Error reading domain index
description: An exception occurred while reading the domain index from the datastore; the exception reported is: {0}
fix: Please check that: the machine hosting the datasource is physically connected to the network, and the connection pool properties as defined in the application server startup properties are valid. and the database schema for the OraBPEL server has been installed in the datasource.

ORABPEL-00212
severity: 10
type: error
name: Error updating domain index
description: An exception occurred while writing the domain index (id\"{0}\", ref \"{1}\") to the datastore; the exception reported is: {2}
fix: Please check that:
+ the machine hosting the datasource is physically connected to the network.
+ the connection pool properties as defined in the application server startup properties are valid.
+ the database schema for the OraBPEL server has been installed in the datasource.

ORABPEL-00213
severity: 10
type: error
name: Error writing domain index
description: An exception occurred while removing the domain index (id \"{0}\", ref \"{1}\") from the datastore; the exception reported is: {2}
fix: Please check that:
+ the machine hosting the datasource is physically connected to the network.
+ the connection pool properties as defined in the application server startup properties are valid.
+ the database schema for the OraBPEL server has been installed in the datasource.

ORABPEL-00214
severity: 10
type: error
name: OraBPEL server not initialized
description: The OraBPEL server has not finished initializing yet; the initialization process may be complete in a few moments.

ORABPEL-00215
severity: 10
type: error
name: Error while creating JDK adaptor
description: An error occurred while attempting to instantiate the JDK adaptor class \"{0}\" for runtime version \"{1}\". The exception reported was: {2}.
fix: Please check the implementation of your JDK adaptor and redeploy the class to the server.

ORABPEL-00216
severity: 10
type: error
name: JDK adaptor class incorrect interface
description: The JDK adaptor class \"{0}\" for runtime version \"{1}\" does not implement the IJDKAdaptor interface. All JDK adaptors must implement this interface.

ORABPEL-00217
severity: 10
type: error
name: JDK version not supported
description: The JDK version \"{0}\" is not supported by the OraBPEL domain runtime. Currently only JDK version 1.4 is supported.

ORABPEL-00218
severity: 10
type: error
name: Wrong Xalan version
description: An unsupported version of the Xalan library was detected in your classpath. The JDK 1.4.1 rt.jar currently bundles the 2.2D11 beta version of Xalan; OraBPEL requires the 2.5.0 release version.
fix: There are several ways to use a later version of Xalan-Java and override the one packaged with the JDK: For the SUN JDK 1.4, use the Endorsed Standards Override Mechanism. Place the xalan.jar, xercesImpl.jar, and xml-apis.jar in the JAVA_HOME/lib/endorsed directory, where JAVA_HOME is where the runtime software is installed. Use the -Xbootclasspath java commandline option to prepend the new xalan.jar, xercesImpl.jar, and xml-apis.jar to the boot class path. When running Xalan-Java: java -Xbootclasspath/p:PATH org.apache.xalan.xslt.Process where PATH is a colon seperated lists of the paths to the files xalan.jar, xercesImpl.jar, and xml-apis.jar (e.g. bin/xalan.jar:bin/xercesImpl.jar:bin/xml-apis.jar) containing the new-version of Xalan- Java.

ORABPEL-00219
severity: 10
type: error
name: Cannot instantiate class
description: Cannot instantiate an instance for the class \"{0}\". Please check that the OraBPEL runtime class \"{1}\" has been granted the necessary security permissions to access the specified class.

ORABPEL-00220
severity: 10
type: error
name: Wrong platform adaptor interface
description: The class \"{0}\" (for the platform adaptor for platform \"{1}\") does not implement the IPlatformAdaptor interface. All platform adaptors used by the OraBPEL server must implement this interface.

ORABPEL-00221
severity: 10
type: error
name: Error while creating platform adaptor
description: An error has occurred while attempting to instantiate the class \"{0}\" as the adaptor for platform \"{1}\". The exception reported is: {2}

ORABPEL-00222
severity: 10
type: error
name: Platform adaptor class not found
description: The class for platform adaptor \"{0}\" (platform \"{1}\") cannot be found.

ORABPEL-00223
severity: 10
type: error
name: Maximum number of namespaces exceeded
description: Failed to create the namespace \"{0}\"; the maximum number of namespaces ({1}) has been reached.

ORABPEL-00224
severity: 10
type: error
name: Could not find namespace index
description: Invalid namespace index \"{0}\".

ORABPEL-00225
severity: 10
type: error
name: Could not read namespace index from db
description: Could not get the namespace index, the reason is {0}

ORABPEL-00226
severity: 10
type: error
name: Could not write namespace index
description: Could not insert the namespace \"{0}\", index \"{1}\", the reason is {2}

ORABPEL-00227
severity: 10
type: error
name: Wrong database adaptor interface
description: The class \"{0}\" (for the database adaptor for \"{1}\", datasource \"{2}\") does not implement the IDatabaseAdaptor interface. All database adaptors used by the OraBPEL server must implement this interface.

ORABPEL-00228
severity: 10
type: error
name: Error while creating database adaptor
description: An error has occurred while attempting to instantiate the class \"{0}\" as the database adaptor for \"{1}\", datasource \"{2}\". The exception reported is: {3}

ORABPEL-00229
severity: 10
type: error
name: Unknown database adaptor classname
description: The database adaptor classname for \"{0}\", datasource \"{1}\" has not been specified.

ORABPEL-00230
severity: 10
type: error
name: Missing adaptor resource configuration
description: The adaptor resource file \"{0}\" for the application server \"{1}\" cannot be found in the current classpath. This resource file contains all the JNDI mappings required for the BPEL process domain to initialize. The application server \"{1}\" may not be currently supported by OraBPEL.

ORABPEL-00231
severity: 10
type: error
name: Error while creating adaptor manifest
description: An error has occurred while attempting to instantiate the class \"{0}\" as the adaptor manifest for \"{1}\", datasource \"{2}\". The exception reported is: {3}

ORABPEL-00232
severity: 10
type: error
name: Wrong adaptor manifest interface
description: The class \"{0}\" (for the adaptor manifest for \"{1}\", datasource \"{2}\") does not implement the IServerAdaptorManifest interface. All adaptor manifests used by the OraBPEL server must implement this interface.

ORABPEL-00233
severity: 10
type: error
name: Unknown adaptor manifest classname
description: The adaptor manifest classname for \"{0}\", datasource \"{1}\" has not been specified.

ORABPEL-00234
severity: 10
type: error
name: Malformed server url
description: The SOAP server url \"{0}\" for the BPEL engine is malformed.