| Author |
Message
|
| zhaider |
 Posted: Thu Oct 29, 2015 9:54 am Post subject: SSL Setup Issue |
 |
|
Apprentice
Joined: 08 Oct 2015
Posts: 40
|
Hi,
I'm trying to setup the SSL for message broker by following some guides on internet but couldn't get it to work. I was provided with a certificate named certnew.cer So far this is what I have done.
1)Import certificate
keytool -import -trustcacerts -alias root.Cert -file certnew.cer -keystore SOABroker.jks
2)traverse to C:\Program Files\IBM\MQSI\9.0.0.0\jre17\lib\security
keytool -import -trustcacerts -alias root.Cert -file "C:\Program Files (x86)\IBM\source\WebSphere MQ 7.5.0.5\jre\jre\bin\certnew.cer" -keypass 123456 -keystore cacerts -storepass 123456
4)Enable SSL
mqsichangeproperties SOABroker -b httplistener -o HTTPListener -n enableSSLConnector -v true
5)Modify Broker to point to Keystore file
mqsichangeproperties SOABroker -b httplistener -o HTTPSConnector -n keystoreFile -v "C:\Program Files (x86)\IBM\source\WebSphere MQ 7.5.0.5\jre\jre\bin\SOABroker.jks"
6)Add Broker Keystore file to broker registry
mqsichangeproperties SOABroker -o BrokerRegistry -n brokerKeystoreFile -v "C:\Program Files (x86)\IBM\source\WebSphere MQ 7.5.0.5\jre\jre\bin\SOABroker.jks"
7)Add Broker Truststore file to broker registry
mqsichangeproperties SOABroker -o BrokerRegistry -n brokerTruststoreFile -v "C:\Program Files\IBM\MQSI\9.0.0.0\jre17\lib\security\cacerts"
 Set registry password for broker trustsore
mqsisetdbparms SOABroker -n brokerTruststore::password -u temp -p changeit
9) associate the broker with keystore password
mqsichangeproperties SOABroker -b httplistener -o HTTPSConnector -n keystorePass -v 123456
10) Associate a port fr broker to serve HTTPS rquests
mqsichangeproperties SOABroker -b httplistener -o HTTPSConnector -n port -v 7094
11) Associate a port for broker to serve HTTP requests
mqsichangeproperties SOABroker -b httplistener -o HTTPConnector -n port -v 7091
12 Change JVM Attributes
mqsichangeproperties SOABroker -o ComIbmJVMManager -n jvmMaxHeapSize -v 1048576000
mqsichangeproperties SOABroker -o ComIbmJVMManager -n jvmMinHeapSize -v 134217728
13) Verify the broker properties
mqsireportproperties SOABroker -b httplistener -o HTTPConnector -n port
mqsireportproperties SOABroker -b httplistener -o HTTPSConnector -n port
mqsireportproperties SOABroker -e Ofam -o ComIbmJVMManager -r
14)Restart the Broker
mqsistop SOABroker
mqsistart SOABroker
+++++++++++++++++++++++++++++++++++++++++++++++++
CONFIGURING PORTS EXCLUSIVELY FOR EXECUTION GROUP
+++++++++++++++++++++++++++++++++++++++++++++++++
mqsichangeproperties SOABroker -e Ofam -o HTTPSConnector -n clientAuth -v true
15)Configure SSL Protocol
mqsichangeproperties SOABroker -e Ofam -o HTTPSConnector -n sslProtocol -v SSLv3
16)Configure the port for SOAP over HTTP requests
mqsichangeproperties SOABroker -e Ofam -o HTTPSConnector -n explicitlySetPortNumber -v 7963
17)Associate the keystore file with broker EG
mqsichangeproperties SOABroker -e Ofam -o HTTPSConnector -n keystoreFile -v "C:\Program Files (x86)\IBM\source\WebSphere MQ 7.5.0.5\jre\jre\bin\SOABroker.jks"
18)Associate keystor type
mqsichangeproperties SOABroker -e Ofam -o HTTPSConnector -n keystoreType -v JKS
19)Associate Keystore password
mqsichangeproperties SOABroker -e Ofam -o HTTPSConnector -n keystorePass -v 123456
+++++++++++++++++++++++++++++++++++++++++++++++
CONFIGURING JVM ATTRIBUTES FOR EXECUTION GROUPS
+++++++++++++++++++++++++++++++++++++++++++++++
20)Configuring Keystore file
mqsichangeproperties SOABroker -e Ofam -o ComIbmJVMManager -n keystoreFile -v "C:\Program Files (x86)\IBM\source\WebSphere MQ 7.5.0.5\jre\jre\bin\SOABroker.jks"
21)Keystore Type
mqsichangeproperties SOABroker -e Ofam -o ComIbmJVMManager -n keystoreType -v JKS
22)
mqsichangeproperties SOABroker -e Ofam -o ComIbmJVMManager -n keystorePass -v 123456
23)
mqsichangeproperties SOABroker -e Ofam -o ComIbmJVMManager -n truststoreFile -v "C:\Program Files (x86)\IBM\source\WebSphere MQ 7.5.0.5\jre\jre\bin\SOABroker.jks"
24)
mqsichangeproperties SOABroker -e Ofam -o ComIbmJVMManager -n truststoreType -v JKS
25)
mqsichangeproperties SOABroker -e Ofam -o ComIbmJVMManager -n truststorePass -v brokerTruststore::password
mqsireportproperties SOABroker -e Ofam -o HTTPSConnector -r
Now I was given an app with a webservice which is configured to run on HTTP as well as HTTPS. WHen I try to acess the WSDL through the HTTP link, it works but when I try to put the HTTPS WSDL link in the Internet Explorer I get the page not found error.
I tried with msireport properties command and it seems to return the correct port I configured for SSL.
Any idea how to debug this thing would be greatly appreciated.
Last edited by zhaider on Thu Oct 29, 2015 11:08 am; edited 2 times in total |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Oct 29, 2015 10:58 am Post subject: Re: SSL Setup Issue |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| zhaider wrote: |
| Any idea how to debug this thing would be greatly appreciated. |
Where do you set the trust store password for the EG listener? I see you setting the key store password in step 9.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 29, 2015 11:01 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
And don't double post. If your query is urgent, raise a PMR; we don't have an SLA.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| zhaider |
| Posted: Thu Oct 29, 2015 11:05 am Post subject: |
|
|
Apprentice
Joined: 08 Oct 2015
Posts: 40
|
@ Vitor
Sorry, I thought some error occured and my post got deleted. I don't remember it being posted into this forum.
And Sorry I forgot to post the complete steps.
+++++++++++++++++++++++++++++++++++++++++++++++++
CONFIGURING PORTS EXCLUSIVELY FOR EXECUTION GROUP
+++++++++++++++++++++++++++++++++++++++++++++++++
mqsichangeproperties SOABroker -e Ofam -o HTTPSConnector -n clientAuth -v true
15)Configure SSL Protocol
mqsichangeproperties SOABroker -e Ofam -o HTTPSConnector -n sslProtocol -v SSLv3
16)Configure the port for SOAP over HTTP requests
mqsichangeproperties SOABroker -e Ofam -o HTTPSConnector -n explicitlySetPortNumber -v 7963
17)Associate the keystore file with broker EG
mqsichangeproperties SOABroker -e Ofam -o HTTPSConnector -n keystoreFile -v "C:\Program Files (x86)\IBM\source\WebSphere MQ 7.5.0.5\jre\jre\bin\SOABroker.jks"
18)Associate keystor type
mqsichangeproperties SOABroker -e Ofam -o HTTPSConnector -n keystoreType -v JKS
19)Associate Keystore password
mqsichangeproperties SOABroker -e Ofam -o HTTPSConnector -n keystorePass -v 123456
+++++++++++++++++++++++++++++++++++++++++++++++
CONFIGURING JVM ATTRIBUTES FOR EXECUTION GROUPS
+++++++++++++++++++++++++++++++++++++++++++++++
20)Configuring Keystore file
mqsichangeproperties SOABroker -e Ofam -o ComIbmJVMManager -n keystoreFile -v "C:\Program Files (x86)\IBM\source\WebSphere MQ 7.5.0.5\jre\jre\bin\SOABroker.jks"
21)Keystore Type
mqsichangeproperties SOABroker -e Ofam -o ComIbmJVMManager -n keystoreType -v JKS
22)
mqsichangeproperties SOABroker -e Ofam -o ComIbmJVMManager -n keystorePass -v 123456
23)
mqsichangeproperties SOABroker -e Ofam -o ComIbmJVMManager -n truststoreFile -v "C:\Program Files (x86)\IBM\source\WebSphere MQ 7.5.0.5\jre\jre\bin\SOABroker.jks"
24)
mqsichangeproperties SOABroker -e Ofam -o ComIbmJVMManager -n truststoreType -v JKS
25)
mqsichangeproperties SOABroker -e Ofam -o ComIbmJVMManager -n truststorePass -v brokerTruststore::password
mqsireportproperties SOABroker -e Ofam -o HTTPSConnector -r |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 29, 2015 11:08 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Does the mqsireportproperties for the HTTPS connector not only show the correct port but the URL you expect being registered with the connector? On the same vein, does a netstat show the SSL port as open?
What errors appear in the broker or EG logs regarding any SSL issues?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 29, 2015 11:10 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| zhaider wrote: |
I don't remember it being posted into this forum.
And Sorry I forgot to post the complete steps.
|
I suppose congratulations are in order for accidentally posting in the right place, tempered only by accidentally failing to post all the steps..... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| zhaider |
| Posted: Thu Oct 29, 2015 11:24 am Post subject: |
|
|
Apprentice
Joined: 08 Oct 2015
Posts: 40
|
| Vitor wrote: |
Does the mqsireportproperties for the HTTPS connector not only show the correct port but the URL you expect being registered with the connector? On the same vein, does a netstat show the SSL port as open?
What errors appear in the broker or EG logs regarding any SSL issues? |
No, the mqsireportproperties don't show me the URL, only the port.
And I haven't checked through netstat but I tried to telnet it and that didn't work.
And, I haven't found any errors regarding this in the log file which is placed under the [WebsphereMQInstalledPath]/errors directory.
Is there any other place should I look for logs? |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 29, 2015 11:39 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| zhaider wrote: |
| Vitor wrote: |
Does the mqsireportproperties for the HTTPS connector not only show the correct port but the URL you expect being registered with the connector? On the same vein, does a netstat show the SSL port as open?
What errors appear in the broker or EG logs regarding any SSL issues? |
No, the mqsireportproperties don't show me the URL, only the port.
And I haven't checked through netstat but I tried to telnet it and that didn't work.
|
Then you might think you're using an HTTPS endpoint, but the broker respectfully disagrees and has the high ground in this debate.
Fix that, then circle back to the SSL configuration.
I speculate about this:
| zhaider wrote: |
| Now I was given an app with a webservice which is configured to run on HTTP as well as HTTPS. WHen I try to acess the WSDL through the HTTP link, it works but when I try to put the HTTPS WSDL link in the Internet Explorer I get the page not found error. |
The WSDL may well contain bindings/port/widgets/web service magic that describes both HTTP and HTTPS endpoints. Are you entirely sure that broker isn't just exposing the HTTP one? How exactly was this "app" put inside the broker?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| zhaider |
| Posted: Thu Oct 29, 2015 11:54 am Post subject: |
|
|
Apprentice
Joined: 08 Oct 2015
Posts: 40
|
| Vitor wrote: |
| zhaider wrote: |
| Vitor wrote: |
Does the mqsireportproperties for the HTTPS connector not only show the correct port but the URL you expect being registered with the connector? On the same vein, does a netstat show the SSL port as open?
What errors appear in the broker or EG logs regarding any SSL issues? |
No, the mqsireportproperties don't show me the URL, only the port.
And I haven't checked through netstat but I tried to telnet it and that didn't work.
|
Then you might think you're using an HTTPS endpoint, but the broker respectfully disagrees and has the high ground in this debate.
Fix that, then circle back to the SSL configuration.
|
I didn't get you. Can you please explain in detail.
| Vitor wrote: |
I speculate about this:
| zhaider wrote: |
| Now I was given an app with a webservice which is configured to run on HTTP as well as HTTPS. WHen I try to acess the WSDL through the HTTP link, it works but when I try to put the HTTPS WSDL link in the Internet Explorer I get the page not found error. |
The WSDL may well contain bindings/port/widgets/web service magic that describes both HTTP and HTTPS endpoints. Are you entirely sure that broker isn't just exposing the HTTP one? How exactly was this "app" put inside the broker? |
Well, I was given a bar file to be deployed on the MQ. it had some services for which I was told that it runs on some other setup just fine. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 29, 2015 12:07 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| zhaider wrote: |
| I didn't get you. Can you please explain in detail. |
What I mean is you're getting a "page not found" because that URL isn't live. Irrespective of your SSL configuration, there's no service there for the browser to connect to.
| zhaider wrote: |
| Well, I was given a bar file to be deployed on the MQ. it had some services for which I was told that it runs on some other setup just fine. |
Does the "some other set up" include SSL? For the exact bar file you've been given? Does the exact bar file you've been given have setting for HTTP or HTTPS? If so, why not just copy their SSL configuration steps?
Also do not talk about MQ. You are not "deploying on the MQ", you are deploying on a broker. That's why this is the right section of the forum for your question and the General MQ Support section was not.
Confusing the 2 products will just make things worse for you.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 29, 2015 12:10 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Also, if you have the WSDL for this endpoint, why not produce a dummy application that supports the endpoint for testing and validation purposes? Why use this opaque bar file?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Oct 30, 2015 6:48 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You did not specify whether you followed the infocenter steps to setup a PKI infrastructure.
From the looks of your posts you might have botched that phase.
Go back to the drawing board and make sure your jks files contain the expected information.
keystore => private key(s) / public key pairs
trustore => public keys and signer certs chain
Note that the keystore file can/may double as trustsore file.
Hae fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| zhaider |
| Posted: Fri Oct 30, 2015 8:43 am Post subject: |
|
|
Apprentice
Joined: 08 Oct 2015
Posts: 40
|
| Vitor wrote: |
| zhaider wrote: |
| I didn't get you. Can you please explain in detail. |
What I mean is you're getting a "page not found" because that URL isn't live. Irrespective of your SSL configuration, there's no service there for the browser to connect to.
| zhaider wrote: |
| Well, I was given a bar file to be deployed on the MQ. it had some services for which I was told that it runs on some other setup just fine. |
Does the "some other set up" include SSL? For the exact bar file you've been given? Does the exact bar file you've been given have setting for HTTP or HTTPS? If so, why not just copy their SSL configuration steps?
Also do not talk about MQ. You are not "deploying on the MQ", you are deploying on a broker. That's why this is the right section of the forum for your question and the General MQ Support section was not.
Confusing the 2 products will just make things worse for you. |
Yes, the other setup include SSL but I don't have their configuration steps noted anywhere. And I tried with simple application by deploying it to Broker, still no luck.
I too think that there's some kind of issue with HTTPS end point and not the SSL configuration. The browser instantaneously displays the page not found error.
Here are the output of mqsireportproperties command from the other live setup:
C:\Windows\system32>mqsireportproperties UBLIIBLIVE -b httplistener -o HTTPSConn
ector -r
HTTPSConnector
uuid='HTTPSConnector'
algorithm='Platform Default'
clientAuth='Platform Default'
keystoreFile='C:\Program Files\IBM\MQSI\9.0.0.0\jre17\lib\security\jkssoa.jks'
keystorePass='********'
keystoreType='Platform Default'
truststoreFile='C:\Program Files\IBM\MQSI\9.0.0.0\jre17\lib\security\soa-trust
store.jks'
truststorePass='********'
truststoreType='Platform Default'
sslProtocol='Platform Default'
ciphers='Platform Default'
keyAlias=''
keypass='********'
keyAlias='Platform Default'
crlFile='Platform Default'
propagateClientCert='Platform Default'
address=''
port='7899'
maxPostSize=''
acceptCount=''
compressableMimeTypes=''
compression=''
connectionLinger=''
connectionTimeout=''
maxHttpHeaderSize=''
maxKeepAliveRequests=''
maxThreads=''
minSpareThreads=''
noCompressionUserAgents=''
restrictedUserAgents=''
socketBuffer=''
tcpNoDelay=''
enableLookups='false'
BIP8071I: Successful command completion.
C:\Windows\system32>mqsireportproperties UBLIIBLIVE -e HRCAPILive -o HTTPSConnec
tor -r
HTTPSConnector
uuid='HTTPSConnector'
userTraceLevel='none'
traceLevel='none'
userTraceFilter='none'
traceFilter='none'
port='7844'
address=''
maxPostSize=''
acceptCount=''
compressableMimeTypes=''
compression=''
connectionLinger=''
connectionTimeout=''
maxHttpHeaderSize=''
maxKeepAliveRequests=''
maxThreads=''
minSpareThreads=''
noCompressionUserAgents=''
restrictedUserAgents=''
socketBuffer=''
tcpNoDelay=''
explicitlySetPortNumber=''
enableLookups=''
enableMQListener=''
shutdownDelay=''
allowCrossConnectorPolling=''
autoRespondHTTPHEADRequests=''
algorithm=''
clientAuth=''
keystoreFile=''
keystorePass='********'
keystoreType=''
truststoreFile=''
truststorePass='********'
truststoreType=''
sslProtocol=''
ciphers=''
keypass='********'
keyAlias=''
sslSessionTimeout=''
crlFile=''
propagateClientCert=''
sessionCacheSize=''
Connector
cachedSSLSessions='0'
port='7844'
type='Embedded'
URLRegistration
url='/UBL_HRC_API/AccountValidationLive'
outstandingRequests='0'
UsedBySOAPNNodes='TRUE'
UsedByHTTPNNodes='FALSE'
nodeLabel='Request'
URLRegistration
url='/UBL_HRC_API/BalanceInquiryLive'
outstandingRequests='0'
UsedBySOAPNNodes='TRUE'
UsedByHTTPNNodes='FALSE'
nodeLabel='Request'
URLRegistration
url='/UBL_HRC_API/TransactionInquiryLive'
outstandingRequests='0'
UsedBySOAPNNodes='TRUE'
UsedByHTTPNNodes='FALSE'
nodeLabel='Request'
URLRegistration
url='/UBL_HRC_API/FundTransferLive'
outstandingRequests='0'
UsedBySOAPNNodes='TRUE'
UsedByHTTPNNodes='FALSE'
nodeLabel='Request'
BIP8071I: Successful command completion.
C:\Windows\system32>
And this is the output from from my environment:
C:\Windows\system32>mqsireportproperties SOAUBLBroker -b httplistener -o HTTPSCo
nnector -r
HTTPSConnector
uuid='HTTPSConnector'
algorithm='Platform Default'
clientAuth='true'
keystoreFile='C:\Program Files\IBM\MQSI\9.0.0.0\jre17\lib\security\jkssoa.jks'
keystorePass='********'
keystoreType='Platform Default'
truststoreFile='C:\Program Files\IBM\MQSI\9.0.0.0\jre17\lib\security\soa-trust
store.jks'
truststorePass='********'
truststoreType='Platform Default'
sslProtocol='Platform Default'
ciphers='Platform Default'
keyAlias=''
keypass='********'
keyAlias='Platform Default'
crlFile='Platform Default'
propagateClientCert='Platform Default'
address=''
port='7094'
maxPostSize=''
acceptCount=''
compressableMimeTypes=''
compression=''
connectionLinger=''
connectionTimeout=''
maxHttpHeaderSize=''
maxKeepAliveRequests=''
maxThreads=''
minSpareThreads=''
noCompressionUserAgents=''
restrictedUserAgents=''
socketBuffer=''
tcpNoDelay=''
enableLookups='false'
BIP8071I: Successful command completion.
C:\Windows\system32>
C:\Windows\system32>mqsireportproperties SOAUBLBroker -e Ofam -o HTTPSConnector
-r
HTTPSConnector
uuid='HTTPSConnector'
userTraceLevel='none'
traceLevel='none'
userTraceFilter='none'
traceFilter='trace'
port='7963'
address=''
maxPostSize=''
acceptCount=''
compressableMimeTypes=''
compression=''
connectionLinger=''
connectionTimeout=''
maxHttpHeaderSize=''
maxKeepAliveRequests=''
maxThreads=''
minSpareThreads=''
noCompressionUserAgents=''
restrictedUserAgents=''
socketBuffer=''
tcpNoDelay=''
explicitlySetPortNumber='7963'
enableLookups=''
enableMQListener=''
shutdownDelay=''
allowCrossConnectorPolling=''
autoRespondHTTPHEADRequests=''
algorithm=''
clientAuth='true'
keystoreFile='C:\Program Files (x86)\IBM\source\WebSphere MQ 7.5.0.5\jre\jre\b
in\SOAUBLBroker.jks'
keystorePass='********'
keystoreType='JKS'
truststoreFile=''
truststorePass='********'
truststoreType=''
sslProtocol='SSLv3'
ciphers=''
keypass='********'
keyAlias=''
sslSessionTimeout=''
crlFile=''
propagateClientCert=''
Connector
port='7963'
type='Embedded'
URLRegistration
url='/OFAMWebEx'
outstandingRequests='0'
outstandingTimeoutRequests='0'
UsedBySOAPNNodes='TRUE'
UsedByHTTPNNodes='FALSE'
nodeLabel='SOAP Input'
BIP8071I: Successful command completion.
C:\Windows\system32>
I even imported the same keystore and trustore file from the other running environment and used it in mine but that still didn't solve the issue. |
|
| Back to top |
|
|
| zhaider |
| Posted: Fri Oct 30, 2015 8:48 am Post subject: |
|
|
Apprentice
Joined: 08 Oct 2015
Posts: 40
|
| fjb_saper wrote: |
You did not specify whether you followed the infocenter steps to setup a PKI infrastructure.
From the looks of your posts you might have botched that phase.
Go back to the drawing board and make sure your jks files contain the expected information.
keystore => private key(s) / public key pairs
trustore => public keys and signer certs chain
Note that the keystore file can/may double as trustsore file.
Hae fun |
I used this guide.
And I redid the whole thing again, and with the truststore and keystore files being taken from the running environment. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Oct 30, 2015 9:02 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| zhaider wrote: |
| I too think that there's some kind of issue with HTTPS end point and not the SSL configuration. The browser instantaneously displays the page not found error. |
Well one thing occurs to me:
| zhaider wrote: |
Here are the output of mqsireportproperties command from the other live setup:
| Code: |
URLRegistration
url='/UBL_HRC_API/AccountValidationLive'
outstandingRequests='0'
UsedBySOAPNNodes='TRUE'
UsedByHTTPNNodes='FALSE'
nodeLabel='Request'
URLRegistration
url='/UBL_HRC_API/BalanceInquiryLive'
outstandingRequests='0'
UsedBySOAPNNodes='TRUE'
UsedByHTTPNNodes='FALSE'
nodeLabel='Request'
URLRegistration
url='/UBL_HRC_API/TransactionInquiryLive'
outstandingRequests='0'
UsedBySOAPNNodes='TRUE'
UsedByHTTPNNodes='FALSE'
nodeLabel='Request'
URLRegistration
url='/UBL_HRC_API/FundTransferLive'
outstandingRequests='0'
UsedBySOAPNNodes='TRUE'
UsedByHTTPNNodes='FALSE'
nodeLabel='Request'
|
|
| zhaider wrote: |
And this is the output from from my environment:
| Code: |
URLRegistration
url='/OFAMWebEx'
outstandingRequests='0'
outstandingTimeoutRequests='0'
UsedBySOAPNNodes='TRUE'
UsedByHTTPNNodes='FALSE'
nodeLabel='SOAP Input'
|
|
If this bar file is their working application, why are there 2 different URLs exposed?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
