Urgent! Change in the HTTP Proxy Service Used for OSN - Oracle Supplier Network Starting February 16th

Oracle Supplier Network currently uses the HTTP Proxy service - www-proxy.oracleoutsourcing.com - for document delivery.  The proxy service is due to be decommissioned on 16th Feb 2014 at 10:00 AM GMT and a new proxy service hosted by Oracle Managed Cloud Services - omcs-proxy.oracleoutsourcing.com - will be used instead.

What does this mean for Oracle Supplier Network customers?

Outbound requests from Oracle HTTP Server mid-tiers should go through the OnDemand HTTP proxy services, www-proxy.oracleoutsourcing.com and omcs-proxy.oracleoutsourcing.com, which are the BIG-IP virtual servers that load balance the actual physical devices.

To ensure continued connectivity, the subnets for the new proxy service must be allowed access in customer's firewall.  Please see 'What are the IP Addresses for OSN' (Doc ID 435409.1) for a listing of the required subnets.  You may open the firewall to receive requests from the subnets mentioned in the note.

These configuration changes need to be done by 16th Feb 2014, 10:00 AM GMT.  If you do not complete these changes before the mentioned time, the documents delivered by Oracle Supplier Network might fail to reach your ERP system."

For more information see the Procurement Community thread: 'Urgent!!! FAQ - Change in the HTTP Proxy Service Used for Oracle Supplier Network (Doc ID 1620906.1)'.

Comments:

Are you blocking outgoing traffic from the OSN test hub to ports in the 8000 range? Our Oracle Apps server that is defined to the OSN test hub uses port 8050. When we run a "Self-test" in OSN, we receive an "SSL Handshake Error" and see no traffic at all hitting our firewall. If I change the port to 443, we then see the traffic hitting our Firewall. However, we do not use port 443 for any of our test systems.

We are trying to test the proxy server changes as described in the OSN notification, but are hitting this issue. Ironically, this is not an issue for our production environment because we use port 443 for production. I opened an SR yesterday, provided all my analysis, and have not heard anything. We are dead in the water from a test environment perspective.

Posted by Jerry Conticchio on February 20, 2014 at 10:31 AM EST #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Welcome to the EBS Support Blog where Oracle insiders share news and information about EBS products including new releases, tips and tricks, troubleshooting guides, upcoming webcasts and links to EBS Communities.

Stay Connected

Twitter

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
5
6
12
13
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today