MQ Queue manager alias
up vote
0
down vote
favorite
In our application we are maintaining queue manager names in the configuration file which are stored in database. At any time, only one queue manager name can be specified in the configuration file.
To support application fail over, it is required to connect to another queue manager with a different name.
It makes no sense to duplicate all configuration files due to different queue manager name. Is there any way at MQ level (alias may be) to refer with the same queue manager in the configuration file, but if the DR location is active it should connect to new queue manager.
websphere ibm-mq
asked Nov 20 at 0:45
Somnath Musib
1,4311336
|
show 1 more comment
up vote
0
down vote
favorite
In our application we are maintaining queue manager names in the configuration file which are stored in database. At any time, only one queue manager name can be specified in the configuration file.
To support application fail over, it is required to connect to another queue manager with a different name.
It makes no sense to duplicate all configuration files due to different queue manager name. Is there any way at MQ level (alias may be) to refer with the same queue manager in the configuration file, but if the DR location is active it should connect to new queue manager.
websphere ibm-mq
asked Nov 20 at 0:45
Somnath Musib
1,4311336
2
Use a blank QM name or a star.
– JoshMc
Nov 20 at 1:13
@JoshMc Thanks for your answer. How does then application know which queue manager to connects to?
– Somnath Musib
Nov 20 at 6:30
It connects to the queue manager that is listening on the ip and port provided.
– JoshMc
Nov 20 at 7:05
Possible duplicate of Connecting IBM MQ queue using F5 virtual ip and C++
– JoshMc
Nov 20 at 17:12
Also take a look at these two "How to create a qmgr alias" and "JMSWMQ2020: Failed to connect to queue manager"
– JoshMc
Nov 20 at 17:13
|
show 1 more comment
up vote
0
down vote
favorite
up vote
0
down vote
favorite
In our application we are maintaining queue manager names in the configuration file which are stored in database. At any time, only one queue manager name can be specified in the configuration file.
To support application fail over, it is required to connect to another queue manager with a different name.
It makes no sense to duplicate all configuration files due to different queue manager name. Is there any way at MQ level (alias may be) to refer with the same queue manager in the configuration file, but if the DR location is active it should connect to new queue manager.
websphere ibm-mq
asked Nov 20 at 0:45
Somnath Musib
1,4311336
In our application we are maintaining queue manager names in the configuration file which are stored in database. At any time, only one queue manager name can be specified in the configuration file.
To support application fail over, it is required to connect to another queue manager with a different name.
It makes no sense to duplicate all configuration files due to different queue manager name. Is there any way at MQ level (alias may be) to refer with the same queue manager in the configuration file, but if the DR location is active it should connect to new queue manager.
websphere ibm-mq
websphere ibm-mq
asked Nov 20 at 0:45
Somnath Musib
1,4311336
asked Nov 20 at 0:45
Somnath Musib
1,4311336
asked Nov 20 at 0:45
Somnath Musib
1,4311336
asked Nov 20 at 0:45
Somnath Musib
1,4311336
asked Nov 20 at 0:45
Somnath Musib
1,4311336
1,4311336
2
Use a blank QM name or a star.
– JoshMc
Nov 20 at 1:13
@JoshMc Thanks for your answer. How does then application know which queue manager to connects to?
– Somnath Musib
Nov 20 at 6:30
It connects to the queue manager that is listening on the ip and port provided.
– JoshMc
Nov 20 at 7:05
Possible duplicate of Connecting IBM MQ queue using F5 virtual ip and C++
– JoshMc
Nov 20 at 17:12
Also take a look at these two "How to create a qmgr alias" and "JMSWMQ2020: Failed to connect to queue manager"
– JoshMc
Nov 20 at 17:13
|
show 1 more comment
2
Use a blank QM name or a star.
– JoshMc
Nov 20 at 1:13
@JoshMc Thanks for your answer. How does then application know which queue manager to connects to?
– Somnath Musib
Nov 20 at 6:30
It connects to the queue manager that is listening on the ip and port provided.
– JoshMc
Nov 20 at 7:05
Possible duplicate of Connecting IBM MQ queue using F5 virtual ip and C++
– JoshMc
Nov 20 at 17:12
Also take a look at these two "How to create a qmgr alias" and "JMSWMQ2020: Failed to connect to queue manager"
– JoshMc
Nov 20 at 17:13
2
2
Use a blank QM name or a star.
– JoshMc
Nov 20 at 1:13
Use a blank QM name or a star.
– JoshMc
Nov 20 at 1:13
@JoshMc Thanks for your answer. How does then application know which queue manager to connects to?
– Somnath Musib
Nov 20 at 6:30
@JoshMc Thanks for your answer. How does then application know which queue manager to connects to?
– Somnath Musib
Nov 20 at 6:30
It connects to the queue manager that is listening on the ip and port provided.
– JoshMc
Nov 20 at 7:05
It connects to the queue manager that is listening on the ip and port provided.
– JoshMc
Nov 20 at 7:05
Possible duplicate of Connecting IBM MQ queue using F5 virtual ip and C++
– JoshMc
Nov 20 at 17:12
Possible duplicate of Connecting IBM MQ queue using F5 virtual ip and C++
– JoshMc
Nov 20 at 17:12
Also take a look at these two "How to create a qmgr alias" and "JMSWMQ2020: Failed to connect to queue manager"
– JoshMc
Nov 20 at 17:13
Also take a look at these two "How to create a qmgr alias" and "JMSWMQ2020: Failed to connect to queue manager"
– JoshMc
Nov 20 at 17:13
|
show 1 more comment
1 Answer
1
active
oldest
votes
up vote
0
down vote
As JoshMc said, use a blank or star for the queue manager name. After the connection, the application can use the getName method to retrieve the name of the queue manager.
MQQueueManager qMgr = new MQQueueManager(" ", mqht);
System.out.println("QMgr="+qMgr.getName());
Note: mqht is a Hashtable with the connection parameters.
answered Nov 20 at 15:37
Roger
4,594713
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
As JoshMc said, use a blank or star for the queue manager name. After the connection, the application can use the getName method to retrieve the name of the queue manager.
MQQueueManager qMgr = new MQQueueManager(" ", mqht);
System.out.println("QMgr="+qMgr.getName());
Note: mqht is a Hashtable with the connection parameters.
answered Nov 20 at 15:37
Roger
4,594713
add a comment |
up vote
0
down vote
As JoshMc said, use a blank or star for the queue manager name. After the connection, the application can use the getName method to retrieve the name of the queue manager.
MQQueueManager qMgr = new MQQueueManager(" ", mqht);
System.out.println("QMgr="+qMgr.getName());
Note: mqht is a Hashtable with the connection parameters.
answered Nov 20 at 15:37
Roger
4,594713
add a comment |
up vote
0
down vote
up vote
0
down vote
As JoshMc said, use a blank or star for the queue manager name. After the connection, the application can use the getName method to retrieve the name of the queue manager.
MQQueueManager qMgr = new MQQueueManager(" ", mqht);
System.out.println("QMgr="+qMgr.getName());
Note: mqht is a Hashtable with the connection parameters.
answered Nov 20 at 15:37
Roger
4,594713
As JoshMc said, use a blank or star for the queue manager name. After the connection, the application can use the getName method to retrieve the name of the queue manager.
MQQueueManager qMgr = new MQQueueManager(" ", mqht);
System.out.println("QMgr="+qMgr.getName());
Note: mqht is a Hashtable with the connection parameters.
answered Nov 20 at 15:37
Roger
4,594713
answered Nov 20 at 15:37
Roger
4,594713
answered Nov 20 at 15:37
Roger
4,594713
answered Nov 20 at 15:37
Roger
4,594713
4,594713
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53384666%2fmq-queue-manager-alias%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
Use a blank QM name or a star.
– JoshMc
Nov 20 at 1:13
@JoshMc Thanks for your answer. How does then application know which queue manager to connects to?
– Somnath Musib
Nov 20 at 6:30
It connects to the queue manager that is listening on the ip and port provided.
– JoshMc
Nov 20 at 7:05
Possible duplicate of Connecting IBM MQ queue using F5 virtual ip and C++
– JoshMc
Nov 20 at 17:12
Also take a look at these two "How to create a qmgr alias" and "JMSWMQ2020: Failed to connect to queue manager"
– JoshMc
Nov 20 at 17:13