Focal Point
[SOLVED] iIT - SM - Internal Queue is not working

This topic can be found at:

September 27, 2016, 12:04 PM
[SOLVED] iIT - SM - Internal Queue is not working
I have channel that is published as application that has internal queue in it. suppose queue name I gave is queue1. and its in application application1.

I published this application and its running on SM / local machine localhost. now I have a flow that I am testing in iIT.

I added internal queue service object on this flow. refereeing to queue name: application1.queue1, or just queue1 or application1.channel1.queue1. but test trace shows, unknown internal queue.

How to access the queue name from PF?


This message has been edited. Last edited by: Tamra,
September 27, 2016, 02:01 PM
An internal queue can only be accessed by channels or agents that are deployed in the same application. Thus internal to the application.

"There is no limit to what you can achieve ... if you don’t care who gets the credit." Roger Abbott
September 30, 2016, 11:07 AM
The following response is from the iWay group:

1. The queue name has nothing to do with the name of the application or a channel or a listener. When you create an internal queue listener, there is a parameter "Name of Internal Queue", which defines the name of the actual queue. So your internal emit service in the pflow should emit the message to that queue, lets say its name is FRED, which has nothing to do with the name of the application/channel/listener.

2. Think of Internal Queues (IQs) as Java in-memory queues. The queue defined by a listener is available only within a given JVM (meaning within a given application/iIA or a managed configuration). If you want to test-run your pflow which has an internal emit service, you need to ensure that the environment you are testing against has that queue up and available. You should be able to achieve this by the following:
* Package your IQ based channel into an iWay Integration Application, then test run your pflow with emit service against that iIA instance. The iIA runs in its own JVM with the running IQ listener and the pflow tested against this JVM executing the IQ Emit should be able to find the queue.
* You can also package the pflow which has the IQ emit + the channel which has IQ listener into the same iIA, deploy it, start it and then run the pflow directly in that iIA. You can run the pflow either from command line such as "flow Name_of_flow" or as part of another channel. For commands accessible from Command prompt you can type in "help" or refer to the manual.

Please let us know if this answers your question.

If this does answer your question then we ask all Focal Point members to update the subject line with Tag your topic with keywords . This way members will know whether the topic has been successfully resolved or not.

Thank your for participating in the Focal Point Forum,
Tamra Colangelo
Focal Point Moderator
Information Builders

WebFOCUS 8x - BI Portal, Developer Studio, App Studio, Excel, PDF, Active Formats and HTML5
October 10, 2016, 03:31 PM
Hi Tamra,

Thank you for your response. I have set it up like this and having trouble writing to queue still..

I have application running on SM that has internal queue and process flow that takes the message coming to it and processing it.

I have another application that has test flow, writing to this internal queue, also running on SM as another application.

Message sent to that queuename is not getting captured, Am I missing something? please advise...

Windows, All Outputs