My Oracle Support Banner

FAQ - Change in the HTTP Proxy Service Used for Oracle Supplier Network (Doc ID 1620906.1)

Last updated on JUNE 21, 2023

Applies to:

Oracle Business Network - Version 5.1 and later
Information in this document applies to any platform.


Explain to the reader the purpose of the FAQ. Enter a clear description of what the questions and answers are trying to achieve. Be precise. It is this section that will guide the reader to decide whether the document is applicable.

 This document is to clarify the questions related to the change in the HTTP Proxy Service used for Oracle Supplier Network scheduled for Feb-16-2014. This date has extended to 23rd Feb 2014.

Questions and Answers

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Questions and Answers
 1. Any changes to access the OSN url?
 2. Is anything required on the database server level?
 3. What  setup changes would be required in the iSupplier Portal Application because of this change.
 4. Will the URL still available to be used in profiles for Punchout for On Demand/Cloud customers?
 5. Any additional configuration changes required other than firewall?  e.g., profile options, auto-config parameters, iProcurement configurations, etc.
 6. Which type of transactions will be affected? Also, which communication methods will be impacted?
 7. If using OXTA do we need to open the firewall?
 8. As a test, should the application server  be able to connect to each IP address / Port listed?
 9. What are the ports involved?
 10. Need to know whether it is Inbound/Outbound from the servers
 11. What server on the EBS side - Internal Tier Application server, External Tier (Application/Proxy) Servers  etc?
 12. Is the supplier or buying organization which needs to execute the changes?
 13. Will this affect the Punch In feature (iSupplier access through OSN)?
 14. What does the "/" mean in the IP address? Does 0/26 mean from 0 to 26?
 15. Due to the changes, were the On Demand/Cloud firewall opened for the IP addresses for OSN and Punchout features used by On Demand/Cloud customers?
 16. For the current OSN connectivity we did not have to make any specific firewall port openings to any of the Oracle OSN IP addresses. Do we need to do the changes now?
 17. Also is there any way we can test this upfront that we are are able to access from/to the new OSN proxy servers?
 18. We have trading partners setup in  our prod/test system using these urls.  Do the new IP address / Ports apply to both dev and prod URLs?
 19. Are there any other changes we would need to make to the XML Gateway, Define Trading partner settings etc.? We use
 20. Where do I check the URL to which OSN is sending the messages?
 21. Is there any way  to have this change deferred to a later date from Feb-16th?
 22. Why there are more IP addresses than before?
 23. I'm getting handshake errors while testing the new connectivity. 
 24. Which IP addresses are for Test and Production OSN?
  25. Which IP addresses should be allowed in the firewall?

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.