Problem with special characters when calling web services via ISG

Hi all,
I have a problem when trying to send or retrieve strings containing some special characters via Integrated SOA Gateway.
For example, when I call a PL/SQL function via ISG that returns a string containing curling single and double quote characters, these are not represented by valid XML character entity references. So when trying to open the response XML (returned by ISG) in a browser, I get a parser error...
Has anybody had a similar experience with ISG? How can I resolve that - is it an ISG bug?
Thanks
Carolin

XML Parsing Error: not well-formed
Location: file:///C:/Users/sanders/Desktop/Text3.xml
Line Number 4734, Column 54: <DESCRIPTION>Overhead Track Lighting 4?</DESCRIPTION>Do you get the same error if you change the description from "Overhead Track Lighting 4?" to "Overhead Track Lighting 4"?
Do you have any invalid characters?
BI Publisher Reports End With Error When There Is An Ampersand Character ( & ) On The Xml Data File [ID 1081175.1]
Journal Entries Report Doesn'T Yield Output: Java Heap Error [ID 1115663.1]
Thanks,
Hussein

Similar Messages

Problems with special characters when exporting to LDAP

Hi,
Im using standard report RPLDAP_EXTRACT to export data to LDAP. The problem is that the special characters (in this case polish letters) do not save correctly (we get for instance '?' instead of normal letter)
I tried switching the configuration of the RFC destination (used: 'found communication Code Page option') but I get a message: "Your selection is restricted" and cannot make any changes.
Can anyone please help in this matter?
Regards,
Hubert

1) Your database should be able to handle and properly store all the supported charactersets needed. With UTF you are in the clear regarding storing all that kind off idfferent characters
See http://www.oracle.com/technology/tech/globalization/htdocs/nls_lang%20faq.htm
2) The recieving party (the cleint software) hopefully has a character set that supports all the characters that are offered by the database and can encode them. If not then you get toe upside down question markt or dark squares or something alike. If the client software is a browser, for instance windows internet explorer, then most encoding settings are buildin and you only have to switch. Sometimes you will have to add extra language support on Windows Internet Explorer. This behaviour is also the same on thick clients. Oracle by default sets these parameters in the registry, but on windows the can be overrulled on several levels like on system level, user level (start --> settings -- control panel --> system --> advanced tab --> environment settings) and or during execution via a app. configuration file or an export of the system variable on the command prompt... A unified business approach for how to handle this is needed otherwise you will have too look for these kinds off issues always all over the place (on windows and/or linux etc).
Have a look at Mark's example of how things work regarding UTF and the like on the FAQ URL on this forum and the URL as show above. If completely lost, you will have to read up on it in the Oracel globalization / NLS manuals and see what is appropriate / can be done in your environment.

Problem with special characters (&) when printing using XSL-FO ...

Hello everybody !!
I have a problem when I want to print a Report with a link to a URL where the character "&" is present :
I want to have something like : src="file:///...webfile?param1=val1*+_&_+*param2=val2"
In my XSL-FO file, I wrote : src="file:///...webfile?param1=<xsl:value-of select="IDARTICLE"/>*+_<xsl:text>&</xsl:text>_+*param2=<xsl:value-of select="MARQUE"/>"
When I try this only with FOP, it works. However, when I upload the XSL-FO file to ApEx, it says my PDF file is corrupted when I want to open it.
What do I have to put the '&' symbol when I want to print the Report ??
Could anyone help me ??
Thanks by advance,
Pierre C.

I believe this relates to something I have actually found in my own testing.
It is probably due to the Template not being URLEncoded prior to transmission to the FOP processor.
I actually determined that special URL characters, like '+' and '&', are lost on transmission because the type of submission is POST with x-www-form-urlencoded, but the fields are not actually encoded entirely. The XML Element contents are encoded prior to transmission in order to preserve data.
Work around would be to URLEncode the template as it sits in the WWV_FLOW_REPORT_LAYOUTS. I have been able to successfully get around the problem by doing that.
-Richard
The post I describe the problem: Reports Layout->storing custom report layouts that aren't FOP/RTF
The post under the enhancement request thread: Re: Enhancement Request Thread : Post 3.1

Problems with special characters like "u00F6" "u00E4" "u00FC"

Hi,
we currently face some major problems with special characters like "ö" "ä" "ü". First I thought it is a SP02 specific problem but it still doesn't work with SP03.
When I start an import the import manager shows correct converted value. "ö"s "ä"s "ü"s are displayed correctly. But after I've done the import I look into the Data manager and I see instead of these characters charcaters like "̈". (note: the character should show a little square box - but the forum cannot desplay it)
How can I solve this problem?
Regards
Nico

Hi Nico
Just try it out the following steps, hope it solves ur issue.
To set one or more values back to their original values:
1. In the Import Manager Source Values grid, select the values that you want to set back to their original values.
2. Right-click on one of the values and choose Set to Original Value from the context menu, or choose Values > Apply Value Conversion Filter > Set to Original Value from the main menu.
3. MDME sets each value back to its original value, which appears in black in the Source Values grid.
NOTE : You can use the Set to Original Value filter only at the value-level and not at the field level.
thanks
Alexander

ORA-28868 error when calling Web service over HTTPS from PL/SQL utl_http

I am getting error message ORA-28868 error when calling Web service over HTTPS from PL/SQL utl_http PL/SQL package,
when browsed through some of the messages they point to setting Oracle Wallet Manager.
I am trying to connect
Any idea on how to resolve this issue ?
your input is appreciated.
Thanks
Ravi

Duplicate post ... please ignore.

Problems with special characters in InputStream or XPath

Hello everyone,
I am having problems with special characters such as ", ', - and so on, everything becomes ? (questionmark). (Not with special nordic characthers (å,æ,ø) though.)
The encoding of the XML is UTF-8, and the server that holds the webservice is setting encoding to UTF-8 also, so no conflict there.
What I have done is something like this:
{code}
String url = "http://www.formula1.com/rss/news/latest.rss"; // This is not the feed I use, it is a custom XML document
InputSource is = new InputSource(url);
DocumentBuilderFactory fct = DocumentBuilderFactory.newInstance();
DocumentBuilder builder = fct.newDocumentBuilder();
Document doc = builder.parse(is);
Element rootElement = doc.getDocumentElement();
XPathFactory factory = XPathFactory.newInstance();
XPath xPath = factory.newXPath();
out.print(xPath.evaluate("/rss/channel/title", rootElement)); // The xml is not a RSS feed, this is just an example.
{code}
Please let me know what I am doing wrong, or give me a hint of how to solve this in another way.
Best regards,
G.Hansen
Edited by: G.Hansen on Mar 24, 2009 2:39 AM

Hello, thanks for you reply. I had to rewrite your code a little, and I think that your code would not really compile, if you tried yourself :-)
I ended up with something like this:
our environment is running in 1.4 mode, so I could not use the for-each loop :-(
public String printEntities(String s) {
 char[] sArray = s.toCharArray();
 StringBuffer sb = new StringBuffer();
 for (int i = 0; i < sArray.length; i++) {
 if (sArray[i] > 256)
 sb.append("&#x" + Integer.toHexString(sArray) + ";");
 } else
 sb.append(sArray[i]);
 return sb.toString();

Calling web service via utl_dbws with unbounded return values

Hello, everyone.
I'm trying to use utl_dbws to call web service from Oracle DB 10 g.
WS has unbounded return value:
<xs:element maxOccurs='unbounded' minOccurs='0' name='return' type='xs:string'/>
I'm setting return paramter in web service call handler like this:
sys.UTL_DBWS.set_return_type(l_h_service_call, cs_qname_type_string);
and when I'm trying to call it from PL/SQL function I'm getting an error:
ORA-29532: Java call terminated by uncaught Java exception:
deserialization error: XML reader error: unexpected character content: "s2"
ORA-06512: at "SYS.UTL_DBWS", line 388
ORA-06512: at "SYS.UTL_DBWS", line 385
ORA-06512: at line 38
I've tried to return values by out parameters and got the same exception.
It looks like utl_dbws needs to know parameters count before calling.
Have anyone succeded in getting arrays from Web Service call?
This is a part of wsdl:
<xs:complexType name='getProcessList'>
<xs:sequence>
<xs:element minOccurs='0' name='nameMask' type='xs:string'/>
</xs:sequence>
</xs:complexType>
<xs:complexType name='getProcessListResponse'>
<xs:sequence>
<xs:element maxOccurs='unbounded' minOccurs='0' name='return' type='xs:string'/>
</xs:sequence>
</xs:complexType>
Throught SoapUI I can produce such kind of request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:proc="http://processmanager.argustelecom.ru/">
<soapenv:Header/>
<soapenv:Body>
<proc:getProcessList>
<processNameMask>*</processNameMask>
</proc:getProcessList>
</soapenv:Body>
</soapenv:Envelope>
and get a response:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<ns2:getProcessListResponse xmlns:ns2="http://processmanager.argustelecom.ru/">
<return>s1</return>
<return>s2</return>
<return>s3</return>
<return>s4</return>
</ns2:getProcessListResponse>
</env:Body>
</env:Envelope>
PL/SQL function:
DECLARE
cs_qname_type_string CONSTANT sys.UTL_DBWS.qname
:= sys.UTL_DBWS.to_qname('http://www.w3.org/2001/XMLSchema', 'string') ;
cs_qname_type_int CONSTANT sys.UTL_DBWS.qname := sys.UTL_DBWS.to_qname('http://www.w3.org/2001/XMLSchema', 'int');
cs_qname_type_any CONSTANT sys.UTL_DBWS.qname
:= sys.UTL_DBWS.to_qname('http://www.w3.org/2001/XMLSchema', 'anyType') ;
cs_endpoint CONSTANT VARCHAR2(256) := 'http://server:8080/process-manager/ProcessManager';
l_service sys.UTL_DBWS.service;
l_service_qname sys.UTL_DBWS.qname;
l_port_qname sys.UTL_DBWS.qname;
l_operation_qname sys.UTL_DBWS.qname;
l_h_service_call sys.UTL_DBWS.call;
l_params sys.UTL_DBWS.anydata_list;
l_ret_val SYS.ANYDATA;
BEGIN
l_service_qname := sys.UTL_DBWS.to_qname(NULL, 'ProcessManagerService');
l_service := sys.UTL_DBWS.create_service(l_service_qname);
l_port_qname := sys.UTL_DBWS.to_qname(NULL, 'ProcessListServiceBinding');
l_operation_qname := sys.UTL_DBWS.to_qname('http://processmanager.argustelecom.ru/', 'getProcessList');
l_h_service_call := sys.UTL_DBWS.create_call(l_service, l_port_qname, l_operation_qname);
sys.UTL_DBWS.set_target_endpoint_address(l_h_service_call, cs_endpoint);
-- return type
sys.UTL_DBWS.set_return_type(l_h_service_call, cs_qname_type_any);
-- param type
sys.UTL_DBWS.ADD_PARAMETER(l_h_service_call, 'processNameMask', cs_qname_type_string, 'ParameterMode.IN');
l_params(1) := anydata.convertvarchar2('*');
l_ret_val := sys.UTL_DBWS.invoke(l_h_service_call, l_params);
IF l_ret_val IS NULL THEN
DBMS_OUTPUT.put_line('l_ret_val is null');
ELSE
DBMS_OUTPUT.put_line('l_ret_val is not null');
END IF;
sys.UTL_DBWS.release_call(l_h_service_call);
END;
Edited by: Ilya on 03.12.2008 3:50

Hi Tony
I'm not sure if you would have solved your problem by now, but with my recent experience with the utl_dbws package, for doc lits with complex data types, you have to call the service with an XML request, as opposed to passing the param array.
If you still need details, reply accordingly.
Ta
cT

Problem with signed SAML assertion and Web Services Manager

Folks,
I’m having some issues trying to generate a proper signed SAML assertion using JDeveloper 10.1.3. I am securing a java proxy class using the wizard as described in http://www.oracle.com/technology/products/jdev/howtos/1013/wssecure/10gwssecurity_howto.html .
On the OWSM side, I have a service that I am securing with SAML - Verify WSS 1.0 Token. If I set the "Allow signed assertions only" property to false I can complete the service call. However, when it is set to true I am receiving the following fault: javax.xml.rpc.soap.SOAPFaultException: SAML token verification failed.
When I examine the message going to OWSM in a packet analyzer, it is missing the signature in the SAML assertion. The <saml:Assertion> tags looks like:
 <saml:Assertion MajorVersion="1" MinorVersion="1"
 xmlns="urn:oasis:names:tc:SAML:1.0:assertion"
 xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion"
 AssertionID="yM0oqZgF0N1a1td6yzKgOQ22"
 IssueInstant="2007-01-23T17:15:27Z"
 Issuer="HealthMarkets_s3">
 <saml:Conditions NotBefore="2007-01-23T17:15:27Z"
 NotOnOrAfter="2007-01-24T17:15:27Z"/>
 <saml:AuthenticationStatement AuthenticationInstant="2007-01-23T17:15:27Z"
 AuthenticationMethod="urn:oasis:names:tc:SAML:1.0:am:password">
 <saml:Subject>
 <saml:NameIdentifier Format="urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified">client_s3</saml:NameIdentifier>
 <saml:SubjectConfirmation>
 <saml:ConfirmationMethod>urn:oasis:names:tc:SAML:1.0:cm:sender-vouches</saml:ConfirmationMethod>
 </saml:SubjectConfirmation>
 </saml:Subject>
 </saml:AuthenticationStatement>
 </saml:AssertionI have selected the Sign Outbound Messages in step 3 of the Secure Web Proxy Wizard. This step uses the DSA-SHA1 algorithm.
Any help is greatly appreciated.
Thanks in advance,
Joseph

Thanks for the response. I am not using any pages for this application yet... just calling the web service from SOAP UI or any Web Service testing tool causes the problem.
All that has to be done to replicate it is to build a simple EJB 3.0 JPA bean using the entities from tables wizard and then add named query as follows:
@NamedQuery(name = "BomHeader.findByDesc", query = "select o from BomHeader o where o.bomDesc like :p_bomDesc")
then build a session bean with the wizard that includes the JPA persistence unit and the entity and subsequently use the wizard to wrap the session bean in a web service.
The whole replication process should take 5 minutes if you have some database tables to work with. It breaks when the web service is called.
Thanks in advance

Problems with special characters with XML/PDF printing

Hi,
Our setup:
Apex Listener 2.0.5
Oracle DB 11G
Weblogic
Apex 4.2.2
Various recent major browsers
We used this blog post so we could do some PDF printing with APEX Listener:
http://marcsewtz.blogspot.be/2013/04/pdf-printing-with-oracle-application.html
The problem is special characters. For example the "&" sign comes out as "%26amp;" when we export an XML.
Could anyone provide some insights of what we can do to fix this?
Regards,
Joni

This is a known bug.
https://support.oracle.com/epmos/faces/BugDisplay?_afrLoop=957905848396285&id=18282188&_afrWindowMode=0&_adf.ctrl-state=168vq5zhn3_233
The bug 18282188 has been fixed in Apex 4.2.5 version.
Upgrade the Apex version to 4.2.5 when it is available.

Problems with special characters in JSP app

Hello!
I am working for a JSP application which uses special characters.
The database used is a Novell MySQL version, it is fine.
I use Tomcat, Apache.
I do not think that the versions are important.
ON NT:
The application works fine with special characters.
Obs: I tried only with Tomcat; I didn't use Apache.
ON NOVELL:
If I try to insert some special characters,
they arrive just fine into the database.
The problem is when I want to display them.
I tried with jsp directive to set the charset,
or with HTML meta tag - no result al all.
Everytime I use the same work station, and the same browser to do the tests.
Please help with any ideas.
Another question, maybe relayed:
Can I set Tomcat so that when it creates the servlets it uses a custom charset I can indicate?
THANK YOU!

The characters I want to use are french characters, e-acute, etc.
I take the data with request.getParameter, POST method, etc.

Problem with special characteres

Hi. I have a problem with java. I�m making an application that works with special characters and displays correctly on my local machine, as I use escape characters such as ì for �. The problem is when I deploy the application on a unix machine. All of the special characters (�, �, �, etc) appear like a �?� (question mark). Any tips, please?
Thanks in advance

Andy2008 wrote:
Hi. I have a problem with java. Im making an application that works with special characters and displays correctly on my local machine, as I use escape characters such as ì for �. The problem is when I deploy the application on a unix machine. All of the special characters (, �, �, etc) appear like a ? (question mark). Any tips, please?First step: read [this excellent introduction into Unicode|http://www.joelonsoftware.com/articles/Unicode.html], it will give you the basics you need to solve this problem.
How do you input and output those characters? Simply print them to the console? Or write them to a HTML file (since you mention &<something>; notation)?
"?" is normally the result when you convert a String (which is always in UTF-16 encoding in Java) to an encoding that can't represent your characters (ASCII for example).

TimeoutException - when calling web services method that opens a PDF

I am updating a legacy program which uses Adobe Acrobat 7.0 Professional. The idea is that the client will call web service methods, which handle opening a PDF, reading from or writing to the PDF, saving if necessary, and closing. It then returns the data (if reading) to the client.
The only issue with this that I'm having is that the client will pause for about 60 seconds, and throw a TimeoutException.
I know that the method on the web services end is working, because I wrote a quick driver which calls the very same method, but it executes normally, and works perfectly.
My question is basically, is there anything that would cause the client to hang/freeze when calling the web services method to do this task? Everything is running on my workstation, and I've debugged to see that the filename being passed is the same in both tests.
Thanks!

Thank you, I somehow missed seeing that subforum. I reposted it in that forum instead. This thread can be deleted/closed. Thanks!

ICM_HTTP_SSL_ERROR when calling web service

Summary: ICM_HTTP_SSL_ERROR was met when I called web service in ABAP with logical port & RFC Connection of type G.
Details:
1. the test of RFC Connection of type G in SM59 works OK, with SSL inactive and basic authentication.
2. while in ABAP code, the calling to web service throws ICM_HTTP_SSL_ERROR, using the logical port with the RFC Connection as HTTp Destination.
3. also, with using URL directly in logical port settings, the calling to web service in ABAP throws ICM_HTTP_SSL_ERROR.
I searched threads and blog for ICM_HTTP_SSL_ERROR, it seems others met ICM_HTTP_SSL_ERROR in SM59; while my case is the test in SM59 works well.
Anybody can help?
Thanks and kind regards.
Said

Dear Sayid,
The document which you had mentioned here is really helpful.
I'am working on Digital Signature for Form16 in SAP.I stucked up with the same issue.
I went through the document of
Enabling SSL and Client Certificates on the SAP J2EE Engine by Angel Dichev
in that document i went through one note
Note: Per default, the SAP J2EE Engine uses the u201Cssl-credentialsu201D entry for SSL, which contains a
public-key certificate that has been signed by a test CA. Although this certificate can be used for
testing purposes, a certificate that has been signed by a well-known, productive CA should be used
when in production mode.
right now i'am doing it for testing purpose, in the above note it is mentioned that we can use default credentials but when i see the expiry date of this default credentials in my server 1) SSL-Credentials 2)SSL-Credentials-cert it is given that these certificates are Valid Not After 2005 year.
So i got confused now whether to use the default credentials or not.
Please guide me with a solution.
With Regards,
Pradeep.B

Problems with Special Characters on Exchange Email

Hello:
People I have a issue with our Corporate Email on my Iphone. We use Exchange 2003 and we have users with special characters on his emails address.
I receive fine the email, just appear a errors on the display name. The issue is when I try to reply thie email. A error message popup said:
Invalid Address
"email with special characters" does not appear to be a valid email address. Do you want to send it anyway?
If I press Yes, Iphone try to send the message But I receive another error message:
Cannot send Mail
An error ocurred while delivering this message.
Any Help or Idea?
Here My Email Configuration
Email = Email
Server = Server IP
Domain = Work Domain Name
Username = my user id
Password = my password
Description = Work
Use SSL = ON
S/Mime = Off

When I Said "we have users with special characters on his emails address" its mean users with ñ,ó, ú, Ñ on his emails address.
When I said "just appear a errors on the display name" I mean characters like ÂÃ±¡
Thanks

Hit TransitionException when call web service in bpm

hello, my mesage of exception like follows:
 
com.sap.glx.core.kernel.api.TransitionException: An exception occurred while executing the script "_FileIn:AUTOMATED_ACTIVITY_FI_Notice_PSP(
 com.sap.glx.adapter.BPMNAdapter:Token_0_CSS_FileIn_58b390c7e1a007da73193237933adb39 token,
 com.sap.glx.adapter.BPMNAdapter:Instance_0_CSS_FileIn_58b390c7e1a007da73193237933adb39 parent,
 com.sap.glx.adapter.internal.ContainerAdapter:Context_0_IRO_58b390c7e1a007da73193237933adb39 context_0){
exit=new com.sap.glx.adapter.BPMNAdapter:Exit();
exit:addParameter(token);
exit:addParameter(parent);
exit:addParameter(context_0);
exit:onActivation("4B1F796E2DC84120E4AC11DEB8BF00016C0D596F", parent, token);
delete exit;
controller=new com.sap.glx.adapter.internal.ExceptionAdapter:ExceptionController();
controller:setContext(token);
delete controller;
callscope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_20_FileIn_58b390c7e1a007da73193237933adb39(parent);
call=new com.sap.glx.adapter.UnifiedConnectivityAdapter:Call_3_FI_Notice_PSP_58b390c7e1a007da73193237933adb39(callscope);
request=callscope:instantiate("http://tsmc.com/csspoc/notice/ejb/sb/", "#entrustSendingNotice");
mapper=new com.sap.glx.adapter.internal.Transformer:DataMapper();
yves_in=new com.sap.glx.adapter.internal.Transformer:Data();
yves_out=new com.sap.glx.adapter.internal.Transformer:Data();
data=context_0:getData();
yves_in:setData("tsmc.com/filein/pc/iresolution/Pool/FileIn", "$tsmc.com/filein/pc/iresolution/Pool/FileIn:IRO", data, "F2E8AB22162217BCFE0495CA03E629FD");
yves_out:setData("http://tsmc.com/csspoc/notice/ejb/sb/", "$http://tsmc.com/csspoc/notice/ejb/sb/:entrustSendingNotice", request, "0B03C177B47A4396F51FAC817E2C3870");
mapper:map("4B1F796E2DCB4E62E4AC11DEB49600016C0D596F_58b390c7e1a007da73193237933adb39", yves_in, yves_out);
request=yves_out:getData("http://tsmc.com/csspoc/notice/ejb/sb/", "$http://tsmc.com/csspoc/notice/ejb/sb/:entrustSendingNotice", "0B03C177B47A4396F51FAC817E2C3870");
delete yves_in;
delete yves_out;
delete mapper;
call:setInputData("http://tsmc.com/csspoc/notice/ejb/sb/", "$http://tsmc.com/csspoc/notice/ejb/sb/:entrustSendingNotice", request);
response=callscope:instantiate("http://tsmc.com/csspoc/notice/ejb/sb/", "#entrustSendingNoticeResponse");
call:setOutputData("http://tsmc.com/csspoc/notice/ejb/sb/", "$http://tsmc.com/csspoc/notice/ejb/sb/:entrustSendingNoticeResponse", response);
call:invoke();
response=call:getOutputData("http://tsmc.com/csspoc/notice/ejb/sb/", "$http://tsmc.com/csspoc/notice/ejb/sb/:entrustSendingNoticeResponse");
mapper=new com.sap.glx.adapter.internal.Transformer:DataMapper();
yves_in=new com.sap.glx.adapter.internal.Transformer:Data();
yves_out=new com.sap.glx.adapter.internal.Transformer:Data();
yves_in:setData("http://tsmc.com/csspoc/notice/ejb/sb/", "$http://tsmc.com/csspoc/notice/ejb/sb/:entrustSendingNoticeResponse", response, "0B03C177B47A4396F51FAC817E2C3870");
mapper:map("4B1F796E2DD00950E4AC11DEC9F000016C0D596F_58b390c7e1a007da73193237933adb39", yves_in, yves_out);
delete yves_in;
delete yves_out;
delete mapper;
delete call;
delete callscope;
token:state=14;
com.sap.glx.core.kernel.execution.transition.ScriptTransition.execute(ScriptTransition.java:69)
com.sap.glx.core.kernel.execution.transition.Transition.commence(Transition.java:241)
com.sap.glx.core.kernel.execution.LeaderWorkerPool$Follower.run(LeaderWorkerPool.java:118)
com.sap.glx.core.resource.impl.common.WorkWrapper.run(WorkWrapper.java:58)
com.sap.glx.core.resource.impl.j2ee.ServiceUserManager$ServiceUserImpersonator$1.run(ServiceUserManager.java:116)
java.security.AccessController.doPrivileged(Native Method)
javax.security.auth.Subject.doAs(Subject.java:337)
com.sap.glx.core.resource.impl.j2ee.ServiceUserManager$ServiceUserImpersonator.run(ServiceUserManager.java:114)
com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
java.security.AccessController.doPrivileged(Native Method)
com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:169)
com.sap.glx.core.kernel.api.TransitionException: An exception occurred while executing the script command "call:invoke()"
com.sap.glx.core.kernel.trigger.config.Script.execute(Script.java:675)
... (11 more)
com.sap.glx.core.kernel.api.TransitionException: com.sap.glx.adapter.api.AdapterException: Unexpected exception occured.
com.sap.glx.core.dock.impl.DockObjectImpl.invokeMethod(DockObjectImpl.java:465)
com.sap.glx.core.kernel.trigger.config.Script$MethodInvocation.execute(Script.java:247)
... (12 more)
com.sap.glx.adapter.api.AdapterException: Unexpected exception occured.
com.sap.glx.adapter.app.ucon.UnifiedWebServiceCallObject.invokeWebServiceOperation(UnifiedWebServiceCallObject.java:333)
com.sap.glx.adapter.app.ucon.UnifiedWebServiceCallClass.invoke(UnifiedWebServiceCallClass.java:197)
... (14 more)
com.sap.glx.adapter.api.AdapterException: Exception occured during wsdas initialization.
com.sap.glx.adapter.app.ucon.UnifiedConnectivityAdapter.createNewWSDAS(UnifiedConnectivityAdapter.java:654)
com.sap.glx.adapter.app.ucon.UnifiedWebServiceCallClass.getWSDAS(UnifiedWebServiceCallClass.java:53)
... (16 more)
com.sap.engine.services.webservices.espbase.discovery.TargetNotMappedException: Logical Target CSD.SystemHome.f7sap03 not mapped to a physical system.
com.sap.esi.esp.service.server.query.discovery.DestinationsHelperImplSoa.getLogicalDestination(DestinationsHelperImplSoa.java:831)
com.sap.esi.esp.service.server.query.discovery.DestinationsHelperImplSoa.getWSDLUrl(DestinationsHelperImplSoa.java:985)
com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.getWSDLUrl(GenericServiceFactory.java:582)
com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:338)
com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:321)
com.sap.engine.services.webservices.espbase.wsdas.impl.WSDASImpl.<init>(WSDASImpl.java:33)
com.sap.engine.services.webservices.espbase.wsdas.impl.WSDASFactoryImpl.createWSDAS(WSDASFactoryImpl.java:39)
... (18 more)
 
i have no idea why and how it happen, it been work well.

Vic,
the vital piece of information in the error stack is this line:
com.sap.engine.services.webservices.espbase.discovery.TargetNotMappedException: Logical Target CSD.SystemHome.f7sap03 not mapped to a physical system.
It seems that there is something wrong with the configuration of the target system for the called Web Service in your AS Java.
Best regards,
Oliver
Edited by: Oliver Goetz on Dec 11, 2009 5:24 PM
Edited by: Oliver Goetz on Dec 11, 2009 5:24 PM

Problem with special characters when calling web services via ISG

Similar Messages

Maybe you are looking for