Service Problems

Problem

Unexpected Errors

Resolution

When Unwired Orchestrator tooling has been running continuously for 24 hours or more and in certain other circumstances, you may encounter unexpected errors. Sybase recommends that you restart the tooling if problems are encountered while managing endpoints or defining new services.

Problem

No Search Results

Resolution

If you specify search criteria in the Service Search Wizard and no results are returned, consider the following:

• The public registry you specified is currently not available. Try later.

• The business entity either no longer exists or none of its published services contain pointers to valid WSDL documents.

• Your search criteria has typographical errors.

Problem

Poor Performance

Resolution

To improve the performance of the database service, apply patches and updates that improve JDBC performance.  Performance increases significantly when Sybase ASE EBF 10972 is applied to the database server.

Construct SQL queries that are tuned for performance because that directly correlates to business process performance.   If you have specific questions regarding this issue, contact Sybase Technical Support.  

Problem

Database Test Fails

Resolution

If a test of a database endpoint fails, check the following:
- Verify that you have specified the correct JDBC driver files.
- Verify endpoint properties.
- Verify that the database service is actually running and accessible on the network.

Problem

Schema Support

Resolution

This version of Unwired Orchestrator supports only those schema that conform to the final recommendation of the W3C regarding schemas. Specifically, we check to make sure the namespace of the WSDL file includes the 2001 W3C schema URI: http://www.w3.org/2001/XMLSchema.

Problem

Database Character Set Errors

Resolution

If ASA returns a warning in your result set about the server charset, use the Endpoint Editor to add the following name/value pair to the Database Connection Properties:

CHARSET=cp1252

Problem

Transports

Resolution

To verify that named transports map to valid session and transport configuration information:

1. In the Services Perspective Orchestration Navigator, right-click on the .wsdl file for the named service.

2. Select Open With>Service Editor.
   The Service Editor appears.

3. Expand the Ports folder.

4. Right-click on each of the defined ports and select Edit to view which transport the port is configured with.

Problem

Engine put into error state and suspended

Resolution

Plug-ins attempting to connect to services must be configured properly, and the service must be available to the engine at runtime. When errors occur (such as losing a connection), the runtime engine suspends and the problem must be resolved before continuing runtime processing.

To verify that the endpoint is defined properly based on the physical resources:

1. Open the Endpoint Manager by selecting Window>Show View>Endpoint Manager or by selecting Window>Show View>Other> Orchestrator>Endpoint Manager.

2. In Endpoint Manager, right-click on an endpoint connection and select Edit.

3. Edit the properties.

To verify that the endpoint is running or available:

This is done using the endpoint's provider. For example, if an endpoint is a queue defined in WebLogic, use WebLogic's web-based administration tool to verify the endpoint.

If the endpoint is a database, you can test the connection. See Testing Database Endpoint Connections.

Problem

Business process put into error state

Resolution

SQL statements defined in the definition of a database endpoint are not validated during the design stage.

Provide manual SQL correction to the business process that is in error and then reintroduce the event into the system.

Note: A rollback on the business process occurs, but a rollback on activities related to the plug-in must be performed manually.

Verify the success of SQL statements by testing the database connection before completing business process design. See Testing Database Connections.

Problem

Instance is running, but output file contains no messages

Resolution

Verify the spelling of the transport and session names in Endpoint Manager.

Error

Directory is not running

Resolution

This error can appear when either the Endpoint Manager or Service Library is opened.

Go into Preferences, correct the UDDI registry values, and restart Unwired Orchestrator.

Error

Format not found in database

Resolution

Change the Format Name of the One-Way Messaging imported format to a normalized format name.

Error

Errors that involve database endpoint configurations:

• JDBC driver is not configured correctly

• Database is not running

• Values specified for endpoint are not correct

Resolution

• Verify that the JDBC driver is defined.

• Use another tool to connect to the database to verify that it is running.