Monday, September 10, 2012

Web Services Trouble Shooting Points


Please check for following things whenever any error occurs during web services:

1)    Check that both Siebel server environment and Siebel Web Server Extension (SWSE) are up and running.
2)    Web Service invoked by external system is Active by navigating to Administration – Web Service screen.
3)    Address specified in the Inbound Web Service is correct. Validate hostname, Webserver, user and password are correct in URL.
4)    Siebel Enterprise Application Integration (EAI) component group is enabled.
5)     In case of Inbound Web service validate whether correct input arguments are being provided.
6)    Increase the log level to 4 for EAI Object Manager Log files are maintained in log directory of Siebel Server. e.g. $SIEBSRVR \log directory where component related log files such as EAIOBJMGR_enu_YYMMDD.log can be checked.
a.    Navigate to the Administration - Server Configuration screen > Servers view
b.    Select the relevant EAI Object Manager and in the middle applet, click the Parameters tab.
c.    Set the Log Level to 4 for all of the following Event Types shown in screenshot.

7)    Enable Siebel Service Argument Tracing to write all inbound and outbound SOAP documents to a log file. Steps will be shared later in this post.
a.    Navigate to the Administration - Server Configuration screen > Servers view
b.    Select the relevant EAI Object Manager and in the middle applet, click the Parameters tab.
c.    Set the Enable Business Service Argument Tracing parameter to True.
d.    Restart or reconfigure the server component.
e.    After enabling above argument following files are created on web service consumer application
                                          i.    OutboundDispatcher_input_args.dmp – It specifies the response being received.
                                         ii.    OutboundDispatcher_output_args.dmp – It specifies about the request being send.

f.     Similarly  on server following files are being created:
                                          i.    InboundDispatcher_input_args.dmp – It specifies the SOAP request received.
                                         ii.    InboundDispatcher_output_args.dmp – It specifies about the response being send.

8)    Also validate the SWSE log files which are available in log directory of SWSE server.

EAI MQSeries Transport -Session 2

In the previous post we have talked about the outbound transport for MQ Series In this post we are going to cover

Inbound MQ Series.


Prerequisite: 

  • The EAI MQSeries Server Transport must be up and running, it connects only to IBM WebSphere MQ Server software. 
  • The MQ and Siebel Server must be running on the same machine.
  •  The IBM MQ team must provide you the following details.
    • Physical Queue Name
    • Queue Manager Name 
  • You must have set up a Dispatch Rule either a dispatch service or  a Dispatch  workflow.

Let’s start with configuring the Siebel Application to be ready to receive the data.

First we need to set up the profiles for the Connection Subsystem and the Data Handling Subsystem for the 
MQ. 

We need to setup both data and connection subsystems while configuring the receiver system.Steps for setup are explained below:

Connection SubSystem.

a)     Login to Siebel Application (Server)

b)    Go to Sitemap>Administration-Server Configuration>Enterprises>Profile Configuration.

c)     Set Connection Subsytem and DataHandling Subsystem parameters for MQ Server Receiver.

d)    Following screenshot shows how to set parameters for 
     
       Siebel_MQ_Receiver_Response_ConnSubsys



The key parameters you need here are:

Required: MQSeries Physical Queue Name (Details are provided by MQ Team).

Required: MQSeries Queue Manager Name (Details are provided by MQ Team).

Optional: MQSeries Response Physical Queue Name (Details are provided by MQ Team).


Data Handling SubSystem
                   
                 
 

 
The key parameters here to note are

Service Method to Execute: Name of the method of the below Dispatch service which you want to use.

Service to Execute: Name of the Dispatch Business Service.

                                                       Or 

              Workflow Process to Execute: 



In case you want the Dispatch workflow to handle the message.We have created a sample workflow

 





In the above steps we have configured the Profiles for the Connection Subsystem and Data Handling Subsystem

now we will be creating the Receiver System.
a)     Go to Component Definitions tab, and set following component parameters as shown below:

b)    Receiver Method Name : ReceiveDispatch

c)     Receiver Service Name : EAI MQSeries Server Transport

d)    Receiver Connection Subsystem: Siebel_MQ_Receiver_Response_ConnSubsys(Connection subsystem profile created above).

e)     Receiver Data Handling Subsystem : Siebel_Mq_Response_DataHandling_Subsys
(Connection data handling subsystem profile created above).
 


With this the receiver is not set up and is ready to receive the message sent from the external system using the IBM WebSphere MQ Server software. 

This concludes our series of EAI MQSeries Transport.