Troubleshooting and Problem Determination
Having deployed the
Sales Fulfillment Application, how do we troubleshoot and diagnose it in
case of problems? Troubleshooting is one of the critical features
needed to diagnose the issues and rectify the problem with as minimum
impact as possible. When troubleshooting, you should be asking these
questions or items you will have to address:
What is causing the problem?
Which part of the application is it occurring in?
When do the problems appear?-Time of the day, certain scenarios, and so on. What are the symptoms of the problem?
How can I reproduce the problem?
You need tools
that assist you in the troubleshooting process. WPS/WESB and WID include
several tools you can use to troubleshoot your applications that you
develop and deploy on the server. The admin console provides
capabilities for troubleshooting. In the admin console, under the Troubleshooting navigation item, you can perform several things to troubleshoot your module(s) if anything goes wrong.
Logs and Trace is used to configure logging and tracing levels for the server logs. These logs can also be viewed through these pages.
Cross-Component Trace allows you to identify data that is captured in the trace.log.
This data can include error and event information, such as corrupted
data or runtime exceptions, captured during SCA processing. The input
and output data passing between WPS and WESB components can also be
captured and used for determining a problem using WID.
Configuration Problems is used to view and identify issues that may exist in the current configuration.
Class Loader Viewer helps you to troubleshoot issues that may occur with class loaders.
Runtime Messages pages show events published by the application server class including errors, warnings, and information.
The runtime messages that
appear in the logs during installation consist of a four- or
five-character message prefix, followed by a four- or five-character
message number, which is followed by a single-letter message type code
(CWWBS0000E, CWWBS0032I, CWWBS0059W, and so on).
C: Indicates a severe message
E: Indicates an urgent message
I: Indicates an informational message
N: Indicates an error message
W: Indicates a warning message
You can often resolve the
problem by reading the entire message text and the recovery actions that
are associated with the message.
First Failure Data Capture
(FFDC) provides the instrumentation for exception handlers (catch
blocks) to record exceptions that are thrown by a component. The
captured data is saved in a logfile for use in analyzing the problem.
These logfiles can be found in your WTE under:
%WID7_WTE_HOME%\runtimes\bi_v7\profiles\qwps\logs\ffdc
Administration tasks using Business Space
Business Space provides templates that help you administer solutions deployed on WPS and WESB. You can create a Solution Administration
space in Business Space to manage and administer the Sales Fulfillment
Application deployed on WPS and WESB. To create a new space, once you
log in to the Business Space, click on the Actions | Create Space
menu option on the top menu. As shown in the following screenshot, this
will bring up a wizard where you can specify a name for the space and
select Solution Administration from the list of available templates. You can also specify a Space style and Space icon to customize its look and feel.
Once you create this Solution Administration space, it becomes the container that allows you to browse all the modules deployed on the server through Module Browser.
When you click on the module name to expand the tree view, as shown in
the following screenshot, you will be able to see the following as
pertinent to the module:
Service imports and service exports
Any properties and policies defined for the module
Business rule groups defined
Processes and process instances
You can view the process instances by clicking on the process component name in the Module Browser widget, clicking the link to open Business Process Choreographer Explorer in a new browser window, and administering the artifact
Business state machines
Human tasks
Business calendars defined
Security roles defined
You must have the BPMAdmin or BPMRoleManager authority to assign or modify roles
Installing versioned SCA modules
You can deploy a different
version of the same SCA module into a server or cell that has a
different version of the same module such that both the versions can
co-exist on the server or in the cell. To be able to do this, you should
make sure that the module is versioned in WID and export it for
command-line deployment.
Now, next are the high-level steps to follow:Export the versioned module as an installable EAR file using serviceDeploy. For example, serviceDeploy BizServices-CustomerBillingMgmt.zip.
Install the module using the admin console by performing the steps mentioned in the earlier sections.
If
you want to install the versioned module on multiple servers or
clusters in a cell, do the following for each module instance you
require:
createVersionedSCAModule -archiveAbsolutePath input_archive_dir -workingDirectory working_dir -uniqueCellID cell_ID
