Receiver Proxy

Do we need to create receiver communication channel and receiver agreement if target is SAP ECC(proxy)?

Hi Naresh,
We have to create receiver comm channel & recv agreement in case of inbound proxys.
Refer to the foolowing links :
ABAP Server proxies
/people/siva.maranani/blog/2005/04/03/abap-server-proxies
Debugging of Inbound ABAP proxies
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
File to R/3 via ABAP Proxy
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy
Regards,
Vinod.

Similar Messages

Java Receiver Proxy Base Info

Hi
i have a File-to-RFC Scenario replaced with a File-to-ABAPProxy Scenario. This works. It's possible to replace the ABAP Proxy on my SAP Target System by a Java Receiver Proxy?
Reason for this question: I understand, that in my ABAP proxy i do the mapping from my PI Dataformat to the RFC destination Format (ABAP Function) manually in the Proxy class in ABAP. I'm actually a Java Programmer and would prefer to do the mapping in Java.
I searched on this subject and understood that i have to install the Java Proxy Runtime, but I'm don't know if this only works for a non-central AE and non-SAP interfaces or if I also can encapsulate a remote ABAP function on my target system.
Thanks in advance
Michael

Michael,
>>I understand, that in my ABAP proxy i do the mapping from my PI Dataformat to the RFC destination Format (ABAP Function) manually in the Proxy class in ABAP.
Yes, You are right
>>I'm actually a Java Programmer and would prefer to do the mapping in Java.
You can do with the help of Java too
>>i have to install the Java Proxy Runtime
You are right
>>but I'm don't know if this only works for a non-central AE and non-SAP interfaces
We can do it for SAP system too, for example thru portal service we can trigger the BAPI
Thanks
Agasthuri

Receiver Proxy Generation error

Hi Experts,
As per scenario. (file to Proxy and Proxy to file)
I am created two namspaces like this
http://SAP/XI (for SAP)
http://SAPto/MQ (for 3rd party)
for all interfaces i have to do proxy to file and file to proxy ASY. so i created
message interfaces like this.
under http://SAP/XI   (for SAP)
         MI_OA_ABC
        MI_IA_123
   http://SAPto/MQ   (for 3rd party)
MI_IA_ABC
MI_OA_123
here i am given same name for inbond/outound interfaces
then i am trying to generate proxy (client) under SAP for proxy to file
I am getting bleo error
same as receiver proxy also
error:
Objects from other namesapces are missing unble to save"

Hi Srinivasreddy,
          U need to save & ACTIVATE the two namespaces.first check it that one.
         You are working with FILE to PROXY & PROXY to FILE scenarios.
FILE to PROXY: U can create one namespace for both file & PROXY that enough.
                        like PROXY to file also.
Regards,
sateesh

REG: Monitoring of Receiver Proxy

Hi All,
           How do we monitor or track Receiver proxy interfaces. Please provide links on the same.
Thanks,
Siva

Hi,
       I have a secnario where proxy is at the receiver side. The interface is sucessfull from the Xi side and I can see checked flag in moni. But at the SAP end the table is not updated.
       So wanted to know where exactly the error could have occuered and hoe to debugg it.
Thanks,
Siva

Citrix Receiver Proxy

Hi
Im trying to configure the Citrix Mobile Receiver Proxy on a ASA but cant get it to work.
The ASA got several VPN configured, both client, clientless vpn and L2L.
It looks like ASA are terminating SSL every time the iPad connects.
What could be missing here? And any good advice on how to troubleshoot appreciated.
ASA 5585 - OS 9.1(8)
Citrix Receiver - 5.8.3
Citrix config:
group-policy DfltGrpPolicy attributes
dns-server value x.x.x.30 x.x.x.31
vpn-simultaneous-logins 10
vpn-tunnel-protocol ikev1 l2tp-ipsec
default-domain value xxx .org
webvpn
customization value DfltCustomization
vdi type citrix url http://citrix.xxx.org domain xxx.org username CSCO_WEBVPN_USERNAME password CSCO_WEBVPN_PASSWORD
From Log Viewer:

I did some captures today and all I got is the outside capture with a RST,ACK back to my test client.
On the inside interface, going to the Citrix server nothing. Did check for both ASA inside IP and the Citrix server IP in diffrent ways (any->ASA, Citrix->any, etc)
Looks like ASA is not listening for, or understands, incomming Citrix traffic?
Edit:
Just saw this: Key size >1024 is not supported as of now.
All certificates on the ASA are 2048, probably the problem?
Cheers

Cannot see PI receiver(Proxy) adapter - advanced adapter specific message

Hello Friends,
I cannot see adapter specific message attributes in receiver adapter XI (abap proxy) for enabling. I want to use these properties for getting a file name dynamically in a receiver structure.
I had seen a blog by Mr.Michal but that gives details for file to file. Here my target is abap proxy so I cannot see advance tab properties in XI adapter used communication channel.
Clearly my interface is file to ecc (using proxy), where i will have to read a file name which my interface picks and has to update in ecc.
I have enabled the sender side File adapter - ASMessage attributes but am not able to find the attributes in receiver side. Does it make any diffrence if am not enable the attributes at receiver adapter.
Thanks very much.

Swarna,
in your scenario in order to have the file name updated on ecc, you must:
1. Set the ASMA properties on sender channel
2. Read the property in mapping and put the value in a custom field on the proxy structure. Create an UD like this:
UD
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
String onixdataset = conf.get(key);
--- END UD
3. Manage the filename in the proxy class with your requirements
Regards,
Andrea

WS Adapter for Receiver Proxy

Hi all,
I am working on an ECC to SRM scenarion on XI 7.1. I am using WS Adapter at the receiver side and there is no ABAP Proxy code in the SRM side. There is however, proxy for the sender side, ECC. I am getting an error about logical port, I raised a question few days ago but I am not able to solve it. I have few doubts.
1) Is it possible to use WS Adapter for receiver system like SRM which is an SAP System and also without using a proxy code ?
2) Do I have to configure a logical port for this scenario using SOAMANAGER as I have only one XI server in the landscape. I saw a blog but that blog talks about multiple XI servers. I have only one XI server but I am getting an error at the call adapter step something like " "Error while determining logical port Cannot find logical port for agreement abc and interface xyz"
I don't want to do the entire thing using Proxy
Regards

>1) Is it possible to use WS Adapter for receiver system like SRM which is an SAP System and also without using a proxy code ?
Yes it is possible if you use direct connection using WS adapter. you dont need proxy code
>Do I have to configure a logical port for this scenario using SOAMANAGER as I have only one XI server in the landscape. I saw a blog but that blog talks about multiple XI servers. I have only one XI server but I am getting an error at the call adapter step something like " "Error while determining logical port Cannot find logical port for agreement abc and interface xyz"
Refer this link for your need
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b043ef4e-e8d1-2c10-7d88-8077b209ce55?quicklink=index&overridelayout=true

Receiver proxy error - CLIENT_RECEIVE_FAILED error code 200

Hi,
Scenario: JDBC to Proxy.
I am getting an error on the receiver side - below is the error.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>200</SAP:P1>
<SAP:P2>Error Parsing Response. No XI Response Received.</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>--SAP_4732F0E6BA080C67E1000000A859B621_END content-type:text/xml content-length:4118 content-id:<[email protected]> <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP:Header xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7"><SAP:MessageClass>ApplicationMessage</SAP:MessageClass><SAP:ProcessingMode>asynchronous</SAP:ProcessingMode><SAP:MessageId>FA074580-8DE5-11DC-9B3E-00144F2B5900</SAP:MessageId><SAP:TimeSent>2007-11-08T10:33:00Z</SAP:TimeSent><SAP:Sender><SAP:Service>BS_ESS</SAP:Service></SAP:Sender><SAP:Receiver><SAP:Party agency="" scheme=""/><SAP:Service>CD103</SAP:Service></SAP:Receiver><SAP:Interface namespace="http://www.Coj.co.za/EssToSapIsu/Ess">MI_EssToSapIsu_EssMiForSapIsu</SAP:Interface></SAP:Main> <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService></SAP:ReliableMessaging> <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Hop timeStamp="2007-11-08T10:33:00Z" wasRead="false"><SAP:Engine type="AE">af.cxd.jssxid0</SAP:Engine><SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter><SAP:MessageId>FA074580-8DE5-11DC-9B3E-00144F2B5900</SAP:MessageId><SAP:Info/></SAP:Hop><SAP:Hop timeStamp="2007-11-08T10:33:00Z" wasRead="false"><SAP:Engine type="IS">is.00.jssxid0</SAP:Engine><SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter><SAP:MessageId>FA074580-8DE5-11DC-9B3E-00144F2B5900</SAP:MessageId><SAP:Info>3.0</SAP:Info></SAP:Hop></SAP:HopList> <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:TraceLevel>Information</SAP:TraceLevel><SAP:Logging>Off</SAP:Logging></SAP:Diagnostic> <SAP:MessageHeader xmlns:SAP="http://sap.com/exchange/MessageFormat" version="1.0" SOAP:mustUnderstand="1"><SAP:From><SAP:Name></SAP:Name><SAP:Interface namespace=""></SAP:Interface></SAP:From><SAP:MessageId>00000000-0000-0000-0000-000000000000</SAP:MessageId><SAP:QualityOfService></SAP:QualityOfService><SAP:TimeSent></SAP:TimeSent><SAP:Direction>Request</SAP:Direction><SAP:Document></SAP:Document></SAP:MessageHeader> <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat"><SAP:Context></SAP:Context><SAP:Code p1="" p2="" p3="" p4="">CALLER.MSG_GUID_NOT_QUALIFIED</SAP:Code><SAP:Text language="EN">Attribute message GUID not specified</SAP:Text></SAP:ErrorHeader> <SAP:HopList xmlns:SAP="http://sap.com/exchange/MessageFormat" Version="1.0"><SAP:Hop SystemName="CD103" Type="SENDER" TimeStamp="2007-11-08T11:00:57Z" WasRead="0"><SAP:MessageInbound><SAP:Type>AENGINE</SAP:Type></SAP:MessageInbound><SAP:MessageOutbound><SAP:Type></SAP:Type></SAP:MessageOutbound></SAP:Hop></SAP:HopList> <SAP:InternalAttributesHeader xmlns:SAP="http://sap.com/exchange/MessageFormat"><SAP:AdapterInbound>AENGINE</SAP:AdapterInbound></SAP:InternalAttributesHeader> </SOAP:Header> <SOAP:Body xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7"><SAP:Payload xlink:href="cid:[email protected]"><SAP:Name>MainDocument</SAP:Name><SAP:Description/><SAP:Type>Application</SAP:Type></SAP:Payload></SAP:Manifest> <SAP:Manifest xmlns:SAP="http://sap.com/exchange/MessageFormat" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.0"> <SAP:Payload xlink:href="cid:[email protected]"> <SAP:Document>TraceDocument</SAP:Document> </SAP:Payload> </SAP:Manifest> </SOAP:Body> </SOAP:Envelope> --SAP_4732F0E6BA080C67E1000000A859B621_END content-type:application/xml content-length:417 content-id:[email protected] <?xml version="1.0" encoding="UTF-8"?> <ns0:MT_EssToSapIsu_EssMtForSapIsu xmlns:ns0="http://www.Coj.co.za/EssToSapIsu/Ess"><TABLE1><BSTKD>A0707120330</BSTKD><BSTDK>12-07-2007 </BSTDK><ZE01>15:33</ZE01><ZE04>JANICE</ZE04><ZE05>DS3</ZE05><ZE06>RIVERLEA</ZE06><ZE02>,957 A KOMANI,RIVERLEA</ZE02><MATNR>A</MATNR><ZE03></ZE03><AUGRU>Medical - General</AUGRU></TABLE1></ns0:MT_EssToSapIsu_EssMtForSapIsu> --SAP_4732F0E6BA080C67E1000000A859B621_END content-type:text/plain content-length:1717 content-id:[email protected] <?xml version="1.0" encoding="UTF-8" standalone="yes" ?><SAP:TraceHeader xmlns:SAP="http://sap.com/exchange/MessageFormat"><Trace level="1" type="B">CL_XMS_TROUBLESHOOT-ENTER_PLSRV</Trace> <Trace level="1" type="E">CL_XMS_TROUBLESHOOT-ENTER_PLSRV</Trace> <Trace level="1" type="T">**************************************************** </Trace> <Trace level="1" type="T">* * </Trace> <Trace level="1" type="T">* * </Trace> <Trace level="1" type="T">XMB entry processing </Trace> <Trace level="1" type="T">system-ID = CD1</Trace> <Trace level="1" type="T">client = 103</Trace> <Trace level="1" type="T">language = E</Trace> <Trace level="1" type="T">user = MOLAIM</Trace> <Trace level="1" type="Timestamp">2007-11-08T11:00:57Z </Trace> <Trace level="1" type="T">* * </Trace> <Trace level="1" type="T">* * </Trace> <Trace level="1" type="T">**************************************************** </Trace> <Trace level="1" type="B">CL_XMS_MAIN-CALL_UC_EXECUTE</Trace> <Trace level="1" type="T">Message-GUID = 00000000000000000000000000000000</Trace> <Trace level="1" type="E">CL_XMS_MAIN-CALL_UC_EXECUTE</Trace> <Trace level="1" type="System_Error">Exit XMB because of system error!</Trace> <Trace level="1" type="System_Error">System-Error: CALLER.MSG_GUID_NOT_QUALIFIED</Trace> <Trace level="1" type="System_Error">Attribute message GUID not specified </Trace> <Trace level="1" type="E">CL_XMS_MAIN-ENTER_XMS</Trace> <Trace level="1" type="E">CL_XMS_HTTP_HANDLER-HANDLE_REQUEST</Trace> </SAP:TraceHeader> SAP_4732F0E6BA080C67E1000000A859B621_END</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while receiving by HTTP (error code: 200, error text: Error Parsing Response. No XI Response Received.)</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Thanks,
Leanne

Are u trying a synch scenario? Ur server proxy must be receiving the data properly. If it is a sync scenario then u should check the response mapping again in sxmb_moni.
Regards,
Prateek

Target Filename generation - receiver proxy.

Hi,
I need to create target filename same as source filename. When receiver communication channel is proxy. Communication channel.
Thanks,
Venu.

Venu,
So the flow will be like,
Step1: file->proxy(with some validation)
Step2: based on the validation from the step1 trigger an outbound proxy and create the file.
For this you need to use the module in your sender file adapter and then pass it as an extra field in the payload...this field you'll be maintaining in your source and target structure of your step1.
Now this file name will be available in your inbound proxy, do the validation and send it in the outbound proxy structure(which again will have the node to hold the file name).
In the step2 as the last part in the receiver file adapter use variable substitution.
This will hold good if you are using XI throughout. If you are not using step 2 still you can use module to get the file name and pass it to the proxy data and in ABAP code, you can use OPEN DATASET command(check for its syntax) and create the file in the R/3 server application layer.
cheers
JK

Receiver Proxy adapter

Hello Experts,
I am getting a message in SXMB_MONI "Pipeline ENTRY does not exist (table SXMSPIPE)" <SAP:Category>XIServer</SAP:Category>
I am using a receiver XI adapter with HTTP protocol. Appreciate your help in resolving this.
Thanks
Ricky

Hi Ricky,
Just curious, but I assume the system that issued the message is the receiving R/3 6.20 System?
The error message says: "Pipeline ENTRY does not exist".
This means that the system that issued the message is looking for a pipeline called 'ENTRY' in its 'XML Message Server: Pipeline Definition' table SXMSPIPE.
The question is "Why would the system that issued the message be looking for a pipeline called 'ENTRY'". A possible answer follows.
I noticed in the SAP Note 602959, mentioned earlier in the forum thread, the following paragraph:
Begin of SAP Note quoted paragraph ****
The correct URL is http://<host>:<port>/sap/xi/engine?type=entry&pipelineid=entry whereby you ... transaction SMICM (Goto -> Services).
If you are working exclusively in XI 2.0 (that is, you do not have a XI 1.0 sender), the correct URL is: http://<host>:<port>/sap/xi/engine?type=entry
End of SAP Note quoted paragraph ****
I notice that the first URL in the above paragraph contains the parameter '&pipelineid=entry' while the second URL does not.
I don't know if you have control over the URL that calls the proxy in the receiving R/3 6.20 System, but if I were you, I'd try to make sure that the URL doesn't contain the parameter '&pipelineid=entry' because I think this parameter might be the reason for the system trying to find a pipeline called 'ENTRY'.
What do you think?
Best Regards,
Andy

Regarding Receiver proxy

Hi
Can any tell me why we use xi adapter when proxy is on receiver side?

Hi,
When ever we are dealing with proxies we dont use any adapter to talk with IS.
Proxies will directly talk with IS .
While Proxies are receiver end we use XI adapter , this for internal communication only.to talk with Integration Engine with IS , we use it.
In Case of Sender means proxies will directly talk with IS . then no need of Adapter here.
If you observe means in case of any receiver means we have to use the receiver adapter ( like IDOC, HTTP )
Please Follow this BLOG to understand the flow, why we are using XI Adapter.
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
Regards
Seshagiri

Receiver Proxy (SOAP) adpater Error in SAP PI 7.1

Hi Experts
I am working on a File to Proxy Scenario, where I am getting the data frm File is absolutely fine and while sending to Proxy I am getting the following error in proxy CC
I have defined a Proxy CC on the recievr side I used adapter type as SOAP
Transport Protocal :HTTP
Message protocal XI3.0
Adapter ENgine : Central Adapter Engine
I gave the connection parameters (Target URL)
Authentication Code: USE Logon data for SAP
User ID & Pwd
I checked the RFC connections on PI side on SM59 and did test run, It looks good
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized
Please give an idea how to resolve this issue
Thanks
PR

Are you using SSL? If yes, please ensure evrything from help page below has been applied
http://help.sap.com/saphelp_nwpi711/helpdata/en/48/9ab5d73e6d062be10000000a42189d/content.htm
- Please check the SOAP FAQ note under question "Q: I get an authorization error "401 Unauthorized" from the
adapter's servlet. What went wrong?"
[Note 856597 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 SOAP Adapter|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=856597]
- Last, try with both users below PIAPPLUSER and PIAFUSER. Should still not work, ensure the role SAP_XI_APPL_SERV_USER has been assigned to currently used user on the destination.
EDIT: Too late for me.

Mail displays received proxy details send return path at the top of all emails. Is this a setting that can changed? Why is this happening.

Not sure why this is displayed. It reveals all the details of date delivered to times to and from.
In all mail sent and received?

Ah just found the answer to this on another post and now fixed
Received Mail Routing Details

HTTP Receiver - Proxy

Hi,
I had to design a file----- XI -
HTTP scenario.
Say i am connect to a 3rd party with address 11.11.111.11 throgh the HTTP call.
But now i am told that a firewall wil be in place between XI and HTTP.
What does that mean ? do i still have to call the address 11.11.111.11 or some thing else ?
do i have to take any specific care in the HTTP receiver ?
Any help is highly appreciated.
Thanks,
Vignesh
Edited by: Vignesh Perumal on Nov 17, 2008 5:48 PM

Hi Vignesh
But now i am told that a firewall wil be in place between XI and HTTP.
What does that mean ? do i still have to call the address 11.11.111.11 or some thing else ?
do i have to take any specific care in the HTTP receiver ?
There is nothing specific you need to do here. Just you need to add a firewall rule that will allow PI to post to this IP.
Give a check doing a ping test to this IP. If not successful contact your network people to solve this.
May be you require HTTPS based on your company security policies. For that you need to install SSL certificate on your PI box, generated from target system and create RFC destination on XI. Use this RFC destination in receiver HTTP
Thanks
Gaurav

Troubleshooting Java not receiving Proxy information

Hello,
I work in an environment where we have Microsoft TMG installed, with the TMG client on every computer. The TMG configuration with Java 1.6 worked properly on computer previously to an upgrade of Windows 7 & Java 1.7
Here is the config of an average computer
Win7 64 bit
Java 7.51
TMG client
IE 8
The symptom we are experiencing is Java doesn't use the proxy settings that are issued using the TMG's default auto-discovery script found at http://TMGserver:8080/array.dll?Get.Routing.Script
When we have the "internet settings" under the control panel set to "Automatically detect settings", then Java doesn't seem to detect the proxy settings and use them. I can verify this by looking in the Java console as I run an app, as I constantly see "proxy=direct" in the trace.
I can fix this by
1. forcing a manual proxy server (with FQDN - simple name doesn't work) in the Java client settings on each user through the control panel applet
2. putting the manual proxy information in a deployment.properties file on each user, or through the "central admin" method of c:\windows\system32\sun\java\deployment\deployment.config & deployment.properties
3. Uncheck the "auto detect settings' and "auto config script" check boxes on the TMG server, so they don't propogate to each TMG client, and aren't put in the "internet settings" of the computer
3. upgrading client to Java 8
Unfortunately Java 8 isn't supported by another application, so upgrading to Java 8 is not a possible fix. Neither is having to manually add (even by script) the Java proxy settings for thousands of users. I've read all about how Java pulls proxy info from the registry, but have proven that Java seems to check multiple places to get proxy info, even if not found in registry. This seems to be a very distinct problem where Java is not accessing the "automatically detect settings" or "use automatic configuration script" settings as set in the "internet settings." It may be that something needs to change with the TMG server, but difficult to understand what and why.
Can anyone point me to useful links or other ideas on how to fix this? The script being issued by the TMG server is the one created by default. I have been troubleshooting this a lot, but I'm not getting any traction on understanding why Java 7.51 doesn't grab proxy information. I would reapply appreciate any assistance that is offered.
thanks,
Brian

When I set the cookiePath to "/" in sun-web.xml, I get the following output ::
[wfad002] netscape /cbsweb/apps/cwi/sun1/appserver/domains/domain1/server1/log telnet wfad002.csm.fub.com 8400
Trying 172.1.114.122...
Connected to wfad002.
Escape character is '^]'.
GET /CwiTest/HeaderServlet HTTP/1.0
HTTP/1.1 500 Internal Server Error
Server: Sun-ONE-Application-Server/7.0
Date: Tue, 24 Sep 2002 16:33:52 GMT
Content-length: 2415
Content-type: text/html
Set-cookie2: JSESSIONID=0FD04CF9167377745F25A1B44776F26B;Version=1;Comment=Sun+ONE+Application+Server+Session+Tracking+Cookie;Discard;Path="/"
Connection: close
<html><head>
<title>
If I don't set the cookiePath in sun-web.xml, I get the following output::
[wfad002] netscape /cbsweb/apps/cwi/sun1/appserver/domains/domain1/server1/log telnet wfad002.csm.fub.com 8400
Trying 172.1.114.122...
Connected to wfad002.
Escape character is '^]'.
GET /CwiTest/HeaderServlet HTTP/1.0
HTTP/1.1 500 Internal Server Error
Server: Sun-ONE-Application-Server/7.0
Date: Tue, 24 Sep 2002 16:20:44 GMT
Content-length: 2415
Content-type: text/html
Set-cookie: JSESSIONID=FA32105878E09E03BFC40E443CFC1A64;Path=/CwiTest
Connection: close
<html><head>
<title>
This shows (as you explained) that when I set the path the Cookie Version changes to "1". Which may not be supported by my Browser.
Thanks,
Shaje

Receiver Proxy

Similar Messages

Maybe you are looking for