How Do WebLogic's Frontend Host and Port Settings Affect a BTM Environment? (Doc ID 2187262.1)

Last updated on SEPTEMBER 27, 2016

Applies to:

APM - Application Performance Management - Version 12.1.0.7.0 and later
Information in this document applies to any platform.

Goal

When using WebLogic's Frontend Host and Port settings it may cause a URL to be rewritten, as seen from OSB and/or BTM.  When BTM tries to access a WSDL's files (via "import") it may fail due to an incorrect URL.

For example, examine the following error:

<Sep 16, 2016 4:51:03 PM> WARNING <Discovery.OSB> [com.amberpoint.nanoagent.esb.osb12c.WsdlHelper][readWsdlUpdater]:
Errors reported reading WSDL located at http://172.1.2.3:8888/sbresource?PROXY/LocationQueryService%2FProxyService%2FLocationQueryServicePS
Found 1 errors and 1 warnings.
WARNING:An IOException occurred with importing WSDL definitions from the location "http://172.1.2.3:80/sbresource?PROXY%2FLocationQueryService%2FProxyService%2FLocationQueryServicePS%3AWSDL%2FCommonWSDL%2FLocationQueryServiceAbstract".
with root cause:
com.amberpoint.util.readers.WSDocumentReader$WSDocumentFileException:
The exception "com.amberpoint.protocol.TransportException: Unable to connect to host 172.1.2.3:80: Connection refused" occurred while reading the document from "http://172.1.2.3:80/sbresource?PROXY%2FLocationQueryService%2FProxyService%2FLocationQueryServicePS%3AWSDL%2FCommonWSDL%2FLocationQueryServiceAbstract".
com.amberpoint.util.readers.WSDocumentReader$WSDocumentFileException:
The exception "com.amberpoint.protocol.TransportException: Unable to connect to host 172.1.2.3:80: Connection refused" occurred while reading the document from "http://172.1.2.3:80/sbresource?PROXY%2FLocationQueryService%2FProxyService%2FLocationQueryServicePS%3AWSDL%2FCommonWSDL%2FLocationQueryServiceAbstract".
at com.amberpoint.util.readers.WSDocumentReader$CredentialFinder.getResource(WSDocumentReader.java:668)
at com.amberpoint.util.wsdl.WSDLReader.findImportedDocument(WSDLReader.java:1327)
at com.amberpoint.util.wsdl.WSDLReader.processImport(WSDLReader.java:1427)
at com.amberpoint.util.wsdl.WSDLUpdater.processImport(WSDLUpdater.java:961)
at com.amberpoint.util.wsdl.WSDLReader.readDefinitions(WSDLReader.java:1071)
at com.amberpoint.util.wsdl.WSDLReader.readDocumentInstance(WSDLReader.java:556)
at com.amberpoint.util.wsdl.WSDLReader.createDocumentInstance(WSDLReader.java:416)

In the above scenario the Frontend Port setting was "80" so it caused OSB to rewrite the port numbers in its "import" statements.  These URLs were not valid in this example environment so BTM's analysis of the WSDL failed.

How do you get all of this to work together and not fail in BTM?

 

Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms