BEA SOAP implementation for WL5.1

Can anyone point me to a step by step guide for setting this up.
I have already read and followed the Soap.htm that is included in the
download, but I am getting nothing.
Among my apparent problems:
[ServletEntityResolver] : Could not resolve entity '-//Sun Microsystems,
Inc.//DTD Web Application 2.2//EN'. Check your
dtd reference.
[DescriptorLoader] : Could not find the WebLogic specific XML descriptor
WEB-INF/weblogic.xml. If this Web application
relies on the WebLogic specific XML descriptor, this may result in
misconfigured application.
Wed Mar 28 13:11:38 GMT+08:00 2001: <ServletContext-soap-webapp>
extracting classfiles to c:\weblogic\myserver\_tmp_war:
When I try runclient.cmd I consistently get an error opening the socket
The other thing I have noticed is that the classpath in the runclient.cmd
file seems to differ to what it should probably be set too.
Any help would be most appreciated
cheers
Jay

Similar Messages

BEA Soap Faults and differentiating them from Normal Soap Faults

Hi,
I've written a webservice client that interfaces with an external soap service. The external soap service generates custom soap exceptions that I am already handling by catching remote exception and then getting the cause from this remote exception to obtain the soap fault.
However, I notice if for example the external webservice is down I get a BEA soap fault returned which is a different format to the faults returned from the external service
IS there a way to easily identify a BEA generated fault from a standard soap fault without interoggating the soap fault manually?

Added the charset to web-service.xml
<web-services xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<handler-chains>
<handler-chain name="SOAPHandler">
<handler class-name="WebServiceHandler"/>
</handler-chain>
</handler-chains>
<web-service name="xxx"
uri="/uri"
targetNamespace="http://xxxx"
style="rpc"
ignoreAuthHeader="true"
exposeWSDL="true"
charset="UTF-8">
<components>
<java-class name="mainClass"
class-name="WebService">
</java-class>
</components>
<operations>
<operation method="x"
component="mainClass" handler-chain="SOAPHandler">
<params>
<param name="data" class-name="java.lang.String" style="in" type="xsd:string"/>
<return-param name="result" class-name="java.lang.String" type="xsd:string"/>
</params>
</operation>
</operations>
</web-service>
</web-services>
But it did not help.
This is beas issue probably because, everything works when I invoke service from some other system.
Any more ideas???

Evaluation of SOAP implementations

Hi,
I'm currently evaluating SOAP to implement a web-services-type application to front a existing system. The server is certainly Java-based, but the client can be anything. I'm a complete newbie with SOAP, so please bear with the idiotic-type questions.
1. Are there still interoperability issues with SOAP implementations between Sun/Apache and Microsoft? I've read several articles on this, but they are dated at least 1-2 years ago. Any glaring issues currently?
2. The AppServer is currently on Java1.4.0. Any known issues?
3. I've tried using the jwsdp to implement a simple (and raw) SOAP service. Anyone with a recommendation whether jwsdp will suffice or would Apache Axis be a better candidate? What does Axis provides that jwsdp doesn't if i already have a http-based MVC framework that I have to re-use?
4. A more general question: Must I deploy a WSDL for my SOAP serivces?
Many thanks in advance.

Hello,
Try to roll back the time of the computer to a few days back until you are able to perform an edition upgrade.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

XMLServer problem with Strings. SOAP implementation

hi,
I've tried to export a Service Objet with XMLServer.
The SO consists of a method that will be called by a JAVA client :
execute (String param) : String
There is no problem when this method returns a String with no special caracters. But when it contains some 'e', for example, the Java client is no more able to get the response.
The error deals with the SOAP envelop of the response,
the Java client crashes :
SOAP Fault; code=SOAP-ENV:Server string=XMLSvr.ProtocolSOAP.getResponseText: Internal Error - no response envelope
I use UDS 5.0 on NT
The Java client uses Apache.SOAP packages
Is this a problem of compatibility between the two SOAP implementations ??
Please help me ...
matt

Hi Matt,
UDS 5.0.1 is able to generate a SOAP Server and Java Proxies (Java clients) but there are some limitations in the current implementation (Does not have support for array of string for example...). I would suggest you to check http://knowledgebase.iplanet.com/ikb/kb/articles/7655.html for further info abou those limitations (by the way, all the questions and answers except one, are from an email I sent to the Iplanet guys last year... :-)

Changing SOAP Namespace for Web Service

Hi Experts,
Got a requirement to modify the SOAP namespace for a BAPI program exposed as a web service on SAP.
The fieldd denoting the SOAP namespace is accessible via transaction SE80 and navigating under: Package Name>Enterprise Services>Service Definitions> and double clicking on the exposed web service and selecting "Properties".
The SAP SOAP namespace provided by default is: urn:sap-com:document:sap:rfc:functions
Is anyone aware of a means to modify this namespace on the web service? Any help would be greatly appreciated. Thanks!
Regards,
Lionel

hi tan,
Although the SOAP Runtime is generally designed for RFC-type calls, it can also be used to access Web Services that are not implemented in a Web AS. For example, the Google search engine offers some services using SOAP, which can be accessed from the SAP Web AS.
Naming Conventions
The SOAP Runtime offers three methods of representing the original ABAP names (everything in upper case and separated by underscores) as data types in XML. Each method is associated with a different XML namespace:
urn:sap-com:document:sap:rfc:functions this is the canonical representation, which means that all names in the XML document are represented as they are in ABAP on a 1:1 basis. For repeating groups (such as the rows of a table), an XML element with the tag name item is generated (in writing) and expected (in parsing).
urn:sap-com:document:sap:soap:functions:uc-style this naming convention is similar to the first one, with the difference that instead of item, the name of the structure of the table row is generated or expected.
urn:sap-com:document:sap:soap:functions:mc-style this third convention also involves conversion of the upper case ABAP names to mixed case (both upper and lower case), according to the following algorithm: All characters except the first one are implicitly in lower case, and the underscore acts as a Shift key to effect an upper case character. RFC_SYSTEM_INFO thus becomes RfcSystemInfo. The addition of an initial underscore makes the first character lower case: RFCSYSTEM_INFO thus becomes rfcSystemInfo. An underscore character is transferred by adding an additional underscore: RFC__SYSTEM_INFO thus becomes Rfc_systemInfo.
When using the SOAP Runtime caller side, note the following points regarding the naming convention:
If the called Web Service is implemented in the Web AS 6.20, always use the namespace convention urn:sap-com:document:sap:rfc:functions. The namespace for the SOAP method must also be set according to this convention. To do this, specify the importing parameter nsvalue of the method set_method in the class CSoapDocument.
Setting the namespace of the naming convention for the SOAP method does NOT automatically mean that the SOAP Runtime also sets the naming convention for serialized SOAP messages. As a developer, you must ensure that the naming conventions are followed. To do this, you can use the methodsset_tag_name_format and set_item_name_format:
The method set_tag_name_format of the class CSoapDokument can be used to control the upper case or mixed case naming convention for tags that correspond to ABAP data types. To activate the normal ABAP format (upper case), use the value CSoapConstants=>ic_tagfmt_default for the importing parameter format. To switch to the mixed format, use the value CSoapConstants=>ic_tagfmt_mixcase.
The method set_item_name_format of the class CSoapDokument is used to control the use of the tag name for repeating groups in ABAP data types (table rows). To implement the structure name of the table row, set the value CSoapConstants=>ic_itemfmt_default for the importing parameter format. To use item as a tag, set the value CSoapConstants=>ic_itemfmt_useitem.
All names passed to the API must be in a format that is expected by the server side. This affects the importing parameter name of both the methods set_method and add_parameter of the class CSoapDocument. The SOAP Runtime caller side does not perform any conversion of these names. The document class on the calling side does NOT take into account the namespace you have selected here.
You should only implement the mixed case naming convention where it is necessary. This particularly applies when calling external Web Services, over the structure of which you have no control.
Sending the SOAP Header in the Call
The SOAP Framework does not provide general support for the handling of SOAP Header elements.
However, for calling external Web services, it is sometimes sufficient to be able to send simple Header entries as part of the request. In this special case, you can use the class CSoapDocumentHeader.
An instance of the class can be filled using the methods set_header_as_string or set_header_as_dataref. Using the method add_header, it can then be added to an instance of the class CSoapDocument, and is then serialized as a part of the document instance when the call is made.
regards
karthik
dont forgrt to reward me points if it helps u

How to add Custom Attributes in the SOAP header for OWSM

Hi,
I like to know how to add the Custom Attributes in the SOAP header for OSWM username token authentication.
Currently we are getting the header element like
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
here we need to add the attribute "soap:mustUnderstand="1" , so the element will look like
<wsse:Security soap:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
Any info on this will be helpful.
Thanks,
ArunM

Hi Jay, you can make it in more than 1 way.
I suggest you the following:
- create an URL iview that points to any URL you want.
- define a Resource that points to the iview (with a window name, to open in new window)
- define an Area that points to the resource
- add your new Area to the your current Area Group
Regards!

I need urgent help in business catalyst SOAP api for [Product_UpdateInsert] operation.

Hi Everyone, I am new in Business Catalyst, but, my company is working with BC for a while. I have a task to import external data (such as catalogue, products, orders, shopping cart etc) to business catalyst native tables via SOAP api. I am able to use "Product_ListRetrieve" function that gave me products from BC. Now I want to insert and update product list, for which the api call is "Product_UpdateInsert". I am not being able to feed in even a single record. I need any code (jquery, php, javascript, java etc) as a sample, that works with SOAP api for this function. It is very urgent. Please help me. Thanks in advance. I have tried with the code below, but I am getting bugs (format not valid):
try
 $soapfileurlUpdate="https://worldsecuresystems.com/catalystwebservice/catalystecommercewebservice.asmx?wsdl";
 $soap_clientUpdate = new SoapClient($soapfileurlUpdate);
 $array_of_products=array("Products",
array("productId"=>"1128",
 "productCode"=>"1128",
 "productName"=>"Bostik 1128 Heat Transfer Sealer (thermo Putty) 460g Cartridge",
 "description"=>"Bostik 1128 Heat Transfer Sealer (thermo Putty) 460g Cartridge",
 "smallImage"=>"images/products/TEMUFF-7_New.jpg",
 "largeImage"=>"/images/products/TEMUFF-7.jpg",
 "cataloguesArray"=>array("DUCTS"), //array("string"=>"DUCTS"),
 "pricesSaleArray"=>array("US/9.95"),//array("string"=>"US/9.95"),
 "pricesRetailArray"=>array("US/9.95"),
 "pricesWholesaleArray"=>array("US/5.00"),
 "wholesaleTaxCodeArray"=>array("US/0.00"),
 "taxCodeArray"=>array("GB/VAT"),
 "groupProducts"=>array(""),
 "groupProductsDescriptions"=>array(""),
 "supplierEntityId"=>"1",
 "supplierCommission"=>"2",
 "weight"=>"20",
 "relatedProducts"=>array(""),
 "tags"=>"",
 "unitType"=>"",
 "minUnits"=>"1",
 "maxUnits"=>"2",
 "inStock"=>"10",
 "onOrder"=>"0",
 "reOrder"=>"0",
 "inventoryControl"=>"true",
 "canPreOrder"=>"0",
 "custom1"=>"",
 "custom2"=>"",
 "custom3"=>"",
 "custom4"=>"",
 "popletImages"=>"",
 "enabled"=>"true",
 "deleted"=>"false",
 "captureDetails"=>"true",
 "downloadLimitCount"=>"22",
 "limitDownloadsToIP"=>"0",
 "isOnSale"=>"true",
 "hideIfNoStock"=>"false",
 "productAttributes"=>"Size*|5|N:Small|,Medium|,Large|;Color*|5|N:Red|,Wh",
 "isGiftVoucher"=>"false",
 "enableDropShipping"=>"true",
 "productWeight"=>"20",
 "productWidth"=>"20",
 "productHeight"=>"29",
 "productDepth"=>"20",
 "excludeFromSearch"=>"0",
 "productTitle"=>"Bostik 1128 Heat Transfer Sealer (thermo Putty) 460g Cartridge",
 "cycletypeId"=>"1",
 "cycletypeCount"=>"1",
 "slug"=>"item-1",
 "hasVariations"=>"false",
 //"variations"=>array("ProductVariation"=>"true"),
 "roleResponsible"=>"",
 "metaDescription"=>""));
echo "SOAP Data To Be Inserted: ";
var_dump($array_of_products);
$vectUpdate = array("soap_version" => SOAP_1_2,
 "username"=>$soapusername,
 "password" => $soappassword,
 "siteId"=> $soapsiteid,
 "productList"=>$array_of_products);
$quoteUpdate = $soap_clientUpdate->Product_UpdateInsert($vectUpdate);
 $status = 1;
echo "BC side is updated.";
catch (SoapFault $sf)
 $errorlogText=date("Y-m-d h:i:s A"). "=> Error occurred while inserting data to business catalyst. \r\n";
echo $errorlogText. " See log for errors.\r\n";
echo $sf->getTrace();
//fwrite($errorLogFile,$errorlogText. "Error Dump: ". $sf->getMessage());
return;

Hi BCMan, Thanks for replying. Yes, the error is from BC side. The format was invalid. I fixed the issue today. Actually, I was pushing data from my PHP server to BC host system using SOAP api. I am still getting format errors, but I am able to insert data into products table.
One more question if you don't mind. Is it possible to use JQuery/Javascript to push data into BC tables in real time (while browsing products table) using customized pages? There are documents to solve this. However, I could not find examples of how I could fetch data from JSON file using JQuery and then populate products/catalog/order tables.
I appreciate your help.
Thank you.

SAP Fiori Apps Error Task Facade not implemented for provider. [/IWBEP/CX_MGW_TECH_EXCEPTION].

Dear All
I am getting the below error while activating the sap Fiori applications
Task Facade not implemented for provider. [/IWBEP/CX_MGW_TECH_EXCEPTION] (error).
I have applied all suggestions in my new fiori system from Masayuki Sekihara posted on his post.
but still I am getting same error message.
I got below error message.
1) If I selected a EC6FIORI system alias to ZTASKPROCESSING services then i got below error message.
Task Facade not implemented for provider.
Task Facade not implemented for provider. [/IWBEP/CX_MGW_TECH_EXCEPTION] (error).
2) some time I got different error message if I selected FIORI system alias to ZTASKPROCESSING.
I have shared below my system Support Package level and all configurations.
Component
Release
SP-Level
Support Package
Short description of comment
SAP_BASIS
740
4
SAPKB74004
SAP Basis Component
SAP_ABA
740
4
SAPKA74004
Cross-Application Component
SAP_GWFND
740
6
SAPK-74006INSAPGWFND
SAP Gateway Foundation
SAP_UI
740
7
SAPK-74007INSAPUI
User Interface Technology
PI_BASIS
740
4
SAPK-74004INPIBASIS
Basis Plug-In
ST-PI
2008_1_700
8
SAPKITLRD8
SAP Solution Tools Plug-In
SAP_BW
740
4
SAPKW74004
SAP Business Warehouse
IW_PGW
100
5
SAPK-10005INIWPGW
Process Gateway
MDG_FND
747
2
SAPK-74702INMDGFND
MDG Foundation
SAP_AP
700
30
SAPKNA7030
SAP Application Platform
SAP_BS_FND
747
2
SAPK-74702INSAPBSFND
SAP Business Suite Foundation
WEBCUIF
747
2
SAPK-74702INWEBCUIF
SAP Web UI Framework
MDG_APPL
617
2
SAPK-61702INMDGAPPL
MDG Applications
SAP_APPL
617
2
SAPKH61702
Logistics and Accounting
SAP_FIN
617
2
SAPK-61702INSAPFIN
SAP_FIN
SAP_HR
604
66
SAPKE60466
Human Resources
SAP_HRCAR
604
66
SAPK-60466INSAPHRCAR
Sub component SAP_HRCAR of SAP_HR
SAP_HRCAT
604
66
SAPK-60466INSAPHRCAT
Sub component SAP_HRCAT of SAP_HR
SAP_HRCAU
604
66
SAPK-60466INSAPHRCAU
Sub component SAP_HRCAU of SAP_HR
SAP_HRCBE
604
66
SAPK-60466INSAPHRCBE
Sub component SAP_HRCBE of SAP_HR
SAP_HRCBR
604
66
SAPK-60466INSAPHRCBR
Sub component SAP_HRCBR of SAP_HR
SAP_HRCCA
604
66
SAPK-60466INSAPHRCCA
Sub component SAP_HRCCA of SAP_HR
SAP_HRCCH
604
66
SAPK-60466INSAPHRCCH
Sub component SAP_HRCCH of SAP_HR
SAP_HRCCL
604
66
SAPK-60466INSAPHRCCL
Sub component SAP_HRCCL of SAP_HR
SAP_HRCCN
604
66
SAPK-60466INSAPHRCCN
Sub component SAP_HRCCN of SAP_HR
SAP_HRCDE
604
66
SAPK-60466INSAPHRCDE
Sub component SAP_HRCDE of SAP_HR
SAP_HRCDK
604
66
SAPK-60466INSAPHRCDK
Sub component SAP_HRCDK of SAP_HR
SAP_HRCES
604
66
SAPK-60466INSAPHRCES
Sub component SAP_HRCES of SAP_HR
SAP_HRCFI
604
66
SAPK-60466INSAPHRCFI
Sub component SAP_HRCFI of SAP_HR
SAP_HRCFR
604
66
SAPK-60466INSAPHRCFR
Sub component SAP_HRCFR of SAP_HR
SAP_HRCGB
604
66
SAPK-60466INSAPHRCGB
Sub component SAP_HRCGB of SAP_HR
SAP_HRCHK
604
66
SAPK-60466INSAPHRCHK
Sub component SAP_HRCHK of SAP_HR
SAP_HRCID
604
66
SAPK-60466INSAPHRCID
Sub component SAP_HRCID of SAP_HR
SAP_HRCIE
604
66
SAPK-60466INSAPHRCIE
Sub component SAP_HRCIE of SAP_HR
SAP_HRCIN
604
66
SAPK-60466INSAPHRCIN
Sub component SAP_HRCIN of SAP_HR
SAP_HRCIT
604
66
SAPK-60466INSAPHRCIT
Sub component SAP_HRCIT of SAP_HR
SAP_HRCJP
604
66
SAPK-60466INSAPHRCJP
Sub component SAP_HRCJP of SAP_HR
SAP_HRCKR
604
66
SAPK-60466INSAPHRCKR
Sub component SAP_HRCKR of SAP_HR
SAP_HRCKW
604
66
SAPK-60466INSAPHRCKW
Sub component SAP_HRCKW of SAP_HR
SAP_HRCMX
604
66
SAPK-60466INSAPHRCMX
Sub component SAP_HRCMX of SAP_HR
SAP_HRCMY
604
66
SAPK-60466INSAPHRCMY
Sub component SAP_HRCMY of SAP_HR
SAP_HRCNL
604
66
SAPK-60466INSAPHRCNL
Sub component SAP_HRCNL of SAP_HR
SAP_HRCNO
604
66
SAPK-60466INSAPHRCNO
Sub component SAP_HRCNO of SAP_HR
SAP_HRCNZ
604
66
SAPK-60466INSAPHRCNZ
Sub component SAP_HRCNZ of SAP_HR
SAP_HRCPH
604
66
SAPK-60466INSAPHRCPH
Sub component SAP_HRCPH of SAP_HR
SAP_HRCPT
604
66
SAPK-60466INSAPHRCPT
Sub component SAP_HRCPT of SAP_HR
SAP_HRCQA
604
66
SAPK-60466INSAPHRCQA
Sub component SAP_HRCQA of SAP_HR
SAP_HRCRU
604
66
SAPK-60466INSAPHRCRU
Sub component SAP_HRCRU of SAP_HR
SAP_HRCSE
604
66
SAPK-60466INSAPHRCSE
Sub component SAP_HRCSE of SAP_HR
SAP_HRCSG
604
66
SAPK-60466INSAPHRCSG
Sub component SAP_HRCSG of SAP_HR
SAP_HRCTH
604
66
SAPK-60466INSAPHRCTH
Sub component SAP_HRCTH of SAP_HR
SAP_HRCTW
604
66
SAPK-60466INSAPHRCTW
Sub component SAP_HRCTW of SAP_HR
SAP_HRCUN
604
66
SAPK-60466INSAPHRCUN
Sub component SAP_HRCUN of SAP_HR
SAP_HRCUS
604
66
SAPK-60466INSAPHRCUS
Sub component SAP_HRCUS of SAP_HR
SAP_HRCVE
604
66
SAPK-60466INSAPHRCVE
Sub component SAP_HRCVE of SAP_HR
SAP_HRCZA
604
66
SAPK-60466INSAPHRCZA
Sub component SAP_HRCZA of SAP_HR
SAP_HRGXX
604
66
SAPK-60466INSAPHRGXX
Sub component SAP_HRGXX of SAP_HR
SAP_HRRXX
604
66
SAPK-60466INSAPHRRXX
Sub component SAP_HRRXX of SAP_HR
EA-IPPE
400
24
SAPKGPID24
SAP iPPE
EA-APPL
617
2
SAPK-61702INEAAPPL
SAP Enterprise Extension PLM, SCM, Financials
EA-DFPS
600
24
SAPKGPDD24
SAP Enterprise Extension Defense Forces & Public Security
EA-FIN
617
2
SAPK-61702INEAFIN
EA-FIN
EA-FINSERV
600
25
SAPKGPFD25
SAP Enterprise Extension Financial Services
EA-GLTRADE
600
24
SAPKGPGD24
SAP Enterprise Extension Global Trade
EA-HR
607
17
SAPK-60717INEAHR
SAP Enterprise Extension HR
EA-HRCAR
607
17
SAPK-60717INEAHRCAR
Sub component EA-HRCAR of EA-HR
EA-HRCAT
607
17
SAPK-60717INEAHRCAT
Sub component EA-HRCAT of EA-HR
EA-HRCAU
607
17
SAPK-60717INEAHRCAU
Sub component EA-HRCAU of EA-HR
EA-HRCBE
607
17
SAPK-60717INEAHRCBE
Sub component EA-HRCBE of EA-HR
EA-HRCBR
607
17
SAPK-60717INEAHRCBR
Sub component EA-HRCBR of EA-HR
EA-HRCCA
607
17
SAPK-60717INEAHRCCA
Sub component EA-HRCCA of EA-HR
EA-HRCCH
607
17
SAPK-60717INEAHRCCH
Sub component EA-HRCCH of EA-HR
EA-HRCCL
607
17
SAPK-60717INEAHRCCL
Sub component EA-HRCCL of EA-HR
EA-HRCCN
607
17
SAPK-60717INEAHRCCN
Sub component EA-HRCCN of EA-HR
EA-HRCDE
607
17
SAPK-60717INEAHRCDE
Sub component EA-HRCDE of EA-HR
EA-HRCDK
607
17
SAPK-60717INEAHRCDK
Sub component EA-HRCDK of EA-HR
EA-HRCES
607
17
SAPK-60717INEAHRCES
Sub component EA-HRCES of EA-HR
EA-HRCFI
607
17
SAPK-60717INEAHRCFI
Sub component EA-HRCFI of EA-HR
EA-HRCFR
607
17
SAPK-60717INEAHRCFR
Sub component EA-HRCFR of EA-HR
EA-HRCGB
607
17
SAPK-60717INEAHRCGB
Sub component EA-HRCGB of EA-HR
EA-HRCHK
607
17
SAPK-60717INEAHRCHK
Sub component EA-HRCHK of EA-HR
EA-HRCID
607
17
SAPK-60717INEAHRCID
Sub component EA-HRCID of EA-HR
EA-HRCIE
607
17
SAPK-60717INEAHRCIE
Sub component EA-HRCIE of EA-HR
EA-HRCIN
607
17
SAPK-60717INEAHRCIN
Sub component EA-HRCIN of EA-HR
EA-HRCIT
607
17
SAPK-60717INEAHRCIT
Sub component EA-HRCIT of EA-HR
EA-HRCJP
607
17
SAPK-60717INEAHRCJP
Sub component EA-HRCJP of EA-HR
EA-HRCKR
607
17
SAPK-60717INEAHRCKR
Sub component EA-HRCKR of EA-HR
EA-HRCKW
607
17
SAPK-60717INEAHRCKW
Sub component EA-HRCKW of EA-HR
EA-HRCMX
607
17
SAPK-60717INEAHRCMX
Sub component EA-HRCMX of EA-HR
EA-HRCMY
607
17
SAPK-60717INEAHRCMY
Sub component EA-HRCMY of EA-HR
EA-HRCNL
607
17
SAPK-60717INEAHRCNL
Sub component EA-HRCNL of EA-HR
EA-HRCNO
607
17
SAPK-60717INEAHRCNO
Sub component EA-HRCNO of EA-HR
EA-HRCNZ
607
17
SAPK-60717INEAHRCNZ
Sub component EA-HRCNZ of EA-HR
EA-HRCPH
607
17
SAPK-60717INEAHRCPH
Sub component EA-HRCPH of EA-HR
EA-HRCPT
607
17
SAPK-60717INEAHRCPT
Sub component EA-HRCPT of EA-HR
EA-HRCQA
607
17
SAPK-60717INEAHRCQA
Sub component EA-HRCQA of EA-HR
EA-HRCRU
607
17
SAPK-60717INEAHRCRU
Sub component EA-HRCRU of EA-HR
EA-HRCSE
607
17
SAPK-60717INEAHRCSE
Sub component EA-HRCSE of EA-HR
EA-HRCSG
607
17
SAPK-60717INEAHRCSG
Sub component EA-HRCSG of EA-HR
EA-HRCTH
607
17
SAPK-60717INEAHRCTH
Sub component EA-HRCTH of EA-HR
EA-HRCTW
607
17
SAPK-60717INEAHRCTW
Sub component EA-HRCTW of EA-HR
EA-HRCUN
607
17
SAPK-60717INEAHRCUN
Sub component EA-HRCUN of EA-HR
EA-HRCUS
607
17
SAPK-60717INEAHRCUS
Sub component EA-HRCUS of EA-HR
EA-HRCVE
607
17
SAPK-60717INEAHRCVE
Sub component EA-HRCVE of EA-HR
EA-HRCZA
607
17
SAPK-60717INEAHRCZA
Sub component EA-HRCZA of EA-HR
EA-HRGXX
607
17
SAPK-60717INEAHRGXX
Sub component EA-HRGXX of EA-HR
EA-HRRXX
607
17
SAPK-60717INEAHRRXX
Sub component EA-HRRXX of EA-HR
EA-PS
600
24
SAPKGPPD24
SAP Enterprise Extension Public Services
EA-RETAIL
600
24
SAPKGPRD24
SAP Enterprise Extension Retail
FINBASIS
600
24
SAPK-60024INFINBASIS
Fin. Basis
ECC-DIMP
600
23
SAPK-60023INECCDIMP
DIMP
ERECRUIT
600
24
SAPK-60024INERECRUIT
E-Recruiting
FI-CA
600
23
SAPK-60023INFICA
FI-CA
FI-CAX
600
23
SAPK-60023INFICAX
FI-CA Extended
HR-CEE
110_604
52
SAPK-60452INHRCEE
HR country version for CEE countries
HR-CEECBG
110_604
52
SAPK-60452INHRCEECBG
Sub component HR-CEECBG of HR-CEE
HR-CEECCO
110_604
52
SAPK-60452INHRCEECCO
Sub component HR-CEECCO of HR-CEE
HR-CEECCZ
110_604
52
SAPK-60452INHRCEECCZ
Sub component HR-CEECCZ of HR-CEE
HR-CEECGR
110_604
52
SAPK-60452INHRCEECGR
Sub component HR-CEECGR of HR-CEE
HR-CEECHR
110_604
52
SAPK-60452INHRCEECHR
Sub component HR-CEECHR of HR-CEE
HR-CEECHU
110_604
52
SAPK-60452INHRCEECHU
Sub component HR-CEECHU of HR-CEE
HR-CEECPL
110_604
52
SAPK-60452INHRCEECPL
Sub component HR-CEECPL of HR-CEE
HR-CEECRO
110_604
52
SAPK-60452INHRCEECRO
Sub component HR-CEECRO of HR-CEE
HR-CEECSI
110_604
52
SAPK-60452INHRCEECSI
Sub component HR-CEECSI of HR-CEE
HR-CEECSK
110_604
52
SAPK-60452INHRCEECSK
Sub component HR-CEECSK of HR-CEE
HR-CEECTR
110_604
52
SAPK-60452INHRCEECTR
Sub component HR-CEECTR of HR-CEE
HR-CEECUA
110_604
52
SAPK-60452INHRCEECUA
Sub component HR-CEECUA of HR-CEE
HR-CEEGXX
110_604
0
Sub component HR-CEEGXX of HR-CEE
HR-CEERXX
110_604
0
Sub component HR-CEERXX of HR-CEE
INSURANCE
600
23
SAPK-60023ININSURANC
SAP Insurance
IS-CWM
600
23
SAPK-60023INISCWM
Industry Solution Catch Weight Management
IS-H
600
34
SAPK-60034INISH
SAP Healthcare
IS-M
600
23
SAPK-60023INISM
SAP MEDIA
IS-OIL
600
23
SAPK-60023INISOIL
IS-OIL
IS-PS-CA
600
23
SAPK-60023INISPSCA
IS-PUBLIC SECTOR CONTRACT ACCOUNTING
IS-UT
600
23
SAPK-60023INISUT
SAP Utilities/Telecommunication
LSOFE
600
24
SAPK-60024INLSOFE
SAP Learning Solution Front-End
SEM-BW
600
24
SAPKGS6024
SEM-BW: Strategic Enterprise Management
GBAPP002
600
4
SAPK-60004INGBAPP002
GBAPP002
GBHCM002
600
11
SAPK-60011INGBHCM002
HCM Employee Requests (Leave)
GBHCM003
600
9
SAPK-60009INGBHCM003
HCM Manager Approvals (Time, Training, L
SRA002
600
3
SAPK-60003INSRA002
Time Recording OData Integration Compone
SRA010
600
3
SAPK-60003INSRA010
Staffing List OData Integration Componen
SRA017
600
3
SAPK-60003INSRA017
Create Purchase Order OData Integration
SRA018
600
3
SAPK-60003INSRA018
Purchase Order Status Tracking OData Int
UIAPP001
100
4
SAPK-10004INUIAPP001
UIAPP001 100: Add-On Installation
UIAPP002
100
3
SAPK-10003INUIAPP002
UIAPP002 100: Add-On Installation
UIGIB001
100
4
SAPK-10004INUIGIB001
UIGIB001 100: Add-On Installation
UIHCM002
100
4
SAPK-10004INUIHCM002
UIHCM002 100: Add-On Installation
UIHCM003
100
4
SAPK-10004INUIHCM003
UIHCM003 100: Add-On Installation
UISRA002
100
3
SAPK-10003INUISRA002
HTML5 Time Recording
UISRA010
100
3
SAPK-10003INUISRA010
HTML5 Staffing List
UISRA017
100
3
SAPK-10003INUISRA017
HTML5 Create Order
UISRA018
100
3
SAPK-10003INUISRA018
HTML5 Order Status Tracking
please help me to resolve that issue
Regards
Pankaj Kamble

Hi Team,
i have created new post.
SAP Fiori getting error message Check the URL parameters and the scenario definition. To check the scenario definition.
Scenario definition configuration screen short.
2) Also getting bellow error message
Property TaskDefinitionID not found in type WorkflowTask
Did not find error details
{"error":{"code":"005056A509B11EE1B9A8FEA8DE87F78E","message":{"lang":"en","value":"Property TaskDefinitionID not found in type WorkflowTask"},"innererror":{"transactionid":"E6A9CEE388D3F1EC940400155DC8D41B","timestamp":"20140428075136.7780000","Error_Resolution":{"SAP_Transaction":"Run transaction /IWFND/ERROR_LOG on SAP NW Gateway hub system and search for entries with the timestamp above for more details","SAP_Note":"See SAP Note 1797736 for error analysis (https://service.sap.com/sap/support/notes/1797736)"}}}}
Regards
Pankaj Kamble

Problem in creating new implementation for filter dependent badi

Hi Experts,
I want to use badi NOTIF_EVENT_POST.It is a filter dependent badi. It is asking filter type while implementing thro se19. Could anyone pls tel me how to create new implementation for the filter dependent badi. Existing filter type is QMART. is there any problem if i change the filter type?
Thanks in Advance!

Hi ,
NOTIF_EVENT_POST is filter dependent and filter values are based on QMART value in table TQ80. You need to specify the filter value ie : QMART value before implimentation , before that check all active implimentations for the same , if u have to impliment on same filter value , you need to deactivate the one which is implimented on same filter value .
You are not supposed to change the filter type.
Regards,
Vamsi
Edited by: CH. VAMSHI on Sep 29, 2009 11:58 AM

Configuring Kodo default implementation for field of Collection type

If I am not mistaken default implementation for field of Collection type in
Kodo is
LinkedList based proxy. It would be great if it were possible to configure
Kodo to use a proxy of my choosing
I did some tests and it seems to me that ArrayList is much more efficient
than Linked list (see below)
Is there any specific reason I am not aware of that makes LinkedList better
than array list
In my applications all collections a relatively small (or at least most of
my collections are definitely small)
and since I use Collection interface there is no inserts into middle of my
collections - only appends (which ArrayList handles very well)
So my question is can I make Kodo to use ArrayListProxy for fields of
Collection type
(except of course using ArrayList field instead of Collection which I do not
want to do)
below is some statistics on collection performance (populating and iterating
collections)
the same test against 3 collections implementations (JDK 1.4.1)
Not only ArrayList by far the fastest and memory friendly it also garbage
collected much sooner and better -
I show here max memory consumption and last to would not be garbage
collected till all memory is in use (old generation GC)
and ArrayList seems to be collected by young gen GC because it was collected
very quickly between test cycles why other only when all memory was used
So please make ArrayList your default collection implementation :-)
Small collection size (40)
time(ms) memory(kb)
ArrayList 5,218 62,154
LinkedList 14,125 240,066
HashSet 27,000 311,825
the same but using using random inserts - append(index, object) rather than
append(object):
ArrayList 8937, 53591
LinkedList 15047, 240066
Larger collection size (200)
ArrayList 4860, 47709
LinkedList 18468, 290704
HashSet 34391, 422282
the same but using using random inserts - append(index, object) rather than
append(object):
ArrayList 11844, 47709
LinkedList 25766, 290704

You should be able to accomplish this fairly easily by extending
SimpleProxyManager:
http://solarmetric.com/Software/Documentation/2.4.3/docs/javadoc/com/solarmetric/kodo/util/SimpleProxyManager.html
and overriding the appropriate methods (getCollectionCopy and
getCollectionProxy).
On Mon, 12 May 2003 12:26:21 -0400, Alex Roytman wrote:
If I am not mistaken default implementation for field of Collection type in
Kodo is
LinkedList based proxy. It would be great if it were possible to configure
Kodo to use a proxy of my choosing
I did some tests and it seems to me that ArrayList is much more efficient
than Linked list (see below)
Is there any specific reason I am not aware of that makes LinkedList better
than array list
In my applications all collections a relatively small (or at least most of
my collections are definitely small)
and since I use Collection interface there is no inserts into middle of my
collections - only appends (which ArrayList handles very well)
So my question is can I make Kodo to use ArrayListProxy for fields of
Collection type
(except of course using ArrayList field instead of Collection which I do not
want to do)
below is some statistics on collection performance (populating and iterating
collections)
the same test against 3 collections implementations (JDK 1.4.1)
Not only ArrayList by far the fastest and memory friendly it also garbage
collected much sooner and better -
I show here max memory consumption and last to would not be garbage
collected till all memory is in use (old generation GC)
and ArrayList seems to be collected by young gen GC because it was collected
very quickly between test cycles why other only when all memory was used
So please make ArrayList your default collection implementation :-)
Small collection size (40)
time(ms) memory(kb)
ArrayList 5,218 62,154
LinkedList 14,125 240,066
HashSet 27,000 311,825
the same but using using random inserts - append(index, object) rather than
append(object):
ArrayList 8937, 53591
LinkedList 15047, 240066
Larger collection size (200)
ArrayList 4860, 47709
LinkedList 18468, 290704
HashSet 34391, 422282
the same but using using random inserts - append(index, object) rather than
append(object):
ArrayList 11844, 47709
LinkedList 25766, 290704

Exception "not implemented for class oracle.jdbc.driver.T4CNumberAccessor"

Hello I'm having some troubles dealing with 'java.sql.Date' I'm working with express edition database and I have three classes(different packages)
1.Mapper
2.Objects Class
3.ConsoleTest
I need to get an arraylist of objects, some of which contain dates, but when try to do it I get this exception
"java.sql.SQLException: Invalid column type: getDate not implemented for class oracle.jdbc.driver.T4CNumberAccessor"
Do you have any idea how I can implement the getDate method for this T4CNumberAccessor
Here are the methods that I'm using
1.Mapper
public ArrayList<Object> getAllTaskAuctions(Connection con)
 ArrayList<Object> l1 = new ArrayList<Object>();
 String SQLString1 = "select * from taskauction natural join tasks";
PreparedStatement statement=null;
try
//=== get taskauctions natural join tasks
statement = con.prepareStatement(SQLString1);
ResultSet rs = statement.executeQuery();
while(rs.next())
l1.add(new TaskAuction(rs.getInt(1), rs.getInt(2), rs.getInt(3),
rs.getDate(4), rs.getDate(5), rs.getInt(6)));
l1.add(new Task(rs.getInt(1), rs.getInt(2), rs.getString(3),
rs.getString(4), rs.getString(5), rs.getString(6), rs.getInt(7)));
catch (Exception exc)
System.out.println("Fail in TaskAuctionMapper - getAllTaskAuctions");
System.out.println(exc);
return l1;
2.ConsoleTest class
Connection con;
 public Connection getConnection(){
 try{
 Class.forName("oracle.jdbc.driver.OracleDriver");
 con = DriverManager.getConnection(
 "jdbc:oracle:thin:@localhost:1521:XE", "Project", "123" );
 //username/password@[/]host[:port][service_name]
 catch (Exception e)
 { System.out.println("fail in getConnection()");
 System.out.println(e); }
 return con;
 public static void main(String[] args) {
 ConsoleTest ct = new ConsoleTest();
 TaskAuctionMapper tam1 = new TaskAuctionMapper();
ArrayList<Object> alt1 = tam1.getAllTaskAuctions(ct.getConnection());
Iterator<Object> itr1 = alt1.iterator();
while (itr1.hasNext())
TaskAuction taskauct = (TaskAuction) itr1.next();
//Problem, exception traced to TaskAuctionMapper
System.out.println(
 "Task ID: " + taskauct.getTaskid()+ ", "+
 "StartDate: "+ taskauct.getStartdate()+", "+
 "User ID: " + taskauct.getUserid());
 }

Found the answer, I shouldn't use integers as parameters of column index in the result set, but instead use String to mark the fields :)

Reading Header data in a SOAP Envelope for SOAP Sender Adapter

Hello All,
Am using a SOAP sender adapter and want to use the data inside the SOAP Header for some routing purpose(extended receiver determination). Any SOAP message coming into XI will look something like below. But XI will pass the contents of <SOAP-ENV:Body> to Payload and <SOAP-ENV:Header> to the SOAP Header category you can see that in SXMB_MONI.
Is there a way to read the data in my SOAP Header to be later used in my extended receiver determination.
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:Q-ENV="/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <SOAP-ENV:Header>
 <Q-ENV:Header>
 <Q-ENV:Sender-Id>1</Q-ENV:Sender-Id>
 <Q-ENV:Receiver-Id></Q-ENV:Receiver-Id>
 <Q-ENV:Correlation-Id></Q-ENV:Correlation-Id>
 <Q-ENV:Message-Id></Q-ENV:Message-Id>
 <Q-ENV:Date-Sent></Q-ENV:Date-Sent>
 <Q-ENV:Document-Type></Q-ENV:Document-Type>
 <Q-ENV:Message-Format></Q-ENV:Message-Format>
 </Q-ENV:Header>
 </SOAP-ENV:Header>
 <SOAP-ENV:Body>
 <Q-ENV:Body>
 <Q-ENV:Content-Type>text/xml</Q-ENV:Content-Type>
 <Q-ENV:Message-Type></Q-ENV:Message-Type>
 <Q-ENV:Encoding>UTF-8</Q-ENV:Encoding>
 <Q-ENV:Message-Body>
 </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Thanks for your replies in advance.
Regards,
Prashanth

Hello,
but they were not getting any response back from XI and the sending system kept resending the message.. may be it was acting like a HTTP post.
The method that is used by the native SOAP Adapter is always HTTP Post. Not sure why you are not getting a response, have you checked the outbound firewall of the sending party or the inbound firewall of XI? To which SOAP URL are you sending to?
Hope this helps,
Mark

SOAP Fault for Application errors

Hi,
I would like to know whether it is OK to raise a SOAP fault for Application or system level exceptions. For example, I'm searching for a user with an ID as request , If the ID is invalid(User is not found) is it OK to raise the SOAP Fault.
Let me know your views regarding the same.

Hi,
With the above explination , please see the below links..
http://help.sap.com/saphelp_nw04/helpdata/en/d0/d4b54020c6792ae10000000a155106/content.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7521a237-0701-0010-499b-b3285b789c0d
/people/thomas.jung3/blog/2005/01/11/publishing-abap-webservices-to-an-external-uddi-server
/people/sap.user72/blog/2005/11/17/xi-how-to-publish-wsdl-generated-from-xi-to-uddi
Alert rule for SOAP adapter
Monitoring problem in async SOAP receiver adapter
Trapping AF errors using Alert framework in XI 3.0 SP13
Alert Configuration
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2f2a9fa2-0a01-0010-32ac-d281db722b86
SOAP Lookup - /people/bhavesh.kantilal/blog/2006/11/20/webservice-calls-from-a-user-defined-function
Regards
Chilla..
Points rewarded if it is useful..

Unable to create the implementation for BBP_PD_DOWNLOAD badi

Hi ,
Iam trying to create a new implementation for this BADI BBP_PD_DOWNLOAD as zbbp_pd_download but when iam trying to activate it .iam getting a message that already active implementation is there and i cannot create a new implementation unless i deactivate the other one.since it is a standard one i cannot deactivate it .
Has any one used this earlier . any inputs on this wil be of great help .
Thanks in advance

Hi
You can create any number of Customer Implementations, provided only one is active at a time.
Here are the steps ->
Either Using SE18 / SE19 Transaction, or
After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.
If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:
1. In the dialog box, enter a name for the implementation of the Add-In and choose Create. (Say ZBADI)
The system displays the initial screen for creating Business Add-In implementations.
2. On this screen, enter a short description for you implementation in the Implementation Short Text field.
3. If you choose the Interface tab, you will notice that the system has filled in the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
4. Save your entries and assign the Add-In to a package.
5. To edit a method, double-click its name.
6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.
7. Save and activate your code. Navigate back to the Change Implementation screen.
Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not carry out the following step:
8. Choose Activate.
When the application program is executed, the system carries out the code in the method you wrote.
Regards
- Atul

Error on SOAP Receiver for Axis

Hi all,
Is there anybody to help for solution?
Thanks.
Error on SOAP Receiver for axis
Error Message
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.ejb.EJBException: Exception in getMethodReady() for stateless bean sap.com/com.sap.aii.axis.appxml|com.sap.aii.adapter.axis.ejb.jarxml|AFAdapterBean; nested exception is: com.sap.engine.services.ejb3.util.pool.PoolException: javax.ejb.EJBException: Exception raised from invocation of public void com.sap.aii.adapter.axis.modules.AFAdapterBean.ejbCreate() throws javax.ejb.CreateException method on bean instance com.sap.aii.adapter.axis.modules.AFAdapterBean@3ff5ea5d for bean sap.com/com.sap.aii.axis.appxml|com.sap.aii.adapter.axis.ejb.jarxml|AFAdapterBean; nested exception is: javax.ejb.CreateException: java.lang.NoClassDefFoundError: org/apache/axis/types/URI$MalformedURIException</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

We deployed com.sap.aii.af.axisproviderlib.sda to use SOAP for axis.
We sent data from SAP to Axis, error below ocured?
What must we do to solve problem?
Thanks.
Error
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: org.apache.axis.ConfigurationException: handler is not instantiated org.apache.axis.ConfigurationException: handler is not instantiated at com.sap.aii.adapter.axis.modules.HandlerCore.process(HandlerCore.java:73) at com.sap.aii.adapter.axis.modules.HandlerBean.process(HandlerBean.java:75) at sun.reflect.GeneratedMethodAccessor360_10000.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy2634_10000.process(Unknown Source) at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:275) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy1431_10000.process(Unknown Source) at com.sap.aii.af.app.listener.AFWListenerBean.onMessage(AFWListenerBean.java:332) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy1479_10000.onMessage(Unknown Source) at com.sap.engine.messaging.impl.spi.ServicesImpl.deliver(ServicesImpl.java:314) at com.sap.aii.adapter.xi.ms.XIEventHandler.onDeliver(XIEventHandler.java:1000) at com.sap.engine.messaging.impl.core.queue.consumer.RequestConsumer.onMessage(RequestConsumer.java:73) at com.sap.engine.messaging.impl.core.queue.Queue.run(Queue.java:921) at com.sap.engine.messaging.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

BEA SOAP implementation for WL5.1

Similar Messages

Maybe you are looking for