| Author |
Message |
 Topic: No auto default HTTPs port after SOUPInput flow deployed |
hopiee
Replies: 7
Views: 6268
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Mon Sep 30, 2013 10:48 pm Subject: No auto default HTTPs port after SOUPInput flow deployed |
Issue solved.
I had re-run all the command to set the brokerproperties. Restart the queue mgr & everything are in order.
 |
| Topic: No auto default HTTPs port after SOUPInput flow deployed |
hopiee
Replies: 7
Views: 6268
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Sep 30, 2013 7:16 pm Subject: No auto default HTTPs port after SOUPInput flow deployed |
lancelotlinc, my mistake in typo. Should be SOAPInput instead of SOUPInput
 |
| Topic: No auto default HTTPs port after SOUPInput flow deployed |
hopiee
Replies: 7
Views: 6268
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Sep 30, 2013 7:11 pm Subject: No auto default HTTPs port after SOUPInput flow deployed |
MQSI 7.0.0.3
Same as dev server. |
| Topic: No auto default HTTPs port after SOUPInput flow deployed |
hopiee
Replies: 7
Views: 6268
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Sep 30, 2013 4:35 am Subject: No auto default HTTPs port after SOUPInput flow deployed |
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 a ... |
| Topic: Cannot invoke webservices HTTPS |
hopiee
Replies: 3
Views: 3858
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sun Jul 07, 2013 12:04 am Subject: Cannot invoke webservices HTTPS |
Hi fjb_saper,
Thanks for your response. After re-generating the wsdl with adding the binding of soapAction = 'executionDecisionService', problem solved.
Thanks for the hint!
|
| Topic: Cannot invoke webservices HTTPS |
hopiee
Replies: 3
Views: 3858
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sat Jul 06, 2013 8:34 pm Subject: Cannot invoke webservices HTTPS |
Additional info:
WSDL file
<?xml version="1.0" encoding="UTF-8" ?>
- <wsdl:definitions name="AlphaSMSStatusHTTPS" targetNamespace="http://te ... |
| Topic: Cannot invoke webservices HTTPS |
hopiee
Replies: 3
Views: 3858
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sat Jul 06, 2013 8:30 pm Subject: Cannot invoke webservices HTTPS |
Hi,
I had hosted the HTTPS web services and i had used the internet browser to check whether the services is up with URL:
https://[IP]:7843/AlphaSMSStatusHTTPSService?wsdl
Everything looks fine. ... |
| Topic: Timer control & notification node for batch processing |
hopiee
Replies: 5
Views: 5807
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue May 21, 2013 2:31 am Subject: Timer control & notification node for batch processing |
| Thanks for all the input. After had the discussion, it is decided to use timer node to perform hourly db extraction which consist the schedule time provided from application. The schedule time which c ... |
| Topic: Timer control & notification node for batch processing |
hopiee
Replies: 5
Views: 5807
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri May 17, 2013 11:09 pm Subject: Timer control & notification node for batch processing |
| Understood that timer control shall have the UID to be associated with one timer notification node. But I need to have a message flow that is flexible enough to hold multiple scheduler (for batch proc ... |
