The SOA Grid in OpenText Process Suite supports seamless connectivity and continuous data transmission among all the internal and external systems of an application. Powered by ESB (Enterprise Service Bus), the grid routes messages generated by underlying business processes across the systems. In this context, the two possible integration scenarios are – Java Integration and Web Services Integration. Let’s take a look at each of the scenarios in detail.
Java integration calls methods from a Java class and interfaces with most of the third-party Java APIs. It supports a variety of integration scenarios and provides access to a plethora of Java features, including published Java libraries and APIs. An application connector builds a Java integration webservice to integrate with an external system, in order to complete a task – retrieve, update and insert data.
Application Connector debugging process involves the following steps:
Web services integration calls methods of external systems using wsdl url, while an uddi application connector helps in integrating with external systems. The log file generated by uddi application connector helps in debugging the application integration errors. The detail log can be accessed by enabling specific log information like SOAP header, request and web service response and severity levels, in uddi application connector.
OpenText Process Suite applications use multiple Service Containers for application integration and generate component specific logs. These logs are stored at different places, further compounding the task of debugging application integration issues.
CAL makes it easy to debug a particular application, by diagnosing why and what of external or internal Web Services executed. It also aids in tracing an error or a SOAP fault through a specific log entry in a file. In addition, CAL facilitates publishing, collecting, storing and viewing log messages for multiple or composite applications.
The best way to analyze messages logged by different services is to take into consideration the chain of relevant messages that hold a causal relationship with each other. E.g. A User Interface initiates a short-lived process, whereas WS-AppServer code accesses another web service causing an error, logged at all levels (Web Service, WS-AppServer, Short-lived Process and User Interface). So, the bottom line is – anyone viewing complete log must understand the causal relationship among these messages.
JMX facilitates an effective way to debug and tune application integration issues for performance, for OpenText Process Suite platform. It collects performance data from different application components in the light of component settings, helps identify and resolve NOM and heap memory issues seamlessly during application integration.