Efiling HTTP destination-Type G

Hi,
We have developed the E-filing interface. For PI communication with Government gateway, we have created an RFC destinatio of type G.
This destination was working till yesterday and today it is failing with ICM_HTTP_INTERNAL_ERROR. This was because the certificate https://secure.dev.gateway.gov.uk/submission which we have imported in strust transaction has expired yesterday.
So we haev deleted that certificate from the system , imported a new one and restarted the ICM but still the same error continues.
Can anyone suggest what can be the reason for this?

Hi
The SMICM trace is
[Thr 1086888256] *** ERROR => IcmConnInitClientSSL: Proxy connection to secure.dev.gateway.gov.uk:443 failed (407:Proxy Authenticati
[Thr 1086359872] Thu Dec 10 13:43:32 2009
[Thr 1086359872] *** ERROR => IcmConnInitClientSSL: Proxy connection to secure.dev.gateway.gov.uk:443 failed (407:Proxy Authenticati
[Thr 1085831488] Thu Dec 10 13:43:45 2009
[Thr 1085831488] *** ERROR => IcmConnInitClientSSL: Proxy connection to secure.dev.gateway.gov.uk:443 failed (407:Proxy Authenticati
thanks
jagruthi

Similar Messages

HTTP destination type G with scpecial characters in the path prefix

Hi guys,
I am having an issue with a RFC destination type G in a ECC 5, the HTTP service that I am trying to use is asking me for an authentication that needs to be embeded on the Path prefix, the user has an "@" and the pwd also contain a special character "!". So the complete uri that I want to access is in the form of https://server:443/path?user=MyUser@MyDomain.com&password=MyPwd! when I tried in my web browser I got authenticated but when I put the information in the RFC destination in the form described below I am not able to authenticate and I am getting an error of Unauthorized.
Target Host: server
Service: 443
Path prfix: /path?user=MyUser@MyDomain.com&password=MyPwd!
Logon procedure: No logon
SSL: Active
I also have tried with the basic authentication but I am still not able to authenticate.
I think the issue is the "@" in the user: MyUser@MyDomain.com , I also have tried replacing the "@" for "%40" and still not working.
Do you know how I can pass this special character?
Do you think it can be something else that it doesn't let me authenticate to the server?
My system is a non unicode ECC 5, SAP_Basis 640
Thanks
Omar Hernandez

Hi Mark,
Thanks for your response, the HTTP service that I am trying to access is not accepting a basic authentication but it is getting the authentication info from the parameters in the URL. Anyway I also have tried to use basic authentication but it is not working.
Regarding SMICM, I havent seem anything useful, maybe the just the "BINDUMP of content denied" string but I am not sure what does this mean.
[Thr 1076382016] IcmHandleNetRead(id=91/11638): pending SSL data: 0, rollout=0
[Thr 1076382016] <<- SapSSLReadPending(sssl_hdl=0x2aaaaf53f380)==SAP_O_K
[Thr 1076382016] out: pendlen = 0
[Thr 1076382016] NiIPeek: peek successful for hdl 79 / socket 46 (r)
[Thr 1076382016] <<- SapSSLRead(sssl_hdl=0x2aaaaf53f380)==SAP_O_K
[Thr 1076382016] result = "max=65312, received=88"
[Thr 1076382016] IcmReadFromConn(id=91/11638): read 259 bytes(timeout 250)
[Thr 1076382016] BINDUMP of content denied
[Thr 1076382016] PlugInHandleNetData: role: 2, status: 2, content-length: 0/88
##buf_len: 259, buf_offset: 171, buf_status: 0, conn reused
[Thr 1076382016] PlugInHandleNetData: read response body (len=88/88)
[Thr 1076382016] PlugInHandleNetData: response completely read(EOS=0)
[Thr 1076382016] IcmFlushBuf: Flushing 259 Bytes, buf_status: 6
[Thr 1076382016] flush buffer with mpi buffer id 10
[Thr 1076382016] MPI<1e8c9>1a#5 FlushOutbuf l10 1 1 1c14e8 311 6 -> 0x2b4bc7cd64e8 0
[Thr 1076382016] IcmConnRollInWP: no need to roll in WP status: ROLLED IN
[Thr 1076382016] PlugInHandleNetData: keep connection
[Thr 1076382016] IcmPlCheckRetVal: Next status: WRITE_REQUEST(3)
[Thr 1076382016] IcmHandleNetRead(id=91/11638): read_len: 88, HandleNetData returned: 3
[Thr 1076382016] IcmConnRollInWP: no need to roll in WP status: ROLLED IN
[Thr 1076382016] IcmWorkerThread: Thread 4: Waiting for event

Problem in Creating HTTP Destination

Hello all,
I am trying to consume a web service from ABAP and for this very reason I am creating a Client proxy and now I need to create a HTTP destination(Type G).
I have created the Destination and when I test the connection I was facing with a error 'Service unavailable'.
Please help me in how to resolve such an error and also let me know if there are any pre requisites before creating a HTTP Destination.
Thanks in advance,
Regards,
Suman.

Hi,
I have raised this issue to the basis team and they are trying to figuring it out regarding the ICM/ICF paramters.
In the mean time when I am creating the client proxy for a webservice which is internaI,I faced a error similar to which Igor has faced.
In the WSDL document, the object
"<complex/simpleType name="ArrayOfAnyType"> <ele..."
from the namespace
"http://NJNWKDEV119.enterprise.pseg.com/"
links to the object
from the namespace
This webservice is from .net framework and I have asked them to check MSDN as mentioned by Anton with regards to problem faced by Igor.
I am pasting my wsdl so that you guys can help me in finding out what exactly the error is. Thank you in advance.
<?xml version="1.0" encoding="utf-8" ?>
- <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://NJNWKDEV119.enterprise.pseg.com/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://NJNWKDEV119.enterprise.pseg.com/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
- <wsdl:types>
- <s:schema elementFormDefault="qualified" targetNamespace="http://NJNWKDEV119.enterprise.pseg.com/">
- <s:element name="ValidatePointAddress">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="streetAddress" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
- <s:element name="ValidatePointAddressResponse">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="ValidatePointAddressResult" type="tns:ArrayOfAnyType" />
</s:sequence>
</s:complexType>
</s:element>
- <s:complexType name="ArrayOfAnyType">
- <s:sequence>
<s:element minOccurs="0" maxOccurs="unbounded" name="anyType" nillable="true" />
</s:sequence>
</s:complexType>
- <s:element name="ValidateLineAddress">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="streetAddress" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
- <s:element name="ValidateLineAddressResponse">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="ValidateLineAddressResult" type="tns:ArrayOfAnyType" />
</s:sequence>
</s:complexType>
</s:element>
- <s:element name="GetCrossStreetforPointAddress">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="streetAddress" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
- <s:element name="GetCrossStreetforPointAddressResponse">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="GetCrossStreetforPointAddressResult" type="tns:ArrayOfAnyType" />
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
- <wsdl:message name="ValidatePointAddressSoapIn">
<wsdl:part name="parameters" element="tns:ValidatePointAddress" />
</wsdl:message>
- <wsdl:message name="ValidatePointAddressSoapOut">
<wsdl:part name="parameters" element="tns:ValidatePointAddressResponse" />
</wsdl:message>
- <wsdl:message name="ValidateLineAddressSoapIn">
<wsdl:part name="parameters" element="tns:ValidateLineAddress" />
</wsdl:message>
- <wsdl:message name="ValidateLineAddressSoapOut">
<wsdl:part name="parameters" element="tns:ValidateLineAddressResponse" />
</wsdl:message>
- <wsdl:message name="GetCrossStreetforPointAddressSoapIn">
<wsdl:part name="parameters" element="tns:GetCrossStreetforPointAddress" />
</wsdl:message>
- <wsdl:message name="GetCrossStreetforPointAddressSoapOut">
<wsdl:part name="parameters" element="tns:GetCrossStreetforPointAddressResponse" />
</wsdl:message>
- <wsdl:portType name="AddValidationSoap">
- <wsdl:operation name="ValidatePointAddress">
<wsdl:input message="tns:ValidatePointAddressSoapIn" />
<wsdl:output message="tns:ValidatePointAddressSoapOut" />
</wsdl:operation>
- <wsdl:operation name="ValidateLineAddress">
<wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">ValidatelineAddress -Public web method to validate the line address for the first call from SAP Address Validation screen</wsdl:documentation>
<wsdl:input message="tns:ValidateLineAddressSoapIn" />
<wsdl:output message="tns:ValidateLineAddressSoapOut" />
</wsdl:operation>
- <wsdl:operation name="GetCrossStreetforPointAddress">
<wsdl:input message="tns:GetCrossStreetforPointAddressSoapIn" />
<wsdl:output message="tns:GetCrossStreetforPointAddressSoapOut" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="AddValidationSoap" type="tns:AddValidationSoap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="ValidatePointAddress">
<soap:operation soapAction="http://NJNWKDEV119.enterprise.pseg.com/ValidatePointAddress" style="document" />
- <wsdl:input>
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
- <wsdl:operation name="ValidateLineAddress">
<soap:operation soapAction="http://NJNWKDEV119.enterprise.pseg.com/ValidateLineAddress" style="document" />
- <wsdl:input>
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
- <wsdl:operation name="GetCrossStreetforPointAddress">
<soap:operation soapAction="http://NJNWKDEV119.enterprise.pseg.com/GetCrossStreetforPointAddress" style="document" />
- <wsdl:input>
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:binding name="AddValidationSoap12" type="tns:AddValidationSoap">
<soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="ValidatePointAddress">
<soap12:operation soapAction="http://NJNWKDEV119.enterprise.pseg.com/ValidatePointAddress" style="document" />
- <wsdl:input>
<soap12:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap12:body use="literal" />
</wsdl:output>
</wsdl:operation>
- <wsdl:operation name="ValidateLineAddress">
<soap12:operation soapAction="http://NJNWKDEV119.enterprise.pseg.com/ValidateLineAddress" style="document" />
- <wsdl:input>
<soap12:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap12:body use="literal" />
</wsdl:output>
</wsdl:operation>
- <wsdl:operation name="GetCrossStreetforPointAddress">
<soap12:operation soapAction="http://NJNWKDEV119.enterprise.pseg.com/GetCrossStreetforPointAddress" style="document" />
- <wsdl:input>
<soap12:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap12:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:service name="AddValidation">
- <wsdl:port name="AddValidationSoap" binding="tns:AddValidationSoap">
<soap:address location="http://njnwkdev119/PSEGAV/AddValidation.asmx" />
</wsdl:port>
- <wsdl:port name="AddValidationSoap12" binding="tns:AddValidationSoap12">
<soap12:address location="http://njnwkdev119/PSEGAV/AddValidation.asmx" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Regards,
Suman.

How to find out the HTTP destination of the Integration Server

Hi,
during the technical configuration of the exchange infrastructure the HTTP destination of the integration server was specified. Unfortunately I don't know this destination and need it now to configure the Business Systems as the Local Integration Engine. I read in the SAP library that the destination consists of the following:
Target Host,
Service No. (HTTP or HTTPS port) and
Path Prefix (path in the HTTP service tree of the SAP NetWeaver AS) which is /sap/xi/engine?type=entry
But when I type in the corresponding address (e.g. http://ccc60:4444/sap/xi/engine?type=entry) I got a message that the requested resource does not exist.
How can I find out this destination?

Hi Marc,
Is your server name the complete qualified name?.
You can get this from SMICM>Goto>parameters-->Dispay
Parameter: icm/host_name_full
HTTP port name: SMICM>Goto>service.
Regards
Vijaya

Dynamic Configuration of HTTP Destinations in SOAPReceiver

Dear PI Developers
I'll define a dynamic Configuration for my HTTP Destination in SOAPReceiver with XI3.0 Protocol.
The solution for that is to use an Adapter Module to set the dynamic Configuration Value.
Process: ... > SOAP Receiver > MyAdapterModule, set HTTP Destination > SOAP Receiver, send Message to HTTP Destination
URL-Adressing work's fine
This works fine for URL-Adressing, here's my Java Code from my Adapter Module:
Message message = (Message) inputModuleData.getPrincipalData();
message.setMessageProperty(new MessagePropertyKey("TServerLocation", "http://sap.com/xi/XI/System/SOAP"), "http://domain.com/foobar");
HTTP Destination, how it works?
If I'll use HTTP Destination as Adressing Type but the HTTP Destination will not set.
I think the "TServerLocation" Property don't work for the HTTP Destination, but I don't find a Property in:
Configuring the Receiver SOAP Adapter - Advanced Adapter Engine - SAP Library
My Questions
Did someone know the coresponding property name for HTTP Destinations instead of "TServerLocation"?
Are there other Solutions to set the HTTP Destination dynamicaly, for Example with variables %my_http_dest% ?
How can I set my own variables %my_http_dest% in my Adapter Module?
Background
We have a lot of Destinations and a lot of Szenarios and won't create a SOAPReceiver and Routing for each Destination in each Szenario.
The Destination depends on a HTTP Header Parameter from Sender, I'll map this Parameters to the coresponding HTTP Destination in the Adapter Module, that's the same Mapping for all Scenarios. To keep the performance, I cache this Routing Table in the Adapter Module.

Here's a way to misapplay "mesage:{var}" variables:
SAP NetWeaver XI: Variable Substitution with Adapter-Specific Message Attributes via DynamicConfigurationBean
But it is a dangerous solution, I think we use URL-Adressing in place of HTTP Destination

Proxy receiver channel with HTTP destination or URL address?

Hi Experts,
     I have a scenario as below:
     (Webservice Client)SOAP --> PI --> PROXY(SAP ECC).
     A webservice client calls PI using SOAP. PI then sends the request to SAP ECC using PROXY.
    I am using AAE. Therefore I have ICO.
    In the receiver PROXY channel I have given:
   ADAPTER TYPE: SOAP
   Transport Protocol: HTTP
   Message Protocol: XI3.0.
   Under connection parameters:
   Addressing Type dropdown as 2 entries HTTP destination and URL address.
   In what cases i should use HTTP destination and URL address respectively?
   Which option is preferred?
   Do they work same or differently? How?
   When I select HTTP destination where should I create the corresponding RFC destination? In PI ABAP stack using SM59 or PI NWA?
   If this HTTP destination is created in PI ABAP stack using SM59 then what type it should be? H? or G?
Thanks
Gopal

Hi Gopal,
In creating XI receiver communication channel, you have 2 options for Addressing Type:
1. URL Address - no need to create RFC destination. You just have to specify the XI receiver host name, HTTP port, path (/sap/xi/engine?type=receiver), Authentication data (logon details for SAP Client number of the PI system).
2. HTTP Destination - create RFC destination in SXMB_ADM and specify the RFC destination name in your receiver communication channel.
For SAP documentation, see this link:
http://help.sap.com/saphelp_nwpi711/helpdata/en/f4/0a1640a991c742e10000000a1550b0/content.htm?frameset=/en/e1/091640a991c742e10000000a1550b0/frameset.htm&current_toc=/en/43/96cbccb9335b77e10000000a11466f/plain.htm&node_id=5
Regards,
Naveen.

RFC Destination type RFC Receiver Adapter?

Hi,
What is the RFC destination type for Sender RFC Adapter?
and what is the need a Program ID for sender Adpter.
What is the RFC destination type for Receiver RFC Adapter?
Regards
Gopi

When we use the RFC Adapter?
SAP systems up to and including SAP Release 4.6 are not able to exchange data by using XML messages and http. The only way you can connect such systems to the Integration Server directly is by using the RFC adapter (or the IDoc adapter).
You require the sender adapter if you want to use the Integration Engine to process RFCs. The RFC adapter converts the incoming RFC data to XML message format (RFC XML) so that it can be processed by the Integration Engine.
You require the receiver adapter if the determined receiver system expects the data from the Integration Engine to arrive in RFC format. In this case, the Integration Engine must transfer the received XML message (RFC XML) to the RFC adapter. The RFC adapter converts the RFC XML message to a valid RFC call and executes the call.
The following three scenarios are possible when using the RFC adapter and the Integration Engine:
    1) SAP R/3 to SAP NetWeaver Application Server
    2) SAP NetWeaver Application Server to SAP R/3
    3) SAP R/3 to SAP R/3
When we use ABAP Proxy ?
SAP systems based on Web AS 6.40 and higher are able to exchange data by using messages and HTTP. These systems can use ABAP proxies to connect to the Integration Server.
To connect the platform-independent message interfaces, which are stored in the Integration Repository, to the Integration Server, use the ABAP proxy interface.
Please Reward the points if it's helpful...
Regards,
Ramana.

RFC destination types

When do we use RFC destination Type T versus Type 3?
While creating RFC destination Type T, the program ID, blogs says we should use "Registered server program" and can give any free text. I tried that but says there is no registered server program called XXX on system. So, i'm really confused here.
my understanding is for IDOCs you need Type 3, and for RFC you need Type T. Is that true or we can use any type with these?
Thanks,
Anika

Hi Anika,
i think this links could be useful:
http://help.sap.com/saphelp_47x200/helpdata/en/22/04262b488911d189490000e829fbbd/frameset.htm
Differences in the RFC destination types
You're right, for Idoc you have to use type 3 and for RFC you have to select a type T destination entering a program ID.
Let's make an example.
Suppose you have defined an RFC destination RFC_X with program id PID_X on ECC.
On XI you have created an RFC sender adapter and you have specified ECC as the sender and PID_X as the program ID.
When from ECC an RFC is called using destination RFC_X then the sapgateway looks for a receiver registered with the program id PID_X, it finds your RFC adapter and sends the call to XI.
Hope it helps.
Kind Regards,
Sergio

Missing destination type for service registry in nwds

Hi,
based on this help [Simple Sample Installation and Configuration|http://esworkplace.sap.com/socoview(bD1lbiZjPTAwMSZkPW1pbg==)/get_mime.asp?id=B135A510223D467B89186B000A89F777&filename=Simple%3FSample%3FInstallation%3Fand%3FConfiguration.pdf&packageid=DE0426DD9B0249F19515001A64D3F462] I try to config the prerequisites to get the samples running.
Like described at chapter 3.3 SAP NetWeaver Developer Studio (NWDS) in NWDS under "Web Service Configuration" two destinations ERP and ERP_META should be created.
In my case the option "Service Registry" at "Destination Type" is missing.
May anybody help me?
Best regards

Hi John,
I think the screenshot is wrong.
You can use WSIL to configure the backend system.
The WSIL url for ABAP systems is http://[host]:[port]/ sap/bc/srt/wsil?sap-client=[client_no]
Regards,
Christian

HTTP destination PI_INTEGRATIONSERVER missing (system , transaction SM59)

Hi Experts,
I am working on ABAP Proxy -> File scenario. When I trigger message in ECC, it is giving error.
When I go to SXI_Monitor in ECC, the message is shown as red with error message "HTTP destination PI_INTEGRATIONSERVER missing (system , transaction SM59)". But the RFC destination PI_INTEGRATIONSERVER exists and when i tested this connection I got 500 empty request received message.
I have configured in SXMB_ADM the ECC system as application system and mentioned 'dest://PI_INTEGRATIONSERVER' as corresponding integration server.
Could you please help me in resolving this issue?
Thanks and regards,
Prasad

Hi Prasad,
Ensure below items in your ECC system.
1. goto SM59
2. ensure your RFC - PI_INTEGRATIONSERVER has this entry '/sap/xi/engine?type=entry' (without quots)
3. Target Host has value your PI/XI hostname and correct port number (HTTP)
4, for Logon& Security Tab, ensure to use userID PIAPPLUSER and correct password (saved)
or Service user of Integration engine (maintained in Exchange profile)
You can write back to me if any further help required.
Regards
Sekhar
Edited by: sekhar on Dec 24, 2009 6:57 PM

Get the http destination, not simple!

Hi all,
I have a Java WebDynpro application that contains some link to BSPs.
I have added the bsp http address in the Destination service (in Visual administrator), and i'm tring to get it from a Java WebDynpro like sap documentation suggested. The code i'm using is:
     try {
     InitialContext ctx = new InitialContext();
     DestinationService dstService = (DestinationService) ctx.lookup(DestinationService.JNDI_KEY);
     if (dstService == null)
     throw new NamingException("Destination Service not available");
     try{
     Destination destination = dstService.getDestination("HTTP","sso_givaudan_OpportunityLink");
     //for HTTP destination: cast
     HTTPDestination httpDestination = (HTTPDestination) destination;
     //obtain a HTTPUrlConnection from the destinationHttpURLConnection
     HttpURLConnection httpConnection = httpDestination.getURLConnection();
     urlOpportunityLink = httpConnection.toString(); //return the http address
     } catch (IDException ex) {}
       catch (RemoteException ex) {};
     } catch (NamingException e) {};
     wdContext.getCurrentElement().setAttributeValue("OpportunityLink",urlOpportunityLink);
I have the follow exception on the ctx.lookup:
An error has occurred:
"Failed to process the request."
Please contact your system administrator.
Hide details
This page was created by SAP NetWeaver. All rights reserved.
Web Dynpro client:
HTML Client
Web Dynpro client capabilities:
User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.0.3705; .NET CLR 1.1.4322), client type: msie6, client type profile: ie6, ActiveX: enabled, Cookies: enabled, Frames: enabled, Java applets: enabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
Accessibility mode: false
Web Dynpro runtime:
Vendor: SAP, build ID: 7.0004.20050812153807.0000 (release=645_VAL_REL, buildtime=2005-09-21:09:00:55[UTC], changelist=362988, host=pwdfm101), build date: Thu Jan 19 11:02:30 CET 2006
Web Dynpro code generators of DC local/GivaudanNavigation:
SapDictionaryGenerationCore: 7.0004.20050713144105.0000 (release=645_VAL_REL, buildtime=2005-09-19:09:56:45[UTC], changelist=357691, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro: 7.0004.20050713144450.0000 (release=645_VAL_REL, buildtime=2005-09-19:09:58:47[UTC], changelist=357707, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore: 7.0004.20050713144259.0000 (release=645_VAL_REL, buildtime=2005-09-19:09:50:51[UTC], changelist=357699, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates: 7.0004.20050812153807.0000 (release=645_VAL_REL, buildtime=2005-09-19:10:17:37[UTC], changelist=362988, host=pwdfm101)
SapWebDynproGenerationCTemplates: 7.0004.20050812153807.0000 (release=645_VAL_REL, buildtime=2005-09-19:10:17:37[UTC], changelist=362988, host=pwdfm101)
SapGenerationFrameworkCore: 7.0004.20050713144242.0000 (release=645_VAL_REL, buildtime=2005-09-19:09:50:22[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 7.0004.20050713144412.0000 (release=645_VAL_REL, buildtime=2005-09-19:10:01:14[UTC], changelist=357705, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary: 7.0004.20050509170017.0000 (release=645_VAL_REL, buildtime=2005-09-19:09:54:51[UTC], changelist=346508, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon: 7.0004.20050713144259.0000 (release=645_VAL_REL, buildtime=2005-09-19:09:50:57[UTC], changelist=357699, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCore: 7.0004.20050713144412.0000 (release=645_VAL_REL, buildtime=2005-09-19:10:01:24[UTC], changelist=357705, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates: (unknown)
Web Dynpro code generators of DC sap.com/tcwddispwda: No information available!
Web Dynpro code generators of DC sap.com/tcwdcorecomp: No information available!
J2EE Engine:
7.00   patchlevel
Java VM:
Java HotSpot(TM) Server VM, version: 1.4.2_09-b05, vendor: Sun Microsystems Inc.
Operating system:
Windows 2003, version: 5.2, architecture: x86
Error stacktrace:
java.lang.ClassCastException
     at com.sap.givaudan.navigation.comp.NavigationComp.wdDoInit(NavigationComp.java:128)
     at com.sap.givaudan.navigation.comp.wdp.InternalNavigationComp.wdDoInit(InternalNavigationComp.java:115)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:95)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:417)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:401)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.getApplicationHandle(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.prepareTasks(AbstractClient.java:216)
     at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:647)
     at com.sap.tc.webdynpro.clientserver.cal.ClientManager.parseRequest(ClientManager.java:144)
     at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.parseRequest(ApplicationHandle.java:79)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:43)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     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:95)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
Could someone help me? I will appreciate.
Thanks,
Vito

<param name="Loop" value="?">
Adjust the question mark to suit
"npqster" <[email protected]> wrote in
message
news:fsshc2$19e$[email protected]..
> In this page below, how do I get the shockwave file to
freeze at the last
> frame?
>
>
http://ltcproduction.com/creative.html

Help Configuring BLOBDestination pluggable report destination type

Hi Folks
I am having problems configuring the BLOBDestination pluggable report destination type on our Oracle 10g mid-tier. Although I believe I have placed the jar file in the correct directory and updated the correct configuration file I am not sure as the details of directory name and configuration file name were not present. Obviously assuming I knew more than I do.
At the moment I am assuming I there is nothing wrong with the BLOBDestination code but with our configuration. Also could it be I have the wrong file because of our multiple instances of the report server?
Any help would be appreciated, even/especially confirmation that someone has gotten this to work or knows that it does not.

Hi Krrish
Yes that is the file and entry that we updated. Here is more information.
When we use the following URL [Sensitive data modified and underlined]
http://SERVER/reports/rwservlet?server=repintg_pplus&report=general_payroll_rpt.rdf&userid=USERID/PASSWORD@DATABASE&destype=blobdestination&desformat=PDF&desname=http://USERID:PASSWORD@SERVER:1251/pplust/REG_PAYROLL_X/EXTRACT/REG_PAYROLL_X_ID/2/FILE_NAME
we get the following error on the web page
REP-50159: Executed successfully but there were some errors when distribute the output
REP-50125: blobdestination : Caught exception: java.lang.NullPointerException

Error: Illegal destination type 'H'

Hello All,
We've maintained an RFC destination type 'H' for the ALE connection from the HR system to FI. When running tcode PC00_M99_CIPE the following error is received:
System error during RFC call BAPI_FIXACCOUNT_GETLIST: Illegal destination type 'H'
Any ideas?

Hi,
The /sap/bc/soaprfc is the "old style" generic node for calling RFC as web services.
It is used up to WAS 6.20.
Beginning with WAS 6.40, it is still there and funcional but you are supposed to use the new web service implementation with one SICF node per RFC module function.
In that case, You can create an HTTP destination per function module to call.
If you just test the HTTP destination from SM59, you will, of course, get an error because you just send a GET to the URL which does not respect the SOAP protocol.
What you need to do is to create a web service proxy from the WSDL.
Regards,
Olivier

Error in Interface for management of HTTP destinations

Hello Experts,
I've go the following error when i'm trying to create a logical port in SOA Manager.
'Error in Interface for management of HTTP destinations'.
I was trying to create a logical port of type WSDL for a consumer proxy, with a URL provided by the EP consultant.
Kindly let me know how can i rectify the above stated error.

Hi
Did you try creating the connection via sm59 (RFC Destination), then try to assign it (instead of direct URL call, specify the RFC destination). That way, you can trace the RFC destination.
Regards
Ronny

Destination type MDM missing

Hello dear MDM gurus
I have installed the latest Sneak Preview of 7.2 CE and also deployed the latest SCA files of MDM 7.1 SP4 Patch 3 on my PC.
According to help.sap.com I have to be able to create my new [Destination|http://help.sap.com/saphelp_nwmdm71/helpdata/en/4a/cdd7c31ca822ace10000000a42189b/content.htm] and configure where my MDM Server is, but Destination type - MDM is not showing up at all.
Any words of advice would be greatly appreciated?

Forget it ... it appeared automatically 30 minutes after the SCAs were deployed... a bounce of the server might have helped too.
Regards,
Boris

Efiling HTTP destination-Type G

Similar Messages

Maybe you are looking for