Error Messages in Siebel

The following table lists errors that occur when using the adapter with either an iBSP or JCA repository project and provides a solution to each error.

Error

Solution

A successful connection is made to Siebel environment, but no values are available in the Business Object, Business Service, and Integration Object nodes in the iWay Explorer tree.

The Repository Name specified on the Advanced tab in the Siebel Target configuration is either void or empty of any components in the targeted Siebel environment, or the Repository Name is not valid for the targeted Siebel environment. Verify that the Repository Name is valid and contains components for interrogation and then, reconnect.

When executing a request, the following error message appears:

AdapterException: Unsupported
Action: {0} Tquery

Verify that the method is available for the specific request by verifying schema.

When executing a request, the following error message appears:

AdapterException: Field
'NFame' does not exist in
definition for business
component 'Account'. Please
ask your systems
administrator to check your
application configuration.

Ensure that the field names are valid within the request document by referring to the schema for that specific object and then, resubmit the request.

When connecting to releases prior to Siebel 7.8 using the Java Data Bean Interface, you cannot reconnect after initial connection loss. This might occur when iWay Explorer experiences a brief loss of network connection or if the Siebel Server or Gateway Service is restarted while iWay Explorer is logged into the Siebel application.

Restart your application server and iWay Explorer in order to log in successfully to the Siebel application. This is a known Siebel API issue. For more information, see Siebel Alert 984.

The iWay Application System Adapter for Siebel does not interact with Integration Objects in a Siebel workflow using Web services or JCA in iWay Explorer. This is a result of a limitation in Siebel software that does not handle the namespaces in the incoming XML document for the Integration Object.

An error similar to the following might appear:

Cannot convert XML Hierarchy
to Integration Object
Hierarchy.--Field with XML
tag 'xmlns:ns' and XML Style
of 'Attribute' is not found
in the definition of EAI
Integration Component
'Account'--Error invoking
service 'EAI XML Converter',
method 'XMLDocToIntObjHier'
at step 'XML to Property
Set'.

The preferred work around is to add to the Integration Object an Integration Object User Property with the name Ignore Undefined XML Tags and a value of Y.

Alternatively, a less preferred work around is to invoke a Siebel workflow that will run the Web service. Pass the XML document that represents the input via a protocol, for example, HTTP or MQ, that the workflow is listening on. You can build the emission of the XML document using that protocol as a Web service in iWay Explorer.


iWay Software