Considerations for webMethods Clients
Use the information in this section when creating a webMethods client that invokes a service that executes an Oracle Applications transaction. It describes:
How to invoke a service that executes an Oracle Applications transaction.
Error conditions that you should be aware of when creating a
webMethods client.
Generating Client Code
You can use the Designer to generate Java client code for services that execute an Oracle Applications transaction in the same manner that you generate Java client code for any other service. However, you must make modifications to the Java if the service expects any input variables that have a complex type (that is, sequences or structures). The Designer does not generate code to prompt for complex input variables. You will need to update your client Java file to prompt for the complex inputs or build the inputs programmatically.
Refer to the Software AG Designer Online Help for instructions on how to create client code for a service
Determining the Input and Output for the Service
Because the input to and output from the service has a specification, you can use Designer to examine the specification of the service to learn more about the required input and output.
Invoking a Service from a Client
You invoke a service created from an Oracle Applications transaction in the same manner that you invoke any other service. Refer to the Software AG Designer Online Help for instructions on how to invoke a service.
Handling Error Conditions
This section identifies some reasons a service might fail. Code your webMethods client to handle these errors.
If an error occurs during an Oracle Applications-to-IS transaction, the
Oracle Apps Adapter throws a service exception.
If an error occurs on an IS-to-Oracle Applications transaction during insertion into the Oracle open interface tables, the
Oracle Apps Adapter throws a service exception.
The
Oracle Apps Adapter provides a service to get error details if an error occurs on an IS-to-Oracle Applications transaction during processing by the Oracle Application import process.
Errors are logged in the
Integration Server’s log files. You can view the log files using the
Integration Server Administrator. Refer to the
webMethods Integration Server Administrator’s Guide for instructions.
JDBC errors. If the transaction fails for any reason, it returns the error information to the Oracle Apps Adapter. The service returns the error information to the client in a document. Most errors that can be returned by a JDBC application can be returned by the Oracle Apps Adapter.
Oracle Applications errors. If an IS-to-Oracle Applications transaction is successfully inserted into the Oracle Applications open interface tables, the transaction service will return success. A service is provided to return transaction status that includes customizable details on Oracle Applications errors for each specific transaction.