ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » No auto default HTTPs port after SOUPInput flow deployed

Post new topic  Reply to topic
 No auto default HTTPs port after SOUPInput flow deployed « View previous topic :: View next topic » 
Author Message
hopiee
PostPosted: Mon Sep 30, 2013 4:35 am    Post subject: No auto default HTTPs port after SOUPInput flow deployed Reply with quote

Newbie

Joined: 17 May 2013
Posts: 9
I was successfully to get the HTTPs message flow with SOUPInput node in development server.

But when come to UAT server, i wasnt able to do so. Deployment was successful, but no default port was assigned. Try on the url with ?wsdl, it mentioned page cannot be found.

Steps done:
1) Newly created execution group: SMS_EG
2) PK implementation was migrated from development server into UAT server, with exactly same directory location.
3) mqsireportproperties QUR_MY_BRK01 -o BrokerRegistry -r showed:

BrokerRegistry
uuid='BrokerRegistry'
brokerKeystoreType='JKS'
brokerKeystoreFile='/opt/IBM/mqsi/7.0/WMBKeys/keystore.jks'
brokerKeystorePass='brokerKeystore::password'
brokerTruststoreType='JKS'
brokerTruststoreFile='/opt/IBM/mqsi/7.0/WMBKeys/truststore.jks'
brokerTruststorePass='brokerTruststore::password'
httpConnectorPortRange=''
httpsConnectorPortRange=''
modeExtensions=''
operationMode='enterprise'
shortDesc=''
longDesc=''

4) Setup accordingly for the below at Execution Group level
mqsichangeproperties QUR_MY_BRK01 -e SMS_EG -o HTTPSConnector -n sslProtocol -v SSL
mqsichangeproperties QUR_MY_BRK01 -e SMS_EG -o HTTPSConnector -n keystoreFile -v /opt/IBM/mqsi/7.0/WMBKeys/truststore.jks
mqsichangeproperties QUR_MY_BRK01 -e SMS_EG -o HTTPSConnector -n keystoreType -v JKS
mqsichangeproperties QUR_MY_BRK01 -e SMS_EG -o HTTPSConnector -n keystorePass -v abc123

5) Display the properties had done at execution group level
mqsireportproperties QUR_MY_BRK01 -e SMS_EG -o HTTPSConnector -r. No default port no. was assigned at this level as i would like WMB to provide the port no after deployment of msg flow.

HTTPSConnector
uuid='HTTPSConnector'
userTraceLevel='none'
traceLevel='none'
userTraceFilter='none'
traceFilter='none'
port='0'
address=''
allowTrace=''
maxPostSize=''
acceptCount=''
bufferSize=''
compressableMimeTypes=''
compression=''
connectionLinger=''
connectionTimeout=''
maxHttpHeaderSize=''
maxKeepAliveRequests=''
maxSpareThreads=''
maxThreads=''
minSpareThreads=''
noCompressionUserAgents=''
restrictedUserAgents=''
socketBuffer=''
tcpNoDelay=''
explicitlySetPortNumber=''
enableLookups=''
enableMQListener=''
shutdownDelay=''
algorithm=''
clientAuth=''
keystoreFile='/opt/IBM/mqsi/7.0/WMBKeys/truststore.jks'
keystorePass='********'
keystoreType='JKS'
sslProtocol='SSL'
ciphers=''
keypass='********'
keyAlias=''
sslSessionTimeout=''

6) Restart of broker.

5) When deployment of HTTP flows, i have no issue to get the ?wsdl display on IE.
When display on the HTTPConnector properties, it showed port with defaulted 7801

But when deployment of HTTPs flow, the HTTPsConnector properties just does not have default 7843 attached.

Everything setup as per development server and what could have wrong?


Im expecting the output below (taken from dev server):
HTTPSConnector
uuid='HTTPSConnector'
userTraceLevel='none'
traceLevel='none'
userTraceFilter='none'
traceFilter='none'
port='7843'
address=''
allowTrace=''
maxPostSize=''
acceptCount=''
bufferSize=''
compressableMimeTypes=''
compression=''
connectionLinger=''
connectionTimeout=''
maxHttpHeaderSize=''
maxKeepAliveRequests=''
maxSpareThreads=''
maxThreads=''
minSpareThreads=''
noCompressionUserAgents=''
restrictedUserAgents=''
socketBuffer=''
tcpNoDelay=''
explicitlySetPortNumber=''
enableLookups=''
enableMQListener=''
shutdownDelay=''
algorithm=''
clientAuth=''
keystoreFile='/opt/IBM/mqsi/7.0/WMBKeys/truststore.jks'
keystorePass='********'
keystoreType='JKS'
sslProtocol='SSL'
ciphers=''
keypass='********'
keyAlias=''
sslSessionTimeout=''
DefaultConnector
port='7843'
URLRegistration='/AlphaSMSStatusService'
nodeLabel='SOAP Input'
outstandingRequests='0'


But in UAT server, it just does not show any response after deployment (same as during setup).

HTTPSConnector
uuid='HTTPSConnector'
userTraceLevel='none'
traceLevel='none'
userTraceFilter='none'
traceFilter='none'
port='0'
address=''
allowTrace=''
maxPostSize=''
acceptCount=''
bufferSize=''
compressableMimeTypes=''
compression=''
connectionLinger=''
connectionTimeout=''
maxHttpHeaderSize=''
maxKeepAliveRequests=''
maxSpareThreads=''
maxThreads=''
minSpareThreads=''
noCompressionUserAgents=''
restrictedUserAgents=''
socketBuffer=''
tcpNoDelay=''
explicitlySetPortNumber=''
enableLookups=''
enableMQListener=''
shutdownDelay=''
algorithm=''
clientAuth=''
keystoreFile='/opt/IBM/mqsi/7.0/WMBKeys/truststore.jks'
keystorePass='********'
keystoreType='JKS'
sslProtocol='SSL'
ciphers=''
keypass='********'
keyAlias=''
sslSessionTimeout=''



Broker version: 7.0

Could anyone give me any clue?
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Mon Sep 30, 2013 4:38 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
Whats the effective level of your UAT server ? SOAP functionality was not delivered until 7.0.0.2.

Also whats your version ? 7.0 is incomplete version specification.

I think the SOUP functionality is still under development. My favorite is tomato.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
hopiee
PostPosted: Mon Sep 30, 2013 7:11 pm    Post subject: Reply with quote

Newbie

Joined: 17 May 2013
Posts: 9
MQSI 7.0.0.3

Same as dev server.
Back to top
View user's profile Send private message
hopiee
PostPosted: Mon Sep 30, 2013 7:16 pm    Post subject: Reply with quote

Newbie

Joined: 17 May 2013
Posts: 9
lancelotlinc, my mistake in typo. Should be SOAPInput instead of SOUPInput

Back to top
View user's profile Send private message
hopiee
PostPosted: Mon Sep 30, 2013 10:48 pm    Post subject: Reply with quote

Newbie

Joined: 17 May 2013
Posts: 9
Issue solved.

I had re-run all the command to set the brokerproperties. Restart the queue mgr & everything are in order.

Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Tue Oct 01, 2013 3:29 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
hopiee wrote:
MQSI 7.0.0.3

Same as dev server.


This is not the effective level. What is your effective level for each ?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
smdavies99
PostPosted: Tue Oct 01, 2013 3:41 am    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
lancelotlinc wrote:
hopiee wrote:
MQSI 7.0.0.3

Same as dev server.


This is not the effective level. What is your effective level for each ?


Does it matter? Is there some feature enhancement between 7.0.0.0 and 7.0.0.3 that enables this functionality?
If there is then fine but if there isn't then the actual effective level of the runtime is irrelevant isn't it?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Tue Oct 01, 2013 4:01 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
smdavies99 wrote:
lancelotlinc wrote:
hopiee wrote:
MQSI 7.0.0.3

Same as dev server.


This is not the effective level. What is your effective level for each ?


Does it matter? Is there some feature enhancement between 7.0.0.0 and 7.0.0.3 that enables this functionality?
If there is then fine but if there isn't then the actual effective level of the runtime is irrelevant isn't it?


As stated above, SOAP functionality was not fully delivered until 7.0.0.2. SO in this instance, it seems relevant.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » No auto default HTTPs port after SOUPInput flow deployed
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.