Siebel CRM - Version: 7.8.2.6 SIA [19230] and later [Release: V7 and later ]
Information in this document applies to any platform.
***Checked for relevance on 19-OCT-2010***
Symptoms
Statement of what the issue is:
Inbound web service calls fail to identify the web service definition in the cache after a few days the OM is servicing requests if the operation name has spaces on it.
The error seen in EAI log is :
"SBL-EAI-04313: There is no active Web Service with operation named 'http://siebel.com/asi/:SNI Solicitation Activity Creation'."
Notice the operation name has spaces on it.
EAI log examples (all events set to 5) :
bad example
CchMgrLog CchMgrAcsInfo 4 0 2009-02-10 07:59:03 Accesses item [SOAP_RPC_LITERAL:http://siebel.com/asi/:SNI Solicitation Activity Creation:HTTP] in cache [].
CchMgrLog CchMgrAcsInfo 4 0 2009-02-10 07:59:03 Item [SOAP_RPC_LITERAL:http://siebel.com/asi/:SNI Solicitation Activity Creation:HTTP] is in cache [].
CchMgrLog CchMgrAcsInfo 4 0 2009-02-10 07:59:03 Accesses item [SNI Solicitation Activity Creation:http://siebel.com/asi/:SNI Solicitation Activity Creation] in cache [].
CchMgrLog CchMgrAcsInfo 4 0 2009-02-10 07:59:03 Item [SNI Solicitation Activity Creation:http://siebel.com/asi/:SNI Solicitation Activity Creation] is in cache [].
WebSvcInbound WSInboundTrace 3 0 2009-02-10 07:59:03 Envelope Processing
WebSvcInbound WSInboundTrace 3 0 2009-02-10 07:59:03 Impersonate
CchMgrLog CchMgrAcsInfo 4 0 2009-02-10 07:59:03 Accesses item [http://siebel.com/asi/:SNI Solicitation Activity Creation] in cache [].
CchMgrLog CchMgrAcsInfo 4 0 2009-02-10 07:59:03 Item [http://siebel.com/asi/:SNI Solicitation Activity Creation] is in cache [].
ObjMgrLog Error 1 0 2009-02-10 07:59:03 (port.cpp (362)) SBL-EAI-04313: There is no active Web Service with operation named 'http://siebel.com/asi/:SNI Solicitation Activity Creation'.
good example, after restarting the OM
CchMgrLog CchMgrAcsInfo 4 0 2009-02-10 08:03:34 Accesses item [SOAP_RPC_LITERAL:http://siebel.com/asi/:SNI Solicitation Activity Creation:HTTP] in cache []..
CchMgrLog CchMgrAcsInfo 4 0 2009-02-10 08:03:34 Item [SOAP_RPC_LITERAL:http://siebel.com/asi/:SNI Solicitation Activity Creation:HTTP] is in cache [].
CchMgrLog CchMgrAcsInfo 4 0 2009-02-10 08:03:34 Accesses item [SNI Solicitation Activity Creation:http://siebel.com/asi/:SNI Solicitation Activity Creation] in cache [].
CchMgrLog CchMgrAcsInfo 4 0 2009-02-10 08:03:34 Item [SNI Solicitation Activity Creation:http://siebel.com/asi/:SNI Solicitation Activity Creation] is in cache [].
WebSvcInbound WSInboundTrace 3 0 2009-02-10 08:03:34 Envelope Processing
WebSvcInbound WSInboundTrace 3 0 2009-02-10 08:03:34 Impersonate
CchMgrLog CchMgrAcsInfo 4 0 2009-02-10 08:03:34 Accesses item [http://siebel.com/asi/:SNI Solicitation Activity Creation] in cache [].
CchMgrLog CchMgrAcsInfo 4 0 2009-02-10 08:03:34 Item [http://siebel.com/asi/:SNI Solicitation Activity Creation] is in cache [].
WebSvcInbound WSInboundDbg 4 0 2009-02-10 08:03:34 Transformed Request Argument 'ActivityType' into 'ActivityType'
WebSvcInbound WSInboundDbg 4 0 2009-02-10 08:03:34 Transformed Request Argument 'ActivityReasonType' into 'ActivityReasonType'
WebSvcInbound WSInboundDbg 4 0 2009-02-10 08:03:34 Transformed Request Argument 'ActivityStatus' into 'ActivityStatus'
Cause
This was caused by product defect : BUG: 10519868
Solution
NOTE: 499406.1 The product defect itself and one of its many possible symptoms are described at "Inbound Web Service starts to produce incomplete responses after stress load "
The issue is actually with XML converter, which is called a bit before the error.
The XML converter itself does not error, but it may corrupt data that has spaces when used under high load/long periods.
As a result, the next step that uses the data will work on corrupt data.
As the XML coverter is widely used both internally by the Siebel application as well as explicitly called by customers the symptoms can vary a lot !
BUG: 10519868 has been fixed by FR # 12-1IDOWKX on 7.8.2.7 Fix Pack
Options going forward are :
1) as a workaround, remove spaces from the operation name.
e.g: SNI Solicitation Activity Creation becomes to SNISolicitationActivityCreation
This will need configuration changes, new WSDL and update at the caller applications.
OR
2) download 7.8.2.7 Fix Pack or higher from My Oracle Support and apply it.
References
BUG:10519868 - NAME WITH SPACE GET LOST WHEN CONCURRENT TASKS RUN IN SAME MT SERVER
NOTE:499406.1 - Inbound Web Service starts to produce incomplete responses after stress load
Related
Applies to:
Siebel System Software - Version: 7.5.2 [15051] to 8.1.1 [21112] - Release: V7 to V8
Information in this document applies to any platform.
Symptoms
SBL-EAI-04313
I am configuring inbound and outbound Web Services on siebel 7.5.3.2.
They are working fine on development environment, but when I tried to migrate them on another environment, they all fail with same error:
I tried to test vanilla inbound web services such as Siebel Account – SiebelAccountQueryById, and they work fine on test but not on production.
I inactivate them, reactivated, stopped and started the server, cleaned the cache and tried again, but it did not work. I tried to find further documentation on the support web, but with no luck.
What am I missing?
Cause
If you experience this kind of behavior in non-ENU environment, it would be recommended to check whether the translated LOV values are available. In order to troubleshoot the behavior, the customer was suggested to do followings:
1. Check if there is any difference for the List of Values (LOV) with the type “WS*” between the development and the production environment.
2. Execute the SQL against Siebel databases:
SELECT NAME, VAL, LANG_ID, ACTIVE_FLG
FROM S_LST_OF_VAL
WHERE TYPE = 'WS_STATUS_CD'
Customer found that the LOV record had been modified by someone in the organization:
LOV Type = "WS_BINDING_PROTOCOL_CD", NAME= "OUTBOUND"
(Language had been set to "ITA")
Solution
By changing LOV values back to ENU, stopping, and restarting the Siebel Server, the reported behavior could be resolved and all inbound and outbound Web services worked fine as expected.
Applies to:
Siebel CRM - Version: 8.1.1 SIA [21111] - Release: V8
Information in this document applies to any platform.
Symptoms
Customer has installed the Siebel 8.1.1.1 SIA QuickFix QF1102, that delivers the software enhancements ACR 474 and ACR 508, required to enable AIA 2.5 PIPs for Communications (Order-to-Bill).
After completion of the installation, following Siebel CRM Error has been reported by AIA middleware process (SyncItemCompositionListSiebelCommsProvABCSImpl ), started to synchronize product record from BRM (Billing) to CRM (Siebel) application:
There is no active Web Service with operation named 'http://siebel.com/asi/V0:SWIProductImportUpsert'.(SBL-EAI-04313)
Cause
The Inbound Web Service "SWEProductImport", that publishes the "SWIProductImportUpsert" operation (document/literal) in the "http://siebel.com/asi/V0" name space, was not present (installed) in Siebel CRM.
This Siebel Inbound Web Service is delivered in the seed data file: "seed_aiacom24.dat" located in the "ACR474\SeedData\ACR463_SEED" folder of the Siebel Repository Patch: ACR 474.
This seed data file must be imported in Siebel to include the core AIA (stated as 2.4) for Communications functionality in the AIA 2.5 Installation.
Solution
The issue has been resolved after completion of the step "Importing Seed Data for ACR 463", gven in the in the "Siebel Quick Fix Installation Guide Version 8.1.1.1 QF1102 for ACR 474 and ACR 508" document (readme.html)
As it is stated in the "Known Issues" section in the beginning of the patch installation guide:
NOTE: During the configuration procedure, you will be asked to import seed data for ACR 463. This ACR provided AIA COM 2.4.
References
NOTE:819603.1 - Siebel 8.1.1 QF1002 for ACR 463: AIA COM 2.4 Order to Active and Order to Bill PIP Enhancements
NOTE:956062.1 - Siebel CRM Integration Pack for Oracle Order Management: Order to Cash 2.5 - Implementation Guide
Related
Applies to:
Siebel System Software
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.7.0.1 [AN307]
Database: Oracle 8.1.7.4
Application Server OS: Sun Solaris 8
Database Server OS: Sun Solaris 8
This document was previously published as Siebel SR 38-1545413181.
***Checked for relevance on 03-FEB-2011***
Symptoms
A customer has configured the web service for 'External ATP Check' by following bookshelf
Siebel Order Management Guide > Preparing for Integration > Process of Setting Up Third-Party Product Availability Applications >Configuring Web Services
Yet when they run this (via the Inquire button for a line item in a quote) it fails saying that there is No active web service with method 'Execute'.
Cause
The error "There is no active Web Service with operation named 'Execute'.(SBL-EAI-04313)" was due to the fact the documentation is missing details for the "Operations" applet (lowermost applet).
The documentation mentions how to call the External ATP Check business service by entering the relevant configuration in Service Ports applet but fails to mention how to indicate which business service method to run at the "Operations" applet.
Solution
Please modify the 'External ATP Check' outbound web service definition (on the Outbound Web Service Administration view of Siebel Client) by adding the 'Execute' operation entry (in the bottom list applet), to make sure it knows it can call method Execute of business service 'External ATP Check'
After this modification, please click the 'Clear Cache' button on this view (otherwise you will have to restart the Siebel Client session) to re-load the modified outbound web service definition in the current application object model cache.
More information on web services can be found at
Integration Platform Technologies: Siebel eBusiness Application Integration Volume ll > Web Services > Invoking Siebel Web Services Using an External System >Publishing Inbound Web Services
and although this documentation is about inbound web services, there is the same corresponding "Operations" applet for outbound services too.
The setup is the same. At the end of the day, all you are doing is entering a business service name in ports, and a business service method in operations plus web service specific information such as the URL to call, encoding methods, etc.
Related
Applies to:
Siebel Clinical Manager - Version: 7.8.2.4 SIA [19224] - Release: V7
Information in this document applies to any platform.
Symptoms
Environment:
-------------------
Product: Siebel Clinical Manager
Version: 7.8.2.4 SIA [19224]
OS platform: HP-UX PA-RISC (64-bit)
DB platform: Oracle Server - Enterprise Edition
Env: dev
Statement of Issue:
-----------------------------
An inbound web service has been set up to enable an external application to query the Siebel database using the EAI Siebel Adapter. The service port's Transport is set to JMS. A JMSReceiver task is started, a message is put onto the receive queue, the task picks up the message but it fails with an error trying to process it.
Error:
-------
There is no active Web Service with operation named 'http://siebel.com/test/:EAISiebAdapt_TestContactIO_CTMS_Contact_QueryPage_Input'.(SBL-EAI-04313)
Business Impact:
-------------------------
The functionality is required is to enable an external application to query the Siebel database using the JMS transport.
Cause
The reported behavior is caused by a defect.
When calling an inbound web service using transport JMS and binding SOAP_DOC_LITERAL, the JMSReceiver task fails with the error "There is no active Web Service with operation named...". CR 10520144 has already been rasied to address the defect.
Solution
The reported error did not occur and the SOAP request was processed correctly when Binding was set to SOAP_RPC_ENCODED or SOAP_RPC_LITERAL.
References
BUG:10520144 - SOAP/JMS WITH DOC_LITERAL BINDING CAUSES CAN'T FIND A WEB SERVICE OPERATION PROPERLY
Related
--------------------------------------------------------------------------------
Products
--------------------------------------------------------------------------------
Applies to:
Siebel Thin Client - Version: 8.0.0.6 [20423] and later [Release: V8 and later ]
Information in this document applies to any platform.
***Checked for relevance on 18-Oct-2010***
Symptoms
The issue is that while invoking a Siebel inbound web service called 'SearchSecurityService', the web service fails and returns the following error:
ObjMgrLog Error 1 0000000749d11860:0 2009-03-30 14:51:19 (factory.cpp (657)) SBL-EAI-04313: There is no active Web Service with operation named 'http://siebel.com/asi/:SearchSecurityServicegetAllSecurityValues_1'.
Cause
The cause of the error is due to the incoming soap request having namespace http://siebel.com/asi, causing the Siebel application to look for the 'SearchSecurityService' web service with the matching namespace of http://siebel.com/asi. However, on the actual web service definition in Siebel client > Inbound Web Services view, the namespace is http://search.oracle.com/AdminService/2006-09-15.
As a result, since the namespace in the database is for the web service is http://search.oracle.com/AdminService/2006-09-15, but Siebel application is looking for namespace of http://siebel.com/asi/ from the incoming soap request message, no record for the web service with namespace http://siebel.com/asi/ could be found, thus Siebel application returned the error:
ObjMgrLog Error 1 0000002e49d10e20:0 2009-03-30 17:14:17 (factory.cpp (657)) SBL-EAI-04313: There is no active Web Service with operation named 'http://siebel.com/asi/:SearchSecurityServicegetAllSecurityValues_1'.
The namespace in the soap request envelope for the web service must match the namespace of the web service definition in the database. When there is no match, Siebel application will not be able to look up the web service properly.
Siebel Technical Support has tested this behaviour and reproduced the same error with the following steps:
1. Using the standard 'SearchSecurityService' web service having the namespace http://siebel.com/asi/
2. Generate the wsdl file with the namespace of: http://siebel.com/asi/
3. On the web service definition in Siebel Inbound Web Services view, update the namespace to: http://search.oracle.com/AdminService/2006-09-15
4. Click Clear Cache button for the web service.
5. Use soapui tool to load original wsdl file with namespace of: http://siebel.com/asi/, submit sample soap request:
Here, the request being submitted has namespace http://siebel.com/asi/
6. SoapUI returned the following error in the soap response:
7. When inspecting the EAI task log file, the following sequence of information can be seen:
SELECT *
FROM
dbo.S_WS_OPERATION T1
INNER JOIN dbo.S_WS_PORT_OPER T2 ON T2.OPERATION_ID = T1.ROW_ID
WHERE
(T2.PORT_ID = ?)
ObjMgrSqlLog Detail 4 0000002e49d10e20:0 2009-03-30 17:14:17 Bind variable 1: 04-JGNAQ
....
ObjMgrLog Error 1 0000002e49d10e20:0 2009-03-30 17:14:17 (factory.cpp (657)) SBL-EAI-04313: There is no active Web Service with operation named 'http://siebel.com/asi/:SearchSecurityServicegetAllSecurityValues_1'.
ObjMgrBusServiceLog InvokeMethod 4 0000002e49d10e20:0 2009-03-30 17:14:17 Begin: Business Service 'XML Hierarchy Converter' invoke method: 'HierToDoc' at 103c9e28
.....
EAITransport EAITransportWarning 2 0000002e49d10e20:0 2009-03-30 17:14:17 Dispatch Service: 'Web Service Inbound Dispatcher', Method: 'Dispatch' failed
EAITransport EAITransportWarning 2 0000002e49d10e20:0 2009-03-30 17:14:17 [0] There is no active Web Service with operation named 'http://siebel.com/asi/:SearchSecurityServicegetAllSecurityValues_1'.(SBL-EAI-04313) (IDS_EAI_WS_OP_NOT_FOUND)
This is the same error reported and same log file sequence leading up to the error.
Solution
In order to fix the error, ensure that the namespace in the soap request envelope matches the namespace specified on the Siebel web service definition. The following steps can be used to check the namespace:
1. Check the web service definition in Siebel client > Inbound Web Services view to see what the namespace is currently. Update it to the correct namespace to be used if needed.
2. For the web service, re-generate the wsdl file again, save the wsdl file. This is to make sure that the wsdl being used for testing by external application has the same namespace as the web service definition currently in the Siebel database.
3. Click {Clear Cache} for the web service.
4. Load the newly generated wsdl file using external tool or soapui application.
5. Submit soap request with the same namespace in the soap envelope as what is displayed in the namespace field for the Siebel web service definition.
Related
אין תגובות:
הוסף רשומת תגובה