You can install this on a number of platforms. Install MQExplorer both on the server Linux for example and a client windows machine Your desktop for example. Most day you will have a JR already installed. However you will not be able to connect to the remote queue manager until you open up the security for remote administration. We cover this as part of topics on Security in my WMQ 7.
Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Can't install Websphere mq client error Ask Question. Asked 6 years, 5 months ago. Active 4 years ago. Viewed 3k times. I run it as administrator, and am a member of the local administrators group.
Edit2: It seems that the error is coming because of our directory structure: Error Improve this question. Switha Switha 21 1 1 silver badge 4 4 bronze badges.
Do you have the full contents of the Client installer unpacked, in the same structure as in the zip? I'd check the license directory in particular. Add a comment. Active Oldest Votes. According to the good folks at MSIGEEK, the following are some common causes for that error: Short file name creation is disabled on the target machine.
An Install Script custom action is prototyped incorrectly. A file is locked and cannot be overwritten. The Microsoft Windows Installer Service is not installed correctly. The Windows Temp folders are full. Listing the product prerequisites Action start iwiListProductPrereqs. MSI c 5C []: Invoking remote custom action. Return value 3. Improve this answer. Rob T. Rob There was only one prerequisite bundled with the package - axis, and that is to be installed afterwards into the installation directory.
The next screen indicates the type of logging that the queue manager will perform, and the maximum number of log files that can be produced. The following step enables the WebSphere MQ applications that are running on your machine to communicate with other machines.
This is the default port number for WebSphere MQ. Check with your system administrator to verify that this is the correct port to use. Click Finish to create your queue manager. It might take a minute to create and start the queue manager. Create one or more local queues for exchanging messages on your queue manager.
These are the queues that SAS applications will use to exchange messages with other applications. Right-click Queues , then select New Local Queue from the popup menu. In the Queue Name field, enter the name of the local queue that you want to create. This queue name is specified in any application programs that use WebSphere MQ. On this screen, you might want to change the Default Persistence value from Not Persistent to Persistent.
This enables messages to remain in the queue even if the queue manager is shut down. Click the various tabs to see the types of values that can be defined. If you will be using high-volume messaging applications like scoring, you might want to change another default value. Click the Extended tab and increase the Maximum Queue Depth to , or more. This value represents the maximum number of messages that a queue can hold.
You can also change the properties after the queue has been defined. Click OK to create the queue. Repeat the process for any additional local queues that you want to create. You should also create the dead letter queue that was defined when you created the queue manager.
It is also a local queue. You will need to create the default transmission queue if you will be exchanging messages with queues on other queue managers.
0コメント